Performance for Axis2 and Axis 1.x compared with other alternatives
I heard that using AXIS's default message transport (SOAP over HTTP) is going to be slow due to marshling & unmarshling; and the through-put decreases exponentially with the size of the SOAP message (Bandwidth).I wonder whether it is a problem for Axis2 as well as Axis 1.x. Has anyone compared the performance of Axis2 or Axis 1.x with alternatives such as XFire, JAX-WS or ActiveSOAP. I'm asking this, because our team is at building a high-load web site, whose front-end (say JSPs or Servlets) will talk to back-end services working as a Web Service. And we looking for a Web Service technology that would give us high transaction rate and low latency. regards,-Hui
Re: Axis2 Release Date (again)
Hi, dims, Sorry for the long delay in response. I had to fly to china for my work and wasn't able to check my axis mailing list for sometime. I'm new to the format of the open source development, particularly about how it works at Aparche. Is there any incentive for people to help out or it's simply based on pure interest. (I would love to be doing it for nothing, but my current work is very consuming, so i asked :-)) thanks,-HuiOn 2/13/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Hui,Could you please help us fix those 2 problems?thanks,dimsOn 2/13/06, Yu-Hui Jin <[EMAIL PROTECTED]> wrote:> I've encountered two bugs for the existing features recently and hope they > will be fixed for the release:>> - The ADB does not handle restriction based enumeration in WSDL.> - The REST support does not work for operations that have parameters.>>> thanks, >> -Hui>>>> On 2/12/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:> >> >> > Sanjiva Weerawarana wrote: > > How does April 1st sound? 6 weeks from today.> >> > Its April fool's day ;-) > >> > Anyway, lets lay down some realistic requirements for Axis2 1.0. I set up> a wiki page for those requirements here> (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0).> Please help us to have a good list, which can be implementable by 1st of > April, 2006.> >> >> > -- Chinthaka> >> >> > Sanjiva.> >> >> >> >> >>>--Davanum Srinivas : http://wso2.com/blogs/
Re: WS works, but cannot view WSDL
How do we do it in Axis2? regards,-HuiOn 2/21/06, Shaoguang Cong <[EMAIL PROTECTED]
> wrote:Assume vmr is a directory under your webapp root. Try specify the tag as
vmr/VMRService.wsdl
By this way you can view the WSDL in the browser or via the Axis servlet (the ?wsdl url). Shaoguang Anne Thomas Manes <
[EMAIL PROTECTED]> wrote: Right -- that's because the WSDL is at the URL you specified:
http://localhost:8084/vmr/VMRService.wsdl,
and it is no longer generated by Axis, so there isn't a WSDL file at http://myip:myport/services/VMRService?wsdl
. Anne On 2/17/06, Greg Michalopoulos <
[EMAIL PROTECTED]> wrote:
I understand all that you replied, except I think I must be doing something wrong. I made all the changes and made
http://localhost:8084/vmr/VMRService.wsdl. Now the output of ?wsdl is
Fault - Unable to find WSDL file or resource http://localhost:8084/vmr/VMRService.wsdl
If I cut and paste that URL into a webbrowser, it shows the wsdl no problem. Any ideas?
From: Anne Tho
mas
Manes [mailto:[EMAIL PROTECTED]] Sent: Friday, February 17, 2006 10:57 AMTo:
axis-user@ws.apache.orgSubject: Re: WS works, but cannot view WSDLSince you have defined your own WSDL, I suggest you tell Axis to use your WSDL rather than generating a new one. You do so by specifying:
[wsdl-url]in the WSDD. (make sure that you change the soap:location attribute to point to the correct URL)Doing so allows you to remove the following parameters from the WSDD:
&
nbsp;
value="http://d2hawkeye.com/api/vmr/"/>
value="http://d2hawkeye.com/api/vmr/"/>
One more note: you should remove the namespace attributes from the definitions in your binding. The namespace attribute should be use only with RPC style services.
Anne On 2/17/06, Greg Michalopoulos <
[EMAIL PROTECTED]> wrote: Using Axis 1.3. I created the WSDL below by hand (via xsl). I created
the skeleton and stub using WSDL2Java no problem, but the deploy.wsdd(below as well) has lines like this - qname="ns:>Claim" - when I expected it to be - qname="ns:Claim". I am able to deploy and use the
web service without issue. The problem is that when I gotohttp://myip:myport/services/VMRService?wsdl
I get the following error:AXIS errorSorry, something seems to have gone wrong... here are the details:Fault - makeTypeElement() was told to create a type"{
http://d2hawkeye.com/api/vmr/}>Claim", with no containing elementAxisFaultfaultCode:{
http://schemas.xmlsoap.org/soap/envelope/}Server.generalException faultSubcode:faultString: makeTypeElement() was told to create a type"{
http://d2hawkeye.com/api/vmr/}>Claim", with no containing elementfaultActor: faultNode:faultDetail:{
http://xml.apache.org/axis/}hostname:So while it appears to be working fine, I know something is wrong butnot
sure
where. I'm guessing my namespaces but am not sure how to figure this out. Any suggestions welcome.Thanks,Greg***WSDL***
http://d2hawkeye.com/api/vmr/"xmlns=" http://schemas.xmlsoap.org/wsdl/ "xmlns:apachesoap="
http://xml.apache.org/xml-soap"xmlns:impl="
http://d2hawkeye.com/api/vmr/"xmlns:intf="http://d2hawkeye.com/api/vmr/"xmlns:soapenc="
http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"xmlns:wsdlsoap=" http://schemas.xmlsoap.org/wsdl/soap/
" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> http://d2hawkeye.com/api/vmr/ "xmlns="
http://www.w3.org/2001/XMLSchema"> /> ... ... type="xsd:date" />
type="xsd:string"/>
transport="http://schemas.xmlsoap.org/soap/http
"/>
http://d2hawkeye.com/api/vmr/ "use="literal"/>
http://d2hawkeye.com/api/vmr/ "use="literal"/>
location="http://localhost:8084/services/VMRService"/>
***WSDL**WSDD***
xmlns="
http://xml.apache.org/axis/wsdd/"xmlns:java="http://xml.apache.org/axis/wsdd/providers/java
"> use="literal"> value=" http://d2hawkeye.com/api/vmr/"/>
value="
http://d2hawkeye.com/api/vmr/"/>value="com.d2hawkeye.api.vmr.VMRServiceSoapBindingSkeleton
"/>
xmlns:ns="
http://d2hawkeye.com/api/vmr/ "qname="ns:>Claim"
type="java:com.d2hawkeye.api.vmr.Claim"serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory
"encodingStyle="" /> xmlns:ns="
http://d2hawkeye.com/api/vmr/"qname="ns:>Member"
type="java:com.d2hawkeye.api.vmr.Member"serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory
"encodingStyle="" /> xmlns:ns="
http://d2hawkeye.com/api/vmr/"qname="ns:>Claims" type="java:com.d2hawkeye.api.vmr.Claim[]"inner
Re: The REST call syntax
Hi, I wanted to add a JITA for this bug (and another one for the databinding). I checked out the following page but couldn't find a way to add new bug. how should I do that? Thanks! http://issues.apache.org/jira/browse/AXIS2regards,-HuiOn 2/7/06, Deepal Jayasinghe < [EMAIL PROTECTED]> wrote:-BEGIN PGP SIGNED MESSAGE-Hash: SHA1 Hi Hui;I am not sure Axis2 support REST very good manner , there are numberof improvements need to be done to get it to the correct level. Andother thing that only support REST using GET , so that is not enough as well, and SOAP envelop has to be create taking schema of theservice taking into account.So pls create a JIRA , so that it will fix in next release.Yu-Hui Jin wrote:> well, if I do that, then it's not a REST call anymore, assuming you > are asking me to write a client side code to do that.>> I thought a REST call can be just made by a URL with optional params.>> So could it be that I'm just not getting the syntax of the URL > right? Is there a working example at all?>>> thanks,>> -Hui On 2/7/06, *Ajith Ranabahu* <[EMAIL PROTECTED] > [EMAIL PROTECTED]>> wrote:>> Hi,> Hmm.. You seem to have done the right thing. Indeed services with> parameters can be invoked through REST and we follow the IRI style > (http://www.w3.org/2005/08/wsdl/style/iri) to construct a> message from> the parameters we get in the query string.> The operation name is picked from the URL so your URL should > contain> the right service name (with correct case) and the opertion name> also> with the correct case.> However I think the problem may be due to the URL based dispatching> not working properly. >> You can try this workaround> - Modify the request to include a SOAPAction with the value of the> operation name> That should force the SOAPActionBasedDispatcher to action and> pick > the right operation>>> --> Ajith Ranabahu>>- --Thanks,Deepal~Future is Open~-BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32)Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.orgiD8DBQFD6aEMjOGcXNDx0CARAgMBAJ9zyUcwIHhiggpr/YF+Achjg/8gLACfUZvq 8hrizfGEBDDFPYoOzmYfmSg==M7j5-END PGP SIGNATURE-
Re: method missing for WSDL containing simpleType use. A BIT URGENT!
Thanks Anne. Your blog article on the wrapped document style is a good read. -HuiOn 2/8/06, Anne Thomas Manes < [EMAIL PROTECTED]> wrote:Actually, there is a problem in the WSDL, although that isn't what's causing your problem. As Ajith says, you're trying to use a feature that isn't yet supported. But meanwhile, for completeness sake... When using style="rpc", your message parts must reference types, not elements. You can fix the WSDL either by changing the style to "document" and removing the @namespace attributes from the definitions (the easy alternative), or by changing the message part definitions to: And change the anonymous complexType definition in your Item element definition to a named type called "Item".Anne On 2/8/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: Hi Hui,There's nothing wrong with your WSDL but it's an Axis2- ADBlimitation for the time. We do not handle simple typerestrictions/enumerations - the schema parser just ignores thesimpletype's restriction and picks up OMElement for that! If you need to use enums I would say you need to move to XMLBeansAjithOn 2/8/06, Yu-Hui Jin < [EMAIL PROTECTED]> wrote:> Yeah, I had hoped so. So I changed the names of form "Property" to > "ItemProperty". It still doesn't work, same exception complaining: The> method convertToPropertyType(String) is undefined for the type ConverterUtil> in the Property.java.>> Can you guys take a brief look at it and see whether I've messed up > anything, Thanks!>> Here's the Types.xsd:> ==>> > http://www.w3.org/2001/XMLSchema"> targetNamespace="http://internal.aaa.com/fims/Types "> xmlns:tns=" http://internal.aaa.com/fims/Types">>> >> > > > > > > > >> > > > > > >> >> >> > > > maxOccurs="unbounded"/>> > > >> >>> And the WSDL:> ===>> > > targetNamespace="http://internal.aaa.com/fims"> xmlns=" http://schemas.xmlsoap.org/wsdl/ " > xmlns:xs="http://www.w3.org/2001/XMLSchema"> xmlns:soap=" http://schemas.xmlsoap.org/wsdl/soap/ "> xmlns:tns="http://internal.aaa.com/fims"> xmlns:xsd=" http://internal.aaa.com/fims/Types ">>> http://internal.aaa.com/fims/Types" > location="Types.xsd"/>>> > > > > > >> > > > > > >> > http://schemas.xmlsoap.org/soap/http "/>> > > > http://internal.aaa.com/fims " use="literal"/>> > > http://internal.aaa.com/fims" use="literal"/> > > > > > > binding="tns:fimsServiceBinding"> > > location="http://yjin-2.desktop.aaa.com:8080/axis2/services/fims > "/>> > > >>>>>>>>>> On 2/7/06, Jim Azeltine < [EMAIL PROTECTED] > wrote:>> Because I figured that since you said that you were using Eclipse, and> you were working with web services, that you were using the WTP plugin.> I would guess that you are picking up the Property class from the wrong > package in your classpath.>> Jim>> Yu-Hui Jin <[EMAIL PROTECTED] > wrote:>> Hi, Jim,>> Not sure how you figure out i'm using WTP. But I don't see how it > has to do with this generation problem. Besides, I'm not using Axis plugin> at all, I simply use the command-line WSDL2Java in Axis2 0.94.>>> -Hui>>> On 2/7/06, Jim Azeltine < [EMAIL PROTECTED]> wrote:>> You need to find out if the Eclipse WTP plugin even supports > Axis 2 yet.>> Jim >>> Yu-Hui Jin < [EMAIL PROTECTED]> wrote:>>> Hi, there, >> I defined the following type in my WSDL. >> > > > > > > > >> The used in in an element:>> > > > > > minOccurs="0" maxOccurs="unbounded"/>>
Re: Axis2 Release Date (again)
I've encountered two bugs for the existing features recently and hope they will be fixed for the release: - The ADB does not handle restriction based enumeration in WSDL.- The REST support does not work for operations that have parameters. thanks,-HuiOn 2/12/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: Sanjiva Weerawarana wrote: How does April 1st sound? 6 weeks from today. Its April fool's day ;-) Anyway, lets lay down some realistic requirements for Axis2 1.0. I set up a wiki page for those requirements here (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0). Please help us to have a good list, which can be implementable by 1st of April, 2006. -- Chinthaka Sanjiva.
Re: The REST call syntax
well, if I do that, then it's not a REST call anymore, assuming you are asking me to write a client side code to do that. I thought a REST call can be just made by a URL with optional params. So could it be that I'm just not getting the syntax of the URL right? Is there a working example at all? thanks,-HuiOn 2/7/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: Hi,Hmm.. You seem to have done the right thing. Indeed services withparameters can be invoked through REST and we follow the IRI style (http://www.w3.org/2005/08/wsdl/style/iri) to construct a message fromthe parameters we get in the query string.The operation name is picked from the URL so your URL should contain the right service name (with correct case) and the opertion name alsowith the correct case.However I think the problem may be due to the URL based dispatchingnot working properly.You can try this workaround - Modify the request to include a SOAPAction with the value of theoperation name That should force the SOAPActionBasedDispatcher to action and pickthe right operation--Ajith Ranabahu
newbie questions on "style" attribute
Hi, Anyone can help me to understand the "style" element better. (well, or pointing me to some good articles on it?)Here's what's puzzling me: In Axis1.x user guide, it says the "service" element can have a "style" attribute. I also see under the "wsdl:binding" element, both "soap:binding" and "soap:operation" elements can have a "style" attribute as well. I've got a few questions: - do they have the same meaning and one will overide the other? - when do I select "rpc" and "document" for my WSDL? It seems "document" is suggested for Axis 1.x, is it still a better choice for Axis2? thanks,-Hui
Re: method missing for WSDL containing simpleType use. A BIT URGENT!
Awesome, this solved my problem. Are there a list of features that are not supported by each of the bindings? Really hope I could use one. thanks,-HuiOn 2/7/06,
Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
Hi Hui,There's nothing wrong with your WSDL but it's an Axis2- ADBlimitation for the time. We do not handle simple typerestrictions/enumerations - the schema parser just ignores thesimpletype's restriction and picks up OMElement for that!
If you need to use enums I would say you need to move to XMLBeansAjithOn 2/8/06, Yu-Hui Jin <[EMAIL PROTECTED]> wrote:> Yeah, I had hoped so. So I changed the names of form "Property" to
> "ItemProperty". It still doesn't work, same exception complaining: The> method convertToPropertyType(String) is undefined for the type ConverterUtil> in the Property.java.>> Can you guys take a brief look at it and see whether I've messed up
> anything, Thanks!>> Here's the Types.xsd:> ==>> >
http://www.w3.org/2001/XMLSchema"> targetNamespace="http://internal.aaa.com/fims/Types "> xmlns:tns="
http://internal.aaa.com/fims/Types">>> >> >
> > > >
> > >> > >
> > >
>> >> >> >
> > maxOccurs="unbounded"/>> >
> >> >>> And the WSDL:> ===>> > > targetNamespace="http://internal.aaa.com/fims"> xmlns="http://schemas.xmlsoap.org/wsdl/ "
> xmlns:xs="http://www.w3.org/2001/XMLSchema"> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/
"> xmlns:tns="http://internal.aaa.com/fims"> xmlns:xsd="http://internal.aaa.com/fims/Types
">>> http://internal.aaa.com/fims/Types"> location="Types.xsd"/>>>
> > > >
> >> > >
> > > >>
> http://schemas.xmlsoap.org/soap/http"/>>
> > > http://internal.aaa.com/fims
" use="literal"/>> > > http://internal.aaa.com/fims" use="literal"/>
> > > > > > binding="tns:fimsServiceBinding">
> > location="http://yjin-2.desktop.aaa.com:8080/axis2/services/fims> "/>>
> > >>>>>>>>>> On 2/7/06, Jim Azeltine <[EMAIL PROTECTED]
> wrote:>> Because I figured that since you said that you were using Eclipse, and> you were working with web services, that you were using the WTP plugin.> I would guess that you are picking up the Property class from the wrong
> package in your classpath.>> Jim>> Yu-Hui Jin <[EMAIL PROTECTED]> wrote:>> Hi, Jim,>> Not sure how you figure out i'm using WTP. But I don't see how it
> has to do with this generation problem. Besides, I'm not using Axis plugin> at all, I simply use the command-line WSDL2Java in Axis2 0.94.>>> -Hui>>> On 2/7/06, Jim Azeltine <
[EMAIL PROTECTED]> wrote:>> You need to find out if the Eclipse WTP plugin even supports> Axis 2 yet.>> Jim
>>> Yu-Hui Jin < [EMAIL PROTECTED]> wrote:>>> Hi, there,>> I defined the following type in my WSDL.
>> > >
> > >
> > >> The used in in an element:>>
> > > > > minOccurs="0" maxOccurs="unbounded"/>> > >
>> The code generates without any problem. But Eclipse reports> compilation error: The method convertToPropertyType(String) is undefined for> the type ConverterUtil in the Property.java
.>> I displayed the line which uses the method in bold here:>> if> ("Type".equals(reader.getLocalName())) {> String content =
> reader.getElementText();> object.setType> (org.apache.axis2.databinding.utils.ConverterUtil.convertToPropertyType> (> content));
> count++;> }>> Is this a bug or am I missing anything?>>> regards,
>> -Hui>>>>>>>--Ajith Ranabahu
Re: method missing for WSDL containing simpleType use.
Sorry, a typo at the end of the first paragraph: I meant the exception is for the ItemProperty.java, since I changed the element's name.thanks,-HuiOn 2/7/06,
Jim Azeltine <[EMAIL PROTECTED]> wrote:
Because I figured that since you said that you were using Eclipse, and you were working with web services, that you were using the WTP plugin. I would guess that you are picking up the Property class from the wrong package in your classpath.
JimYu-Hui Jin <[EMAIL PROTECTED]
> wrote: Hi, Jim,Not sure how you figure out i'm using WTP. But I don't see how it has to do with this generation problem. Besides, I'm not using Axis plugin at all, I simply use the command-line WSDL2Java in Axis2
0.94. -Hui On 2/7/06, Jim Azeltine <
[EMAIL PROTECTED]> wrote:You need to find out if the Eclipse WTP plugin even supports Axis 2 yet.
Jim Yu-Hui Jin < [EMAIL PROTECTED]> wrote:
Hi, there, I defined the following type in my WSDL.
The used in in an element:
The code generates without any problem. But Eclipse reports compilation error: The method convertToPropertyType(String) is undefined for
the type
ConverterUtil in the Property.java. I displayed the line which uses the method in bold here: if ("Type".equals(reader.getLocalName())) { String content =
reader.getElementText(); object.setType (org.apache.axis2.databinding.utils.ConverterUtil.convertToPropertyType (
content)); count++; }Is this a bug or am I missing anything? regards,-Hui
Re: method missing for WSDL containing simpleType use. A BIT URGENT!
Yeah, I had hoped so. So I changed the names of form "Property" to "ItemProperty". It still doesn't work, same exception complaining: The method convertToPropertyType(String) is undefined for the type ConverterUtil in the
Property.java.Can you guys take a brief look at it and see whether I've messed up anything, Thanks!Here's the Types.xsd:==
http://www.w3.org/2001/XMLSchema" targetNamespace="http://internal.aaa.com/fims/Types
" xmlns:tns="http://internal.aaa.com/fims/Types">
And the WSDL:===
targetNamespace="http://internal.aaa.com/fims" xmlns="http://schemas.xmlsoap.org/wsdl/
" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/
" xmlns:tns="http://internal.aaa.com/fims" xmlns:xsd="http://internal.aaa.com/fims/Types">
http://internal.aaa.com/fims/Types" location="Types.xsd"/>
http://schemas.xmlsoap.org/soap/http"/>
http://internal.aaa.com/fims" use="literal"/> http://internal.aaa.com/fims" use="literal"/>
http://yjin-2.desktop.aaa.com:8080/axis2/services/fims
"/> On 2/7/06, Jim Azeltine <[EMAIL PROTECTED]> wrote:
Because I figured that since you said that you were using Eclipse, and you were working with web services, that you were using the WTP plugin. I would guess that you are picking up the Property class from the wrong package in your classpath.
Jim Yu-Hui Jin <[EMAIL PROTECTED]> wrote: Hi, Jim, Not sure how you figure out i'm using WTP. But I don't see how it has to do with this generation problem. Besides, I'm not using Axis plugin at all, I simply use the command-line WSDL2Java in Axis2
0.94. -Hui On 2/7/06, Jim Azeltine <[EMAIL PROTECTED]> wrote: You need to find out if the Eclipse WTP plugin even supports Axis 2 yet.
Jim Yu-Hui Jin < [EMAIL PROTECTED]> wrote: Hi, there, I defined the following type in my WSDL.
The used in in an element:
The code generates without any problem. But Eclipse reports compilation error: The method convertToPropertyType(String) is undefined for the type ConverterUtil in the
Property.java. I displayed the line which uses the method in bold here: if ("Type".equals(reader.getLocalName())) { String content =
reader.getElementText(); object.setType (org.apache.axis2.databinding.utils.ConverterUtil.convertToPropertyType ( content));
count++; } Is this a bug or am I missing anything? regards, -Hui
Re: method missing for WSDL containing simpleType use.
Thanks, Ann. I copied the wrong part in my email. So I used the PropertyType in another type called Property. (Then I used Property to define the element Item.)
Any thoughts? thanks,-hui
On 2/7/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
Is this a typo in your email or in your WSDL: should beAnneOn 2/7/06, Yu-Hui Jin <
[EMAIL PROTECTED]> wrote:
Hi, there, I defined the following type in my WSDL.
The used in in an element:
The code generates without any problem. But Eclipse reports compilation error: The method convertToPropertyType(String) is undefined for the type ConverterUtil in the Property.java. I displayed the line which uses the method in bold here:
if ("Type".equals(reader.getLocalName())) { String content = reader.getElementText(); object.setType
(org.apache.axis2.databinding.utils.ConverterUtil.convertToPropertyType( content)); count++; }Is this a bug or am I missing anything?
regards,-Hui
Re: method missing for WSDL containing simpleType use.
Hi, Jim,Not sure how you figure out i'm using WTP. But I don't see how it has to do with this generation problem. Besides, I'm not using Axis plugin at all, I simply use the command-line WSDL2Java in Axis2 0.94.
-HuiOn 2/7/06, Jim Azeltine <[EMAIL PROTECTED]> wrote:
You need to find out if the Eclipse WTP plugin even supports Axis 2 yet. JimYu-Hui Jin <
[EMAIL PROTECTED]> wrote: Hi, there,
I defined the following type in my WSDL.
The used in in an element:
The code generates without any problem. But Eclipse reports compilation error: The method convertToPropertyType(String) is undefined for the type ConverterUtil in the
Property.java. I displayed the line which uses the method in bold here: if
("Type".equals(reader.getLocalName())) { String content = reader.getElementText(); object.setType (org.apache.axis2.databinding.utils.ConverterUtil.convertToPropertyType
( content)); count++; }Is this a bug or
am I
missing anything? regards,-Hui
method missing for WSDL containing simpleType use.
Hi, there, I defined the following type in my WSDL.
The used in in an element:
The code generates without any problem. But Eclipse reports compilation error: The method convertToPropertyType(String) is undefined for the type ConverterUtil in the Property.java. I displayed the line which uses the method in bold here:
if ("Type".equals(reader.getLocalName())) { String content = reader.getElementText(); object.setType
(org.apache.axis2.databinding.utils.ConverterUtil.convertToPropertyType( content)); count++; }Is this a bug or am I missing anything?
regards,-Hui
Re: RPC turned to Document
Thanks, Deepal, I thought META-INF dir is just used for dumping resources that are needed by the webapp such as context.xm. But anyway, I put the WSDL and XSD under the META-INF dir. Still it does not work. It's surprising to me that by the following syntax of the URL, it'll look for the file under the META-INF dir. Please enlighten, thanks!http://localhost:8080/axis2/services/FusionIMSService?wsdl -HuiOn 2/6/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE-Hash: SHA1yes , the problem is this , you have code gen your service skeletonand using that you have created a service archive file. And you havenot put your original WSDL file into META-INF directory in the service archive file, So all the original WSDL data has lost. And at theruntime when you ask for wsdl using ?wsdl , if there is no wsdl foundin the service archive file , it will create a WSDL for your serviceimpl class using java reflection , that WSDL is doc-lit. If you want to get the original WSDL back when you ask for ?wsdl youhave to put that WSDL file into META-INF directory.Yu-Hui Jin wrote:> Hi,>> I made the example Axis2SampleDocLitService work on Axis2. I found > some strange thing:>> It is specified in the WSDL that the styple is "rpc" in the> following line:>> >> However, when I clicked the Service link and went to the page at:> http://localhost:8080/axis2/services/Axis2SampleDocLitService?wsdl >> The WSDL displayed had all the "rpc" turned into "document" in all> the "soap:operation" lines.>> Anyone knows what happened?>>> thanks, >> -Hui-BEGIN PGP SIGNATURE-Version: GnuPG v1.4.2 (MingW32)Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.orgiD8DBQFD6BXLjOGcXNDx0CARAn+IAKCKfUnR5vMISnaiBsXkLLeeOkjCjgCgzXD+ xHLOJ7+6fQHuUPjErlfg3hY==Rb6V-END PGP SIGNATURE-
Does Axis2 has full REST support?
Hi, I made the Axis2SampleDocLitService working on Axis2 -- The unit test passed. However, I can't make the REST call work. I tried the following calls, but none worked. http://localhost:8080/axis2/services/Axis2SampleDocLitService/echoString?EchoStringParam=nicehttp://localhost:8080/axis2/services/Axis2SampleDocLitService/echoString?EchoStringParam=%22nice%22 Is REST call working for the operation that requires params ???thanks,-HuiReturn message says: ===...java.lang.UnsupportedOperationException : This element was not created in a manner to be switched; nested exception is: java.lang.RuntimeException: java.lang.UnsupportedOperationException: This element was not created in a manner to be switched ..
Re: Axis2 codegen pretty print problem
Thanks. To be more accurate, the following dependent jars are needed as well: jakarta-oro-2.0.8.jarjdom.jarJust curious why they are not added to the Axis/lib directory in the distribution. thanks,-HuiOn 2/6/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: drop jalopy.jar from http://jalopy.sourceforge.net/existing/download.htmlOn 2/6/06, Yu-Hui Jin <[EMAIL PROTECTED] > wrote:> Hi,>> I used Axis2's WSDL2Java to generate the code. The generation works fine.> But I'm getting the following messages among the output:>> Jalopy not found - unable to pretty print > file>/Item.java> ..> ..>> Is there a package missing here?>>> regards,>> -Hui>--Davanum Srinivas : http://wso2.com/blogs/
RPC turned to Document
Hi, I made the example Axis2SampleDocLitService work on Axis2. I found some strange thing:It is specified in the WSDL that the styple is "rpc" in the following line: However, when I clicked the Service link and went to the page at: http://localhost:8080/axis2/services/Axis2SampleDocLitService?wsdl The WSDL displayed had all the "rpc" turned into "document" in all the "soap:operation" lines.Anyone knows what happened? thanks,-Hui
Re: Axis2 WSDL compliance and intelligent support for generation
Thanks, Anne, I switched to use "document" style and @type. The codegen is done without exceptions. However, my eclipse, after compiling the code, says the "org.apache.axis2.om.OMElement.MY_QNAME" could not be found in the following line of code: (org.apache.axis2.om.OMAbstractFactory.getOMFactory(), param.getPullParser(org.apache.axis2.om.OMElement.MY_QNAME));Using @element does not cause the problem. Eclipse compiles fine in that case. thanks,-HuiOn 2/6/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: Note that @type is allowed in the definition only when using RPC style. If you are using document style, then you must specify @element instead.Anne On 2/5/06, Yu-Hui Jin <[EMAIL PROTECTED]> wrote: I noticed that the code generator WSDL2Java for Axis can't take some of the allowable syntax in WSDL 1.1. In WSDL 1.1. spec, the "type" is allowed in a message body: However, WSDL2Java throws NullPointerException on this. I had to define an element ItemId of "xs:string" in the section, then use that element instead. Are there any other non-supported features in WSDL 1.1. that we should be aware of ??BTW, another suggestion is if the code generator could be made more intelligent, that it'll report the specific syntax error on the line of the WSDL, that'll make our life a whole lot easier. Making WSDL 2 Java generation work and compilable is a very demanding and painful job. regards,-Hui
Axis2 codegen pretty print problem
Hi,I used Axis2's WSDL2Java to generate the code. The generation works fine. But I'm getting the following messages among the output: Jalopy not found - unable to pretty print /Item.java Is there a package missing here? regards,-Hui
Axis2 WSDL compliance and intelligent support for generation
I noticed that the code generator WSDL2Java for Axis can't take some of the allowable syntax in WSDL 1.1. In WSDL 1.1. spec, the "type" is allowed in a message body: However, WSDL2Java throws NullPointerException on this. I had to define an element ItemId of "xs:string" in the section, then use that element instead. Are there any other non-supported features in WSDL 1.1. that we should be aware of ??BTW, another suggestion is if the code generator could be made more intelligent, that it'll report the specific syntax error on the line of the WSDL, that'll make our life a whole lot easier. Making WSDL 2 Java generation work and compilable is a very demanding and painful job. regards,-Hui
Re: some minor fix for the Axis2 user guide
Sure. By the way, in the generated test file for the EchoString wsdl Axis2SampleDocLit.wsdl, when creating a stub object of Axis2SampleDocLitPortTypeStub at the beginning of each test case, the comment "the default implementation should point to the right endpoint" is no longer valid. The default one can't be located anymore. To make it work, i have to put in the location of the Service running locally on my box.cheers,-HuiOn 2/4/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: Hi, Yes you are partially right :). The default has been changed to ADB which generates simple class names. The userguide will still be valid if the -d xmlbeans option is used but by default ADB is used now. We'll fix the user guide soonOn 2/5/06, Yu-Hui Jin < [EMAIL PROTECTED]> wrote: Hi, there, Here's what I found what's out-of-sync in the user guide: Some of the generated type classes have been renamed, such as EchoStringReturnDocument has been changed to EchoStringReturn. regards, -Hui -- Ajith Ranabahu
The REST call syntax
Hi, there, In the user guide, there's a RESTful Web Service page in which an example is given -- the REST call to getVersion. After enabling the REST in my axis2.xml, I tried to make a REST to the Axis2SampleDocLitService that I made work by following the instructions. To be more specific, I tried: http://localhost:8080/axis2/services/Axis2SampleDocLitService/EchoString?EchoStringParam=nice However it gives me errors such as the following. Anyone know the syntax for REST when there's input messages? Thanks! --HuiREST Response: − − Client− Operation Not found EPR is http://localhost:8080/axis2/services/Axis2SampleDocLitService/EchoString and WSA Action = "">http://myAxisServer/role/default − − org.apache.axis2.AxisFault: Operation Not found EPR is http://localhost:8080/axis2/services/Axis2SampleDocLitService/EchoString and WSA Action = ""> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:46) at org.apache.axis2.engine.Phase.invoke (Phase.java:391) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:351) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:322) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPGetRequest (HTTPTransportUtils.java:147) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:103) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service (HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java :173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.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:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java :663) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595)
some minor fix for the Axis2 user guide
Hi, there, Here's what I found what's out-of-sync in the user guide: Some of the generated type classes have been renamed, such as EchoStringReturnDocument has been changed to EchoStringReturn.regards, -Hui
