RE: Axis2 problem with invoking methodes through GET requests
Keith, The problem is that when I use GET request, SOAP packet looks like: http://www.w3.org/2003/05/soap-envelope";> 123456789 0 false But stubs are expecting that param should be in the same namespace as makeCall: 123456789 0 false I debugged a bit and found out, that schema, generated for service in runtime doesn't contain namespaces for parameters. From: keith chapman [mailto:keithgchap...@gmail.com] Sent: Wednesday, February 11, 2009 8:45 AM To: axis-user@ws.apache.org Subject: Re: Axis2 problem with invoking methodes through GET requests Hi, In this case if you send a request into axis2 as http://localhost:8080/axis2/services/serviceName/makeCall?param0=SomeValue¶m1=someValue¶m2=someValue it should work just fine. Your schema contains just elements, From your initial post I thought they contained attributes as well. If they did then it would not work. Thanks, Keith. On Tue, Feb 10, 2009 at 5:21 PM, Valerly Provalov wrote: Sure, http://blabla.blabla.com";> ... ... ... ... And operation is defined as: From: keith chapman [mailto:keithgchap...@gmail.com] Sent: Tuesday, February 10, 2009 1:57 PM To: axis-user@ws.apache.org Subject: Re: Axis2 problem with invoking methodes through GET requests Hi Valeriy, Could you post the XML Schema section that defines this message that your refering to. Thanks, Keith. On Tue, Feb 10, 2009 at 3:10 PM, Valerly Provalov wrote: Hi all, I use skeleton generated by WSDL2Java. While parsing request, generated stubs checks attributes namespaces something like this: if ( reader.isStartElement() && new javax.xml.namespace.QName(, ).equals(reader.getName()) Everything works fine with generated stubs, but doesn't with GET requests. In this case, generated SOAP packet doesn't contain attributes namespace for method parameters. Is there any solution for this problem? Regards, Valeriy. -- This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Five 9, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. -- -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org -- This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Five 9, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. -- -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org -- This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Five 9, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. --
Re: Axis2 problem with invoking methodes through GET requests
Hi, In this case if you send a request into axis2 as http://localhost:8080/axis2/services/serviceName/makeCall?param0=SomeValue¶m1=someValue¶m2=someValue it should work just fine. Your schema contains just elements, From your initial post I thought they contained attributes as well. If they did then it would not work. Thanks, Keith. On Tue, Feb 10, 2009 at 5:21 PM, Valerly Provalov wrote: > Sure, > > elementFormDefault="qualified" > targetNamespace="http://blabla.blabla.com";> >... >... > > > > > > > > > >... >... > > And operation is defined as: > > > wsaw:Action="urn:makeCall"/> > wsaw:Action="urn:makeCallResponse"/> > name="AgentBridgeException" wsaw:Action="urn:makeCallException"/> > > > > > > > From: keith chapman [mailto:keithgchap...@gmail.com] > Sent: Tuesday, February 10, 2009 1:57 PM > To: axis-user@ws.apache.org > Subject: Re: Axis2 problem with invoking methodes through GET requests > > Hi Valeriy, > > Could you post the XML Schema section that defines this message that > your refering to. > > Thanks, > Keith. > On Tue, Feb 10, 2009 at 3:10 PM, Valerly Provalov > wrote: > Hi all, > > I use skeleton generated by WSDL2Java. While parsing request, generated > stubs checks attributes namespaces something like this: > > if ( reader.isStartElement() && new > javax.xml.namespace.QName(, > ).equals(reader.getName()) > > Everything works fine with generated stubs, but doesn't with GET > requests. In this case, generated SOAP packet doesn't contain attributes > namespace for method parameters. Is there any solution for this problem? > > Regards, > Valeriy. > > > -- > This e-mail message is for the sole use of the intended recipient(s) and > contains confidential and/or privileged information belonging to > Five 9, Inc. or its customers or partners. Any unauthorized review, use, > copying, disclosure or distribution of this message is strictly > prohibited. If you are not an intended recipient of this message, please > contact the sender by reply e-mail and destroy all soft and hard copies > of the message and any attachments. > Thank you for your cooperation. > -- > > > > -- > Keith Chapman > Senior Software Engineer > WSO2 Inc. > Oxygenating the Web Service Platform. > http://wso2.org/ > > blog: http://www.keith-chapman.org > > > -- > This e-mail message is for the sole use of the intended recipient(s) and > contains confidential and/or privileged information belonging to > Five 9, Inc. or its customers or partners. Any unauthorized review, use, > copying, disclosure or distribution of this message is strictly > prohibited. If you are not an intended recipient of this message, please > contact the sender by reply e-mail and destroy all soft and hard copies of > the message and any attachments. > Thank you for your cooperation. > -- > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
Re: Need Help On AXIS2
Also this might help, Hello World with Apache Axis2 [1] [1] http://wso2.org/library/95/ Thanks, Keith. On Tue, Feb 10, 2009 at 5:56 PM, wrote: > Hi All, > > I am new to web service, i need to develop web service client > and and services. > > Please guide me to go ahead and develop the same. > > > > Regards, > Shilpa > > * Please do not print this email unless it is absolutely necessary. * > > 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 > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
Re: [axis2] Multiref client request to axis2 service
On Tue, Feb 10, 2009 at 11:50 AM, Ashwini Chavan wrote: > I am still stuck on this. Can someone help me? Does axis2 support > multi-ref soap request? it does not support this. and soap encoding. thanks, Amila. > > > 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 the original > message 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. > > Please do not print this email unless it is absolutely necessary. > > -- Forwarded message -- > From: Ashwini Chavan > To: axis-...@ws.apache.org > Date: Fri, 06 Feb 2009 11:17:39 +0530 > Subject: [axis2] Multiref client request to axis2 service > I am newbie to webservice. My axis2 webservice is generated using > wsdl2java tool with XMLBeans data binding extension. Webservice client > is sending multiref soap envelope in the request. My WSDL is > document/encoded. > I have attached my WSDL file and the client request soap envelope that I > receive. > I am receiving the values of input parameters as null in the service. > Can someone help me to find out why? Do I need to do any more changes? > please help > > Also, in the web service response, content-length is not getting set. My > web service is deployed on tomcat. I also tested this with the > standalone axis2 server. > My client request is using HTTP/1.0 protocol and hence tranfer-encoding > chunked is disabled. > > Any response should be of great help. > > Thanks and regards, > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; >xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > >soapenv:encodingStyle=" > http://schemas.xmlsoap.org/soap/encoding/"; >xmlns:ns1="http://www.example.org/test/";> > > >soapenv:encodingStyle=" > http://schemas.xmlsoap.org/soap/encoding/"; >xsi:type="ns2:data" >xmlns:soapenc=" > http://schemas.xmlsoap.org/soap/encoding/"; >xmlns:ns2="http://www.example.org/test/";> >100.100.100.100 > > >soapenv:encodingStyle=" > http://schemas.xmlsoap.org/soap/encoding/"; >xsi:type="ns3:statusCode" >xmlns:ns3="http://www.example.org/test/"; >xmlns:soapenc=" > http://schemas.xmlsoap.org/soap/encoding/";> >1 > > > > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Need Help On AXIS2
On Tue, Feb 10, 2009 at 5:56 PM, wrote: > Hi All, > > I am new to web service, i need to develop web service client > and and services. > > Please guide me to go ahead and develop the same. > Please read the user guide. thanks, Amila. > > > > Regards, > Shilpa > > * Please do not print this email unless it is absolutely necessary. * > > 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 > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Issue with Axis OMElement
Hi,
The problem us that your WSDL specifies the type as xs:any. When sending out
binary data (as Mtom or as Base64) the type of the element should be
type="xs:base64Binary". The stub will take care of it if the attachment is
Mtom or Base64.
Thanks,
Keith.
On Wed, Feb 11, 2009 at 12:18 AM, Sathish C wrote:
> Martin,
>
> That is a good hint. I require Binary optimization and so i am having this
> parameter value set to 'true'.
>
> Now I tried disabling MTOM, so the content is embedded within the
> element (I had to modify generated WSDL to specify
> element to contain ) and not binary optimized so
> that there is no element created. The below issue on <"*
> com.ctc.wstx.exc.WstxParsingException*: Expected a text token, got
> START_ELEMENT"> DOES NOT occur anymore. I made three observations as below
> and their respective queries:
>
> 1) When I return a binary optimized content as OMText, i am having to
> introduce an OMElement to contain it and hence the element in
> the below excerpt of response string. Stub finds this element instead of
> text and throws the error <"*com.ctc.wstx.exc.WstxParsingException*:
> Expected a text token, got START_ELEMENT"> .
> Is there a way to avoid this additional element and attach optimized
> content directly?
>
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope
> ">
> xmlns:ns="http://ws.apache.org/axis2";>
>
> http://www.w3.org/2004/08/xop/include"; />
>
>
> 2) As shown above, the binary optimized content is not set inline within
> element, but as attachment referred by element. The
> stub again throws the error looking at element. The generated
> stub looks for text token for element of type xs:any defined in WSDL. How
> can I make the generated stub sensitive of element and look
> through its reference instead of looking for text content?
>
> 3) When MTOM is disabled, stub is able to construct the OMElement from the
> embedded text content. Is there a way to generate the stub being MTOM aware
> and able to handle element?
>
> Any suggestions/insight on this would be very much appreciated.
>
> Regards,
> Sathish C
>
>
> On Tue, Feb 10, 2009 at 3:06 AM, Martin Gainty wrote:
>
>> can you display the value of enableMtom in axis2.xml?
>>
>> true
>>
>> assuming you are sending XML Binary Optimised Packages
>>
>> *http://ws.apache.org/axis2/0_94/mtom-guide.html*
>> ?
>> Martin
>> __
>> Disclaimer and confidentiality note
>> Everything 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.
>>
>>
>>
>>
>> --
>> Date: Tue, 10 Feb 2009 07:32:11 +0530
>> Subject: Re: Issue with Axis OMElement
>> From: keithgchap...@gmail.com
>>
>> To: axis-user@ws.apache.org
>>
>> Its hard to say what went wrong where from this. The reason it happened is
>> because of some malformed XML. That's all I can tell you looking at the
>> stack trace.
>>
>> Thanks,
>> Keith.
>>
>> On Mon, Feb 9, 2009 at 11:43 PM, Chandra suriya pandian, Sathish (GE
>> Infra, Energy) wrote:
>>
>> Thanks Keith.
>>
>> I am able to get through that error by changing the type to xs:any.
>> But now i am getting the following exception under the same scenario:
>>
>>
>> Caused by:
>> *com.ctc.wstx.exc.WstxParsingException*: Expected a text token, got
>> START_ELEMENT.
>>
>> at [row,col {unknown-source}]: [1,208]
>>
>> at com.ctc.wstx.sr.StreamScanner.constructWfcException(*
>> StreamScanner.java:605*)
>>
>> at com.ctc.wstx.sr.StreamScanner.throwParseError(*StreamScanner.java:461*
>> )
>>
>> at com.ctc.wstx.sr.BasicStreamReader.getElementText(*
>> BasicStreamReader.java:677*)
>> at org.apache.axiom.om.impl.llom.OMStAXWrapper.getElementText(*
>> OMStAXWrapper.java:899*)
>>
>> Any idea on the above problem.
>>
>> Regards,
>> *Sathish Chandra***
>>
>>
>> --
>> *From:* keith chapman [mailto:keithgchap...@gmail.com]
>> *Sent:* 09 February 2009 16:29
>> *To:* axis-user@ws.apache.org
>> *Subject:* Re: Issue with Axis OMElement
>>
>> Hi,
>>
>> This is due to a bug in Axis2. Ideally an OMElement should map to xs:any
>> and not xs:anyType in the WSDL. Therefore the workaround I could suggest is
>> this, Save the WSDL and edit it to use xs:any instead of xs:anyType.
>>
>> Thanks,
>> Keith.
>>
>> On Mon, Feb 9, 2009 at 8:30 PM, Chandra suriya pandian, Sathish (GE Infra,
>> Energy) wrote:
>>
>> Hi,
>>
>> > I have WebService enabled a service method that returns OMElement. The
>> > generated WSDL shows the element type as 'anyType'.
>> >
>> > I generated a stub from the WSDL and executed a client invoking the
>> > WebService method through the stub.
>> >
>> > The HTTP trace shows the response stream returned by WebService is
>> > correct.
>> > But in the client I am getting
Axis2 server with swing frontend - how do I do this?
Hi folks I found tutorials on Swing frontend acting as an Axis2 client only so far. Would you like to seek your advice whether this possible and how to go about it. :-) Currently I have a POJO with say, a method like 'sayHello' . That method echos the message it receives to the command line. When I run it in Axis2, Axis2 dynamically generates the WSDL and everything works great - I can connect to my POJO and send messages through etc etc. Now instead of having my POJO write to the command line, I'd like to first have a Swing UI appear. When my client sends messages across I would like those messages to appear in, say, a JTextArea (or similar) :) The problem is I can't see how to go about this. If I try to have my POJO instantiate my Swing UI, nothing happens (no UI appears). On the other hand I tried to first instantiate my Swing UI, THEN create my POJO by embedding Axis2. This doesn't work either . I also can't figure out how to pass parameters between the two classes. Appreciate your advice please :) Thanks! -- View this message in context: http://www.nabble.com/Axis2-server-with-swing-frontend---how-do-I-do-this--tp21947967p21947967.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Rampart - axis2 fault
Does anyone know about this 'actions mismatch' error? I keep getting it for quite a few of the examples. What is the mismatch on? Thanks for any help, --kumar From: Iyengar, Kumar [mailto:kumar_iyen...@bmc.com] Sent: Monday, February 09, 2009 1:29 PM To: axis-user@ws.apache.org Subject: RE: Rampart - axis2 fault Thanks Nandana for the quick response. Here is the XML that Soap UI sends. I have set the action in services.xml to 'UsernameToken Timestamp' and so SoapUI is sending the password bobPW as a digest Host: localhost:8080 Content-Length: 1053 SOAPAction: "urn:echo" User-Agent: Jakarta Commons-HttpClient/3.0.1 Content-Type: text/xml;charset=UTF-8 http://sample02.samples.rampart.apache.org"; xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse curity-secext-1.0.xsd"> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec urity-utility-1.0.xsd"> bob http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-t oken-profile-1.0#PasswordDigest">b+iddlgeF2hcpof8WQ/iEYo5QEw= B1NdVICiOB2XBBZHQ66ijg== 2009-02-09T21:16:43.652Z How R U I will look at the samples. Unfortunately at this point, I have to get an app working (with Username Token and eventually X509) without depending on Policy. I installed the Sample02, 03 onto a Tomcat server that has Axis2 installed along with Rampart. I can get a simple request without any username token working with SoapUI as the client. Thanks for any help, --kumar From: Nandana Mihindukulasooriya [mailto:nandana@gmail.com] Sent: Monday, February 09, 2009 12:07 PM To: axis-user@ws.apache.org Subject: Re: Rampart - axis2 fault Hi Kumar, Can you please post the SOAP message sent by SOAP UI ? Anyway if you starting to use Rampart, I would recommend you to use policy based approach which is more interoperable and most of the development for new specifications is only available in the policy based configuration. You can look at Rampart policy samples in the binary distribution and these two articles in WSO2 Oxygen Tank will also help you to get started. http://wso2.org/library/3190 https://wso2.org/library/3415 thanks, nandana On Tue, Feb 10, 2009 at 1:12 AM, Iyengar, Kumar wrote: Hi all, Thanks for the help earlier. I managed to get a bit further. I am trying to get the Rampart sample programs working but am getting the following error: [ERROR] WSDoAllReceiver: security processing failed (actions mismatch) org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed (actions mismatch) at org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver. java:344) at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceive r.java:86) at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72) at org.apache.axis2.engine.Phase.invoke(Phase.java:317) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques t(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :126) 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:1 48) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:86 9) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc essConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint .java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow erWorkerThread.java:80) at org.apache.tomcat.util.threads.Th
Applying policies at binding hierarchy in Apache Axis2 1.4.1/Rampart 1.4
Hi everyone, based on this article: http://wso2.org/library/3786, I wrote my own (simple) wsdl with a policy attached to the soap binding. I load that wsdl with a WSDL11ToAxisServiceBuilder [1]. My issue is that when I invoke the service the following AxisFault is thrown: org.apache.axis2.AxisFault: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd: Security at org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:102) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:166) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) After a debugging session, it appears that the policy map of the AxisService holds a policy reference, but the policy include and subject do not. And the policy is never accessed by the RampartReceiver. Could you tell what I'm missing and/or point me to a working sample of embedded policy (I did not find any in Rampart repo)? Thanks in advance, Alexis [1] http://github.com/matthieu/apache-ode/blob/085025ab3639c7aa0255bbb9b905210ff6caf295/axis2/src/main/java/org/apache/ode/axis2/hooks/ODEAxisService.java#L80
Abstract classes in WSDL
Hello,
I have a simple abstract class exposed as part of an an Axis2 service.
When the service WSDL is generated, I expected the complexType
declaration for it to appear as follows:
...
Instead I only got:
...
The class is declared as follows:
public abstract class Test { ...
Is there something else needed to get the generated WSDL to represent
the abstract class?
Thanks,
Jason
creation of jar files- disk space problem
Hello, I'm having a problem where each time I connect to a web service, a jar file gets created (axis##axis2-1.4.jar) and never gets cleaned up, so I'm running out of space. I saw that bug AXIS-2314 which describes exactly the same problem, but it is marked RESOLVED and should have been fixed for 1.2. I'm using Windows XP with axis2 1.4. Should I enter a bug for this? Thanks, kim
Re: Ramapart Config based dynamic client sample code
Can someone give some pointers please.
Thanks,
cbear
On Mon, Feb 9, 2009 at 3:42 PM, Wishing Carebear wrote:
> Hello:Hoping someone could reply.
>
> Thanks for your time,
> Regards,
> cbear
>
>
> On Mon, Feb 9, 2009 at 11:42 AM, Wishing Carebear <
> wishing.careb...@gmail.com> wrote:
>
>> Could someone give some pointers.
>> Thanks,
>> cbear
>>
>>
>> On Fri, Feb 6, 2009 at 4:27 PM, Wishing Carebear <
>> wishing.careb...@gmail.com> wrote:
>>
>>> Hello:The OutflowConfiguration that works right now looks like below:
>>> private static Parameter getOutflowConfiguration() {
>>> OutflowConfiguration ofc = new OutflowConfiguration();
>>> ofc.setActionItems("Encrypt");
>>> ofc.setEncryptionUser("service");
>>> ofc.setEncryptionPropFile("client.properties");
>>> return ofc.getProperty();
>>> }
>>>
>>> Since the OutflowConfiguration is deprecated, would like to use
>>> RampartConfiguration is possible. Don't have any policy defined for the
>>> service. Found some examples of RampartConfig() as below:
>>>
>>> private static Policy getRampartConfig(){
>>> RampartConfig rampartConfig = new RampartConfig();
>>> rampartConfig.setUser("client");
>>> rampartConfig.setPwCbClass("samples.quickstart.clients.PWCBHandler");
>>> CryptoConfig sigCrypto = new CryptoConfig();
>>>
>>> sigCrypto.setProvider("org.apache.ws.security.components.crypto.Merlin");
>>> Properties props = new Properties();
>>> props.setProperty("org.apache.ws.security.crypto.merlin.keystore.type",
>>> "JKS");
>>>
>>> props.setProperty("org.apache.ws.security.crypto.merlin.file","client.jks");
>>> props.setProperty("org.apache.ws.security.crypto.merlin.keystore.password",
>>> "clientPW");
>>> sigCrypto.setProp(props);
>>> rampartConfig.setSigCryptoConfig(sigCrypto);
>>> Policy policy = new Policy();
>>> policy.addAssertion(rampartConfig);
>>> return policy;
>>> }
>>> But don't know how to bind this to the OperationClient. I also have to
>>> encrypt the request and decrycpt the response messages.
>>>
>>> Thanks,
>>> cbear
>>>
>>> On Fri, Feb 6, 2009 at 10:46 AM, Wishing Carebear <
>>> wishing.careb...@gmail.com> wrote:
>>>
Hello:Noticed that the OutflowConfiguration and InFlowConfiguration
classes are deprectaed.
Trying to see if RampartConfig could be used to get the same behavior.
Saw the policy based examples but could not find any code that could add
the
Rampart code programmitically.
1) Please point me to some examples where the RampartConfig is done
programmitically
2) I use the OperationClient to invoke webservices. Would like to add
the RampartConfig() to that. Is it possible
3) Also would like to know the equivalent of OutFlow and InFlow
configuration handlers using the RampartConfig.
Thanks for your help and time,
Regards
cabear
>>>
>>>
>>
>
Re: Issue with Axis OMElement
Martin,
That is a good hint. I require Binary optimization and so i am having this
parameter value set to 'true'.
Now I tried disabling MTOM, so the content is embedded within the
element (I had to modify generated WSDL to specify
element to contain ) and not binary optimized so
that there is no element created. The below issue on <"*
com.ctc.wstx.exc.WstxParsingException*: Expected a text token, got
START_ELEMENT"> DOES NOT occur anymore. I made three observations as below
and their respective queries:
1) When I return a binary optimized content as OMText, i am having to
introduce an OMElement to contain it and hence the element in
the below excerpt of response string. Stub finds this element instead of
text and throws the error <"*com.ctc.wstx.exc.WstxParsingException*:
Expected a text token, got START_ELEMENT"> .
Is there a way to avoid this additional element and attach optimized content
directly?
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope
">
xmlns:ns="http://ws.apache.org/axis2";>
http://www.w3.org/2004/08/xop/include"; />
2) As shown above, the binary optimized content is not set inline within
element, but as attachment referred by element. The
stub again throws the error looking at element. The generated
stub looks for text token for element of type xs:any defined in WSDL. How
can I make the generated stub sensitive of element and look
through its reference instead of looking for text content?
3) When MTOM is disabled, stub is able to construct the OMElement from the
embedded text content. Is there a way to generate the stub being MTOM aware
and able to handle element?
Any suggestions/insight on this would be very much appreciated.
Regards,
Sathish C
On Tue, Feb 10, 2009 at 3:06 AM, Martin Gainty wrote:
> can you display the value of enableMtom in axis2.xml?
>
> true
>
> assuming you are sending XML Binary Optimised Packages
>
> *http://ws.apache.org/axis2/0_94/mtom-guide.html*
> ?
> Martin
> __
> Disclaimer and confidentiality note
> Everything 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.
>
>
>
>
> --
> Date: Tue, 10 Feb 2009 07:32:11 +0530
> Subject: Re: Issue with Axis OMElement
> From: keithgchap...@gmail.com
>
> To: axis-user@ws.apache.org
>
> Its hard to say what went wrong where from this. The reason it happened is
> because of some malformed XML. That's all I can tell you looking at the
> stack trace.
>
> Thanks,
> Keith.
>
> On Mon, Feb 9, 2009 at 11:43 PM, Chandra suriya pandian, Sathish (GE Infra,
> Energy) wrote:
>
> Thanks Keith.
>
> I am able to get through that error by changing the type to xs:any.
> But now i am getting the following exception under the same scenario:
>
>
> Caused by:
> *com.ctc.wstx.exc.WstxParsingException*: Expected a text token, got
> START_ELEMENT.
>
> at [row,col {unknown-source}]: [1,208]
>
> at com.ctc.wstx.sr.StreamScanner.constructWfcException(*
> StreamScanner.java:605*)
>
> at com.ctc.wstx.sr.StreamScanner.throwParseError(*StreamScanner.java:461*)
>
> at com.ctc.wstx.sr.BasicStreamReader.getElementText(*
> BasicStreamReader.java:677*)
> at org.apache.axiom.om.impl.llom.OMStAXWrapper.getElementText(*
> OMStAXWrapper.java:899*)
>
> Any idea on the above problem.
>
> Regards,
> *Sathish Chandra***
>
>
> --
> *From:* keith chapman [mailto:keithgchap...@gmail.com]
> *Sent:* 09 February 2009 16:29
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Issue with Axis OMElement
>
> Hi,
>
> This is due to a bug in Axis2. Ideally an OMElement should map to xs:any
> and not xs:anyType in the WSDL. Therefore the workaround I could suggest is
> this, Save the WSDL and edit it to use xs:any instead of xs:anyType.
>
> Thanks,
> Keith.
>
> On Mon, Feb 9, 2009 at 8:30 PM, Chandra suriya pandian, Sathish (GE Infra,
> Energy) wrote:
>
> Hi,
>
> > I have WebService enabled a service method that returns OMElement. The
> > generated WSDL shows the element type as 'anyType'.
> >
> > I generated a stub from the WSDL and executed a client invoking the
> > WebService method through the stub.
> >
> > The HTTP trace shows the response stream returned by WebService is
> > correct.
> > But in the client I am getting the following error:
> >
> > org.apache.axis2.databinding.ADBException: Any type element type has
> > not been given
> > at
> > org.apache.axis2.databinding.utils.ConverterUtil.getAnyTypeObject(Conv
> > erterUtil.java:1612)
> >
> > Exerpt from WSDL is:
> >
> >
> >
> > > type="xs:anyType"/>
> >
> >
> >
> > Exerpt from the response stream is:
> >
> >
> > > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
> > > xmlns:ns="http://ws.apache.org/axis2";>
> > > href="cid
AW: InOnlyAxisOperation Error
Hi, i had the same problem with Axis2-1.4.1. Before I've updated to 1.4.1 i've used 1.3 and everything was working. My workaround was to add a return type to the method, to use the In-Out-MR any time. Maiko Von: Sanja Gupta [mailto:sanjay.gu...@primal.com] Gesendet: Montag, 9. Februar 2009 21:20 An: axis-user@ws.apache.org Betreff: RE: InOnlyAxisOperation Error Hi Keeth, I am running with the exploded classes directory and a services.xml file. I do have a .aar file but haven't tried it. Do you need to see anything specific like my java wrapper code. I am attaching my services.xml. Thanks Sanjay From: keith chapman [mailto:keithgchap...@gmail.com] Sent: Saturday, February 07, 2009 3:33 AM To: axis-user@ws.apache.org Subject: Re: InOnlyAxisOperation Error Could you post your service archive file. Thanks, Keith. On Sat, Feb 7, 2009 at 2:41 PM, Sanjay Gupta wrote: Agree but I don't see anything wrong with my services.xml. I am clueless on what would cause this issue. I looked at the client code as well and it's using RobustOutOnlyAxisOperation for the operation. Sanjay http://www.w3.org/ns/wsdl/in-only"; class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/> http://www.w3.org/ns/wsdl/in-out"; class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> -Original Message- From: keith chapman [mailto:keithgchap...@gmail.com] Sent: Fri 2/6/2009 7:40 PM To: axis-user@ws.apache.org Subject: Re: InOnlyAxisOperation Error >From the stack trace it looks like an InOutMessageReceiver was used for an InOnly Operation. Thanks, Keith. On Fri, Feb 6, 2009 at 11:27 PM, Sanjay Gupta wrote: > Keith, > Thanks for you reply and pointer. I tried your sugession but I am still > getting the error. Here is the stack trace. > Thanks > Sanjay > > [ERROR] An access occurred that is not valid. > java.lang.UnsupportedOperationException: An access occurred that is not > valid. > at > org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOp eration.java:109) > at > org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(Mess ageContextBuilder.java:190) > at > org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLo gic(AbstractInOutMessageReceiver.java > :37) > at > org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessa geReceiver.java:100) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques t(HTTPTransportUtils.java:275) > at > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:175) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :102) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:2 86) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:84 4) > > > > -Original Message- > From: keith chapman [mailto:keithgchap...@gmail.com > ] > Sent: Fri 2/6/2009 12:17 AM > To: axis-user@ws.apache.org > Subject: Re: InOnlyAxisOperation Error > > In your messageReceivers can you try using the following instead, > > > http://www.w3.org/ns/wsdl/in-only"; > class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/> > http://www.w3.org/ns/wsdl/in-out"; > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> > > > Thanks, > Keith. > > On Fri, Feb 6, 2009 at 11:50 AM, Sanjay Gupta >wrote: > > > Hi Keith, > > Here is my services.xml files. > > Thanks > > Sanjay > > > > > > http://provision.ws.ccb.primalsw.com/";> > > > > Provision Service > > > > > > http://www.w3.org/2004/08/wsdl/in-out"; > > > > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> > > http://www.w3.org/2004/08/wsdl/in-only"; > > > > class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/> > > > > > > http://provision.ws.ccb.primalsw.com/xsd"/> > > > name="ServiceClass">com.primalsw.ccb.ws.ProvisionHandler > > > > > > > > > > > > > > -Original Message- > > From: keith chapman [mailto:keithgchap...@gmail.com > > > ] > > Sent: Thu 2/5/2009 1
Need Help On AXIS2
Hi All, I am new to web service, i need to develop web service client and and services. Please guide me to go ahead and develop the same. Regards, Shilpa Please do not print this email unless it is absolutely necessary. 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
Re: How to intercept soap message from Client
> > Hi: > > I am trying to intercept the Client side SOAP messages. I have done the > following for the same: > > 1. extended class BasicHandler and implemented the invoke method. At > present it just contains a simple Syste.out.println method. > > 2. Since Client does not have a deployment file. Am doing the following in > my client code. > > > IRomanserviceLocator service = > *new* IRomanserviceLocator(); > > IRoman port = service.getIRomanPort(); > > QName portName = service.getServiceName(); > > *HandlerRegistry registry = service.getHandlerRegistry();* > > *List handlerList = * > *new** ArrayList(); * > > *handlerList.add( * > *new HandlerInfo( MyHandler.class, null, null** ) );* > > *registry.setHandlerChain( portName, handlerList );* > > System. > *out*.println( port.intToRoman(551) ); > > However it does not work. > > I tried implementing the Myhandler class by implementing the handler class > also. > > Could anyone help ? > > Thanks > > > >
RE: Axis2 problem with invoking methodes through GET requests
Sure, http://blabla.blabla.com";> ... ... ... ... And operation is defined as: From: keith chapman [mailto:keithgchap...@gmail.com] Sent: Tuesday, February 10, 2009 1:57 PM To: axis-user@ws.apache.org Subject: Re: Axis2 problem with invoking methodes through GET requests Hi Valeriy, Could you post the XML Schema section that defines this message that your refering to. Thanks, Keith. On Tue, Feb 10, 2009 at 3:10 PM, Valerly Provalov wrote: Hi all, I use skeleton generated by WSDL2Java. While parsing request, generated stubs checks attributes namespaces something like this: if ( reader.isStartElement() && new javax.xml.namespace.QName(, ).equals(reader.getName()) Everything works fine with generated stubs, but doesn't with GET requests. In this case, generated SOAP packet doesn't contain attributes namespace for method parameters. Is there any solution for this problem? Regards, Valeriy. -- This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Five 9, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. -- -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org -- This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Five 9, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. --
Re: Axis2 problem with invoking methodes through GET requests
Hi Valeriy, Could you post the XML Schema section that defines this message that your refering to. Thanks, Keith. On Tue, Feb 10, 2009 at 3:10 PM, Valerly Provalov wrote: > Hi all, > > I use skeleton generated by WSDL2Java. While parsing request, generated > stubs checks attributes namespaces something like this: > > if ( reader.isStartElement() && new > javax.xml.namespace.QName(, > ).equals(reader.getName()) > > Everything works fine with generated stubs, but doesn't with GET > requests. In this case, generated SOAP packet doesn't contain attributes > namespace for method parameters. Is there any solution for this problem? > > Regards, > Valeriy. > > > -- > This e-mail message is for the sole use of the intended recipient(s) and > contains confidential and/or privileged information belonging to > Five 9, Inc. or its customers or partners. Any unauthorized review, use, > copying, disclosure or distribution of this message is strictly > prohibited. If you are not an intended recipient of this message, please > contact the sender by reply e-mail and destroy all soft and hard copies of > the message and any attachments. > Thank you for your cooperation. > -- -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
Axis2 problem with invoking methodes through GET requests
Hi all, I use skeleton generated by WSDL2Java. While parsing request, generated stubs checks attributes namespaces something like this: if ( reader.isStartElement() && new javax.xml.namespace.QName(, ).equals(reader.getName()) Everything works fine with generated stubs, but doesn't with GET requests. In this case, generated SOAP packet doesn't contain attributes namespace for method parameters. Is there any solution for this problem? Regards, Valeriy. -- This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Five 9, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. --
