Re: [Axis2] Sandesha2 1.2 plus Rampart 1.2 in Axis2 1.2

[Chamikara Jayalath]

Hi Ted,

No need to change the phase order. Sandesha2 will treat Security phase as
special and will be calling it in each retransmission (for things like
Tamstamp to be updated).

Please attach your client and service code to the JIRA. I'll try to
reproduce the error.

Chamikara



On 6/13/07, Ted Jones <[EMAIL PROTECTED]> wrote:


 Chamikara,

Thanks for the reply. I reset the SecurityManager to the dummy and I am
now getting this:


2007-06-13 10:42:12,703 ERROR org.apache.sandesha2.workers.SenderWorker -
Sandesha2 got an exception when sending a message:
org.apache.axis2.AxisFault: WSDoAllSender: Empty username for specified
action.

org.apache.axis2.AxisFault: WSDoAllSender: Empty username for specified
action

at org.apache.rampart.handler.WSDoAllSender.processMessage(
*WSDoAllSender.java:94*)

at org.apache.rampart.handler.WSDoAllHandler.invoke(
*WSDoAllHandler.java:72*)

at org.apache.axis2.engine.Phase.invoke(
*Phase.java:383*)

at org.apache.axis2.engine.AxisEngine.invoke(
*AxisEngine.java:203*)

at org.apache.axis2.engine.AxisEngine.resumeSend(
*AxisEngine.java:318*)

at org.apache.sandesha2.workers.SenderWorker.run(
*SenderWorker.java:258*)

at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(
*ThreadPoolExecutor.java:665*)

at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
(
*ThreadPoolExecutor.java:690*)

at java.lang.Thread.run(
*Thread.java:534*)
When using Rampart UsernameToken security with Sandesha2, does the phase
order need to change? Perhaps the WS-Security headers need to be added prior
to the RM phase? I will log a JIRA (assuming it is not just a user error).

FYI - I switched to HTTP Basic security with Sandesha2 and it worked fine.

Thanks again,
Ted



 --
*From:* Chamikara Jayalath [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, June 12, 2007 11:34 PM
*To:* axis-user@ws.apache.org
*Subject:* Re: [Axis2] Sandesha2 1.2 plus Rampart 1.2 in Axis2 1.2

Hi Ted,

You do not need the SecurityManager in Non-SecureConversation scenarios.
Can u please try without that.  Also it will be helpful if you can raise a
JIRA and attach ur client code, the error logs etc.

Chamikara


On 6/13/07, Ted Jones <[EMAIL PROTECTED]> wrote:
>
>  I am able to use Rampart 1.2 (UsernameToken) and Sandesha2 1.2 in Axis2
> 1.2 as standalone modules, but when I engage them both I do not see any
> messages in TCPMon and my client times out before I get a response. I
> updated the Sandesha2.mar module.xml Security Manager to use
> org.apache.sandesha2.security.rampart.RampartBasedSecurityManager. Are
> there any steps I am missing?
>
> (I apologize if this is the wrong group for this posting. If so, kindly
> point me to the correct forum.)
>
> Thanks,
> Ted
>



--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs





--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs

Re: [Axis2] Sandesha2 1.2 plus Rampart 1.2 in Axis2 1.2

[Chamikara Jayalath]

Hi Ted,

You do not need the SecurityManager in Non-SecureConversation scenarios. Can
u please try without that.  Also it will be helpful if you can raise a JIRA
and attach ur client code, the error logs etc.

Chamikara


On 6/13/07, Ted Jones <[EMAIL PROTECTED]> wrote:


 I am able to use Rampart 1.2 (UsernameToken) and Sandesha2 1.2 in Axis2
1.2 as standalone modules, but when I engage them both I do not see any
messages in TCPMon and my client times out before I get a response. I
updated the Sandesha2.mar module.xml Security Manager to use
org.apache.sandesha2.security.rampart.RampartBasedSecurityManager. Are
there any steps I am missing?

(I apologize if this is the wrong group for this posting. If so, kindly
point me to the correct forum.)

Thanks,
Ted





--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs

[ANN] Apache Sandesha2 1.2 released

[Chamikara Jayalath]

Hi All,

We are proud to announce the 1.2 release of Apache Sandesha2. This release
is compatible with recently released Apache Axis2 1.2.

Major features of this release include.

Support for the replay model for WSRM 1.0
Improvements to the Rampart integration.
Improvements to the Client API

Also we could do a number of of bug fixes and improvements based on user and
developer comments.

You can download the source and binaries from,
http://ws.apache.org/sandesha/sandesha2/download.cgi


Thanks,
Chamikara

Re: Savan Download

[Chamikara Jayalath]

Hi Smitha,

You can download Savan from the following location
https://svn.apache.org/repos/asf/webservices/savan/trunk/java

We are currently doing a quite a lot of refactoring and additions to the
code base. Hopefully followed by some documents and a release.

Chamikara


On 5/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


 Hi



I need to work with WS-Eventing.

It's a big help if anybody can provide me the link to download savan



Thanks And Regards

Smitha Aldrin

The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s) and
may contain proprietary, confidential or privileged information. If you are
not the intended recipient, you should not disseminate, distribute or copy
this e-mail. Please notify the sender immediately and destroy all copies of
this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses. The
company accepts no liability for any damage caused by any virus transmitted
by this email.

www.wipro.com





--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs

Re: [Axis2] MessageReceiver is Null in Axis2 Operation using WS-RM

[Chamikara Jayalath]

Hi Ted,

Could u please add JIRA (in Sandesha2) and attach whatever the files
necessary to reproduce the error. I just did a test with Axis21.1.1/Sandesha2
1.1 and it ran without trouble.

Chamikara


On 5/2/07, Ted Jones <[EMAIL PROTECTED]> wrote:


 I am using Sandesha2 1.1 with Axis2 1.1.1 and am running into an error
where the MessageReceiver is null for the Axis operation and is causing
a NPE. The following code in the OutInAxisOperation class is where the
exception occurs:

 if (options.isUseSeparateListener()) {
CallbackReceiver callbackReceiver = (CallbackReceiver) axisOp
.getMessageReceiver();
callbackReceiver.addCallback(mc.getMessageID(), callback);

I have the message receivers defined in my client axis2.xml and server
axis.xml. I even have the message receivers defined in the service.xml for
good measure.

I have set the following options in the Axis2 client:

clientOptions.setTransportInProtocol(
org.apache.axis2.Constants.TRANSPORT_HTTP);
clientOptions.setProperty(AddressingConstants.WS_ADDRESSING_VERSION,
org.apache.axis2.addressing.AddressingConstants.Final.WSA_NAMESPACE);
clientOptions.setUseSeparateListener(true);

The client/service works without Sandesha2 since I am not using a separate
listener in that case.

Is there anything else I need to add the the Axis2.xml or client code to
get the receiver set on the operation?

TIA,
Ted







--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs

Re: Axis2 : Savan vs. Muse for WS-Notification

[Chamikara Jayalath]

Hi Gulm

We moved Savan out of the Axis2 codebase and it will not be shipped as a
part of Axis2. We hope to do a separate release of Savan, but the exact time
frames have not been decided yet.

Chamikara


On 4/2/07, Gul Onural <[EMAIL PROTECTED]> wrote:


 Thanks Chamikara. Do you know when Savan will be distributed as part of
Axis2 module ?

 --
*From:* Chamikara Jayalath [mailto:[EMAIL PROTECTED]
*Sent:* Monday, April 02, 2007 3:54 AM
*To:* axis-user@ws.apache.org
*Subject:* Re: Axis2 : Savan vs. Muse for WS-Notification

Hi Gul,

Here is the corret SVN URL for Savan.
https://svn.apache.org/repos/asf/webservices/savan/trunk/java/

The new home page is http://ws.apache.org/savan/ (but this is not fully
complete yet).

Chamikara



On 4/2/07, Gul Onural <[EMAIL PROTECTED]> wrote:
>
>
> Looks like both Savan and Muse are the implementation of
> WS-Notification/Eventing.
>
> None of these two is listed under Axis2 modules 
(*http://ws.apache.org/axis2/modules/index.html
> * <http://ws.apache.org/axis2/modules/index.html>).
>
> I was wondering :
>
> 1.) Are they (Savan and Muse) active projects ?
> 2.) Is there any plans to integrate any of them to Axis2 as module ?
> 3.) Are their functionality equivalent ? (the version of the
> WS-Notification spec. they implement, etc)
> 4.) Is there anyone using either of them with Axis2 ?
>
> The only information I was able to find about Savan is at  *
> http://wso2.org/projects/savan/java*<http://wso2.org/projects/savan/java>,
> however
> link to the Savan source code repository in that page is broken.
>
> And *http://www.apachenews.org/archives/000932.html 
*<http://www.apachenews.org/archives/000932.html>says;
> "***Modules supporting WS-Eventing (Apache Savan) *
> *& WS-Transactions (Apache Kandula2) will be available soon after the
> Apache Axis2 1.1.1 release*.".
> But I haven't seen any recent news on Savan in Axis2 web site, yet.
>
> I would greatly appreciate any information on this subject.
>
> Gul
>







--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs

Re: Axis2 : Savan vs. Muse for WS-Notification

[Chamikara Jayalath]

Hi Gul,

Here is the corret SVN URL for Savan.
https://svn.apache.org/repos/asf/webservices/savan/trunk/java/

The new home page is http://ws.apache.org/savan/ (but this is not fully
complete yet).

Chamikara



On 4/2/07, Gul Onural <[EMAIL PROTECTED]> wrote:



Looks like both Savan and Muse are the implementation of
WS-Notification/Eventing.

None of these two is listed under Axis2 modules (*
http://ws.apache.org/axis2/modules/index.html*
).

I was wondering :

1.) Are they (Savan and Muse) active projects ?
2.) Is there any plans to integrate any of them to Axis2 as module ?
3.) Are their functionality equivalent ? (the version of the
WS-Notification spec. they implement, etc)
4.) Is there anyone using either of them with Axis2 ?

The only information I was able to find about Savan is at  *
http://wso2.org/projects/savan/java* ,
however
link to the Savan source code repository in that page is broken.

And 
*http://www.apachenews.org/archives/000932.html*says;
 "
***Modules supporting WS-Eventing (Apache Savan) *
*& WS-Transactions (Apache Kandula2) will be available soon after the
Apache Axis2 1.1.1 release*.".
But I haven't seen any recent news on Savan in Axis2 web site, yet.

I would greatly appreciate any information on this subject.

Gul

Re: WS-Notification implementation for Axis2

[Chamikara Jayalath]

Hi,

The Savan project provides a WS-Eventing Impl for Axis2 which might help u.
Also the architecture provides flexibility to add support for other Pub/Sub
impls.
You can find the code at [1]

Chamikara

[1] https://svn.apache.org/repos/asf/webservices/savan/trunk/java


On 3/20/07, Doug Davis <[EMAIL PROTECTED]> wrote:



Just wondering... do you want "event driven communication" or just "new
unsolicited messages" from the server to the client.  The latter can be done
by simply providing the server with an EPR to send messages to - no need for
a formal event infrastructure.  Or did you really want to formalize
everything and have a Subscribe(), events, Unsubscribe()  ?

thanks
-Doug
__
STSM  |  Web Services Architect  |  IBM Software Group
(919) 254-6905  |  IBM T/L 444-6905  |  [EMAIL PROTECTED]


 *"Gul Onural" <[EMAIL PROTECTED]>*

03/20/2007 11:39 AM  Please respond to
axis-user@ws.apache.org

  To
  cc

 Subject
RE: WS-Notification implementation for Axis2







Apache Muse implements quite a bit number of WS- specs
(WS-MetadataExchange (WSX),WS-ResourceFramework (WSRF), WS-Notification
(WSN), WS-DistributedManagement (WSDM)...)

What I want to accomplish is to have event driven communication between
our web service (which is implemented using axis2) and web service
clients.

Architecturally with Muse, is it possible to use WS-Notification without
using the implementation of other specs in Muse ? How are they tied
together ?

Gul




-Original Message-
From: Daniel Jemiolo [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 20, 2007 9:24 AM
To: axis-user@ws.apache.org
Subject: Re: WS-Notification implementation for Axis2

The Apache Muse project implements WS-Notification 1.3 (ratified last
year) and runs on Axis2. More info here:

   http://ws.apache.org/muse/docs/2.2.0/tutorial/index.html

   http://ws.apache.org/muse/docs/2.2.0/manual/index.html

Dan


-
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]

Re: Real Asynchronous WebServices with JMS

[Chamikara Jayalath]

Hi All,

I also believe that passing a class than the instance will be a better
approach here. Letting the user pass the object kind of conveys that we will
be preserving the state, which we actually will not be doing.

We still couldn't commit the persistent implementation of the Sandesha2
StorageManager to Apache due to it's dependency on Hibernate. Apache legal
team informed us that we have to wait till some legal issues are solved.
Till then the code is available at [1].

Also +1 for Paul's suggestion to let the user pass an Serializable object
(or an XML) to be managed by the persistence layer.

Chamikara

[1] http://wso2.org/repos/wso2/trunk/commons/sandesha2-persistence/


On 3/15/07, Gul Onural <[EMAIL PROTECTED]> wrote:



I know the WS-RM is not particularly concerned with async. invocation of
web services, but passing class instead of an instance would make
Sandesha2 quite usable for asynchrony purposes.

Any comments from Sandesha2 gurus ? I assume Chamikara is copied to
provide comments ?

Gul

-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 7:55 AM
To: axis-user@ws.apache.org
Cc: axis-dev@ws.apache.org; Chamikara Jayalath
Subject: Re: Real Asynchronous WebServices with JMS

Gil, Gul

This only happens with the persistent implementation of Sandesha.

So - I think you are making a really good point here, and I think we
need to add another approach to the callback model.

Currently the callback only takes an instance. Now, one approach is that
we could try to serialize that instance class. However, I think thats
not necessarily a scalable model.

I would rather that for the truly async case we pass in a class instead
of an instance.

Then the question is whether to leave it up to the user to store their
own state, or whether to help them. If we help them, I would rather
explicitly pass a java.io.Serializable or even better an XML document
and then inject it into the callback class. I think this ends up with a
more solid model than just trying to serialize the existing callback.

e.g.

ServiceClient.sendReceiveNonBlocking(OMElement payload, Class
callbackClass, Serializable state);

then when the response comes back we do..

Callback callback = (Callback)callbackClass.newInstance();
if (callback instanceof Injectable) {
callback.setState(state);
}
callback.onComplete(result)



Paul







On 3/15/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> Gul
>
> A while back we had a discussion about what happens if the system
> crashes and sandesha then delivers the message after a restart. At
> that point it was stated that when Sandesha is involved, it news up
> instances instead of using saved callbacks.
>
> I will check with the Sandesha gurus.
>
> Paul
>
> On 3/14/07, Gul Onural <[EMAIL PROTECTED]> wrote:
> >
> > I have the same issue as Gilbert. We don't just want "unblocking"
> > API, but real async. API.
> > I took a quick look into Sandesha2 and I am trying to understand
> > your comments (reply to Gilbert) on Sandesha2.
> >
> > You say the behavior we want can be achieved using Sandesha2. But I
> > am not sure I truly understand rest of your comments on Sandesha2.
> > Can you elaborate a bit more ?
> >
> >
> > " I believe that when you use Sandesha2 for reliable messaging
> > you get the behavior you want.
> >   I agree that there ought to be a way of specifying a class or
> > a factory instead of an instance.
> >   In that case it would be up to you to manage the correlation
> > based on looking inside the message. "
> >
> > Thanks.
> >
> >
> >
> > -Original Message-
> > From: Paul Fremantle [mailto:[EMAIL PROTECTED]
> > Sent: Monday, March 12, 2007 7:06 PM
> > To: axis-user@ws.apache.org; axis-dev@ws.apache.org
> > Subject: Re: Real Asynchronous WebServices with JMS
> >
> > Gilbert
> >
> > We had a similar discussion to this about Sandesha2. I believe that
> > when you use Sandesha2 for reliable messaging you get the behaviour
you want.
> > I agree that there ought to be a way of specifying a class or a
> > factory instead of an instance. In that case it would be up to you
> > to manage the correlation based on looking inside the message.
> >
> > I guess at the moment you could implement what you desire by
> > implementing the response handling as a new service. Now you need to

> > start the JMS transport and Axis2 as a server at the client end
> > yourself, and find the EPR of the "response service". Set this as
> > the replyTo of the outgoing request and then make a one-way
> > invocation against the real service.
> >
> > Does that make sense? 

Re: [Axis2] ServiceClient question

[Chamikara Jayalath]

Hi Michele,

There is only one listener instance per configuration context. So in this
case you will have to make sure that all the ServiceClients hv done with the
listener, before stopping it.

Chamikara


On 2/14/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:


Hi Chamikara,

what about I want to use my custom configuration ctx across different
service clients (the conf. ctx uses a multithreaded connection manager)?
Is it still ok to call configurationContext.getListenerManager ().stop();
?


Thanks,
Michele

On Tue, 2006-10-24 at 09:58 +0530, Chamikara Jayalath wrote:
> To stop the listner yourself you will have to call the following
> method as well.
>
> configurationContext.getListenerManager().stop();
>
> Chamikara
>
>
> On 10/24/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi Michele;
>
> Yes , cleanup is enough.
> Note : when you are creating service client if you pass your
> own
> configctx , then it will not stop the started listeners , but
> if you
> create that with default constructor it does.
>
> Thanks
> Deepal
>
> >Hi all,
> >
> >what should I use instead of the
> ServiceClient.finalizeInvoke() call
> >(which I guess has been removed)? Is the cleanup() call
> enough?
> >
> >Thanks,
> >Michele
> >
>
>-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
>
> --
> Thanks,
> Deepal
> 
> ~Future is Open~
>
>
>
>
-
> 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]

Re: [Axis2][Sandesha2] 1.1 Release candidates

[Chamikara Jayalath]

Hi Falom,

Still we hvnt done such a comparison. Would be glad if u can give some help
on that.

Chamikara


On 11/28/06, falom <[EMAIL PROTECTED]> wrote:


Hi Chamikara,

  Any comment on whether Sandesha2 1.1 is now better optimized if
compared with ActiveMQ for reliablemessaging. My service needs to be async

and i'm still not sure if i should use RM with persistence or jms. Still
Axis2's support on jms is quite limited.

  falom


*Chamikara Jayalath <[EMAIL PROTECTED]>* 写道：

Hi All,

I have uploaded the Sandesha2 1.1 release candidates to
http://people.apache.org/~chamikara/sandesha2/1.1-RC1/<http://people.apache.org/%7Echamikara/sandesha2/1.1-RC1/>

Please try these out and send any issues you get.

Thanks,
Chamikara


--
雅虎免费邮箱-3.5G容量，20M附件 <http://cn.mail.yahoo.com/>

[Axis2][Sandesha2] 1.1 Release candidates

[Chamikara Jayalath]

Hi All,

I have uploaded the Sandesha2 1.1 release candidates to
http://people.apache.org/~chamikara/sandesha2/1.1-RC1/

Please try these out and send any issues you get.

Thanks,
Chamikara

Re: [AXIS2]Savan Module - possible to notify client instead of another service?

[Chamikara Jayalath]

Hi Bastian,

Yes. The way u suggested will certainly work. All u need to have is a
endpoint that is capable of capturing the events send by the EventSource.

You can set this endpoint as the delivery EPR, of the EventingClient.
e.g.:
   String address = "address of your desired delivery endpoint";
   EventingClientBean bean = new EventingClientBean ();
   String id = "id1";
   bean.setDeliveryEPR(new EndpointReference (address));
   eventingClient.subscribe(bean,ID);


Thanks,
Chamikara


On 11/20/06, Bastian Köhler <[EMAIL PROTECTED]> wrote:


Hi,
I have a question about the Axis2 Savan Module, which provides WS-Eventing
support.
I downloaded the sample application code from the svn repository. In the
example a listenerservice is notified about new events (produced by
another
service).
Is it also possible to send the notification messages to the client
instead
of another Webservice? I want the client(s) to be notified about events
(or
new data). And the second question is, how to do that. My first idea was
to
use the simplehttpserver on the clientside and register a service, which
is
then used as the Listenerservice...Does this make sense or are there any
better solutions to my problem.

Any suggestion would be helpful. Thanks in advance.


Bastian


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

Re: [Axis2] ServiceClient question

[Chamikara Jayalath]

To stop the listner yourself you will have to call the following method as well.configurationContext.getListenerManager().stop();ChamikaraOn 10/24/06, 
Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Hi Michele;Yes , cleanup is enough.Note : when you are creating service client if you pass your ownconfigctx , then it will not stop the started listeners , but if youcreate that with default constructor it does.
ThanksDeepal>Hi all,>>what should I use instead of the ServiceClient.finalizeInvoke() call>(which I guess has been removed)? Is the cleanup() call enough?>>Thanks,
>Michele>>->To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]>--Thanks,Deepal
~Future is Open~-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: sandesh2 v1.0 module load throws NoClassDefFoundError: org/apache/ws/security/WSSecurityException

[Chamikara Jayalath]

Hi Yadav,Guess you'll have to get the wss4j-SNAPSHOT jar file as well.I think this is a good reason not to make the RampartBasedSecurityManager the default in sandesha2.  Axis2 war file does not come with {rampart,rahas,wss4j} jars.
ChamikaraOn 10/19/06, Yadav, Yogendra (IT) <[EMAIL PROTECTED]> wrote:
I downloaded axis2-security-1.1-SNAPSHOT.jar from
http://ws.zones.apache.org/~dims/maven/org.apache.axis2/jars/Now, I get this error:java.lang.NoClassDefFoundError:org/apache/ws/security/WSSecurityExceptionat java.lang.Class.getDeclaredConstructors0
(Native Method)atjava.lang.Class.privateGetDeclaredConstructors(Class.java:2328)at java.lang.Class.getConstructor0(Class.java:2640)at java.lang.Class.newInstance0(Class.java:321)
at java.lang.Class.newInstance(Class.java:303)atorg.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils.java:63)atorg.apache.axis2.deployment.DeploymentEngine.addNewModule(DeploymentEngi
ne.java:311)atorg.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:599)atorg.apache.axis2.deployment.RepositoryListener.loadClassPathModules(RepositoryListener.java
:124)atorg.apache.axis2.deployment.RepositoryListener.(RepositoryListener.java:55)atorg.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:100)
atorg.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:116)atorg.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(
ConfigurationContextFactory.java:61)atorg.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:179)atorg.apache.axis2.transport.http.SimpleHTTPServer.main
(SimpleHTTPServer.java:157)[SimpleHTTPServer] Shutting down-Original Message-From: Yadav, Yogendra (IT)Sent: Wednesday, October 18, 2006 5:29 PMTo: 
axis-user@ws.apache.org; Thilina GunarathneSubject: RE: sandesh2 v1.0 module load throws NoClassDefFoundError:org/apache/rampart/RampartExceptionI downloaded axis2-rahas-1.1-SNAPSHOT.jar  from
http://ws.zones.apache.org/~dims/maven/org.apache.axis2/jars/Now, I get this error:java.lang.NoClassDefFoundError: org/apache/rampart/RampartExceptionat java.lang.Class.getDeclaredConstructors0(Native Method)
atjava.lang.Class.privateGetDeclaredConstructors(Class.java:2328)at java.lang.Class.getConstructor0(Class.java:2640)at java.lang.Class.getConstructor(Class.java:1629)at
org.apache.sandesha2.util.SandeshaUtil.getSecurityManagerInstance(SandeshaUtil.java:986)atorg.apache.sandesha2.util.SandeshaUtil.getSecurityManager(SandeshaUtil.java:970)atorg.apache.sandesha2.SandeshaModule.init
(SandeshaModule.java:102)-Original Message-From: Yadav, Yogendra (IT)Sent: Wednesday, October 18, 2006 4:57 PMTo: axis-user@ws.apache.org; Thilina Gunarathne
Subject: RE: sandesh2 v1.0 module load throws NoSuchMethodErrorHi Thilina,As you said, I am using the snapshot, now I am getting this error:java.lang.NoClassDefFoundError: org/apache/rahas/TokenStorage
at java.lang.Class.getDeclaredConstructors0(Native Method)atjava.lang.Class.privateGetDeclaredConstructors(Class.java:2328)at java.lang.Class.getConstructor0(Class.java:2640)at 
java.lang.Class.getConstructor(Class.java:1629)atorg.apache.sandesha2.util.SandeshaUtil.getSecurityManagerInstance(SandeshaUtil.java:986)atorg.apache.sandesha2.util.SandeshaUtil.getSecurityManager
(SandeshaUtil.java:970)atorg.apache.sandesha2.SandeshaModule.init(SandeshaModule.java:102)-Original Message-From: Thilina Gunarathne [mailto:
[EMAIL PROTECTED]]Sent: Friday, October 13, 2006 10:07 AMTo: axis-user@ws.apache.orgSubject: Re: sandesh2 v1.0 module load throws NoSuchMethodErrorPlease use the snapshots available at
http://ws.zones.apache.org/~dims/maven/sandesha2/~ThilinaOn 10/13/06, Yadav, Yogendra (IT) <
[EMAIL PROTECTED]>wrote: I am testing Sandesh2 v1.0 with AXIS2 RC1. The> org.apache.axis2.description.PolicyInclude.getEffectivePolicy()> returns org.apache.neethi.Policy
 whereas sandesh2 expects> org.apache.ws.policy.Policy>> java.lang.NoSuchMethodError:> org.apache.axis2.description.PolicyInclude.getEffectivePolicy()Lorg/ap> ache/ws/policy/Policy;>  at
> org.apache.sandesha2.util.PropertyManager.loadPropertiesFromModuleDesc> Policy(PropertyManager.java:158)>  at> org.apache.sandesha2.SandeshaModule.init(SandeshaModule.java:50)>  at
> org.apache.axis2.context.ConfigurationContextFactory.initModules(Confi> gurationContextFactory.java:217)>  at> org.apache.axis2.context.ConfigurationContextFactory.init(Configuratio> nContextFactory.java
:193)>  at> org.apache.axis2.context.ConfigurationContextFactory.createConfigurati> onContext(ConfigurationContextFactory.java:70)>  at> org.apache.axis2.context.ConfigurationContextFactory.createConfigurati

Re: [axis2] WS-eventing Savan module

[Chamikara Jayalath]

Hi Tijs,

I did some updates to the Savan sample. It is working correctly now. Could u take a new chackout and try again. 

Chamikara

On 8/4/06, 

[EMAIL PROTECTED] <[EMAIL PROTECTED]
> wrote:
Hi there,I am exploring the Savan module that is available in the Axis2 subversion repository.
When I am deploying the samples, the publisher and listener services on Tomcat and run the client sampleI get the publisher to work. When I choose to subscribe listener 1, I see the in the console of Tomcatthe message that the publisher publishes its messages.
But listener 1 does not receive this published message. I don't see the message in the console.Am I doing something wrong here? Does anybody get this to work?Thanks,Tijs-
To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: [Axis2] Sandesha2 and Rampart module

[Chamikara Jayalath]

On 8/4/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
On 8/3/06, L YSSELSTEIN <[EMAIL PROTECTED]> wrote:> Hi Ruchith,>> I looked at the website and understand how to fetch the username from the message context.
> I'm afraid the problem doesn't change however.>>
Because when the message receiver method is reached the security
handler is not processed. Sandesha has called the handler in the create
sequence call, so won't call the security handler when it resumes
application messages of a RM sequence. In other words there is no user
information in the message context.Hmm... IMHO we should use the original msgCtx when resuming theaplication message. Chamikara, what do you think?

Yes.  It is  the original Message Context that is used when resuming. No information saved there can get lost.

Chamikara
 
Thanks,Ruchith--www.ruchith.org
-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: [Axis2] Sandesha2 and Rampart module

[Chamikara Jayalath]

HI Lennard,

yes,this is a performance hit. I'm doing some performance improvements
to Sandesha2. Will be converting the Invoker and Sender into thread
pools.
Thanks for the comments.

Chamikara
On 8/3/06, L YSSELSTEIN <[EMAIL PROTECTED]> wrote:
Hi Chamikara,Ok. I understand.As a last question.I
was looking through the InOrderInvoker code and saw a loop with a sleep
time of 1 second for each loop. Won't this break performance?Also, are all sequences of messages processed by this one thread?Thanks,Lennard.- Original Message -From: Chamikara Jayalath <
[EMAIL PROTECTED]>Date: Thursday, August 3, 2006 2:16 pmSubject: Re: [Axis2] Sandesha2 and Rampart module> Hi Lennard,>> Please see my comments below,
>>> On 8/3/06, L YSSELSTEIN <[EMAIL PROTECTED]> wrote:> >> > Hi Chamikara,> >> > Basically, what we are trying to do is this. When the first
> invocation> passes the security handler, the handler checks the> user credentials.> > If the username/password is valid, the userprofile is retrieved> from Ldap> > and stored in a context for future reference.
> >> > From the security handler we cannot store it in the message> context. The> > callback interface does not give a handle to the message context.> >> > This leaves us with the following questions.
> > How can we store the userprofile in the current messagecontext?>>>> I guess ruchith will answer this.>>> Also, why does sandesha skip the security phase when resuming a
> message in> > the InOrderInvoker?>>>> Sandesha does not skip any phases. It simply does not repeatedly> send it> through the same Phase.>> If you consider the Application Message when Sandesha2 is not
> engaged it> will go through following set of phases.>> Transport> Security> PreDispatch> Dispatch> RMPhase> OperationOutPhase> RMPhase> OperationInPhase
>>> When RM is present it will go through the usual set of Phases but> sinceInOrder invocation is enabled message will be paused at the> RMPhase. So it> will go through following phases in the first go.
>> Transport> Security> PreDispatch> Dispatch> RMPhase>>> Later Sandesha InOrderInvoker thread will resume the message. (this> guarantees that the messages are invoked in the order of RM Message
> Numbers). So the message will go through the rest of the Phases.>> RMPhase> OperationInPhase>>> Thanks,> >> > Lennard.> >> > - Original Message -
> > From: Chamikara Jayalath <[EMAIL PROTECTED]>> > Date: Thursday, August 3, 2006 11:31 am> > Subject: Re: [Axis2] Sandesha2 and Rampart module
> >> > > Hi Lennard,> > >> > > I'm not fully getting it. What do u mean by a Security Context.> To my> > > knwoedge security handler saves all the information to the message
> > > context.> > > The storage framework should not loose any information when> saving and> > > retrieving information. In the in-memory implementation Message> > > Context is
> > > simply stored in a HashMap and properties and all other> information> > shouldbe there when the message is resumed.> > >> > > R u saying that some of these properties are lost when the
> message is> > > resumed by the Sandesha2 InOrderInvoker ?> > >> > > Chamikara> > >> > >> > > On 8/3/06, L YSSELSTEIN <
[EMAIL PROTECTED]> wrote:> > > >> > > > Hi Chamikara,> > > >> > > > Ok, I understand.> > > > During debugging I can see the first invocation to be passed
> > > through the> > > > security phase.> > > > The problem is that during the security phase the security> > > handler is> > > > adding user information to a acegi security context.
> > > > This context only exists during each invocation.> > > > Because during the second invocation this security handler is> not> > called,> no user information is available. Because of this
> the soap> > > call cannot be> > > > processed correctly.> > > > Can we add the user information to the storage framework of> > > sandesha2?>> > > > Thanks,
> > > >> > > > Lennard.> > > >> > > > - Original Message -> > > > From: Chamikara Jayalath <
[EMAIL PROTECTED]>> > > > Date: Thursday, August 3, 2006 5:30 am> > > > Subject: Re: [Axis2] Sandesha2 and Rampart module> > > >> > > > > Hi Lennard,
> > > > >> > 

Re: [Axis2] Sandesha2 and Rampart module

[Chamikara Jayalath]

Hi Lennard,

Please see my comments below,
On 8/3/06, L YSSELSTEIN <[EMAIL PROTECTED]> wrote:
Hi Chamikara,Basically,
what we are trying to do is this. When the first invocation passes the
security handler, the handler checks the user credentials.If the username/password is valid, the userprofile is retrieved from Ldap and stored in a context for future reference.From
the security handler we cannot store it in the message context. The
callback interface does not give a handle to the message context.This leaves us with the following questions.How can we store the userprofile in the current messagecontext?

 I guess ruchith will answer this.

Also, why does sandesha skip the security phase when resuming a message in the InOrderInvoker?


Sandesha does not skip any phases. It simply does not repeatedly send it through the same Phase.


If you consider the Application Message when Sandesha2 is not engaged it will go through following set of phases.



Transport

Security

PreDispatch

Dispatch

RMPhase

OperationOutPhase

RMPhase

OperationInPhase





When RM is present it will go through the usual set of Phases but since
InOrder invocation is enabled message will be paused at the RMPhase. So
it will go through following phases in the first go.



Transport

Security

PreDispatch

Dispatch

RMPhase





Later Sandesha InOrderInvoker thread will resume the message. (this
guarantees that the messages are invoked in the order of RM Message
Numbers). So the message will go through the rest of the Phases.



RMPhase

OperationInPhase


Thanks,Lennard.- Original Message -From: Chamikara Jayalath <
[EMAIL PROTECTED]>Date: Thursday, August 3, 2006 11:31 amSubject: Re: [Axis2] Sandesha2 and Rampart module> Hi Lennard,>> I'm not fully getting it. What do u mean by a Security Context. To my
> knwoedge security handler saves all the information to the message> context.> The storage framework should not loose any information when saving and> retrieving information. In the in-memory implementation Message
> Context is> simply stored in a HashMap and properties and all other information> shouldbe there when the message is resumed.>> R u saying that some of these properties are lost when the message is
> resumed by the Sandesha2 InOrderInvoker ?>> Chamikara>>> On 8/3/06, L YSSELSTEIN <[EMAIL PROTECTED]> wrote:
> >> > Hi Chamikara,> >> > Ok, I understand.> > During debugging I can see the first invocation to be passed> through the> > security phase.> > The problem is that during the security phase the security
> handler is> > adding user information to a acegi security context.> > This context only exists during each invocation.> > Because during the second invocation this security handler is not
> called,> no user information is available. Because of this the soap> call cannot be> > processed correctly.> > Can we add the user information to the storage framework of> sandesha2?>
> > Thanks,> >> > Lennard.> >> > - Original Message -> > From: Chamikara Jayalath <[EMAIL PROTECTED]>
> > Date: Thursday, August 3, 2006 5:30 am> > Subject: Re: [Axis2] Sandesha2 and Rampart module> >> > > Hi Lennard,> > >> > > There is no way a message could reach the RM Phase without going
> > > trough the> > > global phases (this include Transport, Security, Dispatch phases).> > > If you> > > have enable In-Order invocation in Sandesha2 (which is the> > > default), it has
> > > following behaviour.> > >> > > Every incoming application will be paused at the RMPhase. So in> the> > firstinvocation the messages will go through the Global> Phases and the
> > > Application Phases upto the RM Phase. Later Sandesha2 will invoke> > > application message in the order of Message Numbers. So if you are> > > monitorning in the second invocation you will only see a set of
> > > Applicationlevel Phases. But this message must have gone through> > > the Security Phase in> > > its first invocation. Therefore this does not produce a> security hole.
> > >> > > Chamikara> > >> > >> > >> > > On 8/2/06, Lennard IJsselstein <[EMAIL PROTECTED]
>> wrote:> > >> > > > Hi Ruchith,> > > >> > > > I also expected the phases you mentioned. But when I check the> > > > executionChain in the messagecontext while debugging I only
> see the> > > > phases I mentioned before. For some reason sandesha2 alters the> > > phases> of the messages during invocation.> > > >> > > > Before sandesha2 was added t

Re: [Axis2] Sandesha2 and Rampart module

[Chamikara Jayalath]

Hi Lennard,

I'm not fully getting it. What do u mean by a Security Context. To my
knwoedge security handler saves all the information to the message
context.

The storage framework should not loose any information when saving and
retrieving information. In the in-memory implementation Message Context
is simply stored in a HashMap and properties and all other information
should be there when the message is resumed.

R u saying that some of these properties are lost when the message is resumed by the Sandesha2 InOrderInvoker ?

Chamikara
On 8/3/06, L YSSELSTEIN <[EMAIL PROTECTED]> wrote:
Hi Chamikara,Ok, I understand.During debugging I can see the first invocation to be passed through the security phase.The problem is that during the security phase the security handler is adding user information to a acegi security context.
This context only exists during each invocation.Because
during the second invocation this security handler is not called, no
user information is available. Because of this the soap call cannot be
processed correctly.Can we add the user information to the storage framework of sandesha2?Thanks,Lennard.- Original Message -From: Chamikara Jayalath <
[EMAIL PROTECTED]>Date: Thursday, August 3, 2006 5:30 amSubject: Re: [Axis2] Sandesha2 and Rampart module> Hi Lennard,>> There is no way a message could reach the RM Phase without going
> trough the> global phases (this include Transport, Security, Dispatch phases).> If you> have enable In-Order invocation in Sandesha2 (which is the> default), it has> following behaviour.
>> Every incoming application will be paused at the RMPhase. So in the> firstinvocation the messages will go through the Global Phases and the> Application Phases upto the RM Phase. Later Sandesha2 will invoke
> application message in the order of Message Numbers. So if you are> monitorning in the second invocation you will only see a set of> Applicationlevel Phases. But this message must have gone through
> the Security Phase in> its first invocation. Therefore this does not produce a security hole.>> Chamikara>>>> On 8/2/06, Lennard IJsselstein <
[EMAIL PROTECTED]> wrote:> >> > Hi Ruchith,> >> > I also expected the phases you mentioned. But when I check the> > executionChain in the messagecontext while debugging I only see the
> > phases I mentioned before. For some reason sandesha2 alters the> phases> of the messages during invocation.> >> > Before sandesha2 was added the execution chain was as you described.
> >> > Thanks,> >> > Lennard.> > ||> > Ruchith Fernando wrote:> >> > > Hi Lennard,> > >> > > On 8/2/06, Lennard IJsselstein <
[EMAIL PROTECTED]>> wrote:> >> > >> Hi all,> > >>> > >> We are currently using both the Sandesha2 and the Rampart module.
> > >> The problem we are facing now is when we send a webservice> call the> > >> following happens:> > >> - The CreateSequence soapmessage is send to the Axis2 servlet
> and is> > >> correctly processed.> > >> As expected the following axis2 phases are hit:> > >>Transport, Security, RMPhase OperationInPhase> > >> - The soapmessage with the actual webservice call is send to
> the Axis2> > >> servlet.> > >> The following phases are hit:> > >>soapmonitorPhase, RMPhase, OperationInPhase.> > >> - The TerminateSequence soapmessage is send to the Axis2
> servlet and is> > >> correctly processed.> > >> As expected the following axis2 phases are hit:> > >>Transport, Security, RMPhase, OperationInPhase> > >>
> > >> Our question is:> > >> Why does the 'normal' soapmessage not run through the> Security> >> phase?> > >> > >> > > IMHO the request message should go through the following phases :
> > > Transport, Security, PreDispatch, Dispatch, OperationInPhase> > >> > > Transport and Dispatch phases are used to dispatch and since> you have> > > not mentioned any of these in the phases that the soap message
> hit I> > > wonder how the request reached the OperationInPhase.> > >> > > Thanks,> > > Ruchith> > >> >> > --
> ---> > 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]

Re: [Axis2] Sandesha2 and Rampart module

[Chamikara Jayalath]

Hi Lennard,

There is no way a message could reach the RM Phase without going trough
the global phases (this include Transport, Security, Dispatch phases).
If you have enable In-Order invocation in Sandesha2 (which is the
default), it has following behaviour.

Every incoming application will be paused at the RMPhase. So in the
first invocation the messages will go through the Global Phases and the
Application Phases upto the RM Phase. Later Sandesha2 will invoke
application message in the order of Message Numbers. So if you are
monitorning in the second invocation you will only see a set of
Application level Phases. But this message must have gone through the
Security Phase in its first invocation. Therefore this does not produce
a security hole.

Chamikara

On 8/2/06, Lennard IJsselstein <[EMAIL PROTECTED]> wrote:
Hi Ruchith,I also expected the phases you mentioned. But when I check theexecutionChain in the messagecontext while debugging I only see thephases I mentioned before. For some reason sandesha2 alters the phases
of the messages during invocation.Before sandesha2 was added the execution chain was as you described.Thanks,Lennard.||Ruchith Fernando wrote:> Hi Lennard,>> On 8/2/06, Lennard IJsselstein <
[EMAIL PROTECTED]> wrote:>>> Hi all, We are currently using both the Sandesha2 and the Rampart module.>> The problem we are facing now is when we send a webservice call the
>> following happens:>> - The CreateSequence soapmessage is send to the Axis2 servlet and is>> correctly processed.>> As expected the following axis2 phases are hit:>>Transport, Security, RMPhase OperationInPhase
>> - The soapmessage with the actual webservice call is send to the Axis2>> servlet.>> The following phases are hit:>>soapmonitorPhase, RMPhase, OperationInPhase.>> - The TerminateSequence soapmessage is send to the Axis2 servlet and is
>> correctly processed.>> As expected the following axis2 phases are hit:>>Transport, Security, RMPhase, OperationInPhase Our question is:>> Why does the 'normal' soapmessage not run through the Security
>> phase?>>> IMHO the request message should go through the following phases :> Transport, Security, PreDispatch, Dispatch, OperationInPhase>> Transport and Dispatch phases are used to dispatch and since you have
> not mentioned any of these in the phases that the soap message hit I> wonder how the request reached the OperationInPhase.>> Thanks,> Ruchith>-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: [MTOM/XOP+WSRM] servlet error

[Chamikara Jayalath]

.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:693)atorg.apache.catalina.startup.HostConfig.deployApps
(HostConfig.java:472)atorg.apache.catalina.startup.HostConfig.start(HostConfig.java:1118)atorg.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)atorg.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
(LifecycleSupport.java:119)atorg.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020)atorg.apache.catalina.core.StandardHost.start(StandardHost.java:718)atorg.apache.catalina.core.ContainerBase.start
(ContainerBase.java:1012)atorg.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)atorg.apache.catalina.core.StandardService.start(StandardService.java:450)at
org.apache.catalina.core.StandardServer.start(StandardServer.java:700)at org.apache.catalina.startup.Catalina.start(Catalina.java:551)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)at java.lang.reflect.Method.invoke
(Method.java:585)at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)Caused by: java.util.MissingResourceException
: Cannot find resource'org.apache.sandesha2.i18n.resource'atorg.apache.axis2.i18n.ProjectResourceBundle.getBundle(ProjectResourceBundle.java:259)atorg.apache.sandesha2.i18n.SandeshaMessageHelper
.(SandeshaMessageHelper.java:19)... 32 moreAnd when I check out the project and I create my mar and jar, I have thesame error. The module seems to not be initiate. I search to resolve the
problem but I don't find the solution. I join you the cataliana log,there are errors on listeners classes (ContextListener andSessionListener) but I think it's not the same problem and it don't haveconsequences on my problem.
Thanks for your time.RegardsElodieChamikara Jayalath wrote:> Hi Elodie,>> Please see my comments below.>> On 7/19/06, *Mancinelli Elodie* <
[EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote:>> Hi Chamikara,>> Your solution is correct.  Can you explain me what is this
> property and> why it allows to pass the bug?>>>> In WSRM the messages that belong to a sequence are numbered starting> from one. If this InvokeInOrder property is set to true, Sandesha2
> will make sure that the messages get invoked in the order of these> message numbers. This is a delivery assurance provided by Sadesha2> which is not a must to comply with the WSRM specification. So you can
> safely set it to false if you do not worry abt ardering. Infact> disabling this will improve the performance.>> In implementation wise, we achieve ordering using a seperate thread.> If InvokeInORder is set to true, messages will be paused at the RM
> handlers and invocation will be done in the order of message numbers> using our thread. When a message get paused the current thread get> returned and the incoming sockets with the client get closed.
>> The bug is with axis2 not reading the attachments from the stream> before this closing of the socket.>> Change this property, make other mistake:> The problem is when I implement method addressable ( 
i.e. I define the> ReplyTo and AcksTo value for WSRM implementation). I have also the> same> problem in MTOMRM implementation.> These values change with this code:> String acksTo =
> serviceClient.getMyEPR(Constants.TRANSPORT_HTTP ).getAddress();> options.setProperty(SandeshaClientConstants.AcksTo,acksTo);> and> options.setUseSeparateListener(true);> In this case, for a RequestResponse method I see only the
> CreateSequence> and the first message, others messages never sent. The client never> receive the server response and the  server method is never called.>> For OneWay method, in TCPMon, there are all soap messages, but no
> server> reactions. The  server method is never called.>> Have you an idea?>>>> I guess this is the bug i fixed yested day. Please try the latest> SNAPSHOT from
> http://people.apache.org/repository/sandesha2/mars/>>> Chamikara>>> Thanks for your help.>
> Regards,>> Elodie>> Chamikara Jayalath wrote:>> > Hi Elodie,> >> > I just fixed a bug in Sandesha2 not-in-order case is working
> properly now.> >> > Currently MTOM+RM will not work when InOrderInvocation property> is set> > to true. This is due to a bug in OM  (>

Re: [MTOM/XOP+WSRM] servlet error

[Chamikara Jayalath]

Hi Elodie,

I just fixed a bug in Sandesha2 not-in-order case is working properly now.

Currently MTOM+RM will not work when InOrderInvocation property is set
to true. This is due to a bug in OM  (
https://issues.apache.org/jira/browse/WSCOMMONS-52 ).

But it perfectly works when InOrderInvocation is set to false. I just
added a test case to sandesha2 to demonstrate this (MTOMRMTest).
Currentlly the code in the test method is commented till the previous
bug is fixed. But it passes when InOrderInvation is disabled. 

Hope this will help you.

Chamikara

On 7/17/06, Mancinelli Elodie <[EMAIL PROTECTED]> wrote:
Hi,Can you think the problem is due to the tomcat version? Or the sandesha2version? I download jars and war onhttp://people.apache.org/repository/sandesha2/
.To configure the server,I have only change the axis2.xml. I can't changethe module.xml because I intente to create a common server for allindependante client (WSRM only, MTOM only, MTOM-WSRM).
Sorry to insit.RegardsElodieMancinelli Elodie wrote:> Hi Chamikara,>> I use tomcat in the server side and its version is the> apache-tomcat-5.5.15.> I join in attachment my client code.
>> Thanks for your help.>> Regards>> Elodie>>>> Chamikara Jayalath wrote:>>> Hi Elodie,>>>> Are you using tomcat in the server side. If so which version?
>> Can u send your client code as well.>>>> Chamikara>>>>>> On 7/13/06, *Mancinelli Elodie* <[EMAIL PROTECTED]
>> [EMAIL PROTECTED]>> wrote:>>>> Hi all,>>>> I want to realise an client-server which supports MTOM and WSRM. I
>> created separatly a client-server with MTOM and a client-server>> with WSRM.>>>> My server has two methods: OneWay and RequestResponse.>>>> - When I launch my client to test the RequestResponse method:
>> In TCPMon, I see, the CreateSequence and the>> CreateSequenceResponse. My>> first message is sent and it is accpeted.>> But my client never receives the response and there is no trace
>> on my>> server, the method seems not be executed.>>>> - When I launch my client to test the OneWay method:>> In TCPMon, I see:>> - CreateSequence, CreateSequenceResponse
>> - Three messages have send and three acknowledgments>> But no TerminateSequence.>> And on the server, there is an error:>> - "Servlet.service()" pour la servlet AxisServlet a généré une
>> exception>> java.lang.IllegalStateException: Impossible de créer une>> sessionaprès>> que la réponse ait été envoyée>> at>>>> 
org.apache.catalina.connector.Request.doGetSession(Request.java:2214)>> at>> org.apache.catalina.connector.Request.getSession(Request.java:2024)>> at>>
>> org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:831)>>>> at>> >>
>>package fr.gouv.finances.dgme.presto;>>import java.io.File;>import java.io.FileInputStream;>import javax.activation.DataHandler;>import javax.activation.FileDataSource;
>import javax.xml.stream.XMLInputFactory;>import javax.xml.stream.XMLStreamReader;>import org.apache.axiom.om.OMAbstractFactory;>import org.apache.axiom.om.OMElement;>import org.apache.axiom.om.OMFactory
;>import org.apache.axiom.om.OMNamespace;>import org.apache.axiom.om.OMText;>import org.apache.axiom.om.impl.builder.StAXOMBuilder;>import org.apache.axiom.soap.SOAP12Constants;>import org.apache.axis2.Constants
;>import org.apache.axis2.addressing.EndpointReference;>import org.apache.axis2.client.Options;>import org.apache.axis2.client.ServiceClient;>import org.apache.axis2.client.async.AsyncResult;
>import org.apache.axis2.client.async.Callback;>import org.apache.axis2.context.ConfigurationContext;>import org.apache.axis2.context.ConfigurationContextFactory;>import org.apache.axis2.context.MessageContextConstants
;>import org.apache.sandesha2.client.SandeshaClientConstants;>>>public class PrestoWSRM_MTOMtest extends junit.framework.TestCase{>>   static String fileXMLName="test_data_in.xml";
>   static String fileNameAttach="fichier.txt";>  
private static EndpointReference targetEPR = new
EndpointReference("http://localhost:8080/axis2/services/PrestoSvc");>   private static String targetEPRTcpmon ="
http://localhost:8070/axis2/services/PrestoSvc";>   static String namespace="http://dgme.finances.gouv.fr/presto";>   private static String CLIENT_REPO_PATH = &qu

Re: [Axis2] Reliable Notification

[Chamikara Jayalath]

Hi Eric,

Please see my comments below.On 7/12/06, Eric Winter <[EMAIL PROTECTED]> wrote:
Reliable NotificationI have a pretty simple problem I'd like to solve, but the tool I thinkI should use is not being cooperative.I have a client that has to deliver a message to at least one server
within a reasonable time.Based on that requirement I though I should use MEP InOnly andSandesha2 (Reliable Messaging).  The problem is that I need to knowthat the message arrived and I can't seem to get that using Sandesha
and the InOnly pattern. All I really want from the service is an ACKthat I can pick up somehow at the client.  Clearly this is part andparcel of what Sandesha does... I just want to know about it.


Acknowledgements are handled  inside Sandesha2 and they are not
delivered to the client.  Sandesha2 will retransmit messages
until  a ack is received or till the message sequence times out.
A couple of thoughts came up:1. Manually check via the SequenceReport. (never see anything in the
Outgoing Sequence Report)
After you your messages get successfully delivered the the server and
after the Sandesha2 client receive acknowledgements you should hv those
message numbers in the outgoing sequence report. Dont you see these
values? What are the velues of the other properties of the Sequence
Report (for e.g. Sequece Status).
 2. Use a SandeshaListener (callbacks for onError and onTimeout).  Itried running client w/ server down. No luck.


This will not help ur scenario. You can only use this to know when your sequence times out.
 3. SandeshaClient.waitUntilSequenceCompleted works but who wants toblock?  And if it does time out I still want to be notified.


yes. This will only help if blocking is ok.

None of these fullfill the basic requirement: within a reasonableabout of time, I want to know, at the client, that the message has
been received at the service.FYI I am using the Sandesha2 UserguideEchoClient client - the code w/ myadditions are here.clientOptions.setTo(new EndpointReference (toEPR));ServiceClient serviceClient = new ServiceClient
(configContext,null);clientOptions.setAction("urn:wsrm:Ping");serviceClient.setOptions(clientOptions); clientOptions.setProperty(SandeshaClientConstants.SANDESHA_LISTENER,
new SandeshaListener_Impl());//newclientOptions.setTimeOutInMilliSeconds(1);//trying to cause itto timeout, but it doesn't.serviceClient.fireAndForget(getPingOMBlock("ping1"));
serviceClient.fireAndForget(getPingOMBlock("ping2"));clientOptions.setProperty(SandeshaClientConstants.LAST_MESSAGE,"true");serviceClient.fireAndForget(getPingOMBlock("ping3"));
 SandeshaClient.waitUntilSequenceCompleted(serviceClient,1000*50);//newserviceClient.finalizeInvoke();


My sugestion for you for now is to use the sequence report. May be from
a seperate thread. But a better way will be to have a method in the
SandeshaClient to notify the client when a specific message get
successfully delivered. I'll mark this as a improvement :-)

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

Re: [MTOM/XOP+WSRM] servlet error

[Chamikara Jayalath]

Hi Elodie,

Are you using tomcat in the server side. If so which version?
Can u send your client code as well.

Chamikara
On 7/13/06, Mancinelli Elodie <[EMAIL PROTECTED]> wrote:
Hi all,I want to realise an client-server which supports MTOM and WSRM. Icreated separatly a client-server with MTOM and a client-server with WSRM.My server has two methods: OneWay and RequestResponse.
- When I launch my client to test the RequestResponse method:In TCPMon, I see, the CreateSequence and the CreateSequenceResponse. Myfirst message is sent and it is accpeted.But my client never receives the response and there is no trace on my
server, the method seems not be executed.- When I launch my client to test the OneWay method:In TCPMon, I see:- CreateSequence, CreateSequenceResponse- Three messages have send and three acknowledgments
But no TerminateSequence.And on the server, there is an error:- "Servlet.service()" pour la servlet AxisServlet a généré une exceptionjava.lang.IllegalStateException: Impossible de créer une sessionaprès
que la réponse ait été envoyéeatorg.apache.catalina.connector.Request.doGetSession(Request.java:2214)atorg.apache.catalina.connector.Request.getSession(Request.java:2024)at
org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:831)atorg.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:842)atorg.apache.axis2.transport.http.AxisServlet.createAndSetInitialParamsToMsgCtxt
(AxisServlet.java:81)atorg.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131)at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)at javax.servlet.http.HttpServlet.service
(HttpServlet.java:802)atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java
:173)atorg.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)atorg.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)atorg.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)atorg.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:107)atorg.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)atorg.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)atorg.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
atorg.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)atorg.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)at 
java.lang.Thread.run(Thread.java:595)I have no informations in catalina logs.In precedent mails, somebody advise me to change the value ofInOrderInvoker in the module.xml, but when I change this, client-server
with MTOM only and client-server with WSRM only don't works.I have download the sandesha2-SNAPSHOT.mar(http://people.apache.org/repository/sandesha2/mars/
)Someone have an idea?Thanks a lotElodie-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] Fwd: i18n (NLS) msgs in sandesha2

[Chamikara Jayalath]

added the prefix.-- Forwarded message --From: Chamikara Jayalath <[EMAIL PROTECTED]>
Date: Jul 11, 2006 11:55 AMSubject: Re: i18n (NLS) msgs in sandesha2To: sandesha-dev@ws.apache.orgCc: axis-dev@ws.apache.org
Hi Thomas,

Could you please create an JIRA issue on providing i18n support in Sandesha2. 

Yes. what u mention is correct. The problem is axis2 having some hardcoded values in Message and MessageConstant classes.

It seems like we can do a small modification to Axis2 and make it
provide support for i18n extensions. The approach that came to my mind
is maintaining a HashMap of MessageBundles in the message class
(instaead of one). So Sandesha2 can add its own messageBundle to this
map. Whan retrieving values we can ask the message class to retrieve
the values from this Bundle instead of the default one. I'll try to do
this modification to Axis2.

I'm CCing this to axis-dev so that they can comment on this approach.

Chamikara

On 7/10/06, Thomas McKiernan <[EMAIL PROTECTED]
> wrote:

Hi guys,
I'm just looking into the i18n issues of Sandesha2.
I see Axis2 already has code to loads its 'resource.properties' msg file

and do lookups etc.

It strikes me that the code that we need is virtually identical - just

different values for projectName etc. However, it does not look like there

is any capacity at the moment for using this code with projects outside
of 
Axis2 - do any of you guys have an opinion on this?

Many thanks,
Thomas
--
Thomas McKiernan

WebSphere Messaging Development,
IBM United Kingdom Limited

Internal Phone: 248241 
External Phone: +44 (0)1962 818241
Mobile: +44 (0)789 1737497
Email: [EMAIL PROTECTED]

Mail Point 211, IBM, Hursley Park, Winchester, Hampshire, England, SO21
2JN


Caminante, no hay camino 
Se hace camino al andar.
("Walker, there is no path; the path is made by walking.")  Antonio
Machado

Re: [Axis2,Sandesha2]MTOM/XOP + WSRM

[Chamikara Jayalath]

atcher.java:465)> >> >at> > org.apache.catalina.core.ApplicationDispatcher.doForward> (ApplicationDispatcher.java:398)> >> >at
> >> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)> >> >at> > org.apache.catalina.core.StandardHostValve.custom
> (StandardHostValve.java:363)> >> >at> >> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284)> >> >at
> > org.apache.catalina.core.StandardHostValve.throwable> (StandardHostValve.java:228)> >> >at> >> org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:134)> >> >at> > org.apache.catalina.valves.ErrorReportValve.invoke> (ErrorReportValve.java:105)> >> >at
> >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)> >> >at> > org.apache.catalina.connector.CoyoteAdapter.service
> (CoyoteAdapter.java:148)> >> >at> >> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)> >> >at
> >> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection> (Http11BaseProtocol.java:667)> >> >at> >
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)> >> >at> > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt> (
LeaderFollowerWorkerThread.java:80)> >> >at> >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)> >> >at 
java.lang.Thread.run(Thread.java:595)> >> > I search in the mailling list,and I don't find if there is a> solution> > but I find a JIRA> bug(
http://issues.apache.org/jira/browse/AXIS2-707).> >> > Have you an idea?> >> > Elodie> >> >> >> >> > Chamikara Jayalath wrote:
> >> >> Hi Elodie, Paul,> >>> >> It seems like MTOM + Sandesha2 + NotInOrder case is working.> >> But MTOM + Sadesha2 + InOrder case is not working.
> >>> >> When InOrder Invocation is enabled Sandesha2 always pauses the> >> message before its actual invocation and Axis2 closes the> InPutStream> >> when the message get paused and the thread get returned.
> >>> >> Because of that the service Impl. get exceptions when tring to read> >> the MTOM attachments from the already closed stream. This seems> to be> >> a general problem with message pausing.
> >>> >> So Elodie, for now disable InOrder invocation in Sandesha2. To do> >> that change the 'InvokeInOrder' policy in the module.xml to> 'false'> >> (this is 'true' by default).
> >>> >> Chamikara> >>> >>>

Re: [Axis2,Sandesha2]MTOM/XOP + WSRM

[Chamikara Jayalath]

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 StackTrace:java.lang.NullPointerExceptionorg.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor.setUpHighestMsgNumbers(TerminateSeqMsgProcessor.java:185)org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor.processInMessage
(TerminateSeqMsgProcessor.java:128)org.apache.sandesha2.handlers.SandeshaInHandler.invoke(SandeshaInHandler.java:87)org.apache.axis2.engine.Phase.invoke(Phase.java:381)org.apache.axis2.engine.AxisEngine.invoke
(AxisEngine.java:473)org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:445)org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)org.apache.axis2.transport.http.AxisServlet.doPost
(AxisServlet.java:136)javax.servlet.http.HttpServlet.service(HttpServlet.java:709)javax.servlet.http.HttpServlet.service(HttpServlet.java:802)  This error appear in the response at the TerminateSequence.
ElodieMancinelli Elodie wrote:> 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 ErrorPage[errorCode=500,
> location=/axis2-web/Error/error500.jsp]> org.apache.jasper.JasperException: "getOutputStream()" a déjà été> appelé pour cette réponse>at> org.apache.jasper.servlet.JspServletWrapper.handleJspException
(JspServletWrapper.java:510)>>at> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)>>at> org.apache.jasper.servlet.JspServlet.serviceJspFile
(JspServlet.java:314)>at> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)>at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)>at> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:252)>>at> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)>>at> org.apache.catalina.core.ApplicationDispatcher.invoke
(ApplicationDispatcher.java:672)>>at> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465)>>at> org.apache.catalina.core.ApplicationDispatcher.doForward
(ApplicationDispatcher.java:398)>>at> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)>>at> org.apache.catalina.core.StandardHostValve.custom
(StandardHostValve.java:363)>>at> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284)>>at> org.apache.catalina.core.StandardHostValve.throwable
(StandardHostValve.java:228)>>at> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134)>>at> org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:105)>>at> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)>>at> org.apache.catalina.connector.CoyoteAdapter.service
(CoyoteAdapter.java:148)>>at> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)>>at> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection
(Http11BaseProtocol.java:667)>>at> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)>>at> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt
(LeaderFollowerWorkerThread.java:80)>>at> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)>>at java.lang.Thread.run(Thread.java:595)
>> I search in the mailling list,and I don't find if there is a solution> but I find a JIRA bug(http://issues.apache.org/jira/browse/AXIS2-707).
>> Have you an idea?>> Elodie>>>>> Chamikara Jayalath wrote:>>> Hi Elodie, Paul,>>>> It seems like MTOM + Sandesha2 + NotInOrder case is working.
>> But MTOM + Sadesha2 + InOrder case is not working.>>>> When InOrder Invocation is enabled Sandesha2 always pauses the>> message before its actual invocation and Axis2 closes the InPutStream
>> when the message get paused and the thread get returned.>>>> Because of that the service Impl. get exceptions when tring to read>> the MTOM attachments from the already closed stream. This seems to be
>> a general problem with message pausing.>>>> So Elodie, for now disable InOrder invocation in Sandesha2. To do>> that change the 'InvokeInOrder' policy in the module.xml to 'false'
>> (this is 'true' by default).>>>> Chamikara>>>

Re: [Axis2,Sandesha2]MTOM/XOP + WSRM

[Chamikara Jayalath]

Hi Elodie, Paul,



It seems like MTOM + Sandesha2 + NotInOrder case is working. 

But MTOM + Sadesha2 + InOrder case is not working.



When InOrder Invocation is enabled Sandesha2 always pauses the message
before its actual invocation and Axis2 closes the InPutStream when the
message get paused and the thread get returned.



Because of that the service Impl. get exceptions when tring to read the
MTOM attachments from the already closed stream. This seems to be a
general problem with message pausing.



So Elodie, for now disable InOrder invocation in Sandesha2. To do that
change the 'InvokeInOrder' policy in the module.xml to 'false' (this is
'true' by default).



Chamikara

On 7/3/06, Paul Fremantle <[EMAIL PROTECTED]
> wrote:
ElodieThis looks more like a Sandesha bug. I will do a test as well and letyou know how it goes.PaulOn 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 with ADB, I don't know because I can't
> generate sources.> I'm trying to do MTOM + WSRM with ADB on a other little exemple like> HelloWorld. I tell you the result when I finish it.>> Thanks>> Elodie>

 Paul Fremantle wrote:>> > Elodie> >> > I'm not completely clear on the situation!> >> > 1) Is the MTOM + XMLBeans code working without WSRM?
> > 2) What is the error you get with ADB?> > 3) Can you post the WSDL?> >> > Paul> >> > On 6/29/06, Mancinelli Elodie <

[EMAIL PROTECTED]> wrote:> >> >> Hi Paul> >>> >> Thanks for your response. I wish have more information because I don' t> >> understand why MTOM can't work with XmlBeans? And what is the
> >> marshalling I have to use?> >> I try ADB but it not seems to work, I can't generate the server> >> implementation.> >>> >> In more, I create a client-server with only MTOM and I also create the
> >> same thing with only WSRM(sandesha2) and  both work separetly with> >> XmlBeans. Is the problem is WSRM + MTOM together? And how could I do to> >> resolve my problem?> >>
> >>> >> Thanks a lot.> >>> >> Regards> >> Elodie> >>> >>> >> Paul Fremantle wrote:> >>> >> > 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, Mancinelli Elodie <
[EMAIL PROTECTED]> wrote:> >> >
> >> >> 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 is
> >> on the> >> >> > server after messages.> >> >> >> >> >> > Thanks,> >> >> >> >> >> > Regards,

> >> >> > Elodie> >> >> >> >> >> >> >> >> > Mancinelli Elodie wrote:> >> >> >> >> >> >> 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:
> >> >> >>> >> >> >> org.apache.sandesha2.SandeshaException: Data binding error; nested> >> >> >> exception is:>
>> >>
>>java.lang.RuntimeException:
Data binding error; nested> >> >> >> exception is:>
>> >>
>>org.apache.axis2.AxisFault:
Data binding error; nested> >> >> >> exception is:> >> >> >>java.lang.RuntimeException: Data binding error> >> >> >>at> >> >> >>
> >> >>> >> org.apache.sandesha2.workers.InOrderInvoker.run(InOrderInvoker.java:199)> >> >> >> Caused by: org.apache.axis2.AxisFault: Data binding error; nested

> >> >> >> exception is:> >> >> >>java.lang.RuntimeException: Data binding error> >> >> >>at org.apache.axis2.AxisFault.makeFault(AxisFault.java

:318)> >> >> >>at> >> >> >>> >> >>> >> fr.gouv.finances.dgme.presto.PrestoSvcMessageReceiverInOnly.invokeBusinessLogic(PrestoSvcMessageReceiverInOnly.java

:50)> >>> >> >>> >> >> >>> >> >> >>at> >> >> >>> >> >>> >> org.apache.axis2.receivers.AbstractInMessageReceiver.receive

(AbstractInMessageReceiver.java:34)> >>> >> >>> >> >> >>> >> >> >>at> >> >> >>> >> org.apache.axis2.engine.AxisEngine.resumeReceive

(AxisEngine.java:497)> >> >> >>at> >> >> org.apache.axis2.engine.AxisEngine.resume(AxisEngine.java:543)> >> >> >>at> >> >> >>
> >> >>> >> org.apache.sandesha2.workers.InOrderInvoker.run(InOrderInvoker.java:189)> >> >> >> Caused by: java.lang.RuntimeException: Data binding error> >> >> >>at
> >> >> >>> >> >>> >> fr.gouv.finances

Re: [Axis2 1.0][Sandesha2] Problem connecting server RMSampleService

[Chamikara Jayalath]

Hi Elodie,

Could u make sure that the Axis2 is setup correctly and that the RMSampleService is available when u list the services.

Also check the tomcat logs to see weather u can get any clues to find out the reason for HTTP 500 response.

Chamikara
On 6/7/06, Mancinelli Elodie <[EMAIL PROTECTED]> wrote:
Hi ChamikaraThanks for your help. You are all rigth.Now, I can access tomcat, but it returns an error: HTTP/1.1 500 InternalError ServletThe server met an internal error which stopped the request. I can't say
more because I do not have more information.The http request caugth in tcpmon is:POST /axis2/services/RMSampleService HTTP/1.1User-Agent: Axis2SOAPAction: 
http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceHost: 127.0.0.1:8070Transfer-Encoding: chunkedContent-Type: text/xml; charset=UTF-8320   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:wsa="
http://www.w3.org/2005/08/addressing">  http://127.0.0.1:8080/axis2/services/RMSampleService
 http://129.183.149.72:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__
 urn:uuid:07B228029E7191235511496802483123
http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence xmlns:wsrm="
http://schemas.xmlsoap.org/ws/2005/02/rm">http://www.w3.org/2005/08/addressing/anonymous
  0Do you have an idea?ElodieChamikara Jayalath wrote:
> Hi Elodie,>> Have you configured the tcp monitor correctly. You should start tomcat> in the port 8080 and have a mapping in tcp monitor from port 8070 to 8080.>> Add the following additional line to the client code to send the
> request through the ctp monitor.>> clientOptions.setProperty(MessageContextConstants.TRANSPORT_URL,"http://localhost:8070/axis2/services/RMSampleService
");>>> Chamikara>

Re: [Axis2] in-out operation question

[Chamikara Jayalath]

Hi Michele,

I'll try to reply all ur mails at once :-)

1. Yes. The RelatesTo is set in the Utils.createOutMessageContext() method.

2. You cannot get the contexts directly to ur service object if u write
ur own MessageReceiver. You have to implement that logic. (may be u can
use the 'getTheImplementationObject' method of the
AbstractMessageReceiver).

3. Yes. What I mean by the second invocation is the B to C invocation.


I believe the easiest way for u will be to use a ServiceClient in ur service code and doing the B to C invocation. 


Chamikara



On 6/7/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
Apologies for flooding with my messages.Chamikara, when you say 'second invocation', do you mean the C side?Thanks,MicheleChamikara Jayalath wrote:> Hi Michele,>> Currently it seems that this does not work if you use the
> RawXMLINOutMessageReceiver. The reason is this message receiver setting> the relatesTo addressing header in the response message. When this> message goes to the Dispatching Phase of the second invocation it will
> fail saying that it cannot correlate the message with a OperationContext> object.>> Seems like you hv to write ur own message receiver similar to> RawXMLINOutMessageReceiver but which does not set the relatesTo
> property. Or do the second invocation using a ServiceClient.>> Chamikara On 6/6/06, *Michele Mazzucco* <[EMAIL PROTECTED]
> [EMAIL PROTECTED]>> wrote:>> Hi all,>> suppose a system with 3 elements, A, B and C where B provides a in-out
> operation.> If A sends a request (fireAndForget of sendRobust) to B, supplying the C> target as well, is it possible for the service to return the result> to C> straight away, that is without creating a ServiceClient object?
>>> // This service is provided by B and it is invoked by A> public OMElement foo(OMElement payload) {> // the message context is set>> // process the payload
>>
// use the replyTo if set by A, otherwise set it by using>
// message properties (or some informations included into the> // payload>> return result;> }>> Does the result reach the node C?>>
> Thanks in advance,> Michele>> -> To unsubscribe, e-mail: 
[EMAIL PROTECTED]> [EMAIL PROTECTED]>> For additional commands, e-mail: 
[EMAIL PROTECTED]> [EMAIL PROTECTED]>>>-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] in-out operation question

[Chamikara Jayalath]

Hi Michele,

Currently it seems that this does not work if you use the
RawXMLINOutMessageReceiver. The reason is this message receiver setting
the relatesTo addressing header in the response message. When this
message goes to the Dispatching Phase of the second invocation it will
fail saying that it cannot correlate the message with a
OperationContext object.

Seems like you hv to write ur own message receiver similar to
RawXMLINOutMessageReceiver but which does not set the relatesTo
property. Or do the second invocation using a ServiceClient.
Chamikara


On 6/6/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
Hi all,suppose a system with 3 elements, A, B and C where B provides a in-outoperation.If A sends a request (fireAndForget of sendRobust) to B, supplying the Ctarget as well, is it possible for the service to return the result to C
straight away, that is without creating a ServiceClient object?// This service is provided by B and it is invoked by Apublic OMElement foo(OMElement payload) {// the message context is set
// process the payload// use the replyTo if set by A, otherwise set it by using// message properties (or some informations included into the// payloadreturn result;
}Does the result reach the node C?Thanks in advance,Michele-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2 1.0][Sandesha2] Problem connecting server RMSampleService

[Chamikara Jayalath]

Please see my response in the sandesha-dev list.

Chamikara
On 6/2/06, Charles Souillard <[EMAIL PROTECTED]> wrote:
Hi all,I am trying to use the same example.I am encoutering the same problem. I have also caught the http requestinside tcpmon.You can find it hereafter :POST /axis2/services/RMSampleService HTTP/1.1
User-Agent: Axis2SOAPAction: http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceHost: localhost:13000Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8320xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
"xmlns:wsa="http://www.w3.org/2005/08/addressing">
http://localhost:13000/axis2/services/RMSampleServicehttp://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__
urn:uuid:F568425CAF0692619511492482122053
http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
http://schemas.xmlsoap.org/ws/2005/02/rm">http://www.w3.org/2005/08/addressing/anonymous
0I have entered the wsa adress into my web browser(
http://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__)and I get the following SOAP message :---
http://www.w3.org/2005/08/addressing/anonymousurn:uuid:46BED3F8855DCCC1B2114924808940114
http://www.w3.org/2005/08/addressing/fault--
soapenv:Clientunknown--java.lang.NullPointerExceptionat org.apache.axis2.util.CallbackReceiver.receive
(CallbackReceiver.java:32)at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)atorg.apache.axis2.transport.http.HTTPTransportUtils.processHTTPGetRequest(HTTPTransportUtils.java:138)atorg.apache.axis2.transport.http.HTTPWorker.processRequest
(HTTPWorker.java:226)atorg.apache.axis2.transport.http.server.SimpleConnectionThread.run(SimpleConnectionThread.java:92)atedu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java
:650)atedu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)at java.lang.Thread.run(Thread.java:595)
Does anybody knows why I am getting a NPE into CallbackReceiver ?I tried to debug axis2 into eclipse but I never reached the breakpoint Iput on the line 32...
Can you help me please ?Thanks a lot for your answers.Regards,CharlesMancinelli Elodie wrote:> Hello>> Tools use: Axis2 1.0, Sandesha2 1.0 and apache-tomcat-5.5.15
> I'm trying to use the User guide example with the client> "UserguideClient.java" in sandesha2 1.0-bin.zip. I use the> RMSampleService.aar given in the Sandesha2-1.0-bin.zip. When I launch> the client, it could never get a connection to the server. In the
> Console, I have no response. But when I have a look in TCPMon, I can> see the request "CreateSequence" was sent, because the client didn't> reveive the "ResponseCreateSequence". I tried to change the timeout
> but it doesn't solve the problem, I think the connection to the server> is not available but the ERP is OK.>> A moment later, the time out error appeared for all request> CreateSequence:
>> POST /axis2/services/RMSampleService HTTP/1.1> User-Agent: Axis2> SOAPAction: http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
> Host: www.apache.org:8080>>> java.net.ConnectException: Connection timed out> at java.net.PlainSocketImpl.socketConnect(Native Method)> at 
java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)> at 
java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)> at java.net.Socket.connect(Socket.java:507)> at java.net.Socket.connect(Socket.java:457)> at java.net.Socket.(Socket.java:365)
> at java.net.Socket.(Socket.java:178)> at org.apache.ws.commons.tcpmon.Connection.run(Connection.java:372)>> Code Client>> package client;>> import javax.xml.namespace.QName
;> import org.apache.axiom.om.OMAbstractFactory;> import org.apache.axiom.om.OMElement;> import org.apache.axiom.om.OMFactory;> import org.apache.axiom.om.OMNamespace;> import org.apache.axiom.soap.SOAPBody
;> import org.apache.axis2.AxisFault;> import org.apache.axis2.Constants;> import org.apache.axis2.addressing.EndpointReference;> import org.apache.axis2.client.Options;> import org.apache.axis2.client.ServiceClient
;> import org.apache.axis2.client.async.AsyncResult;> import org.apache.axis2.client.async.Callback;> import org.apache.axis2.context.ConfigurationContext;> import org.apache.axis2.context.ConfigurationContextFactory
;> import org.apache.sandesha2.client.SandeshaClientConstants;>> public class UserguideEchoClient {>> private final static String applicationNamespaceName => "
http://tempuri.org/";> private final static String echoString = "echoString";> private final static String Text = "Text";> private final static String Sequence = "Sequence";
> private final static String echoStringResponse = "echoStringResponse";> private final static String EchoStringReturn = "EchoStringReturn";> private static String toEPR => "
http://localhost:8080/axis2/services/RMSampleService";>> pr

Re: [Axis2 1.0][Sandesha2] Problem connecting server RMSampleService

[Chamikara Jayalath]

Hi Elodie,

Have you configured the tcp monitor correctly. You should start tomcat
in the port 8080 and have a mapping in tcp monitor from port 8070 to
8080.

Add the following additional line to the client code to send the request through the ctp monitor.
       
clientOptions.setProperty(MessageContextConstants.TRANSPORT_URL,"http://localhost:8070/axis2/services/RMSampleService");


Chamikara
On 6/2/06, Mancinelli Elodie <[EMAIL PROTECTED]> wrote:
HelloTools use: Axis2 1.0, Sandesha2 1.0 and apache-tomcat-5.5.15I'm trying to use the User guide example with the client"UserguideClient.java" in sandesha2 1.0-bin.zip. I use theRMSampleService.aar
 given in the Sandesha2-1.0-bin.zip. When I launchthe client, it could never get a connection to the server. In theConsole, I have no response. But when I have a look in TCPMon, I can seethe request "CreateSequence" was sent, because the client didn't reveive
the "ResponseCreateSequence". I tried to change the timeout but itdoesn't solve the problem, I think the connection to the server is notavailable but the ERP is OK.A moment later, the time out error appeared for all request CreateSequence:
POST /axis2/services/RMSampleService HTTP/1.1User-Agent: Axis2SOAPAction: http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceHost: 
www.apache.org:8080java.net.ConnectException: Connection timed out   at java.net.PlainSocketImpl.socketConnect(Native Method)   at java.net.PlainSocketImpl.doConnect
(PlainSocketImpl.java:333)   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java
:366)   at java.net.Socket.connect(Socket.java:507)   at java.net.Socket.connect(Socket.java:457)   at java.net.Socket.(Socket.java:365)   at java.net.Socket.(Socket.java:178)   at 
org.apache.ws.commons.tcpmon.Connection.run(Connection.java:372)   Code Clientpackage client;import javax.xml.namespace.QName;import org.apache.axiom.om.OMAbstractFactory;import org.apache.axiom.om.OMElement
;import org.apache.axiom.om.OMFactory;import org.apache.axiom.om.OMNamespace;import org.apache.axiom.soap.SOAPBody;import org.apache.axis2.AxisFault;import org.apache.axis2.Constants;import org.apache.axis2.addressing.EndpointReference
;import org.apache.axis2.client.Options;import org.apache.axis2.client.ServiceClient;import org.apache.axis2.client.async.AsyncResult;import org.apache.axis2.client.async.Callback;import org.apache.axis2.context.ConfigurationContext
;import org.apache.axis2.context.ConfigurationContextFactory;import org.apache.sandesha2.client.SandeshaClientConstants;public class UserguideEchoClient {   private final static String applicationNamespaceName =
"http://tempuri.org/";   private final static String echoString = "echoString";   private final static String Text = "Text";   private final static String Sequence = "Sequence";
   private final static String echoStringResponse = "echoStringResponse";   private final static String EchoStringReturn = "EchoStringReturn";   private static String toEPR ="
http://localhost:8080/axis2/services/RMSampleService";   private static String CLIENT_REPO_PATH ="/home/mancinee/workspace/exemplewsrm/client/Client_Repo";   public static void main(String[] args) throws AxisFault,
InterruptedException{   String axis2_xml = CLIENT_REPO_PATH + "/client_axis2.xml";   System .out.println (axis2_xml);   ConfigurationContext configContext =ConfigurationContextFactory.createConfigurationContextFromFileSystem
(CLIENT_REPO_PATH,axis2_xml);   ServiceClient serviceClient = new ServiceClient(configContext,null);   Options clientOptions = new Options ();   clientOptions.setTo(new EndpointReference (toEPR));
   clientOptions.setTransportInProtocol(Constants.TRANSPORT_HTTP);   clientOptions.setUseSeparateListener(true);   serviceClient.setOptions(clientOptions);//  serviceClient.engageModule
(new QName ("sandesha2"));//  serviceClient.engageModule(new QName ("addressing"));   clientOptions.setProperty(SandeshaClientConstants.LAST_MESSAGE,"true");   Callback callback1 = new TestCallback ("Callback 1");
   serviceClient.sendReceiveNonBlocking(getEchoOMBlock("echo1","sequence1"),callback1);   Callback callback2 = new TestCallback ("Callback 2");serviceClient.sendReceiveNonBlocking
(getEchoOMBlock("echo2","sequence1"),callback2);   clientOptions.setProperty(SandeshaClientConstants.LAST_MESSAGE,"true");   Callback callback3 = new TestCallback ("Callback 3");
serviceClient.sendReceiveNonBlocking(getEchoOMBlock("echo3","sequence1"),callback3);   while (!callback1.isComplete()) {   Thread.sleep(1000);   }   
Thread.sleep(4000);   }   private static OMElement getEchoOMBlock(String text, StringsequenceKey) {   OMFactory fac = OMAbstractFactory.getOMFactory();   OMNamespace applicationNamespace =
fac.createOMNamespace(applicationNamespaceName,"ns1");   OMEl

Re: [Axis2][1.0] Unexpected EOF in prolog

[Chamikara Jayalath]

Hi Ali,

Even though you have done changes to your service code you are still
using the serviceClient.sendReceive() method in the client side which
uses the OutInAxisOperationClient.

When useSeperateListner=false, OutInAxisOperationClient expects a
same-channel response message and that should be the reason for this
exception. When it is true what is expected is a asnyc response which
you send within your service code.

Chamikara

On 5/14/06, Ali Sadik Kumlali <[EMAIL PROTECTED]> wrote:
Hi all,Has anyone ran into this exception? I could manage :) to get it withfollowing steps:- Used EchoBlockingDualClient sample. Didn't change client code.- Changed message receiver of MyService to RawXMLINOnlyMessageReceiver
- Changed MyService.java as following:--public class MyService {  private MessageContext inMsgCtx;  public void setOperationContext(OperationContext opctx)
   throws AxisFault {inMsgCtx =  opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);  }  public void echo (OMElement incomingPayload)throws XMLStreamException {
incomingPayload.build();incomingPayload.detach();OMElement outgoingPayload = incomingPayload;oldOptions = inMsgCtx.getOptions();String messageID = inMsgCtx.getMessageID();
EndpointReference targetEPR = oldOptions.getReplyTo();String action = "">sendResult(messageID, targetEPR, action, outgoingPayload);  }  public void sendResult(String messageId, EndpointReference targetEPR,
String action, OMElement payload) {ServiceClient sender = null;try {  Options options = new Options();  options.setTo(targetEPR);  options.setTransportInProtocol(Constants.TRANSPORT_HTTP
);  options.setUseSeparateListener(false);  options.setAction(action);  options.setMessageId(UUIDGenerator.getUUID());  options.setRelationships(new RelatesTo[] {  new RelatesTo(messageId,
  AddressingConstants.Submission.  WSA_RELATES_TO_RELATIONSHIP_TYPE_DEFAULT_VALUE)});  ConfigurationContext confCtx =  ListenerManager.defaultConfigurationContext;
  sender = new ServiceClient(confCtx, null);  sender.setOptions(options);  // Blocking Invocation  sender.sendReceive(payload);} catch (AxisFault axisFault) {  axisFault.printStackTrace
();} catch (Exception ex) {  ex.printStackTrace();} finally {  try {  sender.finalizeInvoke();  } catch (AxisFault axisFault) {  // have to ignore this  
axisFault.printStackTrace();  }}  }}--When I pass "true" to setUseSeparateListener(), there is no problem.
Otherwise I get following exception:--[DEBUG][2006-05-13 23:15:08,046] org.apache.axis2.engine.Phase -Checking post-conditions for phase "MessageOut"
postMethod.getStatusCode(): 200contentEncoding: nullorg.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxEOFException:Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0]; nested exception is:
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException:Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0]atorg.apache.axis2.transport.TransportUtils.createSOAPMessage
(TransportUtils.java:126)atorg.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)atorg.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java
:349)atorg.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:279)atorg.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:513)...--
Is it normal behavior due to a missing point in my code, or is it abug?Any help would be appreciated.Regards,Ali Sadik Kumlali__
Do You Yahoo!?Tired of spam?  Yahoo! Mail has the best spam protection aroundhttp://mail.yahoo.com

[ANN][Axis2] Sandesha2 1.0 released

[Chamikara Jayalath]

Hi All,

We are proud to announce the 1.0 release of Apache Sandesha2, WS-ReliableMessaging implementation for  Apache  Axis2.

You can download this release from our official site at
http://ws.apache.org/sandesha/sandesha2/

This release should be used with the Axis2 1.0 distribution which could be obtained from
http://ws.apache.org/axis2/download.cgi

Features of this release include:

1.  Support for WS-ReliableMessaging in both client side and
server side of Axis2. (according to the the WS-ReliableMessaging
specification February 2005).

2. Pluggable storage framework.

3. Configurable delivery assurances. In-order exactly-once delivery
assurance is guaranteed. Users can also instruct the system to stop
ordering (this will give a higher performance).

4. Support for both SOAP 1.1 and 1.2.

5. Mechanisms to support WS-ReliableMessaging policy assertions in both server side and the client side.

6. Improved client API, which provides features for both general and advance users.

7. Sandesha Report functionality to get status information on Sandesha2 system and its sequences.

8. SandeshaListener feature to get informed when specific events happen
(for example, when a fault is retrieved or when a sequence times out).

9. Support for the WSRM specification being developed under OASIS WSRX technical committee.

10. Test cases to test RM scenarios.

11. Documentation


Please use this release and send your comments to sandesha-dev@ws.apache.org.

Thank you,
Sandesha2 team

[Axis2] Sandesha2 1.0-RC1 release

[Chamikara Jayalath]

Hi All,


Sandesha2 1.0-RC1 release artifacts are available at the location
http://people.apache.org/~chamikara/sandesha2/1.0-RC1/

This release should be used with the Axis2 1.0-RC2 distribution which is available in
http://people.apache.org/~deepal/axis2/1.0-RC2/.

Features of this release include.

1.  Support for WS-ReliableMessaging in both client side and
server side of Axis2. (according the the WS-ReliableMessaging
specification February 2005).

2. Pluggable storage framework.

3. Configurable delivery assurances. In-order exactly once delivery
assurance is guaranteed. Users can also instruct the system to stop
ordering (this will give a higher performance).

4. Support for both SOAP 1.1 and 1.2.

5. Mechanisms to support WS-ReliableMessaging policy assertions in both server side and the client side.

6. Improved client API, which provides features for both general and advance users.

7. Sandesha Report functionality to get status information on Sandesha2 system and its sequences.

8. SandeshaListner feature to get informed when specific events happen
(for example when a fault is retrieved or when a sequence times out).

9. Support for the WSRM specification being developed under OASIS WSRX technical committee.

10. Test cases to test RM scenarios.

11. Documentation


Please use this release and send your comments to sandesha-dev@ws.apache.org
We hope to do the Sandesha2 1.0 release soon

Thank you,
Sandesha2 team

Re: [axis2] User guide sample application inconsistency(?)

[Chamikara Jayalath]

Hi Sadik ,

Actually the 'schema' directory mentioned in the userguide is the 'resources' directory that was created by the WSDL2Java tool.

After generating the files you can easily create the service archieve file by running the ant task.  

1. Set the AXIS2_HOME environmental variable to the directory you extracted the Axis2  distribution.

2. Go to a command prompt. Move to your output folder (to which you generated the files) and run the commant 'ant'.
This will create the  'Axis2SampleDocLitService.aar' file in the 'build\lib' subdirectory.

3. Drop this to your 'webapps\axis2\WEB-INF\services' folder and start tomcat.

Thanks,
Chamikara


On 2/26/06, Ali Sadik Kumlali <[EMAIL PROTECTED]> wrote:
Dear all,I'm a new axis2 user and want to learn it by following the instructions in it's user guide.   
First of all, i tried to generate a web service from a given WSDL as
introduced in "Writing Web Services by Code Generating Skeleton".
Therefore, i generated Java files from Axis2SampleDocLit.wsdl found in
samples\wsdl directory. I also passed "-d xmlbeans" parameter to
WSDL2Java.bat to make it use XMLBeans databinding. When i looked at the
generated files, i found two directory created: src and resources.
Under resources folder there was an interesting directory called
"schemaorg_apache_xmlbeans" which i could not found any reference in
user guide. I thought it must be "schema" directory mentioned in the
guide. Anyway, i filled the empty methods in
Axis2SampleDocLitPortTypeSkeleton.java file with the codes given
in the user guide. Created services.xml file and filled with the code
given in the guide. And created a package called
Axis2SampleDocLitPortType.aar by following the instuctions. After all,
i put the  file under the \webapps\axis2\WEB-INF\services
directory. Then after started Tomcat 5.5, clicked the "services" link
listed in http://localhost:8080/axis2/index.jsp.
Since i did not see the Axis2SampleDocLitPortType service listed in the
page, looked at the log files of Tomcat resides under logs directory.
Then i saw a line says "NullPointerException" without any further
information. I also tried to change the name of
schemaorg_apache_xmlbeans directory to schema. It did not work either.Am i missing something?Thans in advance,Ali Sadik Kumlali
		 Yahoo! Mail 
Use Photomail to share photos without annoying attachments.