Hi Claudi

As Paul stated, we wanted to move out of the application server context to be non-blocking. The current code base looks for the system property to pick the synapse.xml configuration, and thus you will need to either set it, or run Synapse standalone. If you are suggesting that we should continue to support the previous method of initialization, we could consider it for the next release through a JIRA.

asankha

cclaudi wrote:
Hello asankha. Thanks for the reply.
Until version 0.91 I used synapse.mar to embed synapse in a web application,
and deploy it in a Websphere Server.
How can I do the same now?


asankha wrote:
  
Hi Claudi

Synapse currently ships as a standalone server, thus you will not be 
able to deploy Synapse into an existing application server - unless you 
know exactly what you are doing. If you could specify your scenario in 
more detail, I may be able to help you with an alternative option.

asankha

cclaudi wrote:
    
Why do you have removed the "SynapseConfiguration" parameter in
axis2.xml?
Initialization based only on the system property "synapse.xml" is less
flexible then the previous option, because I'm not the administrator of
the
application server where I deploy the synapse application. The
administrator
allows me to change the configuration files, not the system properties!

Thanks for the response!
  
      
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



    

  
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to