You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Henrik Plate <he...@yahoo.co.uk> on 2007/11/05 15:27:41 UTC
Re: Multiple responses
Hi Ruwan,
Thank you ... you'll receive my comments soon (as soon as I figured out how
to use the Synapse build with WSO2 ESB which I used so far).
Kind regards,
Henrik
--
View this message in context: http://www.nabble.com/Multiple-responses-tf4651525.html#a13587790
Sent from the Synapse - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Multiple responses
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi Henrik
I'm afraid I have to ask you to move this question to the WSO2 ESB
dev/user list :-)
asankha
Henrik Plate wrote:
> Hi Ruwan,
>
> I used the nightly build you suggested on Nov, 6th. However, I have the same
> problem when using ESB 1.5 (see DEBUG messages appended at the bottom).
>
> Perhaps the whole problem is related to the exception(s) I get when
> launching ".\wso2-esb.bat":
>
> [main] ERROR SchemaUpdate could not get database metadata
> java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041,
> SQLERRMC: Failed to create database '../../../../database/WSO2ESB_DATABASE',
> see the next exception for details.::SQLSTATE: XBM0JD
> irectory
> C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
> already exists.
> at
> org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
> Source)
> at
> org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at java.sql.DriverManager.getConnection(DriverManager.java:582)
> at java.sql.DriverManager.getConnection(DriverManager.java:154)
> at
> org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110)
> at
> org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:27)
> at
> org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:127)
>
> and
>
> [main] ERROR SchemaUpdate could not complete schema update
> java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041,
> SQLERRMC: Failed to create database '../../../../database/WSO2ESB_DATABASE',
> see the next exception for details.::SQLSTATE: XBM0JD
> irectory
> C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
> already exists.
> at
> org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
> Source)
> at
> org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
>
> When I click on a folder in the integrated registry, I get:
>
> [http-9443-Processor2] ERROR JDBCExceptionReporter DERBY SQL error:
> SQLCODE: -1, SQLSTATE: XJ041, SQLERRMC: Failed to create database
> '../../../..
> /database/WSO2ESB_DATABASE', see the next exception for
> details.::SQLSTATE: XBM0JDirectory
> C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
> a
> lready exists.
> [http-9443-Processor2] ERROR RPCMessageReceiver Exception occurred while
> trying to invoke service method getRegistryEntry
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
>
> Kind regards,
> Henrik
> ________________________________
>
> Log messages when calling the clone mediator:
>
> [HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Proxy Service
> MFProxy received a new message from : 127.0.0.1
> [HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Message To:
> /soap/MFProxy
> [HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver SOAPAction:
> http://www.example.org/TestReqRes/NewOperation
> [HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver WSA-Action:
> http://www.example.org/TestReqRes/NewOperation
> [HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Setting the
> fault-sequence to : org.apache.synapse.mediators.base.SequenceMediat
> [HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Using sequence
> named : MFSeq for incoming message mediation
> [HttpServerWorker-1] DEBUG SequenceMediator Start : Sequence <MFSeq>
> [HttpServerWorker-1] DEBUG SequenceMediator Sequence <SequenceMediator>
> :: mediate()
> [HttpServerWorker-1] DEBUG CloneMediator Start : Clone mediator
> [HttpServerWorker-1] DEBUG Axis2SynapseEnvironment Creating Message
> Context
> [HttpServerWorker-1] INFO ESBRegistry ==> Repository fetch of resource
> with key : MOD1
> [HttpServerWorker-1] DEBUG CloneMediator End : Clone mediator
> [HttpServerWorker-1] DEBUG SequenceMediator End : Sequence <MFSeq>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Multiple responses
Posted by Henrik Plate <he...@yahoo.co.uk>.
Hi Ruwan,
I used the nightly build you suggested on Nov, 6th. However, I have the same
problem when using ESB 1.5 (see DEBUG messages appended at the bottom).
Perhaps the whole problem is related to the exception(s) I get when
launching ".\wso2-esb.bat":
[main] ERROR SchemaUpdate could not get database metadata
java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041,
SQLERRMC: Failed to create database '../../../../database/WSO2ESB_DATABASE',
see the next exception for details.::SQLSTATE: XBM0JD
irectory
C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
already exists.
at
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
Source)
at
org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:154)
at
org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110)
at
org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:27)
at
org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:127)
and
[main] ERROR SchemaUpdate could not complete schema update
java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041,
SQLERRMC: Failed to create database '../../../../database/WSO2ESB_DATABASE',
see the next exception for details.::SQLSTATE: XBM0JD
irectory
C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
already exists.
at
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
Source)
at
org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
When I click on a folder in the integrated registry, I get:
[http-9443-Processor2] ERROR JDBCExceptionReporter DERBY SQL error:
SQLCODE: -1, SQLSTATE: XJ041, SQLERRMC: Failed to create database
'../../../..
/database/WSO2ESB_DATABASE', see the next exception for
details.::SQLSTATE: XBM0JDirectory
C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
a
lready exists.
[http-9443-Processor2] ERROR RPCMessageReceiver Exception occurred while
trying to invoke service method getRegistryEntry
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Kind regards,
Henrik
________________________________
Log messages when calling the clone mediator:
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Proxy Service
MFProxy received a new message from : 127.0.0.1
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Message To:
/soap/MFProxy
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver SOAPAction:
http://www.example.org/TestReqRes/NewOperation
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver WSA-Action:
http://www.example.org/TestReqRes/NewOperation
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Setting the
fault-sequence to : org.apache.synapse.mediators.base.SequenceMediat
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Using sequence
named : MFSeq for incoming message mediation
[HttpServerWorker-1] DEBUG SequenceMediator Start : Sequence <MFSeq>
[HttpServerWorker-1] DEBUG SequenceMediator Sequence <SequenceMediator>
:: mediate()
[HttpServerWorker-1] DEBUG CloneMediator Start : Clone mediator
[HttpServerWorker-1] DEBUG Axis2SynapseEnvironment Creating Message
Context
[HttpServerWorker-1] INFO ESBRegistry ==> Repository fetch of resource
with key : MOD1
[HttpServerWorker-1] DEBUG CloneMediator End : Clone mediator
[HttpServerWorker-1] DEBUG SequenceMediator End : Sequence <MFSeq>
--
View this message in context: http://www.nabble.com/Multiple-responses-tf4651525.html#a13726102
Sent from the Synapse - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Multiple responses
Posted by Henrik Plate <he...@yahoo.co.uk>.
Hi Ruwan,
I used the nightly build you suggested on Nov, 6th. However, I have the same
problem when using ESB 1.5 (see DEBUG messages appended at the bottom).
Perhaps the whole problem is related to the exception(s) I get when
launching ".\wso2-esb.bat":
[main] ERROR SchemaUpdate could not get database metadata
java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041,
SQLERRMC: Failed to create database '../../../../database/WSO2ESB_DATABASE',
see the next exception for details.::SQLSTATE: XBM0JD
irectory
C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
already exists.
at
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
Source)
at
org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:154)
at
org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110)
at
org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:27)
at
org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:127)
and
[main] ERROR SchemaUpdate could not complete schema update
java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041,
SQLERRMC: Failed to create database '../../../../database/WSO2ESB_DATABASE',
see the next exception for details.::SQLSTATE: XBM0JD
irectory
C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
already exists.
at
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
Source)
at
org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
When I click on a folder in the integrated registry, I get:
[http-9443-Processor2] ERROR JDBCExceptionReporter DERBY SQL error:
SQLCODE: -1, SQLSTATE: XJ041, SQLERRMC: Failed to create database
'../../../..
/database/WSO2ESB_DATABASE', see the next exception for
details.::SQLSTATE: XBM0JDirectory
C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
a
lready exists.
[http-9443-Processor2] ERROR RPCMessageReceiver Exception occurred while
trying to invoke service method getRegistryEntry
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Kind regards,
Henrik
________________________________
Log messages when calling the clone mediator:
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Proxy Service
MFProxy received a new message from : 127.0.0.1
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Message To:
/soap/MFProxy
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver SOAPAction:
http://www.example.org/TestReqRes/NewOperation
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver WSA-Action:
http://www.example.org/TestReqRes/NewOperation
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Setting the
fault-sequence to : org.apache.synapse.mediators.base.SequenceMediat
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Using sequence
named : MFSeq for incoming message mediation
[HttpServerWorker-1] DEBUG SequenceMediator Start : Sequence <MFSeq>
[HttpServerWorker-1] DEBUG SequenceMediator Sequence <SequenceMediator>
:: mediate()
[HttpServerWorker-1] DEBUG CloneMediator Start : Clone mediator
[HttpServerWorker-1] DEBUG Axis2SynapseEnvironment Creating Message
Context
[HttpServerWorker-1] INFO ESBRegistry ==> Repository fetch of resource
with key : MOD1
[HttpServerWorker-1] DEBUG CloneMediator End : Clone mediator
[HttpServerWorker-1] DEBUG SequenceMediator End : Sequence <MFSeq>
--
View this message in context: http://www.nabble.com/Multiple-responses-tf4651525.html#a13726102
Sent from the Synapse - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Multiple responses
Posted by Henrik Plate <he...@yahoo.co.uk>.
Hi Ruwan,
I used the nightly build you suggested on Nov, 6th. However, I have the same
problem when using ESB 1.5 (see DEBUG messages appended at the bottom).
Perhaps the whole problem is related to the exception(s) I get when
launching ".\wso2-esb.bat":
[main] ERROR SchemaUpdate could not get database metadata
java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041,
SQLERRMC: Failed to create database '../../../../database/WSO2ESB_DATABASE',
see the next exception for details.::SQLSTATE: XBM0JD
irectory
C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
already exists.
at
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
Source)
at
org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:154)
at
org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110)
at
org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:27)
at
org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:127)
and
[main] ERROR SchemaUpdate could not complete schema update
java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041,
SQLERRMC: Failed to create database '../../../../database/WSO2ESB_DATABASE',
see the next exception for details.::SQLSTATE: XBM0JD
irectory
C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
already exists.
at
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
Source)
at
org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
When I click on a folder in the integrated registry, I get:
[http-9443-Processor2] ERROR JDBCExceptionReporter DERBY SQL error:
SQLCODE: -1, SQLSTATE: XJ041, SQLERRMC: Failed to create database
'../../../..
/database/WSO2ESB_DATABASE', see the next exception for
details.::SQLSTATE: XBM0JDirectory
C:\Programs\WSO2ES~1.5\bin\..\webapp\WEB-INF\classes\conf\C:\Programs\wso2esb-1.5\database\WSO2ESB_DATABASE
a
lready exists.
2007-11-13 14:39:48,501 [10.55.131.237-NCEN60128423A]
[http-9443-Processor2] ERROR RPCMessageReceiver Exception occurred while
trying to invoke service method getRegistryEntry
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Kind regards,
Henrik
________________________________
Log messages when calling the clone mediator:
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Proxy Service
MFProxy received a new message from : 127.0.0.1
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Message To:
/soap/MFProxy
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver SOAPAction:
http://www.example.org/TestReqRes/NewOperation
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver WSA-Action:
http://www.example.org/TestReqRes/NewOperation
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Setting the
fault-sequence to : org.apache.synapse.mediators.base.SequenceMediat
[HttpServerWorker-1] DEBUG ProxyServiceMessageReceiver Using sequence
named : MFSeq for incoming message mediation
[HttpServerWorker-1] DEBUG SequenceMediator Start : Sequence <MFSeq>
[HttpServerWorker-1] DEBUG SequenceMediator Sequence <SequenceMediator>
:: mediate()
[HttpServerWorker-1] DEBUG CloneMediator Start : Clone mediator
[HttpServerWorker-1] DEBUG Axis2SynapseEnvironment Creating Message
Context
[HttpServerWorker-1] INFO ESBRegistry ==> Repository fetch of resource
with key : MOD1
[HttpServerWorker-1] DEBUG CloneMediator End : Clone mediator
[HttpServerWorker-1] DEBUG SequenceMediator End : Sequence <MFSeq>
--
View this message in context: http://www.nabble.com/Multiple-responses-tf4651525.html#a13726102
Sent from the Synapse - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Multiple responses
Posted by Ruwan Linton <ru...@gmail.com>.
Henrik,
This is strange. It seems like the Clone mediator can not find the sequences
specified as MOD1 and MOD2. That is why you are getting "ESBRegistry ==>
Repository fetch of resource with key : MOD1". When I try this on the
1.5release it did print the drop mediator logs as well as MOD1 and
MOD2
sequence start and end logs (I am surprised to see your log, but can not
understand what is wrong).
What is the version that you are trying? Is that a nightly build? Can you
please try this on the Synapse-1.1 release [1] or ESB-1.5 release [2].
[1] - http://ws.apache.org/synapse/download/1.1/download.cgi
[2] - http://dist.wso2.org/products/esb/java/1.5/
Thanks,
Ruwan
On Nov 13, 2007 3:37 PM, Henrik Plate <he...@yahoo.co.uk> wrote:
>
> Hi Ruwan,
>
> I used the proposed config (after I deleted the <syn:registry> element
> which
> resulted in a "Cannot locate registry provider class" exception) with the
> following result:
>
> [HttpServerWorker-4] DEBUG ProxyServiceMessageReceiver Proxy Service
> MFProxy
> received a new message from : 127.0.0.1
> [HttpServerWorker-4] DEBUG ProxyServiceMessageReceiver Message To:
> /soap/MFProxy
> [HttpServerWorker-4] DEBUG ProxyServiceMessageReceiver SOAPAction:
> http://www.example.org/TestReqRes/NewOperation
> [HttpServerWorker-4]<http://www.example.org/TestReqRes/NewOperation%5BHttpServerWorker-4%5D>DEBUG ProxyServiceMessageReceiver WSA-Action:
> http://www.example.org/TestReqRes/NewOperation
> [HttpServerWorker-4]<http://www.example.org/TestReqRes/NewOperation%5BHttpServerWorker-4%5D>DEBUG ProxyServiceMessageReceiver Setting the
> fault-sequence to : org.apache.synapse.mediators.base.SequenceMedia
>
> [HttpServerWorker-4] DEBUG ProxyServiceMessageReceiver Using sequence
> named
> : MFSeq for incoming message mediation
> [HttpServerWorker-4] DEBUG SequenceMediator Start : Sequence <MFSeq>
> [HttpServerWorker-4] DEBUG SequenceMediator Sequence <SequenceMediator> ::
> mediate()
> [HttpServerWorker-4] DEBUG CloneMediator Start : Clone mediator
> [HttpServerWorker-4] DEBUG Axis2SynapseEnvironment Creating Message
> Context
> [HttpServerWorker-4] INFO ESBRegistry ==> Repository fetch of resource
> with
> key : MOD1
> [HttpServerWorker-4] DEBUG Axis2SynapseEnvironment Creating Message
> Context
> [HttpServerWorker-4] INFO ESBRegistry ==> Repository fetch of resource
> with
> key : MOD2
> [HttpServerWorker-4] DEBUG CloneMediator End : Clone mediator
> [HttpServerWorker-4] DEBUG SequenceMediator End : Sequence <MFSeq>
>
> As far as I understand, the sequence mediators MOD1 and MOD2 are simply
> not
> called (I do not see anything related to them, e.g. log messages from the
> drop mediators you've put to replace my send mediators).
>
> I made other changes to your test configuration: I declared an endpoint
> TestReqRes for one of my services and a proxy calling this endpoint. My
> client application can perfectly call this proxy and receives a result
> from
> the service.
>
> When I use the same endpoint as "Delivery Endpoint" in the clone mediator,
> I
> get an exception complaining about unexpected chars:
>
> org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxUnexpectedCharException:
> Unexpected character 'E' (code 69) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
> HTTPTransportUtils.java:283)
> at
> org.apache.synapse.transport.nhttp.ServerWorker.processPost(
> ServerWorker.java:218)
> at
> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:182)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.axiom.om.OMException:
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'E'
> (code
> 69) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java
> :239)
> at
> org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(
> OMDocumentImpl.java:130)
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(
> StAXOMBuilder.java:359)
>
> Please find the complete configuration below.
>
> Thanks and kind regards,
> Henrik
> ___________________________________
>
> <?xml version="1.0" encoding="UTF-8"?>
> <syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse">
> <syn:proxy name="MFProxy" startOnLoad="true">
> <syn:target inSequence="MFSeq" outSequence="main"
> faultSequence="fault"/>
> </syn:proxy>
> <syn:proxy name="TestReqRes" startOnLoad="true">
> <syn:target endpoint="TestReqRes" outSequence="main"
> faultSequence="fault"/>
> </syn:proxy>
> <syn:endpoint name="TestReqRes">
> <syn:wsdl service="TestReqRes" port="TestReqResSOAP"
> uri="http://localhost:9000/axis2/services/TestReqRes?wsdl"
> format="soap11"/>
> </syn:endpoint>
> <syn:sequence name="MFSeq">
> <syn:clone>
> <syn:target sequence="MOD1"/>
> <syn:target sequence="" endpoint="TestReqRes"/>
> </syn:clone>
> </syn:sequence>
> <syn:sequence name="MOD1">
> <syn:log level="full"/>
> <syn:drop/>
> </syn:sequence>
> <syn:sequence name="MOD2">
> <syn:log level="full"/>
> <syn:drop/>
> </syn:sequence>
> <syn:sequence name="fault">
> <syn:log/>
> </syn:sequence>
> <syn:sequence name="main">
> <syn:in>
> <syn:log level="full"/>
> <syn:filter source="get-property('To')" regex="
> http://localhost:9000.*">
> <syn:send/>
> </syn:filter>
> </syn:in>
> <syn:out>
> <syn:send/>
> </syn:out>
> </syn:sequence>
> </syn:definitions>
>
> --
> View this message in context:
> http://www.nabble.com/Multiple-responses-tf4651525.html#a13722947
> Sent from the Synapse - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Multiple responses
Posted by Henrik Plate <he...@yahoo.co.uk>.
Hi Ruwan,
I used the proposed config (after I deleted the <syn:registry> element which
resulted in a "Cannot locate registry provider class" exception) with the
following result:
[HttpServerWorker-4] DEBUG ProxyServiceMessageReceiver Proxy Service MFProxy
received a new message from : 127.0.0.1
[HttpServerWorker-4] DEBUG ProxyServiceMessageReceiver Message To:
/soap/MFProxy
[HttpServerWorker-4] DEBUG ProxyServiceMessageReceiver SOAPAction:
http://www.example.org/TestReqRes/NewOperation
[HttpServerWorker-4] DEBUG ProxyServiceMessageReceiver WSA-Action:
http://www.example.org/TestReqRes/NewOperation
[HttpServerWorker-4] DEBUG ProxyServiceMessageReceiver Setting the
fault-sequence to : org.apache.synapse.mediators.base.SequenceMedia
[HttpServerWorker-4] DEBUG ProxyServiceMessageReceiver Using sequence named
: MFSeq for incoming message mediation
[HttpServerWorker-4] DEBUG SequenceMediator Start : Sequence <MFSeq>
[HttpServerWorker-4] DEBUG SequenceMediator Sequence <SequenceMediator> ::
mediate()
[HttpServerWorker-4] DEBUG CloneMediator Start : Clone mediator
[HttpServerWorker-4] DEBUG Axis2SynapseEnvironment Creating Message Context
[HttpServerWorker-4] INFO ESBRegistry ==> Repository fetch of resource with
key : MOD1
[HttpServerWorker-4] DEBUG Axis2SynapseEnvironment Creating Message Context
[HttpServerWorker-4] INFO ESBRegistry ==> Repository fetch of resource with
key : MOD2
[HttpServerWorker-4] DEBUG CloneMediator End : Clone mediator
[HttpServerWorker-4] DEBUG SequenceMediator End : Sequence <MFSeq>
As far as I understand, the sequence mediators MOD1 and MOD2 are simply not
called (I do not see anything related to them, e.g. log messages from the
drop mediators you've put to replace my send mediators).
I made other changes to your test configuration: I declared an endpoint
TestReqRes for one of my services and a proxy calling this endpoint. My
client application can perfectly call this proxy and receives a result from
the service.
When I use the same endpoint as "Delivery Endpoint" in the clone mediator, I
get an exception complaining about unexpected chars:
org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxUnexpectedCharException:
Unexpected character 'E' (code 69) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:283)
at
org.apache.synapse.transport.nhttp.ServerWorker.processPost(ServerWorker.java:218)
at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:182)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.axiom.om.OMException:
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'E' (code
69) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239)
at
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:130)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:359)
Please find the complete configuration below.
Thanks and kind regards,
Henrik
___________________________________
<?xml version="1.0" encoding="UTF-8"?>
<syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse">
<syn:proxy name="MFProxy" startOnLoad="true">
<syn:target inSequence="MFSeq" outSequence="main"
faultSequence="fault"/>
</syn:proxy>
<syn:proxy name="TestReqRes" startOnLoad="true">
<syn:target endpoint="TestReqRes" outSequence="main"
faultSequence="fault"/>
</syn:proxy>
<syn:endpoint name="TestReqRes">
<syn:wsdl service="TestReqRes" port="TestReqResSOAP"
uri="http://localhost:9000/axis2/services/TestReqRes?wsdl" format="soap11"/>
</syn:endpoint>
<syn:sequence name="MFSeq">
<syn:clone>
<syn:target sequence="MOD1"/>
<syn:target sequence="" endpoint="TestReqRes"/>
</syn:clone>
</syn:sequence>
<syn:sequence name="MOD1">
<syn:log level="full"/>
<syn:drop/>
</syn:sequence>
<syn:sequence name="MOD2">
<syn:log level="full"/>
<syn:drop/>
</syn:sequence>
<syn:sequence name="fault">
<syn:log/>
</syn:sequence>
<syn:sequence name="main">
<syn:in>
<syn:log level="full"/>
<syn:filter source="get-property('To')" regex="
http://localhost:9000.*">
<syn:send/>
</syn:filter>
</syn:in>
<syn:out>
<syn:send/>
</syn:out>
</syn:sequence>
</syn:definitions>
--
View this message in context: http://www.nabble.com/Multiple-responses-tf4651525.html#a13722947
Sent from the Synapse - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Multiple responses
Posted by Ruwan Linton <ru...@gmail.com>.
Henrik,
I was unable to reproduce this. I have changed the config a little bit
because those services are not with me and I don't think that will affect
the problem.
Here is the modified configuration that I have tried.
<?xml version="1.0" encoding="UTF-8"?>
<syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse">
<syn:registry provider="org.wso2.esb.registry.ESBRegistry">
<syn:parameter name="cachableDuration">60000</syn:parameter>
<syn:parameter name="root">file:registry/</syn:parameter>
</syn:registry>
<syn:proxy name="MFProxy" startOnLoad="true">
<syn:target inSequence="MFSeq" outSequence="main"
faultSequence="fault"/>
</syn:proxy>
<syn:sequence name="MFSeq">
<syn:clone>
<syn:target sequence="MOD1"/>
<syn:target sequence="MOD2"/>
</syn:clone>
</syn:sequence>
<syn:sequence name="MOD1">
<!--<syn:send>
<syn:endpoint>
<syn:wsdl service="TestReqRes" port="TestReqResSOAP"
uri="http://localhost:9000/axis2/services/TestReqRes?wsdl" format="soap11">
<syn:enableAddressing/>
</syn:wsdl>
</syn:endpoint>
</syn:send>-->
<syn:log level="full"/>
<syn:drop/>
</syn:sequence>
<syn:sequence name="MOD2">
<!--<syn:send>
<syn:endpoint>
<syn:wsdl service="TestReqRes2" port="TestReqResSOAP"
uri="http://localhost:9000/axis2/services/TestReqRes2?wsdl" format="soap11">
<syn:enableAddressing/>
</syn:wsdl>
</syn:endpoint>
</syn:send>-->
<syn:log level="full"/>
<syn:drop/>
</syn:sequence>
<syn:sequence name="fault">
<syn:log/>
</syn:sequence>
<syn:sequence name="main">
<syn:in>
<syn:log level="full"/>
<syn:filter source="get-property('To')"
regex="http://localhost:9000.*">
<syn:send/>
</syn:filter>
</syn:in>
<syn:out>
<syn:send/>
</syn:out>
</syn:sequence>
</syn:definitions>
But I am not getting the error that you pointed. Can you try this config and
let me know your results. Can you change the log level of
org.apache.synapseto DEBUG in the
log4j.properties found at webapp/WEB-INF/classes/conf folder and send me the
full debug log.
Thanks,
Ruwan
On Nov 12, 2007 6:09 PM, Henrik Plate <he...@yahoo.co.uk> wrote:
>
> Hi Ruwan,
>
> I don't think it's related to the proxy not finding sth.
>
> If I replace the clone mediator by two sequence mediators sequentially
> calling MOD1 and MOD2, it works (even though I have the initial problems
> related to the closed HTTP connection when each service sends a response
> message). Please find the complete config below.
>
> Kind regards,
> Henrik
> ______________________________________
>
> <?xml version="1.0" encoding="UTF-8"?>
> <syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse">
> <syn:registry provider="org.wso2.esb.registry.ESBRegistry">
> <syn:parameter name="cachableDuration">60000</syn:parameter>
> <syn:parameter name="root">file:registry/</syn:parameter>
> </syn:registry>
> <syn:proxy name="MFProxy" startOnLoad="true">
> <syn:target inSequence="MFSeq" outSequence="main"
> faultSequence="fault"/>
> </syn:proxy>
> <syn:sequence name="MFSeq">
> <syn:clone>
> <syn:target sequence="MOD1"/>
> <syn:target sequence="MOD2"/>
> </syn:clone>
> </syn:sequence>
> <syn:sequence name="MOD1">
> <syn:send>
> <syn:endpoint>
> <syn:wsdl service="TestReqRes" port="TestReqResSOAP"
> uri="http://localhost:9000/axis2/services/TestReqRes?wsdl"
> format="soap11">
> <syn:enableAddressing/>
> </syn:wsdl>
> </syn:endpoint>
> </syn:send>
> </syn:sequence>
> <syn:sequence name="MOD2">
> <syn:send>
> <syn:endpoint>
> <syn:wsdl service="TestReqRes2" port="TestReqResSOAP"
> uri="http://localhost:9000/axis2/services/TestReqRes2?wsdl"
> format="soap11">
> <syn:enableAddressing/>
> </syn:wsdl>
> </syn:endpoint>
> </syn:send>
> </syn:sequence>
> <syn:sequence name="fault">
> <syn:log/>
> </syn:sequence>
> <syn:sequence name="main">
> <syn:in>
> <syn:log level="full"/>
> <syn:filter source="get-property('To')"
> regex="http://localhost:9000.*">
> <syn:send/>
> </syn:filter>
> </syn:in>
> <syn:out>
> <syn:send/>
> </syn:out>
> </syn:sequence>
> </syn:definitions>
>
>
> --
> View this message in context:
> http://www.nabble.com/Multiple-responses-tf4651525.html#a13704899
> Sent from the Synapse - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Multiple responses
Posted by Henrik Plate <he...@yahoo.co.uk>.
Hi Ruwan,
I don't think it's related to the proxy not finding sth.
If I replace the clone mediator by two sequence mediators sequentially
calling MOD1 and MOD2, it works (even though I have the initial problems
related to the closed HTTP connection when each service sends a response
message). Please find the complete config below.
Kind regards,
Henrik
______________________________________
<?xml version="1.0" encoding="UTF-8"?>
<syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse">
<syn:registry provider="org.wso2.esb.registry.ESBRegistry">
<syn:parameter name="cachableDuration">60000</syn:parameter>
<syn:parameter name="root">file:registry/</syn:parameter>
</syn:registry>
<syn:proxy name="MFProxy" startOnLoad="true">
<syn:target inSequence="MFSeq" outSequence="main"
faultSequence="fault"/>
</syn:proxy>
<syn:sequence name="MFSeq">
<syn:clone>
<syn:target sequence="MOD1"/>
<syn:target sequence="MOD2"/>
</syn:clone>
</syn:sequence>
<syn:sequence name="MOD1">
<syn:send>
<syn:endpoint>
<syn:wsdl service="TestReqRes" port="TestReqResSOAP"
uri="http://localhost:9000/axis2/services/TestReqRes?wsdl" format="soap11">
<syn:enableAddressing/>
</syn:wsdl>
</syn:endpoint>
</syn:send>
</syn:sequence>
<syn:sequence name="MOD2">
<syn:send>
<syn:endpoint>
<syn:wsdl service="TestReqRes2" port="TestReqResSOAP"
uri="http://localhost:9000/axis2/services/TestReqRes2?wsdl" format="soap11">
<syn:enableAddressing/>
</syn:wsdl>
</syn:endpoint>
</syn:send>
</syn:sequence>
<syn:sequence name="fault">
<syn:log/>
</syn:sequence>
<syn:sequence name="main">
<syn:in>
<syn:log level="full"/>
<syn:filter source="get-property('To')"
regex="http://localhost:9000.*">
<syn:send/>
</syn:filter>
</syn:in>
<syn:out>
<syn:send/>
</syn:out>
</syn:sequence>
</syn:definitions>
--
View this message in context: http://www.nabble.com/Multiple-responses-tf4651525.html#a13704899
Sent from the Synapse - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Multiple responses
Posted by Ruwan Linton <ru...@gmail.com>.
Henrik,
This is not any thing related to Clone. Seems like the proxy can not find
the sequence reference.
Can you send me the full synapse.xml file, so that I can try that. (This
should not be a big issue)
Thanks,
Ruwan
On Nov 12, 2007 1:32 PM, Henrik Plate <he...@yahoo.co.uk> wrote:
>
> Hi Ruwan,
>
> I had a look at the ESB nightly build but failed to get the clone mediator
> running.
>
> My configuration is as follows:
>
> I have two sequences MOD1 and MOD2, each containing a send mediator to a
> WSDL endpoint.
>
> <syn:sequence name="MOD1">
> <syn:send>
> <syn:endpoint>
> <syn:wsdl service="TestReqRes" port="TestReqResSOAP"
> uri="http://localhost:9000/axis2/services/TestReqRes?wsdl"
> format="soap11">
> <syn:enableAddressing/>
> </syn:wsdl>
> </syn:endpoint>
> </syn:send>
> </syn:sequence>
>
> <syn:sequence name="MOD2">
> <syn:send>
> <syn:endpoint>
> <syn:wsdl service="TestReqRes2" port="TestReqResSOAP"
> uri="http://localhost:9000/axis2/services/TestReqRes2?wsdl"
> format="soap11">
> <syn:enableAddressing/>
> </syn:wsdl>
> </syn:endpoint>
> </syn:send>
> </syn:sequence>
>
> I defined a third sequence SEQ1 containing a clone mediator which uses
> MOD1
> and MOD2 as target mediation sequences (taken from the local registry).
> SEQ1
> is called by a proxy service for incoming messages.
>
> <syn:proxy name="MFProxy" startOnLoad="true">
> <syn:target inSequence="MFSeq" outSequence="main"
> faultSequence="fault"/>
> </syn:proxy>
>
> <syn:sequence name="MFSeq">
> <syn:clone>
> <syn:target sequence="MOD1"/>
> <syn:target sequence="MOD2"/>
> </syn:clone>
> </syn:sequence>
>
> When calling the proxy service, the console prints the following log
> messages, telling me that the sequences MOD1 and MOD2 have been fetched:
>
> [HttpServerWorker-1] INFO ESBRegistry ==> Repository fetch of resource
> with key : MOD1
> [HttpServerWorker-1] INFO ESBRegistry ==> Repository fetch of resource
> with key : MOD2
>
> However, nothing more seems to happen: A separate Axis2 server does not
> receive the cloned messages and the Axis2 client that called the proxy
> service gets a timeout.
>
> Then I defined the clone mediator target information inline, hereby again
> referring to MOD1:
>
> <syn:sequence name="MFSeq">
> <syn:clone>
> <syn:target>
> <syn:sequence>
> <syn:sequence key="MOD1"/>
> </syn:sequence>
> </syn:target>
> </syn:clone>
> </syn:sequence>
>
> Here, the following error occured:
>
> [SynapseWorker-4] INFO ESBRegistry ==> Repository fetch of resource with
> key : MOD1
> [SynapseWorker-4] ERROR SequenceMediator Sequence named MOD1 cannot be
> found
>
> I'll further try changing the configuration. However, I had the feeling
> this
> should already be it?
>
> Regards,
> Henrik
> --
> View this message in context:
> http://www.nabble.com/Multiple-responses-tf4651525.html#a13701423
> Sent from the Synapse - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Multiple responses
Posted by Henrik Plate <he...@yahoo.co.uk>.
Hi Ruwan,
I had a look at the ESB nightly build but failed to get the clone mediator
running.
My configuration is as follows:
I have two sequences MOD1 and MOD2, each containing a send mediator to a
WSDL endpoint.
<syn:sequence name="MOD1">
<syn:send>
<syn:endpoint>
<syn:wsdl service="TestReqRes" port="TestReqResSOAP"
uri="http://localhost:9000/axis2/services/TestReqRes?wsdl" format="soap11">
<syn:enableAddressing/>
</syn:wsdl>
</syn:endpoint>
</syn:send>
</syn:sequence>
<syn:sequence name="MOD2">
<syn:send>
<syn:endpoint>
<syn:wsdl service="TestReqRes2" port="TestReqResSOAP"
uri="http://localhost:9000/axis2/services/TestReqRes2?wsdl" format="soap11">
<syn:enableAddressing/>
</syn:wsdl>
</syn:endpoint>
</syn:send>
</syn:sequence>
I defined a third sequence SEQ1 containing a clone mediator which uses MOD1
and MOD2 as target mediation sequences (taken from the local registry). SEQ1
is called by a proxy service for incoming messages.
<syn:proxy name="MFProxy" startOnLoad="true">
<syn:target inSequence="MFSeq" outSequence="main"
faultSequence="fault"/>
</syn:proxy>
<syn:sequence name="MFSeq">
<syn:clone>
<syn:target sequence="MOD1"/>
<syn:target sequence="MOD2"/>
</syn:clone>
</syn:sequence>
When calling the proxy service, the console prints the following log
messages, telling me that the sequences MOD1 and MOD2 have been fetched:
[HttpServerWorker-1] INFO ESBRegistry ==> Repository fetch of resource
with key : MOD1
[HttpServerWorker-1] INFO ESBRegistry ==> Repository fetch of resource
with key : MOD2
However, nothing more seems to happen: A separate Axis2 server does not
receive the cloned messages and the Axis2 client that called the proxy
service gets a timeout.
Then I defined the clone mediator target information inline, hereby again
referring to MOD1:
<syn:sequence name="MFSeq">
<syn:clone>
<syn:target>
<syn:sequence>
<syn:sequence key="MOD1"/>
</syn:sequence>
</syn:target>
</syn:clone>
</syn:sequence>
Here, the following error occured:
[SynapseWorker-4] INFO ESBRegistry ==> Repository fetch of resource with
key : MOD1
[SynapseWorker-4] ERROR SequenceMediator Sequence named MOD1 cannot be
found
I'll further try changing the configuration. However, I had the feeling this
should already be it?
Regards,
Henrik
--
View this message in context: http://www.nabble.com/Multiple-responses-tf4651525.html#a13701423
Sent from the Synapse - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Multiple responses
Posted by Ruwan Linton <ru...@gmail.com>.
Henrik,
There will be a WSO2 ESB release coming soon after the Synapse-1.1 release
on 12th or you could get the ESB nightly build [1] to try this, which embeds
the latest synapse build.
[1] - http://dist.wso2.org/products/esb/java/nightly-build/
Thanks,
Ruwan
On Nov 5, 2007 7:57 PM, Henrik Plate <he...@yahoo.co.uk> wrote:
>
> Hi Ruwan,
>
> Thank you ... you'll receive my comments soon (as soon as I figured out
> how
> to use the Synapse build with WSO2 ESB which I used so far).
>
> Kind regards,
> Henrik
>
> --
> View this message in context:
> http://www.nabble.com/Multiple-responses-tf4651525.html#a13587790
> Sent from the Synapse - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"