Re: JSON w/ REST

soapenv:Reason soapenv:Text xml:lang=en-US Mapped formatted JSON with namespaces are not supported in Axis2. Make sure that your request doesn't include namespaces or use the Badgerfish convention /soapenv:Text /soapenv:Reason Badgerfish Mapped are two JSON to XML conversion conventions..

action mappings in the service.xml file.

Hi, When I use wsdl2code to generate my services.xml, stubs and skeletons how do i control the actionMapping uris that are generated and used in these files. For instance the default actionMapping elements generated for my service are shown below operation name=SetupStartElement

Changing the namespace that is being generated by the Axis engine

Good Morning, How do you change the namespace that is used by the Axis engine when it generates the SOAP body and envelope tags? I am trying to call a .Net WS and it expects soap:Body and soap:Envelope, but soapenv:Body and soapenv:Envelope are being created. Thanks, Doug Example of what is

Nillable values in Axis 1.4

Hi I work with axis 1.3 in my wsdl declared type Test: s:complexType name=Test s:sequence s:element minOccurs=0 maxOccurs=1 name=boolField type=s: boolean / s:element minOccurs=1 maxOccurs=1 name=intField type=s:int nillable=true / s:element minOccurs=0

Re: Just point me in the right direction...

Hi All, I am having trouble in installing axis2 application on Websphere 6.1. Did anyone encounter this issue before ? Error: java.lang.NoSuchMethodError: javax/wsdl/Operation.getExtensibilityElements()Ljava/util/List; at

Axis2 on Websphere 6.1

Hi All, I am having trouble in installing axis2 application on Websphere 6.1. Did anyone encounter this issue before ? Error: java.lang.NoSuchMethodError: javax/wsdl/Operation.getExtensibilityElements()Ljava/util/List; at

Re: [Axis2] SOAP header elements

Deepal Jayasinghe wrote: Hi Jack , If this is in the server side , you can get the message context and from that you can get the SOAP envelope and from the soap envelope you can get the soap headers. If it is the in the client side , the the process is , - First you get the last

Re: Axis2 1.1.1 WSDL2JAVA - Not generating java classes for wsdl:portType

Hi, Just wondering if this is still an issue in Axis2 1.2 or I did not put the parameters properly. Thanks, -Bo On 5/17/07, Bo Xie [EMAIL PROTECTED] wrote: Thanks, Amila. I tried your advice using no -pn and -sn. It still only generated last one binding out of the 4. I used asix2 1.2

Re: Capturing the SOAP Message

Can't you listen to the port that Axis will be wrtiting at using the locahost (127.0.0.1) and print out the SOAP as XML text? Isn't that what you want to do? Martin Gainty wrote: Hard to determine what your looking for but looking at your ServiceLocator code the chronology would be something

Re: Changing the namespace that is being generated by the Axis engine

Hi Doug, The namespaces are the same in your two samples - the namespace *prefixes* are different (soapenv vs. soap), but these are just placeholders. I suspect the real issue is that your SOAP Body element is missing the expected Login element. How are you trying to call the service? -

Re: Changing the namespace that is being generated by the Axis engine

Dennis, It's interesting that you mentioned the Login element. Leaving it out was just a cut and paste mistake in the email, but I believe it is the problem. The error that I am trying to correct is There is an error in XML document (2, 16). --- The specified node cannot be inserted as the

Re: Changing the namespace that is being generated by the Axis engine

I don't know if it's just another copy-and-paste artifact, but the Login element namespace in your .NET sample has a leading space before the http://...;. If that space is really there, you'd need to have the space in your namespace, too. That's somewhat bizarre - namespace URIs should not

Re: [Axis2] SOAP header elements

OK. I was able to get the header elements using the getChildElements() method and iterating. But the XMLBenas question remains. How do I get at the class created by XMLBeans for these 2 header elements? Thanks, T Jack Sprat [EMAIL PROTECTED] wrote: Deepal, Thanks for the reply. Yes, this

Re: Changing the namespace that is being generated by the Axis engine

original Axis I am really new to the whole WS world, so if something better is out there let me know. I am not sure about that space, but I am going to look into it. On 5/20/07, Dennis Sosnoski [EMAIL PROTECTED] wrote: I don't know if it's just another copy-and-paste artifact, but the Login

Re: Changing the namespace that is being generated by the Axis engine

There's a newer SOAP engine called Axis2. See http://ws.apache.org/axis2/. But either framework should work just fine. The .NET service should provide you with a WSDL file. Submit that to the WSDL2Java tool (each framework provides one of these tools), and it will generate a client stub for you.

Re: Changing the namespace that is being generated by the Axis engine

Thanks Anne! I just downloaded it and am playing now. The WSDL2java tool generated ServiceServiceSoapStub.java, ServiceServiceSoapCallbackHandler.java, and ServiceServiceSoap12Stub.java, ServiceServiceSoap12CallbackHandler.java. I just have to figure out how to use them now. Hopefully the doc

Re: [Axis2] SOAP header elements

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Samisa and all, You have a very good point here, except that you started from the wrong class. The complete API for the users to use is the OperationClient API. But since most users, yes *most* user's concern is to send and receieve XML fragment

Re: [Axis2] SOAP header elements

Hi jack, U can use the following once you have the SOAPEnvelop to get the header block. SOAPHeader header = envelope.getHeader(); Once you get that you can get the specific header you want by using header.getHeaderBlocksWithNSURI(); or get all the headers and iterate through them using

Re: Axis2 1.1.1 WSDL2JAVA - Not generating java classes for wsdl:portType

Can you send your wsdl? do you have ports for each bining? Actually code is generated per port. On 5/20/07, Bo Xie [EMAIL PROTECTED] wrote: Hi, Just wondering if this is still an issue in Axis2 1.2 or I did not put the parameters properly. Thanks, -Bo On 5/17/07, Bo Xie [EMAIL PROTECTED]

Service vs. Operation client APIs [was Re: [Axis2] SOAP header elements]

OK, I really do not want to criticize the client API here, specially given that it has been around for more than two years. However, I have a problem when deciding whether to use the service client or operation client API for my implementation. As an example, in operation client, I do not have

[Announce] Stylus Studio 2007 Release 2 Now Available

[announce] Dear Apache AXIS Users, Stylus Studio 2007 Release 2, is now available for free trial download or online purchase. Here are some of highlights: * Query Plan: A new query plan utility in the XQuery Editor lets you visualize query execution plans and gain insight into how DataDirect

Re: Service vs. Operation client APIs [was Re: [Axis2] SOAP header elements]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Samisa Abeysinghe wrote: OK, I really do not want to criticize the client API here, specially given that it has been around for more than two years. However, I have a problem when deciding whether to use the service client or operation client