Re: Using some sort of in-VM transport between Synapse and a web app deployed on the same server?
Andreas > * By acquiring a RequestDispatcher for a servlet from the foreign > context and invoking forward or include on this object. > > The first approach can be discarded, again because of class loader > issues and the fact that it would require changes to the second > application. The second approach is more promising because it allows > to invoke the servlet that implements the target service. Note however > that there is an important restriction imposed by the servlet > specification on the use of RequestDispatcher#include/forward: "The > request and response parameters must be either the same objects as > were passed to the calling servlet’s service method or be subclasses > of the ServletRequestWrapper or ServletResponseWrapper classes that > wrap them." This means that these methods can't be called with > arbitrary HttpServletRequest/Response implementations. Obviously this > requirement is there to guarantee that the server gets access to the > original request/response objects. It could be that some servers do > not enforce this requirement, but for those that do, the practical > consequence is that the RequestDispatcher approach would only work if > the original request is received by SynapseAxisServlet, which is > perfectly compatible with the use case described here. > > My question is whether anybody on this list is aware of an existing > Axis2 transport implementation that uses this approach or if anybody > here sees any obstacle that would make it impossible to implement this > kind of transport. Since Synapse would most frequently modify the original request and forward a new (e.g. transformed request of the original) to the back end service, I doubt if this approach would be feasible.. however, although you could theoretically use Synapse with a servlet transport, we built the non-blocking http/s transports for Synapse, as acting as an ESB it needs to handle many connections concurrently passing them between the requester and the actual service. If using a servlet transport, the thread invoking Synapse would block until the backend service replies, and this could lead to the thread pool being exhausted very soon. The objective of the non-blocking http/s transport is to prevent this and it works very well when load tested.. Anyway when two apps communicate on the same host, the TCP overheads are reduced AFAIK by the OS's and the calls passed through locally asankha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to acquire necessary Axis2-jars via Maven2
Hi Thomas, http://repo1.maven.org/maven2/ should contain everything you need. Regards, Andreas On 04 Jan 2008, at 15:20, [EMAIL PROTECTED] wrote: Hello Axis-users, i assume, this is an easy one for you: I want to setup a basic Maven2-based Axis2 project from scratch. The core structure is given by the following projects: 1. a project to generate the aar-jar which contains the generated stubs/skeletons for the wsdl-file via the m2 wsdl2code plugin (version 1.3) 2. a project to generate the aar based on the aar-jar via the m2 aar- plugin 3. a project to generate the war based on the aar 4. a project to generate the ear based on the war i'm able to successfully deploy the ear into an appserver. Now i'm trying to implement a junit-test, which needs a dependency to axis2-kernel which i can only find in version 1.0 in the public repositories. During runtime of the test i get an incompatible class error, probably due to the fact, that i'm using V1.0 of axis2-kernel and the generated aaj-jar is based on the wsdl2code-plugin with version 1.3. I cannot find an M2-repository offering me the latest (1.3) Axis2 components. Is there a reason why axis2 1.3 isn't published as an m2 repository? Is there any alternative to the manuall installation of all necessary Axis2-components in my local repository with all the dependencies I thougt Maven would care about? Thanks in advance, Thomas
Using some sort of in-VM transport between Synapse and a web app deployed on the same server?
Hi all! Consider the following use case for Synapse: * Synapse is deployed as a Web application. * The Synapse configuration has a service proxy that targets a service exposed by another Web application deployed on the same server. * Both the proxy and the target use HTTP as transport protocol. * The target Web application neither uses Axis, nor is it reasonable to change it in any way. The obvious solution is to use HTTP to communicate with the target service. However using HTTP to communicate between two Web applications deployed on the same server, i.e. inside the same VM, seems a bit like an overkill. Therefore my question is if there is some sort of a local transport implementation that would allow to do this in a more efficient way. Obviously the local transport defined in Axis2 can't be used here, because it would require changes to the target application. Also the fact that each of the two Web applications has its own class loader would make this tricky. It appears that the servlet specification actually defines a way for two Web applications hosted in the same container to communicate with each other directly, i.e. in VM. Indeed a Web application can obtain the ServletContext of another Web application using ServletContext#getContext. Usually the server must be configured to allow this kind of cross context access, but this is supported by Tomcat (by specifying crossContext="true" in the context file). Using this mechanism, the Web applications can communicate in two different ways: * By sharing state using get/setAttribute. * By acquiring a RequestDispatcher for a servlet from the foreign context and invoking forward or include on this object. The first approach can be discarded, again because of class loader issues and the fact that it would require changes to the second application. The second approach is more promising because it allows to invoke the servlet that implements the target service. Note however that there is an important restriction imposed by the servlet specification on the use of RequestDispatcher#include/forward: "The request and response parameters must be either the same objects as were passed to the calling servlet’s service method or be subclasses of the ServletRequestWrapper or ServletResponseWrapper classes that wrap them." This means that these methods can't be called with arbitrary HttpServletRequest/Response implementations. Obviously this requirement is there to guarantee that the server gets access to the original request/response objects. It could be that some servers do not enforce this requirement, but for those that do, the practical consequence is that the RequestDispatcher approach would only work if the original request is received by SynapseAxisServlet, which is perfectly compatible with the use case described here. My question is whether anybody on this list is aware of an existing Axis2 transport implementation that uses this approach or if anybody here sees any obstacle that would make it impossible to implement this kind of transport. Regards, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Question regarding deploying Axis Services
Pls check if you have axiom-impl-1.2.5.jar in the lib. On Jan 4, 2008 1:40 PM, <[EMAIL PROTECTED]> wrote: > Hi all, > > Is there any consequence of not bundling Service classes in .aar instead > putting them in WEB-INF/lib where all other axis jars are located. > > I am getting ClassDefNotFound : > org/apache/axiom/soap/impl/llom/soap11/SOAP11HeaderBlockImpl error* only > when I am calling another webservice (on different host) from within our > axis service.* > > *Please share your thoughts.* > > *Thanks,* > *Tushar* > > Visit our website at http://www.ubs.com > > This message contains confidential information and is intended only > for the individual named. If you are not the named addressee you > should not disseminate, distribute or copy this e-mail. Please > notify the sender immediately by e-mail if you have received this > e-mail by mistake and delete this e-mail from your system. > > E-mails are not encrypted and cannot be guaranteed to be secure or > error-free as information could be intercepted, corrupted, lost, > destroyed, arrive late or incomplete, or contain viruses. The sender > therefore does not accept liability for any errors or omissions in the > contents of this message which arise as a result of e-mail transmission. > If verification is required please request a hard-copy version. This > message is provided for informational purposes and should not be > construed as a solicitation or offer to buy or sell any securities > or related financial instruments. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [Axis2] trimming down the xml in axis2 1.3
Hello
I have tried using this option with xmlbeans as databinding and its not
working . Does this option work with xmlbeans ?
Thanks
Gaurav
On Dec 13, 2007 11:37 AM, samir shaikh <[EMAIL PROTECTED]> wrote:
> Raghu,
>
> I use the default databinding i.e. ADB. I typically
> build a service and expose it and let Axis2 generate
> my wsdl for me. This is actually working back.
>
> I'll try it and let you know...
>
> Thanks a lot!
>
> Samir
>
> --- Raghu Upadhyayula <[EMAIL PROTECTED]>
> wrote:
>
> > Samir,
> >
> > Yes, it worked for me.
> >
> > I used the WSDL2Java with -sp option to generate the
> > server code.
> >
> > What data binding are you using?
> >
> > If you are using ADB, then you have to replace all
> > the request &
> > response classes.
> >
> > Thanks
> > Raghu
> > -Original Message-
> > From: samir shaikh [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, December 13, 2007 10:50 AM
> > To: axis-user@ws.apache.org
> > Subject: RE: [Axis2] trimming down the xml in axis2
> > 1.3
> >
> > Raghu,
> >
> > I see in the archives that you ran into the same
> > problem as this. Did wsdl2java with -sp work for
> > you?
> >
> > Samir
> >
> > --- Raghu Upadhyayula <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Samir,
> > >
> > > WSDL2Java can also be used to generate serverside
> > > code. Check
> > > WSDL2Java options, to create serverside code you
> > > need to specify the
> > > options -ss -sd -ssi (check the description for
> > > these options in
> > > WSDL2Java)
> > >
> > > You can use -sp option with WSDL2Java when you
> > > generate the serverside
> > > code in which case the namespace is suppressed on
> > > the serverside.
> > >
> > > Thanks
> > > Raghu
> > >
> > > -Original Message-
> > > From: samir shaikh [mailto: [EMAIL PROTECTED]
> > > Sent: Wednesday, December 12, 2007 5:31 PM
> > > To: axis-user@ws.apache.org
> > > Subject: Re: [Axis2] trimming down the xml in
> > axis2
> > > 1.3
> > >
> > > Martin,
> > >
> > > You mean using QName in the client code?
> > >
> > > I'm trying to tune my server to not send back
> > > excessive xml. I cannot change the xml I send back
> > > to
> > > my clients. the extra "ns:" is causing me trouble
> > > after upgrading from axis2 1.1.1 to axis2 1.3 e.g.
> > > 0. My clients expect
> > > 0.
> > >
> > > Samir
> > >
> > > --- Martin Gainty <[EMAIL PROTECTED]> wrote:
> > >
> > > > you can always use null..e.g.
> > > > QName paramQName = new QName("", paramName);
> > > >
> > > > M--
> > > > - Original Message -
> > > > From: "samir shaikh" < [EMAIL PROTECTED]>
> > > > To:
> > > > Sent: Wednesday, December 12, 2007 7:20 PM
> > > > Subject: RE: [Axis2] trimming down the xml in
> > > axis2
> > > > 1.3
> > > >
> > > >
> > > > > Raghu,
> > > > >
> > > > > Thanks for your help. I tried that out but I
> > > want
> > > > to
> > > > > suppress it on the server. I think WSDL2Java
> > is
> > > > for
> > > > > generating a client, right?
> > > > >
> > > > > I'm hoping to find some configuration in
> > > > services.xml
> > > > > or axis2.xml... any idea?
> > > > >
> > > > > Samir
> > > > >
> > > > >
> > > > > --- Raghu Upadhyayula
> > > <[EMAIL PROTECTED]>
> > > > > wrote:
> > > > >
> > > > > > Samir,
> > > > > >
> > > > > > Try WSDL2Java with -sp option to suppress
> > the
> > > > > > namespace prefix.
> > > > > >
> > > > > > Thanks
> > > > > > Raghu
> > > > > >
> > > > > > -Original Message-
> > > > > > From: samir shaikh
> > > [mailto:[EMAIL PROTECTED]
> > > > > > Sent: Wednesday, December 12, 2007 2:20 PM
> > > > > > To: axis-user@ws.apache.org
> > > > > > Subject: [Axis2] trimming down the xml in
> > > axis2
> > > > 1.3
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I'm trying to trim down the xml exchanged
> > when
> > > > using
> > > > > > a
> > > > > > axis2 client and server. Is there a way I
> > can
> > > > > > configure the serializer to not prefix
> > > namespace
> > > > > > with
> > > > > > every element e.g.
> > > > 0
> > > > > > can
> > > > > > just be 0. Also not
> > send
> > > > back
> > > > > > the additional headers and field types with
> > > each
> > > > > > call.
> > > > > > I was able to do that in Axis1.3 with the
> > wsdd
> > > > file.
> > > > > > Can someone point me to where that is done
> > in
> > > > Axis2.
> > > > > >
> > > > > > Thanks a lot.
> > > > > >
> > > > > > Samir
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
> > > > > >
> > > > > > Be a better friend, newshound, and
> > > > > > know-it-all with Yahoo! Mobile. Try it now.
> > > > > >
> > > > >
> > > >
> > >
> >
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> -
> > > > > > To unsubscribe, e-mail:
> > > > > > [EMAIL PROTECTED]
> > > > > > For additional commands, e-mail:
> > > > > > [EMAIL P
Question regarding deploying Axis Services
Hi all, Is there any consequence of not bundling Service classes in .aar instead putting them in WEB-INF/lib where all other axis jars are located. I am getting ClassDefNotFound : org/apache/axiom/soap/impl/llom/soap11/SOAP11HeaderBlockImpl error only when I am calling another webservice (on different host) from within our axis service. Please share your thoughts. Thanks, Tushar Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mails are not encrypted and cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 Security with Rampart
Thank you so much Paul! I got it work following your advice. I still have a question though: why did I spend so much time trying to figure it out by myself when I could've just emailed you guys!? :) I'm so mad now! Paul Fremantle <[EMAIL PROTECTED]> wrote: Yep you need some kind of policy to tell Rampart what parts of WS-Security to implement. Take a look at rampart-1.3\samples\policy\sample01 Paul On Jan 4, 2008 5:15 PM, red dog wrote: > Hi Paul, > > So do i still need a policy file even if i send the pair username/password > in clear text? Sorry, it seems I missed this part when I read the how-to > steps. > > Thank you. > > > Paul Fremantle wrote: > What is your rampart config/policy. If you just enable Rampart but > don't give it any configuration it doesn't do much. > > Paul > > On Jan 4, 2008 4:51 PM, red dog wrote: > > Reg. message ID: BAY108-DAV6AE19CD9C371CBB93AB9CAE930 () phx ! gbl > > > > > > Hi everyone, > > > > Is there any resolution to this? I'm facing the same issue and I'm using > > Axis 2 and rampart module 1.3. > > > > If I just send a SOAP message with an empty security header my method gets > > called. > > > > POST /axis2/services/sample03 HTTP/1.1 > > User-Agent: Axis2 > > SOAPAction: urn:echo > > Host: localhost:18088 > > Transfer-Encoding: chunked > > Content-Type: text/xml; charset=UTF-8 > > 1ba > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>> > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; > > soapenv:mustUnderstand="1" />> > xmlns:ns1="http://sample03.samples.rampart.apache.org/xsd";>Hello > > world > > > 0 > > > > Response: > > > > HTTP/1.1 200 OK > > Date: Fri, 04 Jan 2008 15:59:48 GMT > > Server: Simple-Server/1.1 > > Transfer-Encoding: chunked > > Content-Type: text/xml; charset=UTF-8 > > 133 > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>> />> > xmlns:ns="http://sample03.samples.rampart.apache.org/xsd";>Hello > > world > > > 0 > > > > > > After debugging I relized that the handle() method from the > > MyServiceCallbackHandler is not getting called although the handler is > > getting invoked (tested by adding an empty constructor to the class). > > > > Your help is much appreciated. > > > > > > Thank you. > > > > > > > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > > now. > > > > -- > Paul Fremantle > Co-Founder and VP of Technical Sales, WSO2 > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > Never miss a thing. Make Yahoo your homepage. -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Never miss a thing. Make Yahoo your homepage.
Re: Axis2 Security with Rampart
Yep you need some kind of policy to tell Rampart what parts of WS-Security to implement. Take a look at rampart-1.3\samples\policy\sample01 Paul On Jan 4, 2008 5:15 PM, red dog <[EMAIL PROTECTED]> wrote: > Hi Paul, > > So do i still need a policy file even if i send the pair username/password > in clear text? Sorry, it seems I missed this part when I read the how-to > steps. > > Thank you. > > > Paul Fremantle <[EMAIL PROTECTED]> wrote: > What is your rampart config/policy. If you just enable Rampart but > don't give it any configuration it doesn't do much. > > Paul > > On Jan 4, 2008 4:51 PM, red dog wrote: > > Reg. message ID: BAY108-DAV6AE19CD9C371CBB93AB9CAE930 () phx ! gbl > > > > > > Hi everyone, > > > > Is there any resolution to this? I'm facing the same issue and I'm using > > Axis 2 and rampart module 1.3. > > > > If I just send a SOAP message with an empty security header my method gets > > called. > > > > POST /axis2/services/sample03 HTTP/1.1 > > User-Agent: Axis2 > > SOAPAction: urn:echo > > Host: localhost:18088 > > Transfer-Encoding: chunked > > Content-Type: text/xml; charset=UTF-8 > > 1ba > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>> > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; > > soapenv:mustUnderstand="1" />> > xmlns:ns1="http://sample03.samples.rampart.apache.org/xsd";>Hello > > world > > > 0 > > > > Response: > > > > HTTP/1.1 200 OK > > Date: Fri, 04 Jan 2008 15:59:48 GMT > > Server: Simple-Server/1.1 > > Transfer-Encoding: chunked > > Content-Type: text/xml; charset=UTF-8 > > 133 > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>> />> > xmlns:ns="http://sample03.samples.rampart.apache.org/xsd";>Hello > > world > > > 0 > > > > > > After debugging I relized that the handle() method from the > > MyServiceCallbackHandler is not getting called although the handler is > > getting invoked (tested by adding an empty constructor to the class). > > > > Your help is much appreciated. > > > > > > Thank you. > > > > > > > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > > now. > > > > -- > Paul Fremantle > Co-Founder and VP of Technical Sales, WSO2 > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > Never miss a thing. Make Yahoo your homepage. -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 Security with Rampart
Hi Paul, So do i still need a policy file even if i send the pair username/password in clear text? Sorry, it seems I missed this part when I read the how-to steps. Thank you. Paul Fremantle <[EMAIL PROTECTED]> wrote: What is your rampart config/policy. If you just enable Rampart but don't give it any configuration it doesn't do much. Paul On Jan 4, 2008 4:51 PM, red dog wrote: > Reg. message ID: BAY108-DAV6AE19CD9C371CBB93AB9CAE930 () phx ! gbl > > > Hi everyone, > > Is there any resolution to this? I'm facing the same issue and I'm using > Axis 2 and rampart module 1.3. > > If I just send a SOAP message with an empty security header my method gets > called. > > POST /axis2/services/sample03 HTTP/1.1 > User-Agent: Axis2 > SOAPAction: urn:echo > Host: localhost:18088 > Transfer-Encoding: chunked > Content-Type: text/xml; charset=UTF-8 > 1ba > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>> > > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; > soapenv:mustUnderstand="1" />> > xmlns:ns1="http://sample03.samples.rampart.apache.org/xsd";> Hello > world > 0 > > Response: > > HTTP/1.1 200 OK > Date: Fri, 04 Jan 2008 15:59:48 GMT > Server: Simple-Server/1.1 > Transfer-Encoding: chunked > Content-Type: text/xml; charset=UTF-8 > 133 > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>> />> > > xmlns:ns="http://sample03.samples.rampart.apache.org/xsd";>Hello > world > 0 > > > After debugging I relized that the handle() method from the > MyServiceCallbackHandler is not getting called although the handler is > getting invoked (tested by adding an empty constructor to the class). > > Your help is much appreciated. > > > Thank you. > > > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now. -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Never miss a thing. Make Yahoo your homepage.
Re: Axis2 Security with Rampart
What is your rampart config/policy. If you just enable Rampart but don't give it any configuration it doesn't do much. Paul On Jan 4, 2008 4:51 PM, red dog <[EMAIL PROTECTED]> wrote: > Reg. message ID: BAY108-DAV6AE19CD9C371CBB93AB9CAE930 () phx ! gbl > > > Hi everyone, > > Is there any resolution to this? I'm facing the same issue and I'm using > Axis 2 and rampart module 1.3. > > If I just send a SOAP message with an empty security header my method gets > called. > > POST /axis2/services/sample03 HTTP/1.1 > User-Agent: Axis2 > SOAPAction: urn:echo > Host: localhost:18088 > Transfer-Encoding: chunked > Content-Type: text/xml; charset=UTF-8 > 1ba > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; > soapenv:mustUnderstand="1" /> xmlns:ns1="http://sample03.samples.rampart.apache.org/xsd";>Hello > world > 0 > > Response: > > HTTP/1.1 200 OK > Date: Fri, 04 Jan 2008 15:59:48 GMT > Server: Simple-Server/1.1 > Transfer-Encoding: chunked > Content-Type: text/xml; charset=UTF-8 > 133 > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> /> xmlns:ns="http://sample03.samples.rampart.apache.org/xsd";>Hello > world > 0 > > > After debugging I relized that the handle() method from the > MyServiceCallbackHandler is not getting called although the handler is > getting invoked (tested by adding an empty constructor to the class). > > Your help is much appreciated. > > > Thank you. > > > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now. -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BAY108-DAV6AE19CD9C371CBB93AB9CAE930 () phx ! gbl
Hi Nandana, I'm planning on sending the username and the password in clear text. I know it's not 100% secure but the call will be done over https anyway... Here is my service.xml org.apache.rampart.samples.sample03.SimpleService UsernameToken org.apache.rampart.samples.sample03.MyServiceCallbackHandler Thank you. Nandana Mihindukulasooriya <[EMAIL PROTECTED]> wrote: Hi, Can you please post your security configuration too ? Thanks, Nandana On 1/4/08, red dog wrote: > Hi everyone, > > Is there any resolution to this? I'm facing the same issue and I'm using > Axis 2 and rampart module 1.3. > > If I just send a SOAP message with an empty security header my method gets > called. > > POST /axis2/services/sample03 HTTP/1.1 > User-Agent: Axis2 > SOAPAction: urn:echo > Host: localhost:18088 > Transfer-Encoding: chunked > Content-Type: text/xml; charset=UTF-8 > 1ba > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>> > > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; > soapenv:mustUnderstand="1" />> xmlns:ns1=" > Hello'>http://sample03.samples.rampart.apache.org/xsd";> Hello > world > 0 > > Response: > > HTTP/1.1 200 OK > Date: Fri, 04 Jan 2008 15:59:48 GMT > Server: Simple-Server/1.1 > Transfer-Encoding: chunked > Content-Type: text/xml; charset=UTF-8 > 133 > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>> />> > > xmlns:ns="Hello'>http://sample03.samples.rampart.apache.org/xsd";>Hello > world > 0 > > > After debugging I relized that the handle() method from the > MyServiceCallbackHandler is not getting called although the handler is > getting invoked (tested by adding an empty constructor to the class). > > Your help is much appreciated. > > > Thank you. > > > - > Looking for last minute shopping deals? Find them fast with Yahoo! Search. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
Re: BAY108-DAV6AE19CD9C371CBB93AB9CAE930 () phx ! gbl
Hi, Can you please post your security configuration too ? Thanks, Nandana On 1/4/08, red dog <[EMAIL PROTECTED]> wrote: > Hi everyone, > > Is there any resolution to this? I'm facing the same issue and I'm using > Axis 2 and rampart module 1.3. > > If I just send a SOAP message with an empty security header my method gets > called. > > POST /axis2/services/sample03 HTTP/1.1 > User-Agent: Axis2 > SOAPAction: urn:echo > Host: localhost:18088 > Transfer-Encoding: chunked > Content-Type: text/xml; charset=UTF-8 > 1ba > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; > soapenv:mustUnderstand="1" /> xmlns:ns1=" > Hello'>http://sample03.samples.rampart.apache.org/xsd";>Hello > world > 0 > > Response: > > HTTP/1.1 200 OK > Date: Fri, 04 Jan 2008 15:59:48 GMT > Server: Simple-Server/1.1 > Transfer-Encoding: chunked > Content-Type: text/xml; charset=UTF-8 > 133 > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> /> xmlns:ns="Hello'>http://sample03.samples.rampart.apache.org/xsd";>Hello > world > 0 > > > After debugging I relized that the handle() method from the > MyServiceCallbackHandler is not getting called although the handler is > getting invoked (tested by adding an empty constructor to the class). > > Your help is much appreciated. > > > Thank you. > > > - > Looking for last minute shopping deals? Find them fast with Yahoo! Search. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 Security with Rampart
Reg. message ID: BAY108-DAV6AE19CD9C371CBB93AB9CAE930 () phx ! gbl Hi everyone, Is there any resolution to this? I'm facing the same issue and I'm using Axis 2 and rampart module 1.3. If I just send a SOAP message with an empty security header my method gets called. POST /axis2/services/sample03 HTTP/1.1 User-Agent: Axis2 SOAPAction: urn:echo Host: localhost:18088 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 1ba http://schemas.xmlsoap.org/soap/envelope/";>http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; soapenv:mustUnderstand="1" />http://sample03.samples.rampart.apache.org/xsd";>Hello world 0 Response: HTTP/1.1 200 OK Date: Fri, 04 Jan 2008 15:59:48 GMT Server: Simple-Server/1.1 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 133 http://schemas.xmlsoap.org/soap/envelope/";>http://sample03.samples.rampart.apache.org/xsd";>Hello world 0 After debugging I relized that the handle() method from the MyServiceCallbackHandler is not getting called although the handler is getting invoked (tested by adding an empty constructor to the class). Your help is much appreciated. Thank you. - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
BAY108-DAV6AE19CD9C371CBB93AB9CAE930 () phx ! gbl
Hi everyone, Is there any resolution to this? I'm facing the same issue and I'm using Axis 2 and rampart module 1.3. If I just send a SOAP message with an empty security header my method gets called. POST /axis2/services/sample03 HTTP/1.1 User-Agent: Axis2 SOAPAction: urn:echo Host: localhost:18088 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 1ba http://schemas.xmlsoap.org/soap/envelope/";>http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; soapenv:mustUnderstand="1" />http://sample03.samples.rampart.apache.org/xsd";>Hello world 0 Response: HTTP/1.1 200 OK Date: Fri, 04 Jan 2008 15:59:48 GMT Server: Simple-Server/1.1 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 133 http://schemas.xmlsoap.org/soap/envelope/";>http://sample03.samples.rampart.apache.org/xsd";>Hello world 0 After debugging I relized that the handle() method from the MyServiceCallbackHandler is not getting called although the handler is getting invoked (tested by adding an empty constructor to the class). Your help is much appreciated. Thank you. - Looking for last minute shopping deals? Find them fast with Yahoo! Search.
Re: WSS4J, AXIS1.X, WSE (interop)
I am asking for a possible configuration client and server side (doesn't need to be with tomcat) Thank you. On Jan 4, 2008 2:56 PM, José Ferreiro <[EMAIL PROTECTED]> wrote: > Hello everybody, > > I would like to ask the developers (or if someone knows) from WSS4J or > AXIS 1.X world > if there is interoperability scenarios that *works* with: > > AXIS + WSS4J (server side with tomcat) > and WSE2.0 or WSE3.0 > > using digital certificates. > > Any information will be very much appreciated. > Thank you in advance. > > >
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Hi, > I'm not completely clear on your setup but it seems to me you are > creating a ConfigurationContext yourself or are not loading the same > axis2.xml as you showed me If you create a ConfigurationContext without specifying an axis2.xml, axis2_default.xml [1] will be used and this will cause problems as the user defined phases are not present there. Anyway Axis2 is going to have dynamic phase support very soon, so these kind of problems will not occur as the modules them selves will be able to define the phases which they require to register their handlers. [1] - http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/axis2_default.xml?view=markup thanks, Nandana - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
On 4 Jan 2008, at 16:00, robert lazarski wrote: I'm not completely clear on your setup but it seems to me you are creating a ConfigurationContext yourself or are not loading the same axis2.xml as you showed me - which is why putting axis2 in debug would help as it would confirm the soapmonitorPhase is being loaded in inflow. The two configuration files (embedded and inside tomcat) are the indeed the same. Anywhich way though, what you are lacking is getting the soapmonitorPhase configured in inflow - be it via axis2.xml, ConfigurationContext etc. Are you able to engage and run the other modules like logging and ping ok in your embedded setup? Not the logging (it throws an exception saying it's not valid), but I can successfully deploy a module of mine. Can you load the phases programtically in your embedded setup? Yes. See the unit tests in the src tree for how to do phase loading programtically - sorry for being a bit vague here but looking at the source is the quickest way to tackle advance cases like this. HTH, Robert Michele On Jan 4, 2008 12:39 PM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, I get that error if I run an embedded version of axis2. If I deploy it to tomcat (clean setup) it works fine. Jan 4, 2008 3:36:45 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Jan 4, 2008 3:36:45 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1011 ms Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.14 Jan 4, 2008 3:36:46 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive axis2.war [INFO] Deploying module: addressing-1.3 [INFO] Deploying module: metadataExchange-1.3 [INFO] Deploying module: ping-1.3 [INFO] Deploying module: script-1.3 [INFO] Deploying module: soapmonitor-1.3 [INFO] script module activated [INFO] HTTP Sender starting [INFO] Deploying Web service: version.aar Jan 4, 2008 3:36:50 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Jan 4, 2008 3:36:50 PM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Jan 4, 2008 3:36:50 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/52 config=null Jan 4, 2008 3:36:50 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 5161 ms Any idea? Michele On 4 Jan 2008, at 14:50, robert lazarski wrote: Michele, can you post your entire stacktrace please? I can't match the error you get with current svn. The error you are getting indicates no soapmonitorPhase in inflow, yet your axis2.xml does have it. So sorry, no clear indication of the problem yet. You could try putting axis2 in debug to see the phases loaded, which may flush out the error by confirming the phase isn't loaded. Alternatively, try out tcpmon ;-) . Good luck, Robert On Jan 4, 2008 10:11 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, if the module is globally engaged I get the error I mentioned in my previous email. The same happens also if I "dynamically" engage the module. Michele On 4 Jan 2008, at 12:01, robert lazarski wrote: You need to engage the module. Search for: Then in the same place, add: HTH, Robert On Jan 4, 2008 8:44 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, in axis2 1.3 all the phases needed by the soap monitor module are already included. Michele On 4 Jan 2008, at 11:07, robert lazarski wrote: The exception is pretty self descriptive... show us the entire axis2.xml and maybe we can help. Robert On Jan 4, 2008 7:39 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Hi all, I can't enage the soapmonitor module under Axis2 1.3 because of the following error org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'soapmonitorPhase' while deploying handler 'InFlowSOAPMonitorHandler'. My axis2.xml differs from the default one only because of the NIO transport listener. Any idea? Thanks, Michele --- -- -- -- 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] - -- -- 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] --- -- To unsubscribe, e-mai
RE: wsdl/schema import
taking a quick look at the include spec at w3c
http://www.w3schools.com/schema/el_redefine.asp
where anyURI is defined in
http://java.sun.com/j2se/1.5.0/docs/api/java/net/URI.html
some examples would be
An opaque URI is an absolute URI whose scheme-specific part does not begin with
a slash character ('/'). Opaque URIs are not subject to further parsing. Some
examples of opaque URIs are:
mailto:[EMAIL PROTECTED]
news:comp.lang.java
urn:isbn:096139210x
A hierarchical URI is either an absolute URI whose scheme-specific part begins
with a slash character, or a relative URI, that is, a URI that does not specify
a scheme. Some examples of hierarchical URIs are:
http://java.sun.com/j2se/1.3/docs/guide/collections/designfaq.html#28../../../demo/jfc/SwingSet2/src/SwingSet2.javafile:///~/calendar
A hierarchical URI is subject to further parsing according to the syntax
[scheme:][//authority][path][?query][#fragment]
(noting the absence of drive specifier c: where
file:///AbsolutePathToXSDFile)Martin
__Disclaimer and confidentiality
noteEverything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and Sender
does not endorse distribution to any party other than intended recipient.
Sender does not necessarily endorse content contained within this
transmission.> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED];
axis-user@ws.apache.org> Date: Fri, 4 Jan 2008 10:26:58 -0500> Subject:
wsdl/schema import> > Hi,> > I am importing a schema as follows:> >
> > > http://www.sas.com/testSchema.xsd/"; />> ...> > This fails with
error message: Unable to locate with a locator the schema referenced at '...'
relative to document base 'meta-inf/mywsdl.wsdl.> > It appears that the Axis2
wsdl processor can only reference schemas relative to the location of the wsdl
itself. If I change the import to:> > > > and add testSchema.xsd to meta-inf/
directory in the AAR, it works.> > > I checked WS-I Basic Profile 1.1 and
didn't see any limitation on schemaLocation. The XML Schema spec does say that
this attribute is only a hint. Is it possible to reference a schema that is not
relative to the wsdl? Is this an Axis2 shortfall or is this the way it works
for all webservice stacks?> > If you did support such an absolute reference,
how would you specify credentials to access the testSchema.xsd if the example
site: http://www.sas.com was secured. You wouldn't want to specify clear text
credentials in the wsdl:> http://username:[EMAIL PROTECTED]/testSchema.xsd.> >
FYI: You can't use a file URI either: file:///c:/testSchema.xsd.> > I'm
thinking that a referenced schema must be relative to the wsdl by design, but I
couldn't find any verbage to back up my suspicion.> > Anyone else have any
thoughts.> > Thanks.> > Tony Dean> SAS Institute Inc.> 919.531.6704> [EMAIL
PROTECTED]> > SAS... The Power to Know> http://www.sas.com> > > >
-> To
unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL
PROTECTED]>
_
Make distant family not so distant with Windows Vista® + Windows Live™.
http://www.microsoft.com/windows/digitallife/keepintouch.mspx?ocid=TXT_TAGLM_CPC_VideoChat_distantfamily_012008
wsdl/schema import
Hi, I am importing a schema as follows: http://www.sas.com/testSchema.xsd/"; /> ... This fails with error message: Unable to locate with a locator the schema referenced at '...' relative to document base 'meta-inf/mywsdl.wsdl. It appears that the Axis2 wsdl processor can only reference schemas relative to the location of the wsdl itself. If I change the import to: and add testSchema.xsd to meta-inf/ directory in the AAR, it works. I checked WS-I Basic Profile 1.1 and didn't see any limitation on schemaLocation. The XML Schema spec does say that this attribute is only a hint. Is it possible to reference a schema that is not relative to the wsdl? Is this an Axis2 shortfall or is this the way it works for all webservice stacks? If you did support such an absolute reference, how would you specify credentials to access the testSchema.xsd if the example site: http://www.sas.com was secured. You wouldn't want to specify clear text credentials in the wsdl: http://username:[EMAIL PROTECTED]/testSchema.xsd. FYI: You can't use a file URI either: file:///c:/testSchema.xsd. I'm thinking that a referenced schema must be relative to the wsdl by design, but I couldn't find any verbage to back up my suspicion. Anyone else have any thoughts. Thanks. Tony Dean SAS Institute Inc. 919.531.6704 [EMAIL PROTECTED] SAS... The Power to Know http://www.sas.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
POJO ComplexObject namespace generation
Hello.
I'm using Pojo mechanism in Axis2 to define some Web Services.
Such services manage instances of my own classes. Here is a Java
interface for one of these services :
### NewsDataSourceInterface.java
package fr.unice.i3s.rainbow.seduite.dataSources.news;
public interface NewsDataSourceInterface {
public News read(int id) throws Exception;
public News[] readThemAll() throws Exception;
}
###
News class definition is the following :
### News.java
public class News implements Serializable {
private int id;
private String author;
private String title;
private String content;
private String entryDate;
// getters & setters ...
}
###
Service business code is basically defined in NewsDataSourceImpl.
I'm creating my aar file without any problems, but the generated WSDL I
retrieve from Axis2 is the following :
http://schemas.xmlsoap.org/wsdl/";
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
xmlns:ns0="http://news.dataSources.seduite.rainbow.i3s.unice.fr/xsd";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
xmlns:ns1="http://news.dataSources.seduite.rainbow.i3s.unice.fr";
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
targetNamespace="http://news.dataSources.seduite.rainbow.i3s.unice.fr";>
http://news.dataSources.seduite.rainbow.i3s.unice.fr/xsd";
attributeFormDefault="qualified"
elementFormDefault="qualified"
targetNamespace="http://news.dataSources.seduite.rainbow.i3s.unice.fr/xsd";>
nillable="true" type="xs:string"/>
nillable="true" type="xs:string"/>
nillable="true" type="xs:string"/>
nillable="true" type="xs:string"/>
type="xs:long"/>
Even if I use a inside my services.xml
descriptor, the complex object News is always generated inside a
"/xsd"-postfixed namespace.
Such definition seems to be non compatible with Eclipse BPEL Designer
mechanisms, as the designer is unable to understand my News data type
when I try to invoke this WS inside a BPEL Process.
Is there a way to avoid the xsd-postifing ?
Cheers,
--
Sebastian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
I'm not completely clear on your setup but it seems to me you are creating a ConfigurationContext yourself or are not loading the same axis2.xml as you showed me - which is why putting axis2 in debug would help as it would confirm the soapmonitorPhase is being loaded in inflow. Anywhich way though, what you are lacking is getting the soapmonitorPhase configured in inflow - be it via axis2.xml, ConfigurationContext etc. Are you able to engage and run the other modules like logging and ping ok in your embedded setup? Can you load the phases programtically in your embedded setup? See the unit tests in the src tree for how to do phase loading programtically - sorry for being a bit vague here but looking at the source is the quickest way to tackle advance cases like this. HTH, Robert On Jan 4, 2008 12:39 PM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Robert, > > I get that error if I run an embedded version of axis2. If I deploy > it to tomcat (clean setup) it works fine. > > Jan 4, 2008 3:36:45 PM org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-8080 > Jan 4, 2008 3:36:45 PM org.apache.catalina.startup.Catalina load > INFO: Initialization processed in 1011 ms > Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardService start > INFO: Starting service Catalina > Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardEngine start > INFO: Starting Servlet Engine: Apache Tomcat/6.0.14 > Jan 4, 2008 3:36:46 PM org.apache.catalina.startup.HostConfig deployWAR > INFO: Deploying web application archive axis2.war > [INFO] Deploying module: addressing-1.3 > [INFO] Deploying module: metadataExchange-1.3 > [INFO] Deploying module: ping-1.3 > [INFO] Deploying module: script-1.3 > [INFO] Deploying module: soapmonitor-1.3 > [INFO] script module activated > [INFO] HTTP Sender starting > [INFO] Deploying Web service: version.aar > Jan 4, 2008 3:36:50 PM org.apache.coyote.http11.Http11Protocol start > INFO: Starting Coyote HTTP/1.1 on http-8080 > Jan 4, 2008 3:36:50 PM org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > Jan 4, 2008 3:36:50 PM org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/52 config=null > Jan 4, 2008 3:36:50 PM org.apache.catalina.startup.Catalina start > INFO: Server startup in 5161 ms > > > Any idea? > Michele > > > On 4 Jan 2008, at 14:50, robert lazarski wrote: > > > Michele, can you post your entire stacktrace please? I can't match the > > error you get with current svn. The error you are getting indicates no > > soapmonitorPhase in inflow, yet your axis2.xml does have it. So > > sorry, no clear indication of the problem yet. You could try putting > > axis2 in debug to see the phases loaded, which may flush out the error > > by confirming the phase isn't loaded. > > > > Alternatively, try out tcpmon ;-) . > > > > Good luck, > > Robert > > > > On Jan 4, 2008 10:11 AM, Michele Mazzucco > > <[EMAIL PROTECTED]> wrote: > >> Robert, > >> > >> if the module is globally engaged I get the error I mentioned in my > >> previous email. The same happens also if I "dynamically" engage the > >> module. > >> > >> Michele > >> > >> > >> On 4 Jan 2008, at 12:01, robert lazarski wrote: > >> > >>> You need to engage the module. Search for: > >>> > >>> > >>> > >>> Then in the same place, add: > >>> > >>> > >>> > >>> HTH, > >>> Robert > >>> > >>> On Jan 4, 2008 8:44 AM, Michele Mazzucco > >>> <[EMAIL PROTECTED]> wrote: > Robert, > > in axis2 1.3 all the phases needed by the soap monitor module are > already included. > > > > > Michele > > On 4 Jan 2008, at 11:07, robert lazarski wrote: > > > The exception is pretty self descriptive... show us the entire > > axis2.xml and maybe we can help. > > > > Robert > > > > On Jan 4, 2008 7:39 AM, Michele Mazzucco > > <[EMAIL PROTECTED]> wrote: > >> Hi all, > >> > >> I can't enage the soapmonitor module under Axis2 1.3 because > >> of the > >> following error > >> org.apache.axis2.phaseresolver.PhaseException: Did not find the > >> desired phase 'soapmonitorPhase' while deploying handler > >> 'InFlowSOAPMonitorHandler'. > >> > >> My axis2.xml differs from the default one only because of the NIO > >> transport listener. > >> > >> > >> Any idea? > >> > >> Thanks, > >> Michele > >> > >> > >> - > >> -- > >> -- > >> 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] Unable to engage the soap monitor module (axis2 1.3)
Robert, I get that error if I run an embedded version of axis2. If I deploy it to tomcat (clean setup) it works fine. Jan 4, 2008 3:36:45 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Jan 4, 2008 3:36:45 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1011 ms Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.14 Jan 4, 2008 3:36:46 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive axis2.war [INFO] Deploying module: addressing-1.3 [INFO] Deploying module: metadataExchange-1.3 [INFO] Deploying module: ping-1.3 [INFO] Deploying module: script-1.3 [INFO] Deploying module: soapmonitor-1.3 [INFO] script module activated [INFO] HTTP Sender starting [INFO] Deploying Web service: version.aar Jan 4, 2008 3:36:50 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Jan 4, 2008 3:36:50 PM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Jan 4, 2008 3:36:50 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/52 config=null Jan 4, 2008 3:36:50 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 5161 ms Any idea? Michele On 4 Jan 2008, at 14:50, robert lazarski wrote: Michele, can you post your entire stacktrace please? I can't match the error you get with current svn. The error you are getting indicates no soapmonitorPhase in inflow, yet your axis2.xml does have it. So sorry, no clear indication of the problem yet. You could try putting axis2 in debug to see the phases loaded, which may flush out the error by confirming the phase isn't loaded. Alternatively, try out tcpmon ;-) . Good luck, Robert On Jan 4, 2008 10:11 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, if the module is globally engaged I get the error I mentioned in my previous email. The same happens also if I "dynamically" engage the module. Michele On 4 Jan 2008, at 12:01, robert lazarski wrote: You need to engage the module. Search for: Then in the same place, add: HTH, Robert On Jan 4, 2008 8:44 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, in axis2 1.3 all the phases needed by the soap monitor module are already included. Michele On 4 Jan 2008, at 11:07, robert lazarski wrote: The exception is pretty self descriptive... show us the entire axis2.xml and maybe we can help. Robert On Jan 4, 2008 7:39 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Hi all, I can't enage the soapmonitor module under Axis2 1.3 because of the following error org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'soapmonitorPhase' while deploying handler 'InFlowSOAPMonitorHandler'. My axis2.xml differs from the default one only because of the NIO transport listener. Any idea? Thanks, Michele - -- -- 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] --- -- 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to acquire necessary Axis2-jars via Maven2
Hello Axis-users, i assume, this is an easy one for you: I want to setup a basic Maven2-based Axis2 project from scratch. The core structure is given by the following projects: 1. a project to generate the aar-jar which contains the generated stubs/skeletons for the wsdl-file via the m2 wsdl2code plugin (version 1.3) 2. a project to generate the aar based on the aar-jar via the m2 aar-plugin 3. a project to generate the war based on the aar 4. a project to generate the ear based on the war i'm able to successfully deploy the ear into an appserver. Now i'm trying to implement a junit-test, which needs a dependency to axis2-kernel which i can only find in version 1.0 in the public repositories. During runtime of the test i get an incompatible class error, probably due to the fact, that i'm using V1.0 of axis2-kernel and the generated aaj-jar is based on the wsdl2code-plugin with version 1.3. I cannot find an M2-repository offering me the latest (1.3) Axis2 components. Is there a reason why axis2 1.3 isn't published as an m2 repository? Is there any alternative to the manuall installation of all necessary Axis2-components in my local repository with all the dependencies I thougt Maven would care about? Thanks in advance, Thomas
[Axis2] try to get help again about handler
hi,dear all: i'm puzzled with the axis2 handler coding.here's my question beneath: 1.what's the difference between msgCtx.pause() and return InvocationResponse.SUSPEND? 2.when a handler in OutFlow try to suspend the execute chain by pause() or return InvocationResponse.SUSPEND,it doesn't work and return a axisFault? 3.when i return the InvocationResponse.SUSPEND ,then try to use AxisEngine.resume(msgCtx) method ,the suspended execute chain dont't resume and return response ,is there anything other to do to resume it? since the article about it is not much , so i spent much time on it ,and any information is appreciated very much. Thank you in advance. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WSS4J, AXIS1.X, WSE (interop)
Hello everybody, I would like to ask the developers (or if someone knows) from WSS4J or AXIS 1.X world if there is interoperability scenarios that *works* with: AXIS + WSS4J (server side with tomcat) and WSE2.0 or WSE3.0 using digital certificates. Any information will be very much appreciated. Thank you in advance.
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Michele, can you post your entire stacktrace please? I can't match the error you get with current svn. The error you are getting indicates no soapmonitorPhase in inflow, yet your axis2.xml does have it. So sorry, no clear indication of the problem yet. You could try putting axis2 in debug to see the phases loaded, which may flush out the error by confirming the phase isn't loaded. Alternatively, try out tcpmon ;-) . Good luck, Robert On Jan 4, 2008 10:11 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Robert, > > if the module is globally engaged I get the error I mentioned in my > previous email. The same happens also if I "dynamically" engage the > module. > > Michele > > > On 4 Jan 2008, at 12:01, robert lazarski wrote: > > > You need to engage the module. Search for: > > > > > > > > Then in the same place, add: > > > > > > > > HTH, > > Robert > > > > On Jan 4, 2008 8:44 AM, Michele Mazzucco > > <[EMAIL PROTECTED]> wrote: > >> Robert, > >> > >> in axis2 1.3 all the phases needed by the soap monitor module are > >> already included. > >> > >> > >> > >> > >> Michele > >> > >> On 4 Jan 2008, at 11:07, robert lazarski wrote: > >> > >>> The exception is pretty self descriptive... show us the entire > >>> axis2.xml and maybe we can help. > >>> > >>> Robert > >>> > >>> On Jan 4, 2008 7:39 AM, Michele Mazzucco > >>> <[EMAIL PROTECTED]> wrote: > Hi all, > > I can't enage the soapmonitor module under Axis2 1.3 because of the > following error > org.apache.axis2.phaseresolver.PhaseException: Did not find the > desired phase 'soapmonitorPhase' while deploying handler > 'InFlowSOAPMonitorHandler'. > > My axis2.xml differs from the default one only because of the NIO > transport listener. > > > Any idea? > > Thanks, > Michele > > > --- > -- > 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] > >>> > >> > >> > >> > >> - > >> 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] > > > > > - > 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] Unable to engage the soap monitor module (axis2 1.3)
Robert, if the module is globally engaged I get the error I mentioned in my previous email. The same happens also if I "dynamically" engage the module. Michele On 4 Jan 2008, at 12:01, robert lazarski wrote: You need to engage the module. Search for: Then in the same place, add: HTH, Robert On Jan 4, 2008 8:44 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, in axis2 1.3 all the phases needed by the soap monitor module are already included. Michele On 4 Jan 2008, at 11:07, robert lazarski wrote: The exception is pretty self descriptive... show us the entire axis2.xml and maybe we can help. Robert On Jan 4, 2008 7:39 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Hi all, I can't enage the soapmonitor module under Axis2 1.3 because of the following error org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'soapmonitorPhase' while deploying handler 'InFlowSOAPMonitorHandler'. My axis2.xml differs from the default one only because of the NIO transport listener. Any idea? Thanks, Michele --- -- 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
You need to engage the module. Search for: Then in the same place, add: HTH, Robert On Jan 4, 2008 8:44 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Robert, > > in axis2 1.3 all the phases needed by the soap monitor module are > already included. > > > > > Michele > > On 4 Jan 2008, at 11:07, robert lazarski wrote: > > > The exception is pretty self descriptive... show us the entire > > axis2.xml and maybe we can help. > > > > Robert > > > > On Jan 4, 2008 7:39 AM, Michele Mazzucco > > <[EMAIL PROTECTED]> wrote: > >> Hi all, > >> > >> I can't enage the soapmonitor module under Axis2 1.3 because of the > >> following error > >> org.apache.axis2.phaseresolver.PhaseException: Did not find the > >> desired phase 'soapmonitorPhase' while deploying handler > >> 'InFlowSOAPMonitorHandler'. > >> > >> My axis2.xml differs from the default one only because of the NIO > >> transport listener. > >> > >> > >> Any idea? > >> > >> Thanks, > >> Michele > >> > >> > >> - > >> 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] > > > > > > - > 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] Unable to engage the soap monitor module (axis2 1.3)
Robert, in axis2 1.3 all the phases needed by the soap monitor module are already included. axis2-xml.tar.gz Description: GNU Zip compressed data Michele On 4 Jan 2008, at 11:07, robert lazarski wrote: The exception is pretty self descriptive... show us the entire axis2.xml and maybe we can help. Robert On Jan 4, 2008 7:39 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Hi all, I can't enage the soapmonitor module under Axis2 1.3 because of the following error org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'soapmonitorPhase' while deploying handler 'InFlowSOAPMonitorHandler'. My axis2.xml differs from the default one only because of the NIO transport listener. Any idea? Thanks, Michele - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Rampart axis fault
I i have deployed a WS with WSSecurity using rampart ( also uses addressing and Notifications ) and when i send a message to the server from my client i allways get the following axis faul: org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed [java] at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434) [java] at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373) Reading the code this is at the first step of verification and i think i have something wrongly configured so please help me to find where in my config files is the bug. CLIENT side is a WS with this config : Timestamp Signature Encrypt client org.apache.rampart.samples.sample10.PWCBHandler client.properties DirectReference SKIKeyIdentifier client client.properties Timestamp Signature Encrypt org.apache.rampart.samples.sample10.PWCBHandler client.properties And the SERVER side is like this: Timestamp Signature Encrypt org.apache.rampart.samples.sample10.PWCBHandler service.properties Timestamp Signature Encrypt service org.apache.rampart.samples.sample10.PWCBHandler service.properties DirectReference SKIKeyIdentifier useReqSigCert -- View this message in context: http://www.nabble.com/Rampart-axis-fault-tp14613784p14613784.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Hi Michele, You have to add the soapmonitorPhase ( at the moment ) to the axis2.xml to use soap monitor module. You can find the details here [1]. Thanks, Nandana [1] - http://ws.apache.org/axis2/1_3/soapmonitor-module.html On Jan 4, 2008 3:09 PM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Hi all, > > I can't enage the soapmonitor module under Axis2 1.3 because of the > following error > org.apache.axis2.phaseresolver.PhaseException: Did not find the > desired phase 'soapmonitorPhase' while deploying handler > 'InFlowSOAPMonitorHandler'. > > My axis2.xml differs from the default one only because of the NIO > transport listener. > > > Any idea? > > Thanks, > Michele > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
The exception is pretty self descriptive... show us the entire axis2.xml and maybe we can help. Robert On Jan 4, 2008 7:39 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Hi all, > > I can't enage the soapmonitor module under Axis2 1.3 because of the > following error > org.apache.axis2.phaseresolver.PhaseException: Did not find the > desired phase 'soapmonitorPhase' while deploying handler > 'InFlowSOAPMonitorHandler'. > > My axis2.xml differs from the default one only because of the NIO > transport listener. > > > Any idea? > > Thanks, > Michele > > > - > 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]
[Axis2] Unable to engage the soap monitor module (axis2 1.3)
Hi all, I can't enage the soapmonitor module under Axis2 1.3 because of the following error org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'soapmonitorPhase' while deploying handler 'InFlowSOAPMonitorHandler'. My axis2.xml differs from the default one only because of the NIO transport listener. Any idea? Thanks, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
