Document style webservice

Hello
I have created a document style webservice, the method signature takes Element as argument and returns elements back. ( i guess this is the limitation of using Document Style Web Service, as I would have rather prefered to have a complex type JAVABEAN as an argument)
Now going ahead, i have deployed this service to OC4J server and when I create the Stub at the client side, the return type of the method gets convered to Vector instead of Element.
Can anyone help me out how to get the Element return type back at the stub end.
Any help will highly be appreciated.
Also is there is a way to create a complex type Webservice using Document style ?
prab

Hello,
It is possible with OracleAS 10.1.3 out of the box.
Which release are you using?
Regards
Tugdual Grall

Similar Messages

Problem with document style webservice

Hi all,
I have written a webservice with the style = document and the protocol = https. I am getting xml passed in correctly, but when I return xml from the webservice it has been encoded, i.e. "<" becomes "<". Additionally the xml header (<?xml versionn....)is not being returned.
Any help would be most appreciated.
Cheers
Andy

Hi Andy,
Sounds like the XML is being converted into a string. Try the example
using a org.w3c.dom.Element [1] or send the XML as an attachment [2].
Regards,
Bruce
[1]
http://webservice.bea.com/dom.zip
[2]
http://manojc.com/?sample5
andy wrote:
>
Hi all,
I have written a webservice with the style = document and the protocol = https. I am getting xml passed in correctly, but when I return xml from the webservice it has been encoded, i.e. "<" becomes "<". Additionally the xml header (<?xml versionn....)is not being returned.
Any help would be most appreciated.
Cheers
Andy

Problem in Web service - document style

Hi,
I want to create document style webservices using axis tool.
so i need any sample codes and procedure for creating document style web services using axis tool . If any one help me in regarding this i will be thankfull to u.
regards
tuty.richard

WSADMIN transaction is obsolete from SAP NetWeaver AS 7.00, SP14. and help documentation says following: The same you can get it from information pop-up.
Start of Help Doc***************
From SAP NetWeaver AS 7.00, SP14, new service definitions in the ABAP development environment are no longer administered using transactions WSADMIN and WSCONFIG.
The transactions WSADMIN and WSCONFIG will remain active until all old web service configurations have been migrated, which means you can continue to configure web services from SAP NetWeaver AS 6.40, 7.00, and web service definitions from the XI 3.0 environment. You can also continue to access the runtime configurations of old service definitions using these transactions.
However, new service definitions created in the ABAP development environment will be hidden in these transactions.
End of Help Doc***************
So, You have to use SOAMANAGER transaction if your release is more than whatever specified above.
Regards,
Siva.

Wsdl2service and document style

Hello everybody.
This is very urgent so any help will be really appreciated.
I have a WSDL which uses document/literal style/encoding. I am running wsdl2service on it to generate java classes, and then proceeding successfully to generate and deploy a web service. The weblogic test page also works successfully.
But when I look at the SOAP on-the-wire message, it is not document style SOAP compliant, for example, for the operation CreateNewAccount, that takes in the schema Customer.xsd, I get the following message :
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:m0="http://www.schema.com/Bank">
     <SOAP-ENV:Body>
          <m:CreateNewAccount xmlns:m="http://www.telcordia.com/TestWebServices/Bank.wsdl">
               <m0:Name></m0:Name>
               <m0:SSN></m0:SSN>
               <m0:Balance>0</m0:Balance>
               <m0:Address>
                    <m0:Number></m0:Number>
                    <m0:Street></m0:Street>
                    <m0:State></m0:State>
                    <m0:Zip></m0:Zip>
               </m0:Address>
          </m:CreateNewAccount>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The way I understand, if this were document styled web-service, the operation name in above should be replaced by Customer.xsd root element name. (Pls see the attached WSDL).
I tried the same WSDL with the Systinet server, and it produced a SOAP message that I was expecting.
If I changed this WSDL to rpc mode, the CreateNewAccount node is followed by the Customer node, which is fine.
So my question is, is this a WLS 81 SP2 bug, or am I doing something wrong or missing something?
The WSDL :
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.telcordia.com/TestWebServices/Bank.wsdl" xmlns:ws="http://www.telcordia.com/TestWebServices/Bank.wsdl" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:sch="http://www.schema.com/Bank" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.telcordia.com/TestWebServices/Bank.wsdl">
     <import namespace="http://www.schema.com/Bank" location="Customer.xsd"/>
     <import namespace="http://www.schema.com/Bank" location="Ack.xsd"/>
     <types>
          <xs:schema xmlns:tns="http://www.telcordia.com/TestWebServices/Bank.wsdl"/>
     </types>
     <message name="CreateNewAccountRequest">
          <part name="body" element="sch:Customer"/>
     </message>
     <message name="CreateNewAccountResponse">
          <part name="body" element="sch:Ack"/>
     </message>
     <portType name="CreateNewAccountPortType">
          <operation name="CreateNewAccount">
               <input message="tns:CreateNewAccountRequest"/>
               <output message="tns:CreateNewAccountResponse"/>
          </operation>
     </portType>
     <binding name="CreateNewAccountBinding" type="tns:CreateNewAccountPortType">
          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="CreateNewAccount">
               <input>
                    <soap:body parts="body" use="literal"/>
               </input>
               <output>
                    <soap:body parts="body" use="literal"/>
               </output>
          </operation>
     </binding>
     <service name="AccountService">
          <port name="ws:CreateNewAccountPort" binding="tns:CreateNewAccountBinding">
               <soap:address location="http://taste.mk.telcordia.com:45000/TWS/NewAccountRequest"/>
          </port>
     </service>
</definitions>
=======================================================
The schemas :
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.schema.com/Bank" targetNamespace="http://www.schema.com/Bank" elementFormDefault="qualified">
     <xsd:element name="Customer">
          <xsd:complexType>
               <xsd:all>
                    <xsd:element name="Name"/>
                    <xsd:element name="SSN"/>
                    <xsd:element name="Balance" type="xsd:integer"/>
                    <xsd:element name="Address">
                         <xsd:complexType>
                              <xsd:all>
                                   <xsd:element name="Number"/>
                                   <xsd:element name="Street"/>
                                   <xsd:element name="State"/>
                                   <xsd:element name="Zip"/>
                              </xsd:all>
                         </xsd:complexType>
                    </xsd:element>
               </xsd:all>
          </xsd:complexType>
     </xsd:element>
</xsd:schema>
++++++++++++++++++++++++++++++++++++++++++++++++++++++
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.schema.com/Bank" targetNamespace="http://www.schema.com/Bank" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xsd:element name="Ack">
          <xsd:complexType>
               <xsd:all>
                    <xsd:element name="SSN"/>
                    <xsd:element name="AccountNumber"/>
               </xsd:all>
          </xsd:complexType>
     </xsd:element>
</xsd:schema>

The generated web-services.xml from wsdl2service can have either style="rpc" or
style="document". And in order to accomodate doc/lit operations that have multiple
params you would need to edit the web-services.xml to have style="documentwrapped".
Regards
Shridhar
Laxman Siyani <[email protected]> wrote:
Hi,
I have been using the autotype and wsdl2service ant tasks to generate
firstly a complex data type from the .xsd, associated with a .WSDL.
Then I use the wsdl2service to generate a Interface class which I implement.
When I deploy this and try to use it from the test page in the Console,
I get an error in the Weblogic.log:
ERROR: Backend components for Document style webservice can only accept
methods with one input parameter.
Does anyone know how I can get wsdl2service to generate documentwrapped
webservice.xml.
Many thanks,
Laxman

Differences between Document Style vs RPC style WS.

Hello All,
Can some body explain me the differences between a document style and rpc style webservices. Apart from JAX-RPC next version is JAX-WS, which supports document style and rpc, I also studied that document style webservices are meant for Asynchronous style of communication, where client would not block until the response is received.
In either way of writing services using JAX-WS, I currently annotate the service with @Webservice, generage the WSDL and from that WSDL I generate the client side artifacts.
Once the artifacts are received, in both styles of communication, I invoke the method on the port. Now, this does not differ in rpc style and document style. So what is the difference and where is that difference visible.
Similarly, in what way SOAP over HTTP differ from XML over HTTP. After all SOAP is also XML document with SOAP namespace. So what is the differnce here.

user13126996 wrote:
Can some body explain me the differences between a document style and rpc style webservices. Apart from JAX-RPC next version is JAX-WS, which supports document style and rpc, I also studied that document style webservices are meant for Asynchronous style of communication, where client would not block until the response is received. no, asynchronous vs. synchronous responses have nothing to do with rpc style vs. document style. they are two orthogonal concepts.
Once the artifacts are received, in both styles of communication, I invoke the method on the port. Now, this does not differ in rpc style and document style. So what is the difference and where is that difference visible.the difference is basically in how the data is encoded over the transport layer. in theory, you can encode some complex data structures more efficiently in the rpc style. in reality, no one ever uses these features. and since the document style is more strongly typed and much more "straightforward", most people tend to prefer the document style to the rpc style these days. (in fact, i don't think jaxws actually supports rpc style).
Similarly, in what way SOAP over HTTP differ from XML over HTTP. After all SOAP is also XML document with SOAP namespace. So what is the differnce here. none really. SOAP over HTTP is XML over HTTP. XML over HTTP has no strong specification, whereas SOAP puts lots of specs around what the XML should look like. also, obviously, SOAP can theoretically be sent over other transport layers besides HTTP (not that i've ever seen that).

Document based webservice failed

Hello:
I am trying to invoke a document style webservice
I am getting this error any idea why I am getting this.
I am returning a Document object which I created using DOM
Failed to invoke service:
java.util.EmptyStackException at java.util.Stack.peek(Stack.java:79) at
java.util.Stack.pop(Stack.java:61) at
weblogic.xml.babel.stream.DOMNodeWriter.write(DOMNodeWriter.java:125) at
weblogic.xml.babel.stream.DOMNodeWriter.write
regards
Boney Jose

Hello,
This error is unfamiliar and there is not enough information in your
post to ascertain the cause. Have you tried the examples of document
based webservices that Manoj has [1]? I think they would be helpful in
your efforts.
Regards,
Bruce
[1]
http://manojc.com/?sample13
http://manojc.com/?sample14
http://manojc.com/?sample31
http://manojc.com/?sample43
Boney Jose wrote:
>
Hello:
I am trying to invoke a document style webservice
I am getting this error any idea why I am getting this.
I am returning a Document object which I created using DOM
Failed to invoke service:
java.util.EmptyStackException at java.util.Stack.peek(Stack.java:79) at
java.util.Stack.pop(Stack.java:61) at
weblogic.xml.babel.stream.DOMNodeWriter.write(DOMNodeWriter.java:125) at
weblogic.xml.babel.stream.DOMNodeWriter.write
regards
Boney Jose

AxisFault seen while invoking document style web service

I am seeing the following stacktrace when I try to invoke a document-style web service.
<partnerRole name="MyWebService1_Role">
<ServiceName>{http://idm.oracle.com/}MyWebService1</ServiceName>
<PortType>{http://idm.oracle.com/}MyWebService1</PortType>
<Address>null</Address>
</partnerRole>
<conversationId>bpel://localhost/default/ProvisioningFromDAS~1.0/4202-BpInv0-BpSeq0.3-3</conversationId>
<properties>{}</properties>
</partnerLink>
<2005-09-06 09:23:37,650> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happened
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: caught exception while handling request: expected element is missing: {http://idm.oracle.com/}attribute
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:caught exception while handling request: expected element is missing: {http://idm.oracle.com/}attribute
at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
What could this mean ?

Hi,
I am getting a similar issue. I created a Document-style/literal webservice and deployed on Weblogic 9.2 . Then I generated client stubs using clientgen. I get the following exception stack trace:
java.rmi.RemoteException: web service invoke failed: javax.xml.soap.SOAPException:
failed to serialize class java.lang.Objectweblogic.xml.schema.binding.SerializationException: type mapping lookup failure on
class=class com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl TypeMapping=TYPEMAPPING SIZE=3
ENTRY 1:
class: java.lang.Object
xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocumentResponse
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@1125127
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@18dfef8
ENTRY 2:
class: java.lang.Object
xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocument
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@15e83f9
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@2a5330
ENTRY 3:
class: java.lang.Object
xsd_type: ['http://www.w3.org/2001/XMLSchema']:xsd:anyType
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@bb7465
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@d6c16c

Document style Problem

We have three issues when trying to implement a document-style service. I will
document them all but I'd suggest you go through them all before attempting to
answer any of them.
We are trying to implement a service that has the following signature:
public void echoDom(Document doc)
We want the delivery of our message to be of style ("document"). Therefore, we
modified our servicegen entry to include the style="document" under the service.
It looks like the following:
<servicegen
destEar="${appDir}/dom.ear"
warName="dom.war">
<service
javaClassComponents="examples.dom.EchoDom"
targetNamespace="http://examples.org"
serviceName="dom"
serviceURI="/EchoDomService"
generateTypes="True"
expandMethods="True"
style="document">
<client
packageName="examples.dom"
clientJarName="client.jar"
/>
</service>
<classpath>
<pathelement path="${temp_dir}"/>
<pathelement path="${java.class.path}"/>
</classpath>
</servicegen>
1. FIRST PROBLEM:
The first problem we're having is that it does not compile with the combination
of our signature being of type void (as shown above) and the style="document"
in build.xml.
The error is the following:
[servicegen] Generating service "dom" ...
[servicegen] Generating XML types and serializers from java classes (examples.do
m.EchoDom) ...
[servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ void:
null ]
[servicegen] at weblogic.utils.Debug.assertion(Debug.java:84)
[servicegen] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile
(Compiler.java:111)
[servicegen] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
pClass(XSDTypeMappingBuilder.java:88)
[servicegen] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
ddMapping(TypeMappingBuilderBase.java:183)
[servicegen] at weblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper
.mapComponent(ComponentAutoTyper.java:155)
[servicegen] at weblogic.ant.taskdefs.webservices.autotype.JavaAutoTyper.run(
JavaAutoTyper.java:80)
[servicegen] at weblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execu
te(AutoTypeTask.java:353)
[servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g
enerateService(ServiceGenTask.java:251)
[servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e
xecute(ServiceGenTask.java:146)
[servicegen] at org.apache.tools.ant.Task.perform(Task.java:217)
[servicegen] at org.apache.tools.ant.Target.execute(Target.java:164)
[servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[servicegen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[servicegen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[servicegen] at org.apache.tools.ant.Main.start(Main.java:153)
[servicegen] at org.apache.tools.ant.Main.main(Main.java:176)
2. SECOND PROBLEM
If we change the signature to become:
public Document echoDom(Document doc)
then the build works but when we try to test our service, it gives us the following:
[java] java.rmi.RemoteException: web service invoke failed; nested exceptio
n is:
[java] javax.xml.soap.SOAPException: failed to serialize xml:weblogic.
xml.schema.binding.SerializationException: type mapping lookup failure on class=
class weblogic.apache.xerces.dom.DocumentImpl TypeMapping=TYPEMAPPING SIZE=6
[java] ENTRY 1:
[java] class: org.w3c.dom.Document
[java] xsd_type: ['http://examples.org']:p3:echoDom
[java] ser: weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@5973ea
[java] deser: weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@49131c
[java] ENTRY 2:
[java] class: java.lang.Object
[java] xsd_type: ['http://examples.org']:p1:echoDomResponse
[java] ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
5b99f
[java] deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
3. THIRD PROBLEM:
Now, when we revert back to style="rpc" and everything works fine and dandy (although
not as we want it because, as I mentioned above, we want a void signature and
a document style), we get the following added tag around our body content, which
we did not add ourselves, nor are we sure yet why it shows up:
We pass it the following argument:
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
We get the following (notice the <document> tag around it):
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
4. PROBLEM FOUR (just remembered this one):
If we use the standard test page (provided with WLS), with (3) above, it chops
off the "those" and it still wraps it within this new <document> element as show
below:

<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
</env:Header>
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
We're not so worried about the fourth because it seems like a bug but the first
three (especially the first) are most important. Any ideas would be appreciated.
Thanks
sami

Ok I tried it out, DOM with document style web
service is not working in WLS 7.0.2. I filed
CR104719. Please contact support with this case
number to get a patch.
Sorry for the trouble.
http://manojc.com
"sami titi" <[email protected]> wrote in message
news:[email protected]...
>
We're using WLS7 SP2, patch: CR102544_70sp2_v2.jar
thanks
"manoj cheenath" <[email protected]> wrote:
Quick question, before i try this out.
Which version of WLS? SP?
http://manojc.com
"sami titi" <[email protected]> wrote in message
news:[email protected]...
We have three issues when trying to implement a document-style service.I
will
document them all but I'd suggest you go through them all beforeattempting to
answer any of them.
We are trying to implement a service that has the following signature:
public void echoDom(Document doc)
We want the delivery of our message to be of style ("document").Therefore, we
modified our servicegen entry to include the style="document" underthe
service.
It looks like the following:
<servicegen
destEar="${appDir}/dom.ear"
warName="dom.war">
<service
javaClassComponents="examples.dom.EchoDom"
targetNamespace="http://examples.org"
serviceName="dom"
serviceURI="/EchoDomService"
generateTypes="True"
expandMethods="True"
style="document">
<client
packageName="examples.dom"
clientJarName="client.jar"
/>
</service>
<classpath>
<pathelement path="${temp_dir}"/>
<pathelement path="${java.class.path}"/>
</classpath>
</servicegen>
1. FIRST PROBLEM:
The first problem we're having is that it does not compile with thecombination
of our signature being of type void (as shown above) and thestyle="document"
in build.xml.
The error is the following:
[servicegen] Generating service "dom" ...
[servicegen] Generating XML types and serializers from java classes(examples.do
m.EchoDom) ...
[servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED*****[ void:
null ]
[servicegen] at weblogic.utils.Debug.assertion(Debug.java:84)
[servicegen] atweblogic.xml.schema.binding.internal.codegen.Compiler.compile
(Compiler.java:111)
[servicegen] atweblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
pClass(XSDTypeMappingBuilder.java:88)
[servicegen] atweblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
ddMapping(TypeMappingBuilderBase.java:183)
[servicegen] atweblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper
mapComponent(ComponentAutoTyper.java:155)
[servicegen] atweblogic.ant.taskdefs.webservices.autotype.JavaAutoTyper.run(
JavaAutoTyper.java:80)
[servicegen] atweblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execu
te(AutoTypeTask.java:353)
[servicegen] atweblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g
enerateService(ServiceGenTask.java:251)
[servicegen] atweblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e
xecute(ServiceGenTask.java:146)
[servicegen] at org.apache.tools.ant.Task.perform(Task.java:217)
[servicegen] at org.apache.tools.ant.Target.execute(Target.java:164)
[servicegen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[servicegen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[servicegen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[servicegen] at org.apache.tools.ant.Main.start(Main.java:153)
[servicegen] at org.apache.tools.ant.Main.main(Main.java:176)
2. SECOND PROBLEM
If we change the signature to become:
public Document echoDom(Document doc)
then the build works but when we try to test our service, it givesus the
following:
[java] java.rmi.RemoteException: web service invoke failed; nestedexceptio
n is:
[java] javax.xml.soap.SOAPException: failed to serializexml:weblogic.
xml.schema.binding.SerializationException: type mapping lookup failureon
class=
class weblogic.apache.xerces.dom.DocumentImpl TypeMapping=TYPEMAPPINGSIZE=6
[java] ENTRY 1:
[java] class: org.w3c.dom.Document
[java] xsd_type: ['http://examples.org']:p3:echoDom
[java] ser:weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@5973ea
[java] deser:weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@49131c
[java] ENTRY 2:
[java] class: java.lang.Object
[java] xsd_type: ['http://examples.org']:p1:echoDomResponse
[java] ser:weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
5b99f
[java] deser:weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
3. THIRD PROBLEM:
Now, when we revert back to style="rpc" and everything works fine anddandy (although
not as we want it because, as I mentioned above, we want a void
signature
and
a document style), we get the following added tag around our body
content,
which
we did not add ourselves, nor are we sure yet why it shows up:
We pass it the following argument:
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
We get the following (notice the <document> tag around it):
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
4. PROBLEM FOUR (just remembered this one):
If we use the standard test page (provided with WLS), with (3) above,it
chops
off the "those" and it still wraps it within this new <document>
element
as show
below:

<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
</env:Header>
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
We're not so worried about the fourth because it seems like a bug butthe
first
three (especially the first) are most important. Any ideas would beappreciated.
Thanks
sami

Trouble Communicating with Document-Style Web Service

I have a flash app that currently communicates with a
RPC-style web service. I changed the web service to be
document-style, and the flash app no longer sends valid requests. I
was under the impression that one could simple swtich styles, and
flash would play along. Apparently, this is not the case. Does
anyone have an insight in this area?

Clarified with Partick Calahan, who is maintaining this tool.
Currently, doc style is not handled by this tool. I guess it will be
supported in the future.
Thanks.
"Karthik V" <[email protected]> wrote in message
news:[email protected]..
I'm using WebLogic Webservice Explorer v.02 (WEX).
I'm able to test rpc style web services without any problem.
But whenever I try to open a document style web service WSDL, I get the
following exception.
I would appreciate if you have any suggestions for the to over come this
issue.
java.lang.IllegalArgumentException at
weblogic.webservice.tools.wex.MessagePanel.<init>(MessagePanel.java:33)at
>
weblogic.webservice.tools.wex.ServicePanel.operationChanged(ServicePanel.jav
a:153) at
weblogic.webservice.tools.wex.ServicePanel.portChanged(ServicePanel.java:133
) at
weblogic.webservice.tools.wex.ServicePanel.serviceChanged(ServicePanel.java:
121) at
weblogic.webservice.tools.wex.ServicePanel.<init>(ServicePanel.java:69)at
>
weblogic.webservice.tools.wex.tasks.FetchWsdlTask.perform(FetchWsdlTask.java
:45) at
weblogic.webservice.tools.wex.tasks.TaskQueue.run(TaskQueue.java:47) at
java.lang.Thread.run(Unknown Source)

Problem deploying document style web service(urgent help required)

I am getting this particular exception on my browser when I am trying to view the list of services after having deployed the service. The exception and complete stack trace is follows. I have also included the portion of the WSDD file giving details about the service.
And now... Some Services
AXIS error
Sorry, something seems to have gone wrong... here are the details:
Exception - org.apache.axis.ConfigurationException: java.lang.ClassCastException
java.lang.ClassCastException
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:302)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
     at org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment.java:394)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:276)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
     at org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
     at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:430)
     at org.apache.axis.deployment.wsdd.WSDDDeployment.getDeployedServices(WSDDDeployment.java:503)
     at org.apache.axis.configuration.FileProvider.getDeployedServices(FileProvider.java:296)
     at org.apache.axis.transport.http.AxisServlet.reportAvailableServices(AxisServlet.java:482)
     at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:260)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
     at java.lang.Thread.run(Thread.java:534)
org.apache.axis.ConfigurationException: java.lang.ClassCastException
java.lang.ClassCastException
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:302)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
     at org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment.java:394)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:276)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
     at org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
     at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:430)
     at org.apache.axis.deployment.wsdd.WSDDDeployment.getDeployedServices(WSDDDeployment.java:503)
     at org.apache.axis.configuration.FileProvider.getDeployedServices(FileProvider.java:296)
     at org.apache.axis.transport.http.AxisServlet.reportAvailableServices(AxisServlet.java:482)
     at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:260)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
     at java.lang.Thread.run(Thread.java:534)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:304)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
     at org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment.java:394)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:276)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
     at org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
     at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:430)
     at org.apache.axis.deployment.wsdd.WSDDDeployment.getDeployedServices(WSDDDeployment.java:503)
     at org.apache.axis.configuration.FileProvider.getDeployedServices(FileProvider.java:296)
     at org.apache.axis.transport.http.AxisServlet.reportAvailableServices(AxisServlet.java:482)
     at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:260)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
     at java.lang.Thread.run(Thread.java:534)
The snippet from the WSDD is as follows:
<handler name="RequestHandler" type="java:com.doc.service.DataHandler"/>
<service name="AddCalcService" provider="java:MSG">
<parameter name="allowedMethods" value="*"/>
<parameter name="className" value="com.doc.service.AddCalcService"/>
<requestFlow>
     <handler type="RequestHandler"/>
</requestFlow>
<responseFlow>
     <handler type="RequestHandler"/>
</responseFlow>
</service>
Could someone tell what the cause of this exception and how it could be resolved.

Hi Bruce,
Thanks for all the links - am trudging through them now.
-Leena
Bruce Stephens <[email protected]> wrote:
Hi Lenna,
You might take a look at the SOAPBuilders interop tests.
See: http://www.whitemesa.com/r3/interop3.html and notice the DocLit
tests.
Our endpoints are http://webservice.bea.com:7001 and the code for the
client and servers can be located here:
http://webservice.bea.com/index.html#qz40
The good folks with WS-I have spent many cycles on interop issues. You
might have a look at their work:
http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html
Hope this is of some value,
Bruce
leena wrote:
Hi,
I am trying to build a synchronous document-style web service, andthe bea
site doesnt seem to have much documentation on it. I have a samplewritten with
SOAPElement as the input and output of my method, no schemas, my reqand response
are anyType, but im not sure if that is the best way to go. AND, itdoesnt work
yet.
Can anyone point me to a place where i can look for information ?i am on weblogic
8.1. I would eventually also want my input/output xml to be definedby my schema.
I see in examples that DOM Documents may also be passed as parameters(inand out)
? is there any place i can read up on this and decide what the bestoption for
me is ? Also, i will be running a .Net client against this, so if thereis anything
i need to keep in mind, i would appreciate it if anyone gave me anyinfo.
Thanks in advance!
leena.

Issue when Converting RPC styled Webservice to Document Styled Webservice

Hi All,
My requirement is to create a Document style WS using Jdev10.1.2 and deploy it in the OAS server 10.1.2 which follows J2EE1.3 standards.
since jdev10.1.2 does not have inherit option of developing Doc'Style WS,
I created a RPC Styled Webservice using Jdeveloper10.1.2 and converted it into Document styled webservice by changing the WEB.xml file in the WS project.
The link from which i learned the changes is given below
http://radio-weblogs.com/0132036/2003/12/07.html
PFB the changes made in my WEB.xml file.
<servlet-class>oracle.j2ee.ws.StatelessJavaRPCWebService</servlet-class> to <servlet-class>oracle.j2ee.ws.StatelessJavaDocWebService</servlet-class>.
I deployed the WS in the OAS10.1.2 server successfully.
Now the ISSUE is when im invoking the webservice. It is failing with the following error.
Error parsing the WSDL for this endpoint.
javax.servlet.ServletException: WSDL Generation exception: Error: method HelloWorld -- cannot use document style binding when output requires encoding
how to solve this error ?
If any one came across this error.
pls help.

What does the registry key you installed ?
If you want to get rid of the save dialog box, you can try to use the VBA code.
Private Sub Workbook_BeforeClose(Cancel As Boolean)
Me.Close savechanges:=True "close and save changes, don't ask".
Me.Close savechanges:=False "close and don't save changes, don't ask".
End Sub
Wind Zhang
TechNet Community Support

Problem invoking document type webservices with SAAJ

I cannot invoke document type webservices with SAAJ. No problems invoking rpc-style services. Can anyone help me to invoke doc-type webservices with SAAJ. Very urgent. Thank you.

Siva Sankar
You may use Field Exit to do this enhancement. You can create fieldexit from report RSMODPRF.
In order to use field exit check/activate Profile Parameter abap/fieldexit using t code RZ11.
Thanks & regards
Amol Lohade

Rpc & document style WSDL

Hi guys,
I have WSDL which contains both " rpc " & " document" style soap operation.
Can i used "rpc" style to call the webservice ? Does PI 7.0 supports the style="rpc" to call the webservice?
Please suggest me on this.
Thanks & regards
Ashwin Kumar Dhakne

Hi,
please read question:
Does the RPC or Document style in WSDL play a role in the SOAP adapter?
from OSS note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
Regards,
Michal Krawczyk

WS using document-style encoding

Could someone point me to article(s)/tutorial(s) how to create WebService with document-style encoding (as oposed to RPC-encoding) using NetWeaver?
Thanks in advance,
VS

[ -closed with no resolution- ]

Axis Document Style Support ???

I'm trying to develop a document style web service using axis and castor framework. Got help from
http://www-106.ibm.com/developerworks/webservices/library/ws-castor/ article.
All the development is done and the web service is working fine.'
But when I try to create the WSDL file from the ?wsdl query string, it doesn't give me the complete wsdl file. It has some types which are not defined in the schema. Is there anyone who has done this successfully. I would like to know how you did it..Basically what I want is to create a web reference from .Net and consume the webservice.
Thanks

>
wscompile -keep -verbose -import -f:documentliteral
-f:nodatabinding config.xml
wscompile -cp . -keep -verbose -gen:server
serverconfig.xml
[creating model: test]
[creating service: Test]
[creating port: MyIntf]
[creating operation: callTXLife]
error: Type "javax.xml.soap.SOAPElement" implements
more than one interface, interfaces:
"javax.xml.soap.Node", "org.w3c
.dom.Element" ...
I have the same problem with J2EE 1.4 AS Developer Release.

Document style webservice

Similar Messages

Maybe you are looking for