Fault element name issues

Question

Back in January I noticed a post concerning generated WSDL files and fault
element not containing a required attribute "name".
I seem to be having the same problem in WLS8.1
Can this be possible since it was fixed in version 7SP2?
After I generate the web service, when I try to generate a JAXRPC client
(via the JavaSoft web services toolkit), it complains that the WSDL file is
invalid because there are <FAULT> elements without name attributes.
Also, I'm having a problem using the clientgen Ant task, its having an error
generating types. This worked 2 days ago when I was running 8.1beta, but
since I upgraded to 8.1 it no longer works.
M
"Bruce Stephens" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDLseems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late thisquarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write
my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a lookat this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people
too.
>>
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the
exception
messages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty(
"weblogic.webservice.servicenamechecking","false" );
>>>
>>
This is not a client issue. The WSDL is generating incorrect WSDL.Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException"xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey"xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal"xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException"xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL itis redefined
every time a method has the AgentisException in its interface (which inmy case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed in
the upcoming
release that will be
available for beta testing shortly. Contact [email protected]
if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types before
the EAR is deployed.There is an example to show how to do this:
http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
>>
Unfortunately this doesn't solve my problem. I still don't have an EARor WSDL
file from which I can generate a client to be included in the final EARfile that
gets deployed to the server. My original post explains this a bitbetter.
>>
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
Take a look at http://dev2dev.bea.com/direct/webservice/wswa.html#qz50
and others
in this area.
This was more in reference to the building of the web services in thefirst place
rather than registering custom datatypes at runtime. The manualprocedure is
documented athttp://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to writemy own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark

Answer 1

Please try 8.1 sp1, it is strictly wsdl spec complaint. It generates
<fault> with name.. Clientgen requires fault name to correctly parse wsdl.
thanks,
-Neal
"Mark Fine" <[email protected]> wrote in message
news:[email protected]...
Back in January I noticed a post concerning generated WSDL files and fault
element not containing a required attribute "name".
I seem to be having the same problem in WLS8.1
Can this be possible since it was fixed in version 7SP2?
After I generate the web service, when I try to generate a JAXRPC client
(via the JavaSoft web services toolkit), it complains that the WSDL fileis
invalid because there are <FAULT> elements without name attributes.
Also, I'm having a problem using the clientgen Ant task, its having anerror
generating types. This worked 2 days ago when I was running 8.1beta, but
since I upgraded to 8.1 it no longer works.
M
"Bruce Stephens" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDLseems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late thisquarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write
my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a
look
at this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people
too.
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the
exception
messages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty(
"weblogic.webservice.servicenamechecking","false" );
>
This is not a client issue. The WSDL is generating incorrect WSDL.Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException"
xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey"xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal"
xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException"
xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL
it
is redefined
every time a method has the AgentisException in its interface (which
in
my case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed
in
the upcoming
release that will be
available for beta testing shortly. Contact [email protected]
if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types
before
the EAR is deployed.There is an example to show how to do this:
http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
Unfortunately this doesn't solve my problem. I still don't have an
EAR
or WSDL
file from which I can generate a client to be included in the final
EAR
file that
gets deployed to the server. My original post explains this a bitbetter.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.Take a look at
http://dev2dev.bea.com/direct/webservice/wswa.html#qz50
and others
in this area.
This was more in reference to the building of the web services in thefirst place
rather than registering custom datatypes at runtime. The manualprocedure is
documented at
http://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to
write
my own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark