from:"Ruwan Linton"

[
https://issues.apache.org/jira/browse/SYNAPSE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ruwan Linton updated SYNAPSE-514:
-

Affects Version/s: (was: 1.3)
1.2

The affected version has to be 1.2 because this is going to be fixed in the 1.3
once we commit in this patch

Enhance HessianMessageBuilder with fault detection
--

Attachments: HessianMessageBuilder.patch, restresources.zip

Currently there is no way to detect Hessian faults in the mediation. For most
other message formats this has already been implemented. Once a fault is
detected a property indicating the fault is stored inside the Axis message
context.
The attached patch add the same behavior for binary Hessian messages. It
extends the existing HessianMessageBuilder. Additionally the patch includes
unit tests to test the added functionality as well as the existing one. So
far there were no unit tests.
The unit test need some binary hessian messages as test resources. I included
them in the patch to ease the review but do think it might make more sense to
put them in the svn repo individually. So I'll attach those files separately
as well.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Commented: (SYNAPSE-514) Enhance HessianMessageBuilder with fault detection

[
https://issues.apache.org/jira/browse/SYNAPSE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680024#action_12680024
]

Ruwan Linton commented on SYNAPSE-514:
--

Eric, I think we need to improve the HessianMessageFormatter to serialize these
hessian faults into the wire, isn't it?

Thanks,
Ruwan

Enhance HessianMessageBuilder with fault detection
--

Attachments: HessianMessageBuilder.patch, restresources.zip

Currently there is no way to detect Hessian faults in the mediation. For most
other message formats this has already been implemented. Once a fault is
detected a property indicating the fault is stored inside the Axis message
context.
The attached patch add the same behavior for binary Hessian messages. It
extends the existing HessianMessageBuilder. Additionally the patch includes
unit tests to test the added functionality as well as the existing one. So
far there were no unit tests.
The unit test need some binary hessian messages as test resources. I included
them in the patch to ease the review but do think it might make more sense to
put them in the svn repo individually. So I'll attach those files separately
as well.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Commented: (SYNAPSE-514) Enhance HessianMessageBuilder with fault detection

[
https://issues.apache.org/jira/browse/SYNAPSE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680040#action_12680040
]

Ruwan Linton commented on SYNAPSE-514:
--

well, I think that is already handled because it is a hessian message itself
isn't it?

Enhance HessianMessageBuilder with fault detection
--

Attachments: HessianMessageBuilder.patch, restresources.zip

Currently there is no way to detect Hessian faults in the mediation. For most
other message formats this has already been implemented. Once a fault is
detected a property indicating the fault is stored inside the Axis message
context.
The attached patch add the same behavior for binary Hessian messages. It
extends the existing HessianMessageBuilder. Additionally the patch includes
unit tests to test the added functionality as well as the existing one. So
far there were no unit tests.
The unit test need some binary hessian messages as test resources. I included
them in the patch to ease the review but do think it might make more sense to
put them in the svn repo individually. So I'll attach those files separately
as well.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Resolved: (SYNAPSE-514) Enhance HessianMessageBuilder with fault detection

[
https://issues.apache.org/jira/browse/SYNAPSE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ruwan Linton resolved SYNAPSE-514.
--

Resolution: Fixed

Committed the patch and fixed on the trunk. Thanks Eric for the contribution

Enhance HessianMessageBuilder with fault detection
--

Attachments: HessianMessageBuilder.patch, restresources.zip

Currently there is no way to detect Hessian faults in the mediation. For most
other message formats this has already been implemented. Once a fault is
detected a property indicating the fault is stored inside the Axis message
context.
The attached patch add the same behavior for binary Hessian messages. It
extends the existing HessianMessageBuilder. Additionally the patch includes
unit tests to test the added functionality as well as the existing one. So
far there were no unit tests.
The unit test need some binary hessian messages as test resources. I included
them in the patch to ease the review but do think it might make more sense to
put them in the svn repo individually. So I'll attach those files separately
as well.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Assigned: (SYNAPSE-365) REST support not working in synapse 1.2


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton reassigned SYNAPSE-365:


Assignee: Ruwan Linton  (was: Asankha C. Perera)

 REST support not working in synapse 1.2
 ---

 Key: SYNAPSE-365
 URL: https://issues.apache.org/jira/browse/SYNAPSE-365
 Project: Synapse
  Issue Type: Bug
  Components: Endpoints, Proxy Services, Transports
Reporter: Jasper Spoel
Assignee: Ruwan Linton
 Fix For: 1.3


 When submitting a GET request to a synapse proxy service that points to a 
 REST webservice
 AND Content-Type is not text/xml or application/xml the error: Cannot create 
 DocumentElement without destination EPR comes out. (e.g try to approach the 
 service proxy with a webbrowers and it will do this)
 configuration is as follows:
 definitions xmlns=http://ws.apache.org/ns/synapse;
   proxy name=Forwarder
   target
   endpoint
   address uri=http://localhost:1/MyService/echo; 
 format=get/
   /endpoint
   outSequence
   send/
   /outSequence
   /target
   /proxy
 /definitions
 If the message is send with the 'correct' content-type like for example so: 
 curl -G -H Content-Type: text/xml http://localhost:8280/Forwarder/mediate
 Synapse gives me the following output:
 2008-06-18 15:10:59,714 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG ServerHandler HTTP connection [/0:0:0:0:0:0:0:1%0:56697]: Connected
 2008-06-18 15:10:59,732 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG ServerHandler HTTP connection [/0:0:0:0:0:0:0:1%0:56697]: GET 
 /soap/Forwarder/mediate HTTP/1.1
 2008-06-18 15:10:59,780 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG headers  GET /soap/Forwarder/mediate HTTP/1.1
 2008-06-18 15:10:59,780 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG headers  User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) 
 libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3
 2008-06-18 15:10:59,780 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG headers  Host: localhost:8280
 2008-06-18 15:10:59,780 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG headers  Accept: */*
 2008-06-18 15:10:59,780 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG headers  Content-Type:application/xml
 2008-06-18 15:10:59,797 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG TransportUtils createSOAPEnvelope using Builder (class 
 org.apache.axis2.builder.ApplicationXMLBuilder) selected from type 
 (application/xml)
 2008-06-18 15:10:59,841 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SynapseMessageReceiver Synapse received a new message for message 
 mediation...
 2008-06-18 15:10:59,841 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SynapseMessageReceiver Received To: null
 2008-06-18 15:10:59,841 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SynapseMessageReceiver SOAPAction: null
 2008-06-18 15:10:59,843 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SynapseMessageReceiver WSA-Action: null
 2008-06-18 15:10:59,845 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG Axis2SynapseEnvironment Injecting MessageContext
 2008-06-18 15:10:59,845 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG Axis2SynapseEnvironment Using Main Sequence for injected message
 2008-06-18 15:10:59,845 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SequenceMediator Start : Sequence main
 2008-06-18 15:10:59,845 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SequenceMediator Sequence SequenceMediator :: mediate()
 2008-06-18 15:10:59,846 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG LogMediator Start : Log mediator
 2008-06-18 15:10:59,846 [10.0.0.12-equilibrium.local] [HttpServerWorker-1]  
 INFO LogMediator To: , MessageID: urn:uuid:27AA6F4DF24676A7641213794659778, 
 Direction: request
 2008-06-18 15:10:59,846 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG LogMediator End : Log mediator
 2008-06-18 15:10:59,846 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG DropMediator Start : Drop mediator
 2008-06-18 15:10:59,852 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG DropMediator End : Drop mediator
 2008-06-18 15:10:59,852 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SequenceMediator End : Sequence main
 2008-06-18 15:10:59,853 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG ServerWorker Sending 202 Accepted response for MessageID : 
 urn:uuid:27AA6F4DF24676A7641213794659778 response written : null response 
 will follow : true acked : false forced ack : false
 2008-06-18 15:10:59,862 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG ServerHandler HTTP connection [localhost/0:0:0:0:0:0:0:1%0:56697]: 
 Output ready

[jira] Resolved: (SYNAPSE-365) REST support not working in synapse 1.2


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton resolved SYNAPSE-365.
--

   Resolution: Fixed
Fix Version/s: (was: NIGHTLY)
   1.3

This is fixed on the trunk and will be available for the 1.3 release..

 REST support not working in synapse 1.2
 ---

 Key: SYNAPSE-365
 URL: https://issues.apache.org/jira/browse/SYNAPSE-365
 Project: Synapse
  Issue Type: Bug
  Components: Endpoints, Proxy Services, Transports
Reporter: Jasper Spoel
Assignee: Ruwan Linton
 Fix For: 1.3


 When submitting a GET request to a synapse proxy service that points to a 
 REST webservice
 AND Content-Type is not text/xml or application/xml the error: Cannot create 
 DocumentElement without destination EPR comes out. (e.g try to approach the 
 service proxy with a webbrowers and it will do this)
 configuration is as follows:
 definitions xmlns=http://ws.apache.org/ns/synapse;
   proxy name=Forwarder
   target
   endpoint
   address uri=http://localhost:1/MyService/echo; 
 format=get/
   /endpoint
   outSequence
   send/
   /outSequence
   /target
   /proxy
 /definitions
 If the message is send with the 'correct' content-type like for example so: 
 curl -G -H Content-Type: text/xml http://localhost:8280/Forwarder/mediate
 Synapse gives me the following output:
 2008-06-18 15:10:59,714 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG ServerHandler HTTP connection [/0:0:0:0:0:0:0:1%0:56697]: Connected
 2008-06-18 15:10:59,732 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG ServerHandler HTTP connection [/0:0:0:0:0:0:0:1%0:56697]: GET 
 /soap/Forwarder/mediate HTTP/1.1
 2008-06-18 15:10:59,780 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG headers  GET /soap/Forwarder/mediate HTTP/1.1
 2008-06-18 15:10:59,780 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG headers  User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) 
 libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3
 2008-06-18 15:10:59,780 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG headers  Host: localhost:8280
 2008-06-18 15:10:59,780 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG headers  Accept: */*
 2008-06-18 15:10:59,780 [10.0.0.12-equilibrium.local] [I/O dispatcher 5] 
 DEBUG headers  Content-Type:application/xml
 2008-06-18 15:10:59,797 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG TransportUtils createSOAPEnvelope using Builder (class 
 org.apache.axis2.builder.ApplicationXMLBuilder) selected from type 
 (application/xml)
 2008-06-18 15:10:59,841 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SynapseMessageReceiver Synapse received a new message for message 
 mediation...
 2008-06-18 15:10:59,841 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SynapseMessageReceiver Received To: null
 2008-06-18 15:10:59,841 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SynapseMessageReceiver SOAPAction: null
 2008-06-18 15:10:59,843 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SynapseMessageReceiver WSA-Action: null
 2008-06-18 15:10:59,845 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG Axis2SynapseEnvironment Injecting MessageContext
 2008-06-18 15:10:59,845 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG Axis2SynapseEnvironment Using Main Sequence for injected message
 2008-06-18 15:10:59,845 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SequenceMediator Start : Sequence main
 2008-06-18 15:10:59,845 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SequenceMediator Sequence SequenceMediator :: mediate()
 2008-06-18 15:10:59,846 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG LogMediator Start : Log mediator
 2008-06-18 15:10:59,846 [10.0.0.12-equilibrium.local] [HttpServerWorker-1]  
 INFO LogMediator To: , MessageID: urn:uuid:27AA6F4DF24676A7641213794659778, 
 Direction: request
 2008-06-18 15:10:59,846 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG LogMediator End : Log mediator
 2008-06-18 15:10:59,846 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG DropMediator Start : Drop mediator
 2008-06-18 15:10:59,852 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG DropMediator End : Drop mediator
 2008-06-18 15:10:59,852 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG SequenceMediator End : Sequence main
 2008-06-18 15:10:59,853 [10.0.0.12-equilibrium.local] [HttpServerWorker-1] 
 DEBUG ServerWorker Sending 202 Accepted response for MessageID : 
 urn:uuid:27AA6F4DF24676A7641213794659778 response written : null response 
 will follow : true acked : false forced ack : false
 2008-06-18 15:10:59,862 [10.0.0.12-equilibrium.local] [I/O

Re: Could I use BSD licensed binary with in the synapse?

2009-03-06 Thread Ruwan Linton

May I ask you why you want to use this?

Thanks,
Ruwan

On Fri, Mar 6, 2009 at 9:15 AM, indika kumara indika.k...@gmail.com wrote:

 Hi All

 I want to use [1]. Could some please advice me on the $subject?

 Thanks
 Indika

 [1] http://jline.sourceforge.net/

 -
 To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
 For additional commands, e-mail: dev-h...@synapse.apache.org




-- 
Ruwan Linton
http://wso2.org - Oxygenating the Web Services Platform
http://ruwansblog.blogspot.com/

Re: Could I use BSD licensed binary with in the synapse?

2009-03-06 Thread Ruwan Linton

Indika,

So we will need to distribute this library if we uses this with synapse, in
which case I *think* we cannot use it in apache :(

Thanks,
Ruwan

On Fri, Mar 6, 2009 at 3:02 PM, indika kumara indika.k...@gmail.com wrote:

 With JDK 5, it is impossible (clear way) to reading passwords without
 echoing their text (With JDK 1.6, it can be). JLine provide this. I
 need to add an option for getting password for root level secret
 repository (SYNAPSE-376) based on JLine. Minimally, it (Jline binary)
 is needed in the compile time as this is a just one option.

 Thanks
 Indika

 On Fri, Mar 6, 2009 at 2:31 PM, Ruwan Linton ruwan.lin...@gmail.com
 wrote:
  May I ask you why you want to use this?
 
  Thanks,
  Ruwan
 
  On Fri, Mar 6, 2009 at 9:15 AM, indika kumara indika.k...@gmail.com
 wrote:
 
  Hi All
 
  I want to use [1]. Could some please advice me on the $subject?
 
  Thanks
  Indika
 
  [1] http://jline.sourceforge.net/
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
  For additional commands, e-mail: dev-h...@synapse.apache.org
 
 
 
 
  --
  Ruwan Linton
  http://wso2.org - Oxygenating the Web Services Platform
  http://ruwansblog.blogspot.com/
 

 -
 To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
 For additional commands, e-mail: dev-h...@synapse.apache.org




-- 
Ruwan Linton
http://wso2.org - Oxygenating the Web Services Platform
http://ruwansblog.blogspot.com/

Re: Could I use BSD licensed binary with in the synapse?

2009-03-06 Thread Ruwan Linton

Thanks Asankha and Paul for the correction :-)

Ruwan

On Fri, Mar 6, 2009 at 9:21 PM, Paul Fremantle pzf...@gmail.com wrote:

 Indika

 You can use this library - BSD is fine with Apache. However, I am
 still not convinced by the idea of requiring command-line input from
 the user at runtime. I can't imagine any production system that
 requires an admin to be there to type passwords in when the system is
 rebooted.

 Paul

 On Fri, Mar 6, 2009 at 10:48 AM, Asankha C. Perera asan...@apache.org
 wrote:
  Indika
 
  As I know BSD licenses are OK to be used with Apache projects,.. Paul,
  Sanjiva or Ant etc may know better.. I would like to keep the JDK 1.5
  support so I am ok to this if the license is compatible..
 
  ...
 
   Minimally, it (Jline binary)
  is needed in the compile time as this is a just one option.
 
  Do you mean to say that this library is only required at compile time? I
  haven't looked at it much yet, but then how does it work ?
 
  cheers
  asankha
 
  --
  Asankha C. Perera
  AdroitLogic, http://adroitlogic.org
 
  http://esbmagic.blogspot.com
 
 
 
 



 --
 Paul Fremantle
 Co-Founder and CTO, WSO2
 Apache Synapse PMC Chair
 OASIS WS-RX TC Co-chair

 blog: http://pzf.fremantle.org
 p...@wso2.com

 Oxygenating the Web Service Platform, www.wso2.com

 -
 To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
 For additional commands, e-mail: dev-h...@synapse.apache.org




-- 
Ruwan Linton
http://wso2.org - Oxygenating the Web Services Platform
http://ruwansblog.blogspot.com/

[jira] Assigned: (SYNAPSE-509) XML name space mismatch in Synapse sample 2 ,4 and 7


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton reassigned SYNAPSE-509:


Assignee: Ruwan Linton

 XML name space mismatch in Synapse sample 2 ,4 and 7
 

 Key: SYNAPSE-509
 URL: https://issues.apache.org/jira/browse/SYNAPSE-509
 Project: Synapse
  Issue Type: Bug
Affects Versions: NIGHTLY
Reporter: Charith Dhanushka Wickramarachchi
Assignee: Ruwan Linton
Priority: Minor
 Attachments: patch.txt


 Hi ,
 while running synapse samples i have found out that there is a xml namespace 
 mismatch in synapse samples 2 ,4 and 7
 following is the body of the soap message that i was able to trace while 
 sending the getquote request using the axis2client that is bundled in synapse.
 soapenv:Body
   m0:getQuote xmlns:m0=http://services.samples;
   m0:request
   m0:symbolIBM/m0:symbol
   /m0:request
   /m0:getQuote
 /soapenv:Body
 but in sample 2 4 and 7 are configured to accept a message with a different 
 namespace so they does not work properly
 (even though the sample 7 seems running perfectly the with the incomming 
 'Invalid custom quote request' axis fault that fault is generated due to the 
 xmlns mismatch.you can check this by changing stocksymbol -- symbol where 
 you get the same message)
 thank you,  
 Charith

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Commented: (SYNAPSE-509) XML name space mismatch in Synapse sample 2 ,4 and 7


[ 
https://issues.apache.org/jira/browse/SYNAPSE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679254#action_12679254
 ] 

Ruwan Linton commented on SYNAPSE-509:
--

Applied the patch Thanks charith for the contribution.

 XML name space mismatch in Synapse sample 2 ,4 and 7
 

 Key: SYNAPSE-509
 URL: https://issues.apache.org/jira/browse/SYNAPSE-509
 Project: Synapse
  Issue Type: Bug
Affects Versions: NIGHTLY
Reporter: Charith Dhanushka Wickramarachchi
Assignee: Ruwan Linton
Priority: Minor
 Attachments: patch.txt


 Hi ,
 while running synapse samples i have found out that there is a xml namespace 
 mismatch in synapse samples 2 ,4 and 7
 following is the body of the soap message that i was able to trace while 
 sending the getquote request using the axis2client that is bundled in synapse.
 soapenv:Body
   m0:getQuote xmlns:m0=http://services.samples;
   m0:request
   m0:symbolIBM/m0:symbol
   /m0:request
   /m0:getQuote
 /soapenv:Body
 but in sample 2 4 and 7 are configured to accept a message with a different 
 namespace so they does not work properly
 (even though the sample 7 seems running perfectly the with the incomming 
 'Invalid custom quote request' axis fault that fault is generated due to the 
 xmlns mismatch.you can check this by changing stocksymbol -- symbol where 
 you get the same message)
 thank you,  
 Charith

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Resolved: (SYNAPSE-509) XML name space mismatch in Synapse sample 2 ,4 and 7


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton resolved SYNAPSE-509.
--

   Resolution: Fixed
Fix Version/s: 1.3

Fixed on the trunk... 

 XML name space mismatch in Synapse sample 2 ,4 and 7
 

 Key: SYNAPSE-509
 URL: https://issues.apache.org/jira/browse/SYNAPSE-509
 Project: Synapse
  Issue Type: Bug
Affects Versions: NIGHTLY
Reporter: Charith Dhanushka Wickramarachchi
Assignee: Ruwan Linton
Priority: Minor
 Fix For: 1.3

 Attachments: patch.txt


 Hi ,
 while running synapse samples i have found out that there is a xml namespace 
 mismatch in synapse samples 2 ,4 and 7
 following is the body of the soap message that i was able to trace while 
 sending the getquote request using the axis2client that is bundled in synapse.
 soapenv:Body
   m0:getQuote xmlns:m0=http://services.samples;
   m0:request
   m0:symbolIBM/m0:symbol
   /m0:request
   /m0:getQuote
 /soapenv:Body
 but in sample 2 4 and 7 are configured to accept a message with a different 
 namespace so they does not work properly
 (even though the sample 7 seems running perfectly the with the incomming 
 'Invalid custom quote request' axis fault that fault is generated due to the 
 xmlns mismatch.you can check this by changing stocksymbol -- symbol where 
 you get the same message)
 thank you,  
 Charith

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Assigned: (SYNAPSE-499) Synapse.war not contain synapse .mar file in where should i put a patch ?is synapse NIGHTLY version?


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton reassigned SYNAPSE-499:


Assignee: Ruwan Linton

 Synapse.war not contain synapse .mar file in where should i put a patch ?is 
 synapse NIGHTLY version?
 

 Key: SYNAPSE-499
 URL: https://issues.apache.org/jira/browse/SYNAPSE-499
 Project: Synapse
  Issue Type: Bug
Affects Versions: NIGHTLY
Reporter: Charith Dhanushka Wickramarachchi
Assignee: Ruwan Linton
Priority: Minor
 Attachments: synapse.war.patch


 Synapse.war file does not contain a synapse-SNAPSHOT .mar file in 
 synapse.home/WEB-INF/repository/modules/ directory. Because of that synapse 
 cant be started in a web container.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Commented: (SYNAPSE-499) Synapse.war not contain synapse .mar file in where should i put a patch ?is synapse NIGHTLY version?


[ 
https://issues.apache.org/jira/browse/SYNAPSE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679258#action_12679258
 ] 

Ruwan Linton commented on SYNAPSE-499:
--

Applied the patch onto the trunk, thanks charith 

 Synapse.war not contain synapse .mar file in where should i put a patch ?is 
 synapse NIGHTLY version?
 

 Key: SYNAPSE-499
 URL: https://issues.apache.org/jira/browse/SYNAPSE-499
 Project: Synapse
  Issue Type: Bug
Affects Versions: NIGHTLY
Reporter: Charith Dhanushka Wickramarachchi
Assignee: Ruwan Linton
Priority: Minor
 Fix For: 1.3

 Attachments: synapse.war.patch


 Synapse.war file does not contain a synapse-SNAPSHOT .mar file in 
 synapse.home/WEB-INF/repository/modules/ directory. Because of that synapse 
 cant be started in a web container.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Resolved: (SYNAPSE-499) Synapse.war not contain synapse .mar file in where should i put a patch ?is synapse NIGHTLY version?


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton resolved SYNAPSE-499.
--

   Resolution: Fixed
Fix Version/s: 1.3

Fixed on the trunk

 Synapse.war not contain synapse .mar file in where should i put a patch ?is 
 synapse NIGHTLY version?
 

 Key: SYNAPSE-499
 URL: https://issues.apache.org/jira/browse/SYNAPSE-499
 Project: Synapse
  Issue Type: Bug
Affects Versions: NIGHTLY
Reporter: Charith Dhanushka Wickramarachchi
Assignee: Ruwan Linton
Priority: Minor
 Fix For: 1.3

 Attachments: synapse.war.patch


 Synapse.war file does not contain a synapse-SNAPSHOT .mar file in 
 synapse.home/WEB-INF/repository/modules/ directory. Because of that synapse 
 cant be started in a web container.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Commented: (SYNAPSE-100) Synapse could be improved to support WS-RM 1.1


[ 
https://issues.apache.org/jira/browse/SYNAPSE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679278#action_12679278
 ] 

Ruwan Linton commented on SYNAPSE-100:
--

Now Synapse is using Sandesha2 as its RM module and hence now we support RM 
1.1..

Thanks Amila for the great help in getting this fixed.

 Synapse could be improved to support WS-RM 1.1
 --

 Key: SYNAPSE-100
 URL: https://issues.apache.org/jira/browse/SYNAPSE-100
 Project: Synapse
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.0-RC2-B1
Reporter: Asankha C. Perera
Assignee: Ruwan Linton
Priority: Minor
 Fix For: FUTURE


 Sandesha2 is building up support for WS-RM 1.1. However this work is still in 
 progress, and the current code base of Synapse does not support WS-RM 1.1 
 with the Sandesha2 snapshot code.
 Due to this limitation, the version=1. attribute of the RMSequence mediator 
 will not be functional

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Resolved: (SYNAPSE-100) Synapse could be improved to support WS-RM 1.1


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton resolved SYNAPSE-100.
--

   Resolution: Fixed
Fix Version/s: (was: FUTURE)
   1.3

Fixed on the trunk and will be available with the 1.3 release

 Synapse could be improved to support WS-RM 1.1
 --

 Key: SYNAPSE-100
 URL: https://issues.apache.org/jira/browse/SYNAPSE-100
 Project: Synapse
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.0-RC2-B1
Reporter: Asankha C. Perera
Assignee: Ruwan Linton
Priority: Minor
 Fix For: 1.3


 Sandesha2 is building up support for WS-RM 1.1. However this work is still in 
 progress, and the current code base of Synapse does not support WS-RM 1.1 
 with the Sandesha2 snapshot code.
 Due to this limitation, the version=1. attribute of the RMSequence mediator 
 will not be functional

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Assigned: (SYNAPSE-500) Error in Serializing the fault mediator fault code with a QName having default prefix


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton reassigned SYNAPSE-500:


Assignee: Ruwan Linton

 Error in Serializing the fault mediator fault code with a QName having 
 default prefix 
 --

 Key: SYNAPSE-500
 URL: https://issues.apache.org/jira/browse/SYNAPSE-500
 Project: Synapse
  Issue Type: Bug
  Components: Core
Reporter: Nandana Mihindukulasooriya
Assignee: Ruwan Linton
 Attachments: SYNAPSE-500.patch


 When I set the FaultCode vaule as given below,
 faultMediator.setFaultCodeValue(new 
 QName(http://www.w3.org/2003/05/soap-envelope,Reciver;));
 it is serialized as  
 syn:makefault
 syn:code xmlns:axis2ns2=http://www.w3.org/2003/05/soap-envelope; 
 value=:Receiver / 
 /syn:makefault
 The problem is when the QName is having the default prefix which is . When 
 I set the fault code with a QName with some other prefix 
 faultMediator.setFaultCodeValue(new 
 QName(http://www.w3.org/2003/05/soap-envelope,Reciver,myPrefix;));
 it is serialized correctly. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Resolved: (SYNAPSE-500) Error in Serializing the fault mediator fault code with a QName having default prefix


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton resolved SYNAPSE-500.
--

   Resolution: Fixed
Fix Version/s: 1.3

Fixed on the trunk and will be available in the 1.3 release

 Error in Serializing the fault mediator fault code with a QName having 
 default prefix 
 --

 Key: SYNAPSE-500
 URL: https://issues.apache.org/jira/browse/SYNAPSE-500
 Project: Synapse
  Issue Type: Bug
  Components: Core
Reporter: Nandana Mihindukulasooriya
Assignee: Ruwan Linton
 Fix For: 1.3

 Attachments: SYNAPSE-500.patch


 When I set the FaultCode vaule as given below,
 faultMediator.setFaultCodeValue(new 
 QName(http://www.w3.org/2003/05/soap-envelope,Reciver;));
 it is serialized as  
 syn:makefault
 syn:code xmlns:axis2ns2=http://www.w3.org/2003/05/soap-envelope; 
 value=:Receiver / 
 /syn:makefault
 The problem is when the QName is having the default prefix which is . When 
 I set the fault code with a QName with some other prefix 
 faultMediator.setFaultCodeValue(new 
 QName(http://www.w3.org/2003/05/soap-envelope,Reciver,myPrefix;));
 it is serialized correctly. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Assigned: (SYNAPSE-493) Synapse sets the HttpCoreRequestResponseTransport status value to INITIAL


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton reassigned SYNAPSE-493:


Assignee: Ruwan Linton

 Synapse sets the HttpCoreRequestResponseTransport status value to INITIAL
 -

 Key: SYNAPSE-493
 URL: https://issues.apache.org/jira/browse/SYNAPSE-493
 Project: Synapse
  Issue Type: Bug
Reporter: Amila Chinthaka Suriarachchi
Assignee: Ruwan Linton
 Attachments: patch.txt


 ServletRequestResponseTransport and SimpleHTTPRequestResponseTranspor set 
 this value to WAITING.
 This gives a problem with sandesah2. Sandesha2 has this code.
 if((toEPR==null || toEPR.hasAnonymousAddress()) 
  (makeConnection == null || 
 !makeConnection.booleanValue()) 
  (t == null || 
 !t.getStatus().equals(RequestResponseTransportStatus.WAITING))) {
   
   // Mark this sender bean so that we know that 
 the transport is unavailable, if the
   // bean is still stored.
   SenderBean bean = 
 senderBeanMgr.retrieve(senderBean.getMessageID());
   if(bean != null  bean.isTransportAvailable()) 
 {
   bean.setTransportAvailable(false);
   senderBeanMgr.update(bean);
   }
   
   // Commit the update
   if(transaction != null  
 transaction.isActive()) transaction.commit();
   transaction = null;
   
   if (log.isDebugEnabled())
   log.debug(Exit: SenderWorker::run, no 
 response transport for anonymous message);
   return;
   }
 it does not send the response back if the status of the 
 RequestResponseTransport is WAITING. 
 Setting this initial value to WAITING makes the Sandesha2 works with the 
 synapse.
 is it possible to change this initial value to WAITING?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: svn commit: r749766 - /synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/nhttp/HttpCoreRequestResponseTransport.java

2009-03-04 Thread Ruwan Linton

Done !

Thanks,
Ruwan

On Wed, Mar 4, 2009 at 2:24 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:

 If it is properly documented in the code and if you add a comment to
 SYNAPSE-493 so that we can keep track of this, then I'm fine with it.

 Andreas

 On Wed, Mar 4, 2009 at 03:31, Ruwan Linton ruwan.lin...@gmail.com wrote:
  Andreas,
 
  I didn't note this earlier. My intention was to switch back to sandesha2
  because the current RM implementation that Synapse is using for the
 moment
  (WSO2 Mercury) is not supported by the WSO2 any more at least in this
 year
  and I wanted to move back to sandesha2.
 
  If I describe the history of the RM implementation switching we couldn't
 get
  Sandesha2 to work with NIO HTTP transport after the 1.0 release of
 synapse
  and that is why we moved to the Mercury implementation and now I don't
 want
  synapse to depend on that because the project is not live at this moment.
 
  So I suggest that we use this as a work around till we get this fixed in
  Sandesha2 I have tested all the scenarios which might be affected by
  this change and if there is any issue please do let me know. I will add a
  TODO documentation in to this piece of code as well.
 
  (We need to get RM to work with Sandesha2 for the 1.3 release)
 
  Thanks,
  Ruwan
 
  On Wed, Mar 4, 2009 at 4:18 AM, Andreas Veithen 
 andreas.veit...@gmail.com
  wrote:
 
  Ruwan,
 
  This change was proposed in SYNAPSE-493, but there the conclusion was
  that this change would be in contradiction with the available
  documentation in Axis2 and that it is more likely an issue in
  Sandesha2.
 
  Andreas
 
  On Tue, Mar 3, 2009 at 22:37,  ru...@apache.org wrote:
   Author: ruwan
   Date: Tue Mar  3 21:37:47 2009
   New Revision: 749766
  
   URL: http://svn.apache.org/viewvc?rev=749766view=rev
   Log:
   set the status to WAITING for fixing some RM scenarios, I have tested
   with all dual channel invocations and it seems to work fine
  
   Modified:
  
  
  
 synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/nhttp/HttpCoreRequestResponseTransport.java
  
   Modified:
  
 synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/nhttp/HttpCoreRequestResponseTransport.java
   URL:
  
 http://svn.apache.org/viewvc/synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/nhttp/HttpCoreRequestResponseTransport.java?rev=749766r1=749765r2=749766view=diff
  
  
 ==
   ---
  
 synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/nhttp/HttpCoreRequestResponseTransport.java
   (original)
   +++
  
 synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/nhttp/HttpCoreRequestResponseTransport.java
   Tue Mar  3 21:37:47 2009
   @@ -39,7 +39,7 @@
public class HttpCoreRequestResponseTransport implements
   RequestResponseTransport {
  
   private static final Log log =
   LogFactory.getLog(HttpCoreRequestResponseTransport.class);
   -private RequestResponseTransportStatus status =
   RequestResponseTransportStatus.INITIAL;
   +private RequestResponseTransportStatus status =
   RequestResponseTransportStatus.WAITING;
   private MessageContext msgContext = null;
   private boolean responseWritten = false;
  
  
  
  
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
  For additional commands, e-mail: dev-h...@synapse.apache.org
 
 
 
 
  --
  Ruwan Linton
  http://wso2.org - Oxygenating the Web Services Platform
  http://ruwansblog.blogspot.com/
 

 -
 To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
 For additional commands, e-mail: dev-h...@synapse.apache.org




-- 
Ruwan Linton
http://wso2.org - Oxygenating the Web Services Platform
http://ruwansblog.blogspot.com/

[jira] Assigned: (SYNAPSE-511) Properly handle the ?wsdl out put when the proxy service doesn't have a WSDL specified


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton reassigned SYNAPSE-511:


Assignee: Ruwan Linton

 Properly handle the ?wsdl out put when the proxy service doesn't have a WSDL 
 specified
 --

 Key: SYNAPSE-511
 URL: https://issues.apache.org/jira/browse/SYNAPSE-511
 Project: Synapse
  Issue Type: Improvement
  Components: Transports
Affects Versions: 1.2
 Environment: all envs
Reporter: Ruwan Linton
Assignee: Ruwan Linton
 Fix For: 1.3


 If you request a ?wsdl on a proxy service which doesn't have a WSDL specified 
 when building the proxy service, for the moment we just drop the connection 
 and there is an NPE in the console. We should handle this properly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Resolved: (SYNAPSE-511) Properly handle the ?wsdl out put when the proxy service doesn't have a WSDL specified


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton resolved SYNAPSE-511.
--

Resolution: Fixed

Fixed on the trunk and will be available with the 1.3 release

 Properly handle the ?wsdl out put when the proxy service doesn't have a WSDL 
 specified
 --

 Key: SYNAPSE-511
 URL: https://issues.apache.org/jira/browse/SYNAPSE-511
 Project: Synapse
  Issue Type: Improvement
  Components: Transports
Affects Versions: 1.2
 Environment: all envs
Reporter: Ruwan Linton
Assignee: Ruwan Linton
 Fix For: 1.3


 If you request a ?wsdl on a proxy service which doesn't have a WSDL specified 
 when building the proxy service, for the moment we just drop the connection 
 and there is an NPE in the console. We should handle this properly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Assigned: (SYNAPSE-492) synapse does not add addressing headers to addresing client response


 [ 
https://issues.apache.org/jira/browse/SYNAPSE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton reassigned SYNAPSE-492:


Assignee: Ruwan Linton

 synapse does not add addressing headers to addresing client response
 

 Key: SYNAPSE-492
 URL: https://issues.apache.org/jira/browse/SYNAPSE-492
 Project: Synapse
  Issue Type: Bug
Reporter: Amila Chinthaka Suriarachchi
Assignee: Ruwan Linton
 Attachments: patch.txt


 Create a proxy service with the following synapse configuration.
 definitions xmlns=http://ws.apache.org/ns/synapse;
 proxy name=StockQuoteProxy
 target
 inSequence
 header name=wsrm:SequenceAcknowledgement 
 action=remove
 
 xmlns:wsrm=http://schemas.xmlsoap.org/ws/2005/02/rm/
 header name=wsrm:Sequence action=remove
 
 xmlns:wsrm=http://schemas.xmlsoap.org/ws/2005/02/rm/
 send
 endpoint
 address 
 uri=http://localhost:9001/services/SimpleStockQuoteService/
 /endpoint
 /send
 /inSequence
 outSequence
 send/
 /outSequence
 /target
 /proxy
 /definitions
 Note that for proxy service end point addressing is not engaged. 
 Then invoke this proxy service with the following client request.
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
   soapenv:Header xmlns:wsa=http://www.w3.org/2005/08/addressing;
  wsa:Tohttp://localhost:8281/services/StockQuoteProxy/wsa:To
  
 wsa:MessageIDurn:uuid:7A24BA37E7FBA1158F1230053211470/wsa:MessageID
  wsa:Actionurn:getQuote/wsa:Action
   /soapenv:Header
   soapenv:Body
  m0:getQuote xmlns:m0=http://services.samples;
 m0:request
m0:symbolIBM/m0:symbol
 /m0:request
  /m0:getQuote
   /soapenv:Body
/soapenv:Envelope
 Then the response message does not have the addressing headers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Resolved: (SYNAPSE-492) synapse does not add addressing headers to addresing client response