Web service deployment using generated wsdl

Hi,
As u know app server is generating the wsdl and mapping files in deployment time if you dont include these files in the archive.
What i m trying to do is to use the pregenerated wsdl and mapping file in the archieve, i don't want app server to generate wsdl and mapping. I'm generating these files in build phase and placing them under META-INF folder of resulting jar file.
And i expect oc4j to use these supplied files but it continues to generate and uses the generated.
(I'm using wsa.jar to generate wsdl, mean i'm generating in oracle way, not other tool)
(I dont want to use the auto generated wsdl cause i need to update them before deployment. Auto generated wsdl have data definition with object graphs which is not supported by document-literal message format. i will try to clean object graph dependencies in wsdl and deploy) Or shall i use Rpc-Encoded which supports object graphs??
Thanks...

it seems that it is hard to extract main question from the preview post. The question is that:
how can i deploy web service for a stateless session bean annotated with @webService annotations with supplied wsdl and mapping file in the ejb jar file...
(oc4j always generates a new wsdl,does;t use the one given in the jar)

Similar Messages

Errors creating a Web Service Proxy using Microsoft WSDL.exe tool

I have deployed a BPEL process using JDeveloper. This process can be invoked from the BPEL console and completes as expected. I am trying to create a Web Service Proxy using the Microsoft WSDL.exe tool so that the process can be invoked from a Microsoft Word document. This process is based on the AutoLoan example in the Developer's Guide for Microsoft Office Interoperability B25781-01.
WSDL.exe returns the following error message
Error: There was an error processing 'http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0/HonorariumSmartDoc?wsdl'.
- The document at the url http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0/HonorariumSmartDoc?wsdl was not recognized as a known document type. The error message from each known type may help you fix the problem:
- Report from 'WSDL Document' is 'There is an error in XML document (19, 7).'.
- A schema with the namespace '' has already been added.
- Report from 'DISCO Document' is 'Discovery document at the URL http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0/HonorariumSmartDoc?wsdl could not be found.'.
- The document format is not recognized.
- Report from 'XML Schema' is 'Expected Schema root. Make sure that the root element is <schema> and the namespace is 'http://www.w3.org/2001/XMLSchema' for an XSD schema or 'urn:schemas-microsoft-com:xml-data' for an XDR schema. An error occurred at , (2, 2).'.
How do I resolve this error?

The WSDL file is below.
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions name="HonorariumSmartDoc" targetNamespace="http://xmlns.oracle.com/HonorariumSmartDoc" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.oracle.com/HonorariumSmartDoc" xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:client="http://xmlns.oracle.com/HonorariumSmartDoc">
- <types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/HonorariumSmartDoc" schemaLocation="HonorariumSmartDoc.xsd" />
</schema>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://erp.template.co.uk:8889/orabpel/xmllib/ws-addressing.xsd" />
</schema>
</types>
- <message name="HonorariumSmartDocResponseMessage">
<part name="payload" element="tns:HonorariumSmartDocProcessResponse" />
</message>
- <message name="HonorariumSmartDocRequestMessage">
<part name="payload" element="tns:HonorariumSmartDocProcessRequest" />
</message>
- <message name="WSARelatesToHeader">
<part name="RelatesTo" element="wsa:RelatesTo" />
</message>
- <message name="WSAReplyToHeader">
<part name="ReplyTo" element="wsa:ReplyTo" />
</message>
- <message name="WSAMessageIDHeader">
<part name="MessageID" element="wsa:MessageID" />
</message>
- <portType name="HonorariumSmartDocCallback">
- <operation name="onResult">
<input message="tns:HonorariumSmartDocResponseMessage" />
</operation>
</portType>
- <portType name="HonorariumSmartDoc">
- <operation name="initiate">
<input message="tns:HonorariumSmartDocRequestMessage" />
</operation>
</portType>
- <binding name="HonorariumSmartDocBinding" type="tns:HonorariumSmartDoc">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="initiate">
<soap:operation style="document" soapAction="initiate" />
- <input>
<soap:header message="tns:WSAReplyToHeader" part="ReplyTo" use="literal" encodingStyle="" />
<soap:header message="tns:WSAMessageIDHeader" part="MessageID" use="literal" encodingStyle="" />
<soap:body use="literal" />
</input>
</operation>
</binding>
- <binding name="HonorariumSmartDocCallbackBinding" type="tns:HonorariumSmartDocCallback">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="onResult">
<soap:operation style="document" soapAction="onResult" />
- <input>
<soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle="" />
<soap:body use="literal" />
</input>
</operation>
</binding>
- <service name="HonorariumSmartDocCallbackService">
- <port name="HonorariumSmartDocCallbackPort" binding="tns:HonorariumSmartDocCallbackBinding">
<soap:address location="http://set.by.caller" />
</port>
</service>
- <service name="HonorariumSmartDoc">
- <port name="HonorariumSmartDocPort" binding="tns:HonorariumSmartDocBinding">
<soap:address location="http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0" />
</port>
</service>
- <plnk:partnerLinkType name="HonorariumSmartDoc">
- <plnk:role name="HonorariumSmartDocProvider">
<plnk:portType name="tns:HonorariumSmartDoc" />
</plnk:role>
- <plnk:role name="HonorariumSmartDocRequester">
<plnk:portType name="tns:HonorariumSmartDocCallback" />
</plnk:role>
</plnk:partnerLinkType>
</definitions>

Unable to Start web service deployed using jaxws

Hi guys,
I have created a web service using jax-ws and have deployed it using JWSDP Web Application Manager(tomcat 5.0). I'm using JDK 1.6.
The service is getting deployed fine without any error. but when i try to start the service it gives me the following error.
I have tried by myself but not able to reach at end
following is the error message
Caused by: java.lang.IllegalArgumentException: com.sun.xml.internal.messaging.saaj.soap.LocalStrings != com.sun.xml.messaging.saaj.soap.LocalStrings
     at java.util.logging.Logger.getLogger(Logger.java:328)
     at com.sun.xml.messaging.saaj.soap.ExpressMessageFactoryImpl.<clinit>(ExpressMessageFactoryImpl.java:52)
     ... 49 moreFull Stack Trace
2008-02-18 16:54:39 StandardContext[/manager]HTMLManager: start: Starting web application at '/StockQuoteService'
2008-02-18 16:54:43 StandardContext[/StockQuoteService]Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
java.lang.ExceptionInInitializerError
     at com.sun.xml.xwss.SystemHandlerDelegateImpl.<init>(SystemHandlerDelegateImpl.java:129)
     at com.sun.xml.xwss.SystemHandlerDelegateFactory.create(SystemHandlerDelegateFactory.java:26)
     at com.sun.xml.ws.spi.runtime.SystemHandlerDelegateFactory.getDelegate(SystemHandlerDelegateFactory.java:59)
     at com.sun.xml.ws.binding.soap.SOAPBindingImpl.setupSystemHandlerDelegate(SOAPBindingImpl.java:205)
     at com.sun.xml.ws.binding.soap.SOAPBindingImpl.<init>(SOAPBindingImpl.java:66)
     at com.sun.xml.ws.binding.BindingImpl.getBinding(BindingImpl.java:179)
     at com.sun.xml.ws.transport.http.servlet.RuntimeEndpointInfoParser.parseEndpoints(RuntimeEndpointInfoParser.java:118)
     at com.sun.xml.ws.transport.http.servlet.RuntimeEndpointInfoParser.parse(RuntimeEndpointInfoParser.java:64)
     at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:112)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4226)
     at org.apache.catalina.core.StandardHostDeployer.start(StandardHostDeployer.java:722)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:957)
     at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1280)
     at org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:531)
     at org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:106)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:790)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:709)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:572)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:644)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalArgumentException: com.sun.xml.internal.messaging.saaj.soap.LocalStrings != com.sun.xml.messaging.saaj.soap.LocalStrings
     at java.util.logging.Logger.getLogger(Logger.java:328)
     at com.sun.xml.messaging.saaj.soap.ExpressMessageFactoryImpl.<clinit>(ExpressMessageFactoryImpl.java:52)
     ... 46 moreEdited by: Amie on Feb 18, 2008 5:03 PM

I'm facing the same problem in my own application on client side :
Exception in thread "main" java.lang.ExceptionInInitializerError
     at com.sun.xml.ws.message.AttachmentUnmarshallerImpl.<clinit>(AttachmentUnmarshallerImpl.java:55)
     at com.sun.xml.ws.message.stream.StreamMessage.readPayloadAsJAXB(StreamMessage.java:201)
     at com.sun.xml.ws.fault.SOAPFaultBuilder.create(SOAPFaultBuilder.java:463)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:239)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
     at $Proxy30.index(Unknown Source)
     at com.xxxxxxxxx(IndexClientTest.java:64)
Caused by: java.lang.IllegalArgumentException: com.sun.xml.internal.messaging.saaj.soap.LocalStrings != com.sun.xml.messaging.saaj.soap.LocalStrings
     at java.util.logging.Logger.getLogger(Logger.java:328)
     at com.sun.xml.messaging.saaj.soap.AttachmentPartImpl.<clinit>(AttachmentPartImpl.java:71)
     ... 8 more
The Web service has been using JAXWS under JDK 1.6.0_10-ea and deployed under tomcat 6.0.14. It seems to work well. The client have problem while handling the response and crash.
Any ideas ?

Can not set up Web Service datastore using HTTPS WSDL DS 4.1

I have been trying to configure a Web services data store to connect to an HTTPS Wsdl file
Here is some background.
DS Version: 14.1.1.210
Job Server Windows 2008
if i configure the datastore and leave the field for Keystore path empty, i get the following error:
Error loading [https://stgbbaaviation.taleo.net/enterprise/soap?ServiceName=CorporateRecruitmentSourceService&wsdl]:
org.apache.xmlbeans.XmlException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://stgbbaaviation.taleo.net/enterprise/soap?ServiceName=CorporateRecruitmentSourceService&wsdl
If i put the path C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\mds\DSJavaKeyStore.keystore for the keystone path,
I get the following different error:
An error ocurred while importing metadata: WSDLException: faultCode=OTHER_ERROR: Unable to resolve imported document at 'https://stgbbaaviation.taleo.net/enterprise/soap?ServiceName=CandidateService&wsdl':javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building faild: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target (BODI-1111469) (BODI-1112446)
I have recreated the DSJavaKeyStore.keystore and added in additional certificates but nothing seems to work.
As a workaround i saved the wsdl file down to the local machine (I'm currently running designer on the job server machine)
i can then save the web service datastore and import the wsdl function. but at runtime I get the following error:
There is no response for the web service <getMessageByIdentifier>. Ensure that the network, web server, and service are running
properly. Also ensure that the service client call time out is set properly.
I have edited the
C:\Program Files (x86)\SAP BusinessObjects\Data Services\ext\webservice-c\axis2.xml file as follows for the sections that are listed in the documentation:
    <transportReceiver name="https" class="axis2_http_receiver">
        <parameter name="port" locked="false">6060</parameter>
        <parameter name="exposeHeaders" locked="true">false</parameter>
    </transportReceiver>

    <transportSender name="https" class="axis2_http_sender">
        <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
        <parameter name="xml-declaration" insert="false"/>
    </transportSender>
    <parameter name="SERVER_CERT">C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\server\DS_server_cert.crt</parameter>
    <parameter name="KEY_FILE">C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\server\DS_server_privatekey.pem</parameter>
    <parameter name="SSL_PASSPHRASE">C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\server\DS_server_privatekey_password.txt</parameter>
I'm not sure what i'm doing wrong. Not much detail in the documentation on what to enter for the Keystore path in the Datastore config.
also it is unclear if i don't have the correct certifications added to the keystore.
Please help

Hi Prashant,
Please refer the below KBA related to BODI-1111469 issue in SAP Data Services 4.1 Support Pack 1 Patch 1 (Version 14.1.1.284).
ADAPT01664699
An importing operation from a WSDL that has a recursive import of a schema would fail with the error: "An error occurred while importing metadata: Unknown JNI error... (BODI-1111469)”. This issue has been fixed in this release.
1804623 - Release Notes for SAP BusinessObjects Data Services 4.1 Support Pack 1 Patch 1 (Version 14.1.1.284)
https://service.sap.com/sap/support/notes/1804623
Thanks,
Daya

Invoking Web Services Without Using the WSDL File - RPC

I would apprecite if someone can provide sample code
for RPC client for WeatherEJB sample code without using wsdl file.
Thanks ,
ag

Hi,
Attached is a small program that calls a service CurrencyExchangeRate
registered at www.xmethods.com.
The program uses pure java to call the service.
Hope that helps
Thanks
Amit Chauhan
ag <[email protected]> wrote in message
news:3c59734d$[email protected]..
>
I would apprecite if someone can provide sample code
for RPC client for WeatherEJB sample code without using wsdl file.
Thanks ,
ag[webservice.java]

Failure to generate WSDL from web service when use xmlbean

Hi, I have a web service that uses xmlbean generated by schema. The schema from 3rd party is in a separate project since it's used by another web app and ejb project. In wlw103 I have included the schema project in this web service project's Java Build Path. The web service compiles, but when I tried to generate WSDL a Error window shows and says "The WSDL cannot be generated from the web service due to unexpected runtime errors".
The following is the detail. What do I need to do to make the xmlbean available for my web service? Thanks
com.bea.workshop.webservices.core.gen.WebServicesException: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\workspace\ws\src\myPackage\testWS.java
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl$3.invoke(WebServiceCompilerImpl.java:335)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.accessCompiler(WebServiceCompilerImpl.java:390)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.compile0(WebServiceCompilerImpl.java:330)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.compile(WebServiceCompilerImpl.java:275)
     at com.bea.workshop.webservices.ui.actions.GenerateWsdlFromJwsAction.run(GenerateWsdlFromJwsAction.java:169)
     at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
Caused by: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\workspace\ws\src\myPackage\testWS.java
     at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:526)
     at weblogic.wsee.tools.jws.build.JwsCompiler.compile(JwsCompiler.java:483)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl$3.invoke(WebServiceCompilerImpl.java:333)
     ... 46 more
Caused by: weblogic.wsee.tools.WsBuildException: weblogic.wsee.bind.buildtime.BindingException: ERROR ! could not add Xml Schema Type for XmlBean named '\[com.domain.UserDocument\]'. This is completely unexpected and might be caused by missing *.xsb and *.xsd files in the build environment. The building and running of this Service is likely to FAIL.
     at weblogic.wsee.tools.jws.jaxrpc.JAXRPCWebServiceInfo.createBindings(JAXRPCWebServiceInfo.java:227)
     at weblogic.wsee.tools.jws.wsdl.WsdlBuilder.processImpl(WsdlBuilder.java:43)
     at weblogic.wsee.tools.jws.jaxrpc.JAXRPCProcessor.process(JAXRPCProcessor.java:27)
     at weblogic.wsee.tools.jws.process.CompositeProcessor.process(CompositeProcessor.java:47)
     at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:522)
     ... 48 more
Caused by: weblogic.wsee.bind.buildtime.BindingException: ERROR ! could not add Xml Schema Type for XmlBean named '\[com.domain.UserDocument\]'. This is completely unexpected and might be caused by missing *.xsb and *.xsd files in the build environment. The building and running of this Service is likely to FAIL.
     at weblogic.wsee.bind.buildtime.internal.SoapAwareJava2Schema.bindAsExplodedTylar(SoapAwareJava2Schema.java:1414)
     at weblogic.wsee.bind.buildtime.internal.TylarJ2SBindingsBuilderImpl.createBuildtimeBindings(TylarJ2SBindingsBuilderImpl.java:216)
     at weblogic.wsee.tools.jws.jaxrpc.JAXRPCWebServiceInfo.createBindings(JAXRPCWebServiceInfo.java:223)
     ... 52 more

HI,
I hope this issue can resolved by adding this patch CR349256
Try to contact weblogic support to get more details about this patch.
Regards,
Kal.

Problem generating stubs for Java EJB web service deployed in OAS

I created an EJB web service and I've successfully deployed it in my Oracle App Server. Some of the methods work fine but others produce the ff error:
org.apache.soap.SOAPException - java.lang.IllegalArgumentException: No Serializer found to serialize [classname] using encoding style [encoding]It seems that the objects specified as parameters in the web service methods exposed are the only ones that had stubs generated for them. Other objects I use, which are usually wrapped inside a Vector, did not have generated stubs.
Example:
public String loginUser(UserDTO userDTO) throws RemoteException, NamingException, SQLException;
public String addItems (Vector vecItems) throws RemoteException, NamingException, SQLException; // where vecItems is a collection of ItemDTO objects In this scenario, stubs were generated for the UserDTO class, but not for the ItemDTO class. In effect, calling the addItems method resulted to the exception I mentioned above.
I did a workaround wherein I declared a dummy method which accepted all the types of objects I needed as parameters so all the necessary stubs can be generated, but this fix doesn't feel like it's the proper solution to my problem.
If anyone can help me, it would be greatly appreciated. Thanks!

Crossposted:
Problem generating stubs for Java EJB web service deployed in OAS

Web Service Project using WSDL file

Hi All,
I want to create web service project using WSDL file(I already have a wsdl file), which needs axis2 run time to generate correct project structure, I did this in eclipse but now I want to do it through JDeveloper(11.1.2.0.0), so please suggest me any ways on how can I configure axis2 runtime in Jdeveloper, and is it possible do it in Jdevloper?
Thank You,
Sunny
Edited by: Sunny on May 8, 2012 1:51 AM

Have you installed the 64-bit Access driver on your machine? See
Data Source Names and 64-Bit Operating Systems for the differences in odbcad32. Call %SystemRoot%\system32\odbcad32.exe to check the drivers.
How do you host your service? Stand-alone or IIS or embedded to another application? Keep in mind that IIS7 runs it in its application pool which is defaullt 64bit. Thus the bad image exception, when compiling your service as 32bit.
When you need the Access database for your service to store informtation, then I would switch to SQL Server (Express) or XML files depending on your actual needs.
Also check whether your account under which your service is run has the necessary NTFS file permissions on the access file and the folder. This is getting even more complex when it's a remote folder.

Generating Web Services bases on the WSDL interface

Hello everybody.
my question is.
How can i generated all the java classes of a web services basen on a wsdl definition.
how can i generate a simple java classe or how can i generate a ejb session, thet serve as a end point for my services
any sugestion could be so helpfull

The tool used to generate java class from WSDL is vender dependent, because each JAX-RPC engine is implemented differently (even they have to implement all JAX-RPC API, but low level stub call is engine dependent).
So to generate you class from WSDL, you have to have tool first. Since all J2EE 1.4 app servers are required to have implementation of JAX-RPC API and its run time engine (but many J2EE 1.3 app servers also included JAX-RPC API and engine) , what you want to do could be to find any J2EE 1.4 app server, such as WAS or WSAD, or Sun's Application Server PE 8.1, read their examples carefull and you will find the way how to generate classes from WSDL.

How to retrieve the multiple rows data on PDF form in a web service method using WSDL DataConnection

How to retrieve the multiple rows data on PDF form in a web service method using WSDL DataConnection.
I have a multiple rows on PDF form. All rows have 4 textfields. I want to submit the multiple rows data to a method defiened in webservice.
Unable to retrieve the data in multiple rows within webservice method.

Hi Paul,
I'm now able to save the retrieved xml in a hidden text field and create dynamic table, and I'm able to fill this table from the XML, but the problem is that I could not find the correct way to loop on the xml, what I'm trying to say, the table will have number of rows with the data of the first row only, so can you tell me the right way to loop on the xml!
this is my code
TextField1.rawValue=xmlData.document.rawValue;
xfa.datasets.data.loadXML(TextField1.rawValue, true, false);
for(var i=0; i<count; i++)
xfa.form.resolveNode("form1.P1.Table1.Row1["+i+"].Num").rawValue = xfa.datasets.data.record.num.value;
xfa.form.resolveNode("form1.P1.Table1.Row1["+i+"].Name").rawValue = xfa.datasets.data.record.name.value;
Table1.Row1.instanceManager.addInstance(true);
Thanks
Hussam

Create Web Service System using WSDL URL

Hi,
Please help me create a Web Service System.
Following is the test result when I perform Connection Test after creating a system
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
Thanks,
Atul

Let me reiterate my problem.
I created the System as following
Creating System's Object:
1) Go to System Administration
2) Go to System Configuration
3) Go to Portal Content on Object Based Navigation Area (Right Side Panel)
Note: For avoiding confusion it is recommended to create a folder in which we are creating System Object.
4) Right Click on Portal Content, select New -> System (from Template)
5) This action will display a new view on right side, now choose Web Service System using WSDL URL radio button from the existing templates. Click Next
6) Give the System Name i.e. System_WS and System Id (which are mandatory fields) incase you want to give any brief notes about the system then give it in Description field. Click Finish.
8) Choose Open the object for editing Click OK.
9) Now to create a Web Service System, we need WSDL URL.
10) There are lots of freely available WSDL files on internet, search for any such WSDL file.
11) In the Properties area of system give the appropriate WSDL URL
12) Choose System alias, from display menu and give alias as System_WS.
This alias name will be the name of Web Service System.
I used the following url
http://soap.amazon.com/schemas2/AmazonWebServices.wsdl
After the system is created,
1) Right click on the created system> open > object
2) Drop down for Display options is changed to Connection Tests from what it shows as object
3) Check the check box for the test name Connection Test for Connectors
4) Result shows that the connection failed. The error message was posted in my first question.
Thanks,
Atul

Help: Creating web service proxy using JAXB generated domains

Hi,
I'm currently doing some investigation considering the use of web services (BPEL) as a complete application backend.
The application should contain a pojo facade which communicates with some web service proxies. By making a datacontrol
of the pojo facade, I'm able to expose methods to the client layer.
I generated my domain objects by using the JAXB Compilation option in JDeveloper. By using that, a java class can be generated
based on an XSD. Disadvantage of this use, seems to be the fact that the ObjectFactory class, generated by JAXB, is overwritten
each time I create java classes from an XSD.
Q1: Is there a solution to prevent the ObjectFactory class to be overwritten? I also could decide not to use it.
After the domain objects are created, I want to call the actual webservice and receive the response by using the JAXB marshaller
and unmarshaller. Problem here is:
Q2: How do I (manually?) create a proxy which calls the web service, by using the domain objects generated by JAXB?
Q3: An important requirement is that it needs to be simple to switch from several environments (eg from development to test). How
can I fulfill this requirement in a nice, solid solution?
Any tips working with web services as the backend layer are welcome!
JDeveloper 10.1.3.4
ADF Faces/JSF
BPEL
Thanks,
Koen Verhulst

repost.

How to create Web Service based on PI WSDL message

Hi all,
we have following scenario:
Within PI (version 7.1) we set up a message type and inbound service interface. This service interface should send the PI message to a web service running on a SAP J2EE (version 7.01). As the PI message is sent as WSDL I thought it should be easy to build a web service on the SAP J2EE based on this WSDL from PI.
Unfortunately, I have problems creating the Web Service.
For my current project we integrated the NWDI to the SAP NetWeaver Developer Studio and I'm required to add the Web Service to an existing DC (Development Component) within the NWDI.
What I tried so far is:
- I created a Deployable Proxy Project and within this I created a Client Proxy Definition based on the WSDL from the PI. But I can't add this Proxy to the DCs of the NWDI and I don't know how to implement my own coding here in order execute specific functions.
- I created a new class within the NWDI DC and a public method. Based on this I created a Virtual Interface and a Web Service Definition (WSD). Then I added this to a Web Service Deployment Descriptor. I uploaded this to the SAP J2EE. But I'm not able to access this and I don't know hoe to assign the WSDL here.
I also tried here to create a client proxy based on this WSD as I thought I might assign the WSDL here. But I don't see the WSD in the list of Web Services uploaded to the SAP J2EE...
Can you please advice me how to create a Web Service in such an environment?
regards
René Jurmann

Hi Tahir,
sorry that you needed to wait this long - but this is how I created the web service:
The steps on how to create the web service in NetWeaver Developer studio are nearly the same as described in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5838. [original link is broken] [original link is broken] [original link is broken]
Some steps I just skipped and some others I added. Some of the steps I did the way I described it as I needed to connect the web service with the SAP PI.
Prerequisites:
Add Java Perspective and J2EE Development Perspective to the open perspectives.
Within "Window - Preferences - Web Services" check "Soap extensions visible in the virtual interface editor"
The SDM of the corresponding SAP J2EE is configured within "Window - Preferences"
Create a Development Component (DC) with type "J2EE -> EJB Module"
The business logic of the web service will be implemented in an Enterprise Java Bean (EJB). So first the EJB component must be created:
     Choose "File -> New -> Other"
     In opening PopUp choose "Development Component -> Development Component Project"
     Select the Software Component for which you want to add the DC (e.g. "Local Development -> MyComponents")
     Choose now vendor, name and type:
          vendor is an alpha-numeric string of 20 characters starting with a letter - all in lower case
          name is an alpha-numeric string starting with a letter - all in lower case
          vendor and name concatenated must not be longer then 40 characters
          the name can be separated into different part using "/" as separator
          each part of the name must not be longer than 8 characters
          the type is "J2EE - EJB Module"
          you can specify a Caption as general description for the web service
Create new EJB
To create the EJB itself:
     In J2EE DC Explorer of J2EE Development Perspective expand new DC and right-click on folder "ejbModule"
     Choose "New - EJB" with following details:
          EJB Name: <name as for PI service Interface to be created - starting in upper case>
          EJB Project: <pre selected>
          Bean Type: Stateless Session Bean
          Default EJB Package: <corresponds to namespace in PI>
          generate default interfaces: Checked
Regarding the "Default EJB Package" this should be created according the namespace in PI for which all PI objects will be created. This only applies if you have some naming conventions here.
Example:
Namespace in PI is: http://company.net/pi/SOFTWARE_COMP/Application
The corresponding package then is: net.company.pi.software_comp.application
Implement coding for web service
As the web service will be called via PI some transfer variables will be submitted. Most likely, those variables will not be standard type (e.g. String) but a complex type. Those types must be generated as Java classes. Below an example of a complex type I needed:
Data Type
net.company.pi.software_comp.application.types.MessageProcessingInformation
Structure:
     Element name          Element type
     sendingSystemID          String
     interfaceID               String
     businessProcessVariantCode     String
     testIndicator               Boolean
For every element described a public "get", "set" and "has" method must be created in the corresponding Java class:
package net.company.pi.software_comp.application.types;
import java.io.Serializable;
public class MessageProcessingInformation implements Serializable {
     protected String sendingSystemID;
     protected String interfaceID;
     protected String businessProcessVariantCode;
     protected Boolean testIndicator;
     public String getSendingSystemID() {
          return sendingSystemID;
     public void setSendingSystemID(String value) {
          this.sendingSystemID = value;
     public boolean hasSendingSystemID() {
          if(sendingSystemID != null && !sendingSystemID.equals("")){
               return true;
          return false;
All Java classes representing complex types and all classes referenced here (used for sub-types) must implement java.io.Serializable. Java standard types which do not implement this class must not be used as sub-types.
As soon as all data types are declared the real business logic can be implemented:
     In J2EE DC Explorer of J2EE Development Perspective expand DC - "ejb-jar.xml" - <Name> and double click on "ejbCreate"
     In detail view select folder "Business Methods" and click "Add"
     choose name of business method - this should be the same as the PI message type used for the service interface - starting lower case
     return type should be "void"
     add needed parameters fully qualified - including package (as specified in PI and created previously in DC)
     you can mark certain parameters as array if necessary
Remark:
It might be that after saving you get an error. This might be as the package name of one component is copied to the corresponding Java class at the very beginning (before the package declaration within the Java class). Simply delete the string here.
It also might be, that the new business method is only defined in the remote interface class but not in the bean class. Just create an according method in the bean class.
Within the newly created business method within the bean class you can now implement the business logic.
Create a DC with type "J2EE -> Enterprise Application"
In order to create the "real" web service and deploy it to the J2EE an Enterprise Application project has to be created. So create a new DC as for the EJB Module but choose as type "J2EE -> Enterprise Application".
After the DC is created right click on the EJB DC and choose "Add to EAR Project". Choose the new DC.
Create web service for EJB
As soon as you implemented the business logic you can create the "real" web service. Therefore:
     Right click on the EJB name below "ejb-jar.xml"
     Choose "New - Web Service"
     Choose proper "Web Service Name" and "Configuration Name" (probably oriented at the EJB name)
     Copy the URL of the web service - you'll need it later for PI configuration
     on the second next screen use the same name for "Virtual Interface" and "Web Service Definition" (the name should be the name of the "Endpoint")
     the "EAR Project" should be preselected
Unfortunately, the web service can't be used in its current configuration to be accessed by PI. Therefore the Virtual Interface must be changed. To do so, expand folder "Virtual Interfaces" and double click the virtual interface created.
Within the detail view expand in tabs "Mapping" and "Types" the complete folder structure. For any "SOAP Extension" where a namespace can be defined use as namespace the corresponding namespace in PI (e.g. http://corpintra.net/pi/CBFC_GLOBAL_SAP_APPL/BillerDirect) but do not change any "Soap Extension" of a standard Java type. (if you don't have any naming convetions for namespaces in PI you can leave the SOAP Extension here. But then the namespace in PI should be set accordingly.)
Probably it can be necessary on top level "Soap Extensions" in tab "Mapping" to leave "Use Namespaces for Parameters" unchecked. For some of my web services this parameter must be checked for others not - just try.
If you can define a "New Name", "Local Name" or "Item Label" for a Soap Extension then use a name with starting upper case letter. (For Java Naming conventions most of the data type names will start with lower case letters.) Especially the method name must be renamed this way in order to stick to the PI namings.
As a last point to change here check in tab "Mapping" all "Incoming Parameters" which you specified as array. Use for those as "New Name" a different name - do not just simply change from lower case to upper case. This is necessary as on PI we need to create two levels although here only one is specified.
For any own sub-type declared as array the name within the coding should also differ from the corresponding Java Class name the type refers to.
If all this is done you can deploy the web service to the J2EE:
     right click on "Enterprise Application" DC and choose "Development Component - Build..." and build all corresponding components
     right click on "Enterprise Application" DC and choose "Development Component - Deploy"
Test the new web service via <J2EE URL>/wsnavigator/enterwsdl.html
Create PI interface
After the web service is created successfully the PI integration can be started.
Therefore, within the Enterprise Services Builder create a data type according to the web service definition. All components defined on top-level for this data type should be declared as incoming parameter for the web service business method. Therefore it could be necessary to create some sub data types on PI first and add those to the "master" data type.
Ensure that the names of the components correspond to the names defined in the web service (see virtual interface here). Those names must exactly be the same - including lower/upper case. Also take care for the ordering of the components.
In case you need to include arrays following applies:
The upper level is of occurrence "1:1". This has only one sub-entry with occurrence "1:n". The names for upper and sub-level must not equal.
Based on the data type a message type is created. The name of the message type must be exactly the same as the name of the web service business method. (Hint: the name of the web service business method was most likely changed in the virtual interface. Then this name must correspond to the message type name.) Based on the message type an asynchronous inbound interface is to be created (which will be referred in the Integration Directory). The operation name for this interface (left panel) should be the same as the name for the web service business method.
Create PI mappings and routings
How to map (message mapping and operation mapping) from source to the web service message I wont explain here as this depends on the source message. The only important things here are:
     When creating the SOAP communication channel within the Integration Builder the "Target URL" is:
          <J2EE URL>/<Access URL as specified in web service creation>?wsdl&style=document
     The soap action is the name of the web service business method.
     Most likely the web service needs authentication to be executed.

Connection reset error while calling web service deployed on tomcat

Hello Friends,
I am trying to invoke a web service from web dynpro application. The web service is deployed on tomcat 5.5 server.
I am creating an adaptive web service model using wsdl file. The model gets created without any error.
But when application is deployed and run it is giving following exception:
java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream.java:168)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
    ... 102 more
I tried to call the service from a simple java application. There the service works fine.
Also, in the web services navigator, if I specify the wsdl url for testing it gives the same error of "Connection reset".
I don't think this is a proxy server issue as the tomcat is within the local network.
Can someone please help me with this?
Thanks and regards,
Mayuresh
Edited by: Mayuresh Kanvinde on Mar 27, 2008 7:03 PM

Hi Sumit,
Thanks for the reply.
Here is the stack trace:
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://<host>:<port>/WebServicesTest/DummyWebService?wsdl' and service factory configuration 'null'
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:422)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
     at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
     at com.tcs.vis.Vishy.<init>(Vishy.java:73)
     at com.tcs.app.AppView.wdDoInit(AppView.java:101)
     at com.tcs.app.wdp.InternalAppView.wdDoInit(InternalAppView.java:143)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:150)
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:50)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:91)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:420)
     ... 45 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:147)
     ... 49 more
Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Connection reset -> java.net.SocketException: Connection reset
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1039)
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1126)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
     ... 50 more
Caused by: java.net.SocketException: Connection reset
     at java.net.SocketInputStream.read(SocketInputStream.java:168)
     at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
     at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
     at com.sap.engine.services.webservices.jaxm.soap.LimitedInputStream.read(LimitedInputStream.java:61)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.readData(EncodedDataReader.java:269)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.fetchData(EncodedDataReader.java:332)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:165)
     at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
     at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.addInputFromInputStream(AdvancedXMLStreamReader.java:292)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:220)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
     at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1023)
     ... 52 more
Thanks and regards,
Mayuresh
Edited by: Mayuresh Kanvinde on Mar 28, 2008 1:10 PM

Web Service portlet using pdk documentation issue

Hi,
I have followed the instructions in
http://portalcenter.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/PDK/ARTICLES/how.to.build.web.services.portlets.html
on how to build web service portlets.
I have successfully deployed the WS portlet and can happily call my web Service (RPC style) passing a set of parameters which I have formatted using a stylesheet.
However, every time I refresh the page within portal, it recalls the WS with the previously submitted parameters. Also, if I switch between view and edit mode in portal, it again calls the WS with previously entered parameters.
Can I stop this happening either through a setting in portal or code in my Stub class. (Stub class below)
Thanks alot
Joel.
package mypackage;
import oracle.soap.transport.http.OracleSOAPHTTPConnection;
import org.apache.soap.encoding.SOAPMappingRegistry;
import java.math.BigDecimal;
import java.net.URL;
import org.apache.soap.rpc.Call;
import org.apache.soap.Constants;
import java.util.Vector;
import org.apache.soap.rpc.Parameter;
import org.apache.soap.rpc.Response;
import org.apache.soap.Fault;
import org.apache.soap.SOAPException;
import java.util.Properties;
* Generated by the Oracle JDeveloper 10g Web Services Stub/Skeleton Generator.
* Date Created: Thu Feb 03 15:38:22 GMT 2005
* WSDL URL: file:/D:/Software/Oracle/NT/jdev_10.1.2/jdev/mywork/blah/CreateSR2/src/LG02/CreateSR2.wsdl
public class CreateSR2Stub
public CreateSR2Stub()
m_httpConnection = new OracleSOAPHTTPConnection();
m_smr = new SOAPMappingRegistry();
public static void main(String[] args)
try
CreateSR2Stub stub = new CreateSR2Stub();
// Add your own code here.
catch(Exception ex)
ex.printStackTrace();
private String _endpoint = "http://myServer:7779/Blah-CreateSR2-context-root/CreateSR2";
public String getEndpoint()
return _endpoint;
public void setEndpoint(String endpoint)
_endpoint = endpoint;
private OracleSOAPHTTPConnection m_httpConnection = null;
private SOAPMappingRegistry m_smr = null;
public String createSrStub(BigDecimal pCitizen, String pAccountType, String pSummary, String pReferral, String pReason, String pHouse, String pRos, BigDecimal pGroup, String pOwner, String pMode, String pFrom) throws Exception
String returnVal = null;
URL endpointURL = new URL(_endpoint);
Call call = new Call();
call.setSOAPTransport(m_httpConnection);
call.setTargetObjectURI("CreateSR2");
call.setMethodName("createSrStub");
call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
Vector params = new Vector();
params.addElement(new Parameter("pCitizen", BigDecimal.class, pCitizen, null));
params.addElement(new Parameter("pAccountType", String.class, pAccountType, null));
params.addElement(new Parameter("pSummary", String.class, pSummary, null));
params.addElement(new Parameter("pReferral", String.class, pReferral, null));
params.addElement(new Parameter("pReason", String.class, pReason, null));
params.addElement(new Parameter("pHouse", String.class, pHouse, null));
params.addElement(new Parameter("pRos", String.class, pRos, null));
params.addElement(new Parameter("pGroup", BigDecimal.class, pGroup, null));
params.addElement(new Parameter("pOwner", String.class, pOwner, null));
params.addElement(new Parameter("pMode", String.class, pMode, null));
params.addElement(new Parameter("pFrom", String.class, pFrom, null));
call.setParams(params);
call.setSOAPMappingRegistry(m_smr);
Response response = call.invoke(endpointURL, "");
if (!response.generatedFault())
Parameter result = response.getReturnValue();
returnVal = (String)result.getValue();
else
Fault fault = response.getFault();
throw new SOAPException(fault.getFaultCode(), fault.getFaultString());
return returnVal;
public void setMaintainSession(boolean maintainSession)
m_httpConnection.setMaintainSession(maintainSession);
public boolean getMaintainSession()
return m_httpConnection.getMaintainSession();
public void setTransportProperties(Properties props)
m_httpConnection.setProperties(props);
public Properties getTransportProperties()
return m_httpConnection.getProperties();
}

Hi Joel,
You can enable caching for your portlet. There are three types of caching you can use: expiry, validation, and invalidation-based caching. You can learn about your options in the Enhancing Portlet Performance with Caching section of the Portal Developer's Guide.
Regards,
Peter

Web service deployment using generated wsdl

Similar Messages

Maybe you are looking for