Re: Fault - makeTypeElement()

[Vishist Mandapaka <vi...@gmail.com>]

Hi Anil,
At last, I could get my webservices to work. I had to tweak in the
auto-generated code to get it to work. Please send me your wsdl, xsd and
build.xml to test. I could take a look and let you know.
As for me, there are ">" symbols that are generated in the queue names. I
removed them from all the generated code and it is working fine now.
thanks
vishist.

On 9/28/05, Anil Arora <aa...@interlacesystems.com> wrote:
>
>  Thanks Chris for that catch. That was just stupidity on my part.
>
>  Vishist, definitely let me know if you solve this.
>
>  I'm starting to think it has something to do with the custom serializers
> that I implemented. I tried to just use the BeanSerializers, and I still get
> the exception. The weird thing is that the exception is different everytime
> I start up my webserver.
>
>  Anil
>
>     ------------------------------
>
> *From:* Vishist Mandapaka [mailto:vishistm@gmail.com]
> *Sent:* Tuesday, September 27, 2005 3:23 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Fault - makeTypeElement()
>
>  Hi Anil,
> As Anne has suggested, I presume Axis 1.1 is a bit buggy with the
> document/literal operation. For me, when I try to deploy, it is giving
> NullPointerException.
> Now in order to come around it, I did one thing,
>
> First reverse engineer from java to wsdl. So your command would be
> java org.apache.axis.wsdl.Java2WSDL yourServiceClassInstance
> ......options.....
> This will give you the wsdl file. Now, if you regenerate the java classes
> and try to deploy it, it will work. Deploy in the sense you need to copy the
> deploy.wsdd info. You should be able to see the wsdl file. But I presume
> you won't be able to invoke the webservice. It will give all kinds of
> exception.
> There is lot more to it to understand. As per my results, the wsdl that is
> generated from Service classes will have rpc/encoded format instead of
> document/literal. I am still trying to figure out. I will let you know if I
> succeed with this.
> thanks
> Vishist.
>
> On 9/27/05, *Ebert, Chris* <ch...@hp.com> wrote:
>
>
> Hi Anil,
>
> I don't know if it's your problem, but your attributes should say
> use="optional" instead of optional="true" (and use="required" instead of
> optional="false"). Dunno if that's causing your problems, but it's not
> correct...
>
> Chris
>
> -----Original Message-----
> From: Anil Arora [mailto:aarora@interlacesystems.com]
> Sent: Tuesday, September 27, 2005 11:55
> To: axis-user@ws.apache.org; Anne Thomas Manes; Vishist Mandapaka
> Subject: RE: Fault - makeTypeElement()
>
> I am running into a similar issue with my webservice. I had to
> downgrade to AXIS 1.1 so I am struggling to get this to work.
>
> I embedded the schema inline as suggested. Attached is my wsdl file.
> Anyone have any ideas?
>
>
>
> Anil
>
>
>
>
>
> ________________________________
>
> From: Anne Thomas Manes [mailto: atmanes@gmail.com]
> Sent: Saturday, September 24, 2005 6:40 PM
> To: Vishist Mandapaka
> Cc: axis-user@ws.apache.org
> Subject: Re: Fault - makeTypeElement()
>
>
>
> Axis 1.1 is a bit buggy when it comes to document/literal, but it should
> work if you're doing WSDL first.
>
> I did find problems with your WSDL in the echo operation:
> 1- message part definitions for a doc/literal operation must reference
> elements, not types.
> 2- the parts attribute in a soap:body definition must reference a part
> definition, not a message definition.
>
> I can't immagine why these mistakes would produce the error you're
> seeing, but who knows.
>
> In any case, because Axis 1.1 is a bit temperamental about doc/literal,
> I suggest you remove the echo operation, and I suggest that you embed
> you schema inline rather than including an external file.
>
> Anne
>
> On 9/24/05, Vishist Mandapaka <vi...@gmail.com> wrote:
>
> I have two more question, why Axis 1.1 is putting ">" symbols infront of
> elements that are part of messages. and also the corresponding generated
> classes have "_" leading to their class names.
> The documentation did not help much in this aspect.
>
>
>
>
>
>
>
> On 9/24/05, Vishist Mandapaka < vishistm@gmail.com
> <ma...@gmail.com> > wrote:
>
> Anne,
> I modified the schema. Still it did not work. The same
> "makeTypeElement" error came up. Scanning through the schema, wsdl,
> server-config.wsdd, all of them look fine to me.
> Generated the java classes
> Compiled the java classes
> moved the generated class to WEB-INF/classes directory copied/pasted
> deploy.wsdd to server-config.wsdd from <service>to </service> part since
> deploy through command line is not working (it is giving
> NullPointerException) started the server then came up the error..
>
> :)
>
>
>
>
>
> On 9/24/05, Anne Thomas Manes < atmanes@gmail.com
> <ma...@gmail.com> > wrote:
>
> 1. The code should not work in Axis 1.2. I guess it is more forgiving
> than Axis 1.1.
> 2. Schema inclusion does not change the namespace qualification status
> of the elements defined in the included schema. In the schema spec
> terminology, inclusion does not "coerce" the included schema. An
> included schema must have the same namespace as the including schema or
> no namespace.
>
> Anne
>
>
>
> On 9/24/05, Vishist Mandapaka < vishistm@gmail.com
> <ma...@gmail.com> > wrote:
>
> Then I have the following questions
> 1. How come the code is working in Axis 1.2 2. In the schema inclusion
> statement, I have defined the targetNamespace. Wouldn't it be
> sufficient?
>
> Anyway, as you said, I will try to put the namespace declaration in the
> schema and verify it. I will let you know the progress.
> thanks a lot
> vishist.
>
>
>
> On 9/24/05, Anne Thomas Manes < atmanes@gmail.com
> <mailto: atmanes@gmail.com> > wrote:
>
> Looking just at your schema, I suspect you might have a namespace
> problem.
> The fault indicates that it is trying to define the
> {ssi_esap_lnp}>SSILNPResponse type (a qualified element name) but your
> schema doesn't define a targetnamespace, so all elements in the schema
> are unqualified.
>
> Anne
>
> On 9/24/05, Anne Thomas Manes < atmanes@gmail.com
> <mailto: atmanes@gmail.com> > wrote:
>
> Please also provide the WSDL.
>
>
>
> On 9/23/05, Vishist Mandapaka < vishistm@gmail.com
> <mailto: vishistm@gmail.com> > wrote:
>
> hi,
> I am using Axis 1.1 and deployed the webservice on Iplanet 6.1
> webserver. When I try to access the WSDL, I get the following exception
> "
>
> Sorry, something seems to have gone wrong... here are the
> details:
>
> Fault - makeTypeElement() was told to create a type
> "{ssi_esap_lnp}>SSILNPResponse", with no containing element
>
>
>
> AxisFault
>
> faultCode: {
> <http://schemas.xmlsoap.org/soap/envelope/%7DServer.generalException>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> http://schemas.xmlsoap.org/soap/envelope/}Server.generalException<http://schemas.xmlsoap.org/soap/envelope/%7dServer.generalException>
> < http://schemas.xmlsoap.org/soap/envelope/%7DServer.generalException>
>
> faultSubcode:
>
> faultString: makeTypeElement() was told to create a type
> "{ssi_esap_lnp}>SSILNPResponse", with no containing element
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> faultActor:
>
> faultNode:
>
> faultDetail:
>
> "
>
>
>
> It seems there is something wrong with my webservice. But I'm
> unable to figure it out. There is nothing in webserver logs.
>
>
>
>
> The same webservice is working in Axis
>
>
>
>
>
>
>
>
>
>
>
>
>
> 1.2. But our companys spec is to use Axis 1.1 :).
>
> I am outlining the steps I followed
>
> 1. Created an xsd describing the complex elements
>
> 2. Created the wsdl, with the include statement for xsd.
>
>
>
>
>
>
>
>
> 3. generated the java classes using Axis utility class
>
>
>
>
>
>
>
>
>
> 4. Compiled the source files and then deployed it.
>
> 5. The process of deploying is like, I have a server-config.wsdd
> in WEB-INF directory and I deployed that webservice using
>
>
>
>
>
>
> deploy.wsdd file generated by Axis.
>
>
>
>
>
>
>
>
>
> When I try to access the wsdl, I get this error.
>
>
>
> Your help in this matter will be lot to me. I am including the
> xsd, wsdl and wsdd.
>
> thanks
>
> vishist.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>