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.

Similar Messages

Does UTL_HTTP support calling document style web service??

Hi,
I am exploring UTL_HTTP options for one of the web service call requirement at a customer site.
Can any one tell if they have used UTL_HTTP for a document style service.
If so, pls share the code.
TIA,
-Bhawani

>
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.

Faults with document style operation

I am getting the following error when attempting to generate stubs from my WSDL:
warning: ignoring fault "TestError" of document-style operation "testOperationWithFault"
Are faults not supported for document-style operations or is my WSDL incorrect. (I was able to succesfully generate stubs with exceptions with this same WSDL using Apache Axis).
Also, you can see that I have commented out the attribute elements on my complex type definition. It seems that when I use attributes the generated stub has methods that take a javax.xml.soap.SOAPElement as an argument instead of an object of type TestInputType. Does the Sun wscompile tool not support attributes or again, is my WSDL incorrect?
Thanks.
Here is my test WSDL:
<?xml version="1.0"?>
<definitions
targetNamespace="http://www.convergys.com/services/Test"
xmlns:tns="http://www.convergys.com/services/Test"
          xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
          xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<xsd:schema targetNamespace="http://www.convergys.com/services/Test">
     <xsd:simpleType name="ReportingLevel">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="S" />
          <xsd:enumeration value="D" />
          <xsd:enumeration value="M" />
          <xsd:enumeration value="" />
          </xsd:restriction>
     </xsd:simpleType>
<xsd:element name="inputTest" type="tns:TestInputType" />
<xsd:complexType name="TestInputType">

<xsd:all>
<xsd:element name="user" type="xsd:string" />
<xsd:element name="passwd" type="xsd:string" />
<xsd:element name="auditId" type="xsd:string"
minOccurs="0" />
<xsd:element name="intAttr" type="xsd:int" />
<xsd:element name="shortAttr" type="xsd:short" />
<xsd:element name="booleanAttr" type="xsd:boolean" />
<xsd:element name="dateTimeAttr" type="xsd:dateTime" />
<xsd:element name="dateAttr" type="xsd:date"/>
<xsd:element name="base64BinaryAttr" type="xsd:base64Binary" />
<xsd:element name= "anyAttr" type="xsd:anyType"
minOccurs="0" maxOccurs="1" />
<xsd:element name= "enumAttr" type="tns:ReportingLevel" />
</xsd:all>
</xsd:complexType>
<xsd:element name="outputTest" type="tns:TestOutputType" />
<xsd:complexType name="TestOutputType">
<xsd:all>
<xsd:element name="token" type="xsd:string" />
<xsd:element name="roleUserId" type="xsd:string"
minOccurs="0" />
</xsd:all>
</xsd:complexType>
</xsd:schema>
</types>
<message name="TestRequest">
<part name="parameters" element="tns:inputTest" />
</message>
<message name="TestResponse">
<part name="result" element="tns:outputTest" />
</message>

<message name="TestError">
<part name="errorString" type="xsd:string" />
</message>
<portType name="MyServicePort">
<operation name="testOperation">
<input message="tns:TestRequest" />
<output message="tns:TestResponse" />
</operation>

<operation name="testOperationWithFault">
<input message="tns:TestRequest" />
<output message="tns:TestResponse" />
<fault name="TestError" message="tns:TestError" />
</operation>
</portType>
<binding name="MyServiceSOAPBinding" type="tns:MyServicePort">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document" />
<operation name="testOperation">
<soap:operation soapAction="" />
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
</operation>

<operation name="testOperationWithFault">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
<fault name="TestError">
<soap:fault name="TestError" use="literal" />
</fault>
</operation>
</binding>
<service name="MyServiceService">
<port name="MyServicePort" binding="tns:MyServiceSOAPBinding">
<soap:address location="http://azure:15481/MyTestWebApp/mysnoop" />
</port>
</service>
</definitions>

msauer, the JAXRPC-RI does not support faults in document/literal. JAXRPC does not support the xsd:date type, that is why you are getting SOAPElement. If you change this to be xsd:dateTime it should work for you.

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

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.

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.

JAX-RPC Document style WS

Is it possible to create a JAX-RPC document style web service that
returns an array of bytes ?
I have problems, but with jdeveloper 10.1.3 ´s tools.
With Axis I have NO problems.
Does anybody know why?
Sincerely
Jon Kepa Gerrikagoitia

Hello Mr. Grall,
I´m using jDeveloper 10.1.3 preview version.
I use bottom-up design so I rely on jDeveloper to do all the "dirty" job.
If I create a class that returns an array I cant create a document/Literal WS because jDev shows an error.
But If I choose document/wrapped it works !
Do tou know the reason of this ?
Sincerely,
Jon Kepa Gerrikagoitia.

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).

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

Custom Document Style Upgrade Error

After we upgraded from 3.6.1 multi-user version to 11.1 multi-user version, when I log in (as the administrator) it immediately displays a window saying:
"The system is upgrading the custom document styles..."
However it ends with "Partial Custom Document Style Upgrade" saying not all of the documents were processed. When I view the activity log, it says:
"Could not find original style in brand."
What does this mean, and how do we fix this? We are unable to publish now.
Thanks.
Update - this was resolved by working with Oracle Support.
Edited by: user9288563 on May 9, 2012 11:06 AM

Update - this was resolved by working with Oracle Support.

Quick Web Services Using Document Style Messaging

Hello all,
I am using Apache Axis and am trying to set up a document style (message based) webservice that will receive a DOM object, modify that DOM object, and return it as a new DOM object. I have not problems with standard RPC style webservices, but am unsure as to where to go with the more complex. I have included everything that may be helpful to give me an answer.....
I have set up my webservice (a very simple one to get this going):
package testing.webservices;
import org.w3c.dom.Document;
import org.apache.axis.MessageContext;
public class DocTest{
public Document doSubmission(MessageContext msgContext, Document inDoc)throws Exception{
return inDoc;
I set this class up in Axis with my deploy.wsdd file:
<deployment name="test" xmlns="http://xml.apache.org/axis/wsdd/"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance">
<service name="DocService" style="java:MSG">
<parameter name="className" value="testing.webservices.DocTest" />
<parameter name="allowedMethods" value="doSubmission" />
</service>
</deployment>
When I look at Axis it lists this DocService as an active service. Can anyone tell me what the client code would look like to send a Document object to my simple webservice and receive a document object back? Any help would be greatly appreciated.
J-Rod
NOTE: This is what I have so far:
import .....
public class DocTestClient{
public static void main(String[] args) throws Exception {
String fileName = "C:\\Dev\\MyXmlFile.xml";
String uri = "file:" + new File(fileName).getAbsolutePath( );
DocumentBuilderFactory factory =DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
Document doc = builder.parse(uri);
String endpointURL = "http://localhost:8080/axis/services/DocService";
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(new java.net.URL(endpointURL) );
call.setOperationName(new QName("http://testing.webservices", "doSubmission") );
?????? WHAT DO I DO HERE to access the send the doc object and receive it back?????
}

Just thought I'd post an update. We figured out how to stream the required data as a string so I OK now. We ended up going with java:RPC to string data back and forth.
Thanks
J-Rod

My iPad say document not supported for all in one 6450 printer

I have installed the e print for my iPad and while trying to print, it says document not supported. I have a wireless All in One 6450 Printer

Eddy955, hope you are doing well and welcome to the HP forums;
What document are you trying to print and what application are you using to print it.
If you are using ePrint, bear in mind that there some limitations to the files that you can print this are the limitations in type of document and size.
"supported format:
Microsoft Word
Microsoft PowerPoint
Microsoft Outlook
Microsoft Excel*
Text files (.txt)
PDF
Images (bmp, jpg, png, gif, tiff)
also there are size limitations for this docs
the document cannot be larger than 5 mb's and it cannot be more that 10 attatchments, for a more comprehensive list go to this link.
https://h30495.www3.hp.com/help/
Do not hesitate to let me know if you need more assistance. I will do my best to help you.
RobertoR
▼
You can say THANKS by clicking the KUDOS STAR. If my suggestion resolves your issue Mark as a "SOLUTION" this way others can benefit Thanks in Advance!

Calling a document style web service using a pl/sql wrapper method

Just wanted to find out if anybody has a working example of invoking a document style web service from Oracle 10g database on a Unix environment.
We have java test class that invokes the web service, and we are trying to use a pl/sql wrapper to invoke a Java Web Service client. So far, we are encountering an End of File Communication error from Oracle which essentially terminates the session with the database.
On the Oracle application server side we are able to see a successful HTTP request made to the application server via server log, which is hosting the web service, since we are registering HTTP 200 success codes. However, we do not see any other errors from the application in the server logs. Most likely since the client side fails, before actually getting a chance to invoke the web service. This has been verified by commenting the client code leaving the print statements. The first call to the Service Factory method (XFire) to look up the service is where the PL/SQL procedure fails with an End of File communication error.

Remove the when others section and see the actual error and post that.
http://tkyte.blogspot.com/2008/06/when-others-then-null-redux.html
http://tkyte.blogspot.com/2007/03/dreaded-others-then-null-strikes-again.html

Axis Document Style Support ???

Similar Messages

Maybe you are looking for