'Re: [esb-java-dev] Using one Synapse installation'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: esb-java-dev
Subject: Re: [esb-java-dev] Using one Synapse installation
From: "Asankha C. Perera" <asankha () wso2 ! com>
Date: 2008-07-27 18:41:55
Message-ID: 488CBEA3.8050709 () wso2 ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Hi Eric

The main reason for the WSO2 ESB distribution to be an exploded WAR is 
because for a standalone deployment, we start up an embedded Tomcat 
server, and for a deployment on any other JEE server, we simply deploy 
the "same" distribution. This allows us to ensure to a great extent that 
the WAR deployment will work on other JEE servers, since we infact do 
the same for the standalone version by deploying to the embedded Tomcat. 
This is the reason for the tomcat/conf and this has no direct 
configuration on the ESB rules.
> I started reviewing the code and found several places which would cause
> problems. Right now what I described would not work at all.....
> ...........
> Maybe a few others as well...
>
> Sources which would need to be changed in Synapse-land:
>
> I could not identify a single place. The code looks quite flexible,
> using either the system properties instead of init parameters or loading
> everything from the classpath.
>
> Having a system property like "ESB_CONFIG_DIR" for most cases it would
> be sufficient to define only this and saving the need to define
> server.xml, synapse.xml, and axis2.xml. If those are specified, the
> defaults could be overridden.
>
> What do you think?
>   
We are generally going to drop use of system properties as much as 
possible in future, but may keep core properties for backwards 
compatibility. This is because System properties generally creates 
issues at deployment time..

However, I am fully open to evaluating suggestions for improvement, and 
if we could capture a proposal as an enhancement request on our JIRA, we 
will certainly look at the posibilities

asankha

-- 
Asankha C. Perera

WSO2 - http://wso2.org
http://esbmagic.blogspot.com

[Attachment #5 (text/html)]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Eric 
 
The main reason for the WSO2 ESB distribution to be an exploded WAR is
because for a standalone deployment, we start up an embedded Tomcat
server, and for a deployment on any other JEE server, we simply deploy
the "same" distribution. This allows us to ensure to a great extent
that the WAR deployment will work on other JEE servers, since we infact
do the same for the standalone version by deploying to the embedded
Tomcat. This is the reason for the tomcat/conf and this has no direct
configuration on the ESB rules. 
<blockquote
 cite="mid:A9856B86EDA25144A734574D0338C13501098B95@berwnexmb01.jcorp.ad.jamba.net"
 type="cite">
 <pre wrap="">I started reviewing the code and found several places which would cause
problems. Right now what I described would not work at all.....
...........
Maybe a few others as well...

Sources which would need to be changed in Synapse-land:

I could not identify a single place. The code looks quite flexible,
using either the system properties instead of init parameters or loading
everything from the classpath.

Having a system property like "ESB_CONFIG_DIR" for most cases it would
be sufficient to define only this and saving the need to define
server.xml, synapse.xml, and axis2.xml. If those are specified, the
defaults could be overridden.

What do you think?
 </pre>
</blockquote>
We are generally going to drop use of system properties as much as
possible in future, but may keep core properties for backwards
compatibility. This is because System properties generally creates
issues at deployment time.. 
 
However, I am fully open to evaluating suggestions for improvement, and
if we could capture a proposal as an enhancement request on our JIRA,
we will certainly look at the posibilities 
 
asankha 
 
<div class="moz-signature">-- 
<title></title>
Asankha C. Perera 
 
WSO2 - <a href="http://wso2.org">http://wso2.org</a> 
<a href="http://esbmagic.blogspot.com">http://esbmagic.blogspot.com</a> 
 
</div>
</body>
</html>

_______________________________________________
Esb-java-dev mailing list
Esb-java-dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev

[prev in list] [next in list] [prev in thread] [next in thread] 