Hi Chamikara,
I chekout Sandesha2 and run maven.
I take the sandesha2-SNAPSHOT.mar, sandesha2-client-SNAPSHOT.jar et
sandesha2-SNAPSHOT.jar. I put them on catalina and on the client. Now I
have an error when I launch catalina. The problem to the
sandesha2-SNAPSHOT.mar.
- Deploying module :
Hi Elliod,
This is because u hv the old Neethi jar in you tomcat lib directory. Remove this and add the latest Neethi-SNAPSHOT.jar from
http://people.apache.org/repository/ws-commons/jars/
Chamikara
On 7/4/06, Mancinelli Elodie [EMAIL PROTECTED] wrote:
Hi Chamikara,I chekout Sandesha2 and run
Elodie
This looks more like a Sandesha bug. I will do a test as well and let
you know how it goes.
Paul
On 7/3/06, Mancinelli Elodie [EMAIL PROTECTED] wrote:
Hi Paul
1) Yes, MTOM + XMLBeans code works without WSRM and also WSRM + XMLBeans
code works without WSRM.
2) The error for MTOM + WSRM
Hi Chamikara,
Thanks you for your help.
I change the 'InvokeInOrder' policy in the module.xml to 'false' in the
sandesha2_1.0 mar.
And now,I have an other error. I give you the catalina log:
3 juil. 2006 15:01:45 org.apache.catalina.core.StandardHostValve custom
GRAVE: Exception Processing
Sorry I forget the StackTrace:
java.lang.NullPointerException
org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor.setUpHighestMsgNumbers(TerminateSeqMsgProcessor.java:185)
Hi Elodie,
This was due to a bug, fixed now. Please take a latest checkout of Sandesha2.
Chamikara
On 7/3/06, Mancinelli Elodie [EMAIL PROTECTED] wrote:
Sorry I forget the
Hi all,
I try to create an OneWay method which supports WSRM and an attachment.
My service is really simple, it's only a println.
The method runs successfully when there is only the WSRM implementation,
but when I add the attachement part, I have an server error:
Mancinelli Elodie wrote:
Sorry, I want to precise my request. When I observe with TCPMon the
soap message, the differents messages of WSRM's protocole are created
(CreateSequence, CreateSequenceResponse, Message, Acknowldgement and
TerminateSequence). These messages are correct. The problem
Elodie
I think the problem is that you are using MTOM with XMLBeans which
does not work.
Paul
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
Oxygenating the Web Service Platform, www.wso2.com
On 6/28/06,
