You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Vishist Mandapaka <vi...@gmail.com> on 2005/09/24 02:37:16 UTC
Fault - makeTypeElement()
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/}Server.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.
--
Vishist Mandapaka
email: vishistm@gmail.com
Ph: (313) 282 8348
Re: Fault - makeTypeElement()
Posted by Vishist Mandapaka <vi...@gmail.com>.
Hi Anne,
Thanks for responding. Here I am enclosing the WSDL also. I am using
wsdl2java emitter for Axis 1.1. Let me mention it clearly. This whole
scenario is working for Axis 1.2. Only it is not working for Axis 1.1. and I
have to make it to work for Axis 1.1
thanks
Vishist.
On 9/24/05, Anne Thomas Manes <at...@gmail.com> wrote:
>
> Please also provide the WSDL.
>
> On 9/23/05, Vishist Mandapaka <vi...@gmail.com> wrote:
> >
> > hi,
> > I am using Axis 1.1 and deployed the webservice on Iplanet 6.1webserver. 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/}Server.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.
> >
> >
> >
> > --
> > Vishist Mandapaka
> > email: vishistm@gmail.com
> > Ph: (313) 282 8348
> >
>
>
--
Vishist Mandapaka
email: vishistm@gmail.com
Ph: (313) 282 8348
Re: Fault - makeTypeElement()
Posted by Anne Thomas Manes <at...@gmail.com>.
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 <vi...@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 > 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> 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> 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> wrote:
> > > > > >
> > > > > > Please also provide the WSDL.
> > > > > >
> > > > > > On 9/23/05, Vishist Mandapaka < vishistm@gmail.com> wrote:
> > > > > > >
> > > > > > > hi,
> > > > > > > I am using Axis 1.1 and deployed the webservice on Iplanet 6.1webserver. 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/}Server.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.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Fault - makeTypeElement()
Posted by Vishist Mandapaka <vi...@gmail.com>.
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 <vi...@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 > 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> 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> 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> wrote:
> > > > >
> > > > > Please also provide the WSDL.
> > > > >
> > > > > On 9/23/05, Vishist Mandapaka < vishistm@gmail.com> wrote:
> > > > > >
> > > > > > hi,
> > > > > > I am using Axis 1.1 and deployed the webservice on Iplanet 6.1webserver. 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/}Server.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.
> > > > > >
> > > > > >
> > > >
> > >
> >
>
Re: Fault - makeTypeElement()
Posted by Vishist Mandapaka <vi...@gmail.com>.
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 <at...@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 <vi...@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> 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> wrote:
> > > >
> > > > Please also provide the WSDL.
> > > >
> > > > On 9/23/05, Vishist Mandapaka < vishistm@gmail.com> wrote:
> > > > >
> > > > > hi,
> > > > > I am using Axis 1.1 and deployed the webservice on Iplanet 6.1webserver. 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/}Server.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.
> > > > >
> > > > >
> > >
> >
>
Re: Fault - makeTypeElement()
Posted by Anne Thomas Manes <at...@gmail.com>.
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 <vi...@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 <at...@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> wrote:
> > >
> > > Please also provide the WSDL.
> > >
> > > On 9/23/05, Vishist Mandapaka < vishistm@gmail.com> wrote:
> > > >
> > > > hi,
> > > > I am using Axis 1.1 and deployed the webservice on Iplanet 6.1webserver. 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/}Server.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.
> > > >
> > > >
> >
>
Re: Fault - makeTypeElement()
Posted by Vishist Mandapaka <vi...@gmail.com>.
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 <at...@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 <at...@gmail.com> wrote:
> >
> > Please also provide the WSDL.
> >
> > On 9/23/05, Vishist Mandapaka < vishistm@gmail.com> wrote:
> > >
> > > hi,
> > > I am using Axis 1.1 and deployed the webservice on Iplanet 6.1webserver. 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/}Server.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.
> > >
> > >
>
Re: Fault - makeTypeElement()
Posted by Anne Thomas Manes <at...@gmail.com>.
After looking at your WSDL, I still think this is the problem.
Modify your schema declaration (in the xsd file -- not the WSDL) to this and
try it again:
<xs:schema targetNamespace="ssi_esap_lnp"
xmlns="ssi_esap_lnp"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
Anne
On 9/24/05, Anne Thomas Manes <at...@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 <at...@gmail.com> wrote:
> >
> > Please also provide the WSDL.
> >
> > On 9/23/05, Vishist Mandapaka < vishistm@gmail.com> wrote:
> > >
> > > hi,
> > > I am using Axis 1.1 and deployed the webservice on Iplanet 6.1webserver. 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/}Server.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.
> > >
> > >
> > >
> > > --
> > > Vishist Mandapaka
> > > email: vishistm@gmail.com
> > > Ph: (313) 282 8348
> > >
> >
> >
>
Re: Fault - makeTypeElement()
Posted by Anne Thomas Manes <at...@gmail.com>.
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 <at...@gmail.com> wrote:
>
> Please also provide the WSDL.
>
> On 9/23/05, Vishist Mandapaka <vi...@gmail.com> wrote:
> >
> > hi,
> > I am using Axis 1.1 and deployed the webservice on Iplanet 6.1webserver. 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/}Server.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.
> >
> >
> >
> > --
> > Vishist Mandapaka
> > email: vishistm@gmail.com
> > Ph: (313) 282 8348
> >
>
>
Re: Fault - makeTypeElement()
Posted by Anne Thomas Manes <at...@gmail.com>.
Please also provide the WSDL.
On 9/23/05, Vishist Mandapaka <vi...@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/}Server.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.
>
>
>
> --
> Vishist Mandapaka
> email: vishistm@gmail.com
> Ph: (313) 282 8348
>