Problem in using the Web Service generated from BAPI_FLIGHT_GETLIST

Hi all,
I am trying to use the Web Service generated from BAPI_FLIGHT_GETLIST. I have got the wsdl file, and trying to invoke it. But, while I can test the BAPI using the Airline ID AA, I can't test from the Web Service using the same data. It shows the error message - "Airline AA not found". Anyone having solution, please help. This is urgent.
Thanks,
Anirban
Message was edited by:
Anirban Das

Yes, I am connecting to the same system where we have data..
Anirban

Similar Messages

Problems doing the "Web Service" example from the 2-Day-Developer Guide

Hello,
I want to do the "web service" example from the 2-Day-Developer Guide.
I give the application my proxy server address in the format address:port and go through the assistant creating the web service. After selecting the IBM UDDI-service and searching for %xMethods% as business name I get the following error:
ORA-31011: XML-Parsing not successful ORA-19202: Error parsing XML LPX-00104: Warning: Element "html" is not declared in DTD Error at line 2
What have I done wrong?
With kind regards
Florian Reiser

Please.. Could you change your forum handle to something more human, we are a friendly group here and lik to know who we are talking to.. Secondly, WHy are you using such an OLD version oft he product. You would be better off installing 3.2.1 (latest released build) and asking your questions after you do that..
(I am sorry, it's like asking for help in a Windows support forum about issues you are having with Windows 3.1)
Thank you,
Tony Miller
Webster, TX

JCAPS UDDI - Problem Using the Web Service Management Application

Hi everyone, this is my problem:
1.) I installed the JCAPS UDDI Server in a Solaris. <-- Ok
2.) In the eManager I installed the Web Services Access Manager. <-- Ok
3.) I started the UDDI server. <-- Ok
4.) I check that the process is running (in Solaris). <-- Ok
5.) I'm trying to load the Web Service Management Application Login Page, but it doesn't show the page so I can't login and in consequence I can't publish, remove, view, and search WSDLs by using the Web Service Management Application.
I appreciate some help about this.
Regards

Yes, I am connecting to the same system where we have data..
Anirban

How can i use the web services

i have a web service ,but what is need that can i use the web services?
is only then oc4j,or anything?

You need to write a client that will access the Web service and invoke it.
You can write the client in Java for example - and JDeveloper provides wizards for this.
There is a sample in the JDeveloper Reviewer guide here:
http://www.oracle.com/technology/products/jdev/collateral/papers/10g/reviewer/reviewerguide.html

How to use RESTful Web Services provided from BO Enterprise

Hi Experts,
i am trying to use the Web Service "BIPLATFORM" provided by BusinessObjects Enterprise. As I have trouble reading the WSDL i tried to use the REST interface.
Unfortunatally I cannot find any Docu about that in the internet.
Does anybody have experience in using the BIPLATFORM web service?
Thank you in advance

Thank you very much for your instant answer and help!
I got it now: "no rest in biplatform service"
What made me think REST is possible was only the following entry in ...\webapps\dswsbobje\WEB-INF\conf\axis2.xml
"
- 
- 
- 
- 
- 
<parameter name="disableREST" locked="true">false</parameter>
- 
Anyway I was only hoping to get REST work as the WSDL provided by BusinessObjects Enterprise is not valid to be parsed by SAP Netweaver ABAP SOAP Runtime...
I regret but i have to add: The fact that the web service is only meant to work with certain consumers shows that the people responsible have little to no understanding what the idea of SOAP, SOA and WSDL really is. On the one hand SAP was always pushing their ESOA idea but on the other hand we got this strange limitations like "only for these clients..."
This is exactly the opposite of the SOAP-idea:
"The framework has been designed to be independent of any particular programming model and other implementation specific semantics." - http://www.w3.org/TR/2007/REC-soap12-part1-20070427/

Problem in accessing the Web Service using standalone Java Client

Dear Friends,
Hi,
I have an active web service and I have tested the same with XML Spy and Apache Axis and is giving me the output perfectly. For the same, I have developed a standalone Java client but getting problem in fetching the output.
The Exception is :
<Jan 4, 2006 5:54:16 PM GMT+05:30> <Info> <WebService> <BEA-220025> <Handler weblogic.webservice.core.handler.ClientHandler threw
an exception from its handleResponse method.
The exception was:
javax.xml.rpc.JAXRPCException: java.io.IOException: Received a response from url: http://10.20.15.59:18004/amountToWords which did
not have a valid SOAP content-type: text/html;charset=ISO-8859-1. .>
SOAP Fault **************** Exception during processing: java.io.IOException: Received a response from url: http://10.20.15.59:18
004/amountToWords which did not have a valid SOAP content-type: text/html;charset=ISO-8859-1.
(see Fault Detail for stacktrace)
javax.xml.rpc.soap.SOAPFaultException: Exception during processing: java.io.IOException: Received a response from url: http://10.2
0.15.59:18004/amountToWords which did not have a valid SOAP content-type: text/html;charset=ISO-8859-1.
(see Fault Detail for sta
cktrace)
at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:566)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:419)
at HelloClient.main(HelloClient.java:100)
I have tried some ways to set the content type explicitly but the results are same(throwing an exception).
I appreciate you all for helping me out of this.
Thanks
VR

Hi Amit
We also have this issue with weblogic webservices. Did you get any resolution for this issue.
When the service is executed for lesser number of hits, all the responses are processed properly. But as load (Number of hits for the same service) increases, few responses are failed to be parsed in the web service client. We could confirm that the producer responds with proper content type (text/xml)
Any help or pointers will be greatly appreciated.
Thanks,
Finny

Urgent - Error calling web service generated from plsql package

Hi,
I am using Jdeveloper 10.1.3 production release.
I am trying to publish a plsql packaged procedure as a web service.
My first question is -
When I am publishing the plsql API as a WS, should I choose the style Document/Wrapped or RPC Literal? Document Wrapped is the default in the wizard.
My second question - Depending on whether I choose Document/Wrapped or RPC Literal style, I get 2 different errors when I try to run the client java file (generated by Jdeveloper) that calls the web service. The client java compiles successfully but when I run I get these messages:
Document/Wrapped error -
D:\jdev1013\jdk\bin\javaw.exe -ojvm -classpath H:\jdevhome\jdev\mywork\Genesis\Test\classes;D:\jdev1013\sqlj\lib\runtime12.jar;D:\jdev1013\jdbc\lib\ojdbc14dms.jar;D:\jdev1013\jdbc\lib\orai18n.jar;D:\jdev1013\jdbc\lib\ocrs12.jar;D:\jdev1013\diagnostics\lib\ojdl.jar;D:\jdev1013\lib\dms.jar;D:\jdev1013\jdev\lib\jdev-rt.jar;D:\jdev1013\webservices\lib\soap.jar;D:\jdev1013\webservices\lib\saaj-api.jar;D:\jdev1013\lib\xmlparserv2.jar;D:\jdev1013\jlib\javax-ssl-1_1.jar;D:\jdev1013\jlib\jssl-1_1.jar;D:\jdev1013\j2ee\home\lib\activation.jar;D:\jdev1013\j2ee\home\lib\mail.jar;D:\jdev1013\j2ee\home\lib\http_client.jar;D:\jdev1013\webservices\lib\jaxrpc-api.jar;D:\jdev1013\webservices\lib\wsclient.jar;D:\jdev1013\webservices\lib\wsserver.jar;D:\jdev1013\webservices\lib\wssecurity.jar;D:\jdev1013\webservices\lib\wsdl.jar;D:\jdev1013\webservices\lib\orasaaj.jar;D:\jdev1013\webservices\lib\orawsdl.jar;D:\jdev1013\webservices\lib\orawsrm.jar;D:\jdev1013\webservices\lib\jaxr_api.jar;D:\jdev1013\webservices\lib\orajaxr.jar;D:\jdev1013\webservices\lib\relaxngDatatype.jar;D:\jdev1013\webservices\lib\jaxb-impl.jar;D:\jdev1013\webservices\lib\jaxb-libs.jar;D:\jdev1013\webservices\lib\xsdlib.jar;D:\jdev1013\webservices\lib\mdds.jar;D:\jdev1013\jlib\jaxen.jar;D:\jdev1013\jlib\oraclepki.jar;D:\jdev1013\jlib\ojpse.jar;D:\jdev1013\jlib\osdt_core.jar;D:\jdev1013\jlib\osdt_cert.jar;D:\jdev1013\jlib\osdt_xmlsec.jar;D:\jdev1013\jlib\osdt_wss.jar;D:\jdev1013\jlib\osdt_saml.jar;D:\jdev1013\jlib\repository.jar;D:\jdev1013\jlib\ojmisc.jar;D:\jdev1013\j2ee\home\jazncore.jar;D:\jdev1013\j2ee\home\oc4jclient.jar;D:\jdev1013\rdbms\jlib\xdb.jar;D:\jdev1013\diagnostics\lib\ojdl2.jar;D:\jdev1013\lib\xsu12.jar;D:\jdev1013\lib\xml.jar;D:\jdev1013\j2ee\home\lib\ejb.jar;D:\jdev1013\j2ee\home\lib\jms.jar;D:\jdev1013\j2ee\home\lib\jta.jar;D:\jdev1013\j2ee\home\lib\servlet.jar;D:\jdev1013\jakarta-taglibs\commons-logging-1.0.3\commons-logging-api.jar;D:\jdev1013\jakarta-taglibs\commons-logging-1.0.3\commons-logging.jar;D:\jdev1013\j2ee\home\lib\ojsp.jar;D:\jdev1013\j2ee\home\jsp\lib\taglib\ojsputil.jar;D:\jdev1013\j2ee\home\oc4j.jar;D:\jdev1013\j2ee\home\lib\oc4j-internal.jar;D:\jdev1013\jdev\lib\ojc.jar genc2dv1.TestWebServiceSoapHttpPortClient
calling http://rchellam-PC1:8888/Genesis-Test-context-root/TestWebServiceSoapHttpPort
java.rmi.RemoteException: Error parsing envelope: (1, 1) Start of root element expected.; nested exception is:
     javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
     at test.proxy.runtime.TestWebServiceSoapHttp_Stub.getAttributes(TestWebServiceSoapHttp_Stub.java:157)
     at genc2dv1.TestWebServiceSoapHttpPortClient.getAttributes(TestWebServiceSoapHttpPortClient.java:46)
     at genc2dv1.TestWebServiceSoapHttpPortClient.main(TestWebServiceSoapHttpPortClient.java:29)
Caused by: javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
     at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:104)
     at oracle.j2ee.ws.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:76)
     at oracle.j2ee.ws.saaj.soap.MessageImpl.getSOAPBody(MessageImpl.java:713)
     at oracle.j2ee.ws.client.StreamingSender._preHandlingHook(StreamingSender.java:673)
     at oracle.j2ee.ws.client.StubBase._preHandlingHook(StubBase.java:664)
     at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:201)
     at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:111)
     at test.proxy.runtime.TestWebServiceSoapHttp_Stub.getAttributes(TestWebServiceSoapHttp_Stub.java:134)
     ... 2 more
Caused by: oracle.xml.parser.v2.XMLParseException: Start of root element expected.
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:333)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:295)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:201)
     at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:78)
     ... 9 more
Process exited with exit code 0.
RPC Literal error -
D:\jdev1013\jdk\bin\javaw.exe -ojvm -classpath H:\jdevhome\jdev\mywork\Genesis\Test\classes;D:\jdev1013\sqlj\lib\runtime12.jar;D:\jdev1013\jdbc\lib\ojdbc14dms.jar;D:\jdev1013\jdbc\lib\orai18n.jar;D:\jdev1013\jdbc\lib\ocrs12.jar;D:\jdev1013\diagnostics\lib\ojdl.jar;D:\jdev1013\lib\dms.jar;D:\jdev1013\jdev\lib\jdev-rt.jar;D:\jdev1013\webservices\lib\soap.jar;D:\jdev1013\webservices\lib\saaj-api.jar;D:\jdev1013\lib\xmlparserv2.jar;D:\jdev1013\jlib\javax-ssl-1_1.jar;D:\jdev1013\jlib\jssl-1_1.jar;D:\jdev1013\j2ee\home\lib\activation.jar;D:\jdev1013\j2ee\home\lib\mail.jar;D:\jdev1013\j2ee\home\lib\http_client.jar;D:\jdev1013\webservices\lib\jaxrpc-api.jar;D:\jdev1013\webservices\lib\wsclient.jar;D:\jdev1013\webservices\lib\wsserver.jar;D:\jdev1013\webservices\lib\wssecurity.jar;D:\jdev1013\webservices\lib\wsdl.jar;D:\jdev1013\webservices\lib\orasaaj.jar;D:\jdev1013\webservices\lib\orawsdl.jar;D:\jdev1013\webservices\lib\orawsrm.jar;D:\jdev1013\webservices\lib\jaxr_api.jar;D:\jdev1013\webservices\lib\orajaxr.jar;D:\jdev1013\webservices\lib\relaxngDatatype.jar;D:\jdev1013\webservices\lib\jaxb-impl.jar;D:\jdev1013\webservices\lib\jaxb-libs.jar;D:\jdev1013\webservices\lib\xsdlib.jar;D:\jdev1013\webservices\lib\mdds.jar;D:\jdev1013\jlib\jaxen.jar;D:\jdev1013\jlib\oraclepki.jar;D:\jdev1013\jlib\ojpse.jar;D:\jdev1013\jlib\osdt_core.jar;D:\jdev1013\jlib\osdt_cert.jar;D:\jdev1013\jlib\osdt_xmlsec.jar;D:\jdev1013\jlib\osdt_wss.jar;D:\jdev1013\jlib\osdt_saml.jar;D:\jdev1013\jlib\repository.jar;D:\jdev1013\jlib\ojmisc.jar;D:\jdev1013\j2ee\home\jazncore.jar;D:\jdev1013\j2ee\home\oc4jclient.jar;D:\jdev1013\rdbms\jlib\xdb.jar;D:\jdev1013\diagnostics\lib\ojdl2.jar;D:\jdev1013\lib\xsu12.jar;D:\jdev1013\lib\xml.jar;D:\jdev1013\j2ee\home\lib\ejb.jar;D:\jdev1013\j2ee\home\lib\jms.jar;D:\jdev1013\j2ee\home\lib\jta.jar;D:\jdev1013\j2ee\home\lib\servlet.jar;D:\jdev1013\jakarta-taglibs\commons-logging-1.0.3\commons-logging-api.jar;D:\jdev1013\jakarta-taglibs\commons-logging-1.0.3\commons-logging.jar;D:\jdev1013\j2ee\home\lib\ojsp.jar;D:\jdev1013\j2ee\home\jsp\lib\taglib\ojsputil.jar;D:\jdev1013\j2ee\home\oc4j.jar;D:\jdev1013\j2ee\home\lib\oc4j-internal.jar;D:\jdev1013\jdev\lib\ojc.jar genc2dv1.TestWebService2SoapHttpPortClient
calling http://rchellam-PC1:8888/Genesis-Test-context-root/TestWebService2SoapHttpPort
unexpected null value for literal data
     at oracle.j2ee.ws.common.util.exception.JAXRPCExceptionBase.<init>(JAXRPCExceptionBase.java:52)
     at oracle.j2ee.ws.common.encoding.SerializationException.<init>(SerializationException.java:26)
     at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:191)
     at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:137)
     at test.proxy.runtime.TestWebService2SoapHttp_getAttributes_ReqS_LiteralSerializer.doSerialize(TestWebService2SoapHttp_getAttributes_ReqS_LiteralSerializer.java:154)
     at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:199)
     at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:137)
     at oracle.j2ee.ws.client.StreamingSender._writeRequest(StreamingSender.java:625)
     at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:137)
     at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:111)
     at test.proxy.runtime.TestWebService2SoapHttp_Stub.getAttributes(TestWebService2SoapHttp_Stub.java:89)
     at genc2dv1.TestWebService2SoapHttpPortClient.getAttributes(TestWebService2SoapHttpPortClient.java:57)
     at genc2dv1.TestWebService2SoapHttpPortClient.main(TestWebService2SoapHttpPortClient.java:32)
Process exited with exit code 0.
Now all the classes are generated by JDeveloper automatically from the plsql API. So I am not sure why the errors occur and how to fix these.
Also, these errors are occurring on plsql APIs that have input or output parameters of plsql record type or pslql table of record type. These errors don't occur if the api is simple with scalar input or output parameters only.
I would appreciate any help on how to resolve these errors.
Thanks,
Raji

Hi,
I'm wondering if the problem is actually that the client is failing to connect to the server correctly. Can I suggest that you switch on the HTTP Analyzer and see what comes back there.
Is it possible it is a proxy problem? If you are working locally then I first suggest that you ensure that the Web Browser Proxy is off (see Tools -> Preferences -> Web Browser Proxy) - and that there are no exceptions listed (either with the proxy on or off) before you start the HTTP Analyzer.
As to Doc/Wrapped or RPC. see this blog entry for a little more explanation:
http://susanduncan.blogspot.com/2006/05/rpc-document-bare-wrapped-literal-get.html
regards
Susan

Problems with using old web service project with new WLS/OEPE install

I developed a java web service two years ago using WLS 10.3.3 and OEPE. After development I checked the workspace into Subversion including the .metadata directory. The web service was deployed to a production WLS box and is running fine.
Now I have a new Windows 7 desktop computer. I have installed WLS 10.3.3 and OEPE on my new desktop and am trying to get the web service I wrote two years ago to run locally. When OEPE launches I point the workspace to the workspace project directory (from two yrs ago) that I have just checked out from Subversion. However when the OEPE IDE comes up I have many errors in the java code. Pretty much every java class is flagged with a "cannot be resolved to a type" error.
Also, when I try to create a new server and domain, I have a problem there. I select "Oracle WebLogic Server 11gR1 PatchSet 2" as the server type, click Next on the wizard, but then on the next window where you select the Domain, the Domain Directory is disabled and will not let me enter a value, and the link to allow you to create a new Domian is not visible.
Feeling kind of stupid as this should be really simple to do. Am I proceeding correctly by saving off the entire workspace and then trying to use that workspace in the new WLS/OEPE install? Any help would be greatly appreciated.

Have you tried creating a new workspace, then import the project from your subversion workspace?

Using the local service registry from other applications (VC, GP)

Hi all,
I am not sure if this is the appropriate forum, but my problem is the service registry I think.
I am facing the problem of using services that I publish to my local service registry from VC and GP.
The problem is as follows:
I publish the services via the "publish" tab on the http://localhost:50000/sr page. The process is executed successfully according to the message.
Then on the Service Definitions Tab of http://localhost:50000/sr I can find and test the service, though on the System Details Tab All parameters are set to "No data available".
When I then try to search the service from the VC (searching in a Ws of type service registry, which I have previously configured through destination templates), I get "no services found".
In the GP I see the published services, but when I try to use them as callable objects, I get the following error message:
"WS-Interface initialization problem of GenericServiceFactory..., Local_Service_Registry - ServiceName not found. possible changes in the WSDL"?
I also tried publishing the web services through the ws restrictions, but they dont get published.
I have adjusted the UDDI_DESTINATION and CLASSIFICATION_DESTINATION properties according to the help page for the localhost system. I also use a Local_Service_Registry destination of type service registry as I thought I need it in oder to use the service registry.
Has somebody experienced this problem before?
Thanks in advance!
Best regards,
Vera

Hi,
the exact error trace is as follows:
#1#javax.ejb.EJBException: Exception raised from invocation of public com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesResponseType com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesType) throws com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishClassificationSystemValuesFault method on bean instance [email protected]8 for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxy~ejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)*
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:158)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:117)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)
     at $Proxy56_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(ServicesRegistryProxyFacade.java:302)
     at sun.reflect.GeneratedMethodAccessor810_10002.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
     at $Proxy34_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.createUDDIClassifications(SOACentralSRPublisherImpl.java:742)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.publishServiceDefinitions(SOACentralSRPublisherImpl.java:435)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.publish(PublishRulesHandler.java:282)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.process(PublishRulesHandler.java:248)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.process(SOATimeoutListenerImpl.java:128)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:51)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:72)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:144)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:242)
Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:340)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:961)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:700)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:152)
     ... 37 more
Caused by: java.io.IOException: Unable to connect to localhost:50100 - Connection refused: connect
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:666)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:658)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:621)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:499)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:450)
     at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getRequestStream(ClientHTTPTransport.java:481)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:298)
     ... 41 more
javax.ejb.EJBException: Exception raised from invocation of public com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesResponseType com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesType) throws com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishClassificationSystemValuesFault method on bean instance [email protected]8 for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
     at $Proxy34_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.createUDDIClassifications(SOACentralSRPublisherImpl.java:742)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.publishServiceDefinitions(SOACentralSRPublisherImpl.java:435)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.publish(PublishRulesHandler.java:282)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.process(PublishRulesHandler.java:248)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.process(SOATimeoutListenerImpl.java:128)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:51)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:72)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:144)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:242)
Caused by: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:158)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:117)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)
     at $Proxy56_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(ServicesRegistryProxyFacade.java:302)
     at sun.reflect.GeneratedMethodAccessor810_10002.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
     ... 28 more
Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:340)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:961)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:700)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:152)
     ... 37 more
Caused by: java.io.IOException: Unable to connect to localhost:50100 - Connection refused: connect
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:666)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:658)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:621)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:499)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:450)
     at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getRequestStream(ClientHTTPTransport.java:481)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:298)
     ... 41 more

Support for xs:date types in web services generated from EJB components

I need to generate a Web Service from an EJB session bean based upon EJB entities generated from the Oracle 11g database that contain DATE type columns.
JDeveloper creates java.sql.Timestamp types in the EJB Session bean and this results in an exception error when I try to generate a web service from this bean via webservice annotations:
java.security.PrivilegedActionException: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
java.sql.Timestamp does not have a no-arg default constructor
I expected the web service wizard to generate argument types xs:dateTime or xs:date so this was an unwelcomed surprise.
I tried manually adding a method to the session bean with java.util.date arguments and had no problems with the web service wizard that correctly created xs:dateTime arguments. Is there any particular reason why the EJB wizard does not generate java.util.date arguments or handle java.sql.Timestamp without failing with an exception?
Since I begin with database tables and generate EJB entity classes and then web services with the Jdeveloper wizards it seems to me that there is a problem here in JDeveloper. Would you agree?
There are several possible more or less appealing workarounds, such as doing manually adding methods to the EJB facade with java.util.date arguments and doing the conversion from/to java.sql.timestamp manually. Is this a reasonable approach or does JDeveloper support date/time for Date columns in some other way that I have missed?
Very Grateful for any comments or suggestions.
Edited by: user10601664 on May 2, 2009 1:14 PM
Edited by: user10601664 on May 2, 2009 1:43 PM

Checkout this example:
http://www.manojc.com/?sample3
public class HelloWorldService{
* @wlws:exclude
public void dontExpose(){
Regards,
-manoj
http://manojc.com
"Jacob Anderson" <[email protected]> wrote in message
news:4036581e$[email protected]..
>
hello,
I created the descriptor file for a web service that had a protectedmethod in
it and noticed the protected method showed up in the descriptor file!Should
the "source2wsdd" task only output PUBLIC methods as service actions? Isthere
any way to specify methods to be 'ignored' when generating the webservices descriptor
file?
here was the generated descriptor XML:
<web-service name="BindingService"
protocol="https"
style="document"
targetNamespace="http://www.foo.com/ws/BindingService/"
portName="BindingServicePort"
uri="/BindingService"
portTypeName="BindingServicePort">
<types>
</types>
<wsdd:type-mappingxmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdd="http://www.bea.com/servers/wls70">
<wsdd:type-mapping-entrydeserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec"
type="xsd:anyType"
class-name="org.w3c.dom.Document"
serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec">
</wsdd:type-mapping-entry>
</wsdd:type-mapping>
<components>
<java-class name="BindingService"
class-name="com.arrow.ws.vendor.BindingService">
</java-class>
</components>
<operations>
<operation name="getConfigName"
component="BindingService"
method="getConfigName()">
<params>
<return-param xmlns:typeNS="http://www.w3.org/2001/XMLSchema"
location="body"
type="typeNS:string"
name="result"
class-name="java.lang.String">
</return-param>
</params>
</operation>
</operations>
</web-service>

Deployment Error using the Web Services sample ?

All,
I am running the Web Services sample, the compile works fine, but the deployment fails with the following error -
Any suggestions on what needs to be fixed ?
Sameer.
C:\jdev9\jdk\jre\bin\javaw.exe -jar C:\ias\j2ee\home\admin.jar ormi://127.0.0.1/ admin **** -deploy -file C:\jdev9\jdev\mywork\WorkspaceStatelessJava\Project\WorkspaceStatelessJava-ProjectStatelessJava-WS.ear -deploymentName WorkspaceStatelessJava-ProjectStatelessJava-WS
Error: java.lang.NoSuchMethodError: java.net.URL: method getPath()Ljava/lang/String; not found
Exit status of OC4J admin tool (-deploy): 1

Thanks Mike, your guess was right on target.
I realize this sample was originally tested for Oracle9i Web Services
Quickstart Install (9.0.2) , but I have been able to get it running on
(9.0.3) as well.
1) I pointed to a jdk 1.3 directory and then was able to
create a password for oc4j.
C:\jdev9\j2ee\home>D:\jdk1.3.1\bin\java -jar oc4j.jar -install
Enter an admin password to use: admin
Confirm admin password: admin
Installation done
2) This time the deployment worked -
---- Deployment started. ---- Dec 6, 2002 10:57:42 AM
Wrote WAR file to
C:\jdev9\jdev\mywork\WorkspaceStatelessJava\Project\WebServices.war
Wrote EAR file to
C:\jdev9\jdev\mywork\WorkspaceStatelessJava\Project\WorkspaceStatelessJ
ava-ProjectStatelessJava-WS.ear
Invoking OC4J admin tool...
C:\jdev9\jdk\jre\bin\javaw.exe -jar C:\jdev9\j2ee\home\admin.jar
ormi://127.0.0.1/ admin **** -deploy -file
C:\jdev9\jdev\mywork\WorkspaceStatelessJava\Project\WorkspaceStatelessJ
ava-ProjectStatelessJava-WS.ear -deploymentName
WorkspaceStatelessJava-ProjectStatelessJava-WS
Auto-unpacking
C:\jdev9\j2ee\home\applications\WorkspaceStatelessJava-ProjectStateless
Java-WS.ear... done.
Auto-unpacking
C:\jdev9\j2ee\home\applications\WorkspaceStatelessJava-ProjectStateless
Java-WS\WebServices.war... done.
Copying default deployment descriptor from archive at
C:\jdev9\j2ee\home\applications\WorkspaceStatelessJava-ProjectStateless
Java-WS/META-INF/orion-application.xml to deployment directory
C:\jdev9\j2ee\home\application-deployments\WorkspaceStatelessJava-Proje
ctStatelessJava-WS...
Auto-deploying WorkspaceStatelessJava-ProjectStatelessJava-WS (New
server version detected)...
Exit status of OC4J admin tool (-deploy): 0
C:\jdev9\jdk\jre\bin\javaw.exe -jar C:\jdev9\j2ee\home\admin.jar
ormi://127.0.0.1/ admin **** -bindWebApp
WorkspaceStatelessJava-ProjectStatelessJava-WS WebServices
http-web-site /WorkspaceStatelessJava-ProjectStatelessJava-context-root
Exit status of OC4J admin tool (-bindWebApp): 0
Use the following context root(s) to test your web application(s):
http://127.0.0.1:8888/WorkspaceStatelessJava-ProjectStatelessJava-conte
xt-root
Elapsed time for deployment: 22 seconds
---- Deployment finished. ---- Dec 6, 2002 10:58:04 AM
3) Running the Client.java worked.
Project Message Window
C:\jdev9\jdk\bin\javaw.exe -ojvm -classpath
C:\jdev9\jdev\mywork\WorkspaceStatelessJava\Project\classes;C:\jdev9\jd
ev\lib\jdev-rt.jar;C:\jdev9\jdev\lib\jdev-rt.jar;C:\jdev9\soap\lib\soap
.jar;C:\jdev9\lib\xmlparserv2.jar;C:\jdev9\jlib\javax-ssl-1_2.jar;C:\jd
ev9\jlib\jssl-1_2.jar;C:\jdev9\j2ee\home\lib\activation.jar;C:\jdev9\j2
ee\home\lib\mail.jar;C:\jdev9\j2ee\home\lib\http_client.jar Client
Hello Mike! The current time is Fri Dec 06 11:08:36 EST 2002Process
exited with exit code 0.
4) TCP Tunnel Utility runs correctly
HTTP/1.1 100 ContinueServer: Oracle9iAS (9.0.3.0.0) Containers for
J2EEDate: Fri, 06 Dec 2002 16:14:59 GMTHTTP/1.1 200 OKDate: Fri, 06 Dec
2002 16:14:59 GMTServer: Oracle9iAS (9.0.3.0.0) Containers for
J2EEContent-Length: 517Connection: CloseContent-Type: text/xml;
charset=utf-8<?xml version='1.0' encoding='UTF-8'?><SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body><ns1:sayHel
loResponse xmlns:ns1="HelloImpl"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><ret
urn xsi:type="xsd:string">Hello Mike! The current time is Fri Dec 06
11:15:00 EST
2002</return></ns1:sayHelloResponse></SOAP-ENV:Body></SOAP-ENV:Envelope
>
POST
/WorkspaceStatelessJava-ProjectStatelessJava-context-root/HelloImpl
HTTP/1.1Host: 127.0.0.1:8900Connection: Keep-Alive, TETE: trailers,
deflate, gzip, compressUser-Agent: RPT-HTTPClient/0.3-3SOAPAction:
""Accept-Encoding: deflate, gzip, x-gzip, compress,
x-compressContent-type: text/xml; charset=utf-8Content-length: 441<?xml
version='1.0' encoding='UTF-8'?><SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body><ns1:sayHel
lo xmlns:ns1="HelloImpl"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><par
am
xsi:type="xsd:string">Mike</param></ns1:sayHello></SOAP-ENV:Body></SOAP
-ENV:Envelope>
--------------------------

Problem while opening the Web Service Homepage

Hi All,
I have created a Web Service and in Tcode WSADMIN , I am trying to open the Web Service Homepage (Ctrl+F8) and getting an error message "Could not determine WSDL Address(ICF Error)".
Please suggest...
Regards
Pravesh

Hi,
In transaction SICF
<b>/sap/bc/bsp/sap/learning_map</b>
Choose Activate Service from the context menu.
Also refer this thread.
Solution Manager Learning Map http error 403
Regards,
Sarvesh

How to code in java to use the web services of CRM

Hi,
I am new to CRM on demand web services. I want to develope a java J2EE application to insert some lead data into CRM on demand. But i have no idea of how the wsdl provided by CRM can be converted to a java class so that i can use the API's provided by them in my program. I am using Eclipse Galileo IDE for my java application development. Can any one tell me the way to reference the wsdl in my program or any other way to build my application.
Please help me out.
Thanx in advance.

May be it's the 'stub' you should be looking for.
Any Account related queries/creations - AccountStub
--> Query : Populate AccountQuery, populate AccountQueryPage_Input, call accountStub.accountQueryPage(input);
--> Creation: Populate AccountData, populate AccountInsert_Input, call accountStub.accountInsert(input)
It's the same procedure for other objects like Contact, Lead, Opportunity.
I worked on other web-services using Axis2, and 'Stub' has been the one which we use to connect to the web-service.
Edited by: 838315 on Mar 30, 2011 11:17 PM
Edited by: 838315 on Mar 30, 2011 11:59 PM

Problem in invoking the web services

Hi all,
I am new to java web services
i develoed a simple webservices here i am posting the code
i generated every thing using wstools of Jboss4.0.5AS
package com.javasrc.webservices.age;
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface Age extends Remote
public String age( String name, Integer age ) throws RemoteException;
package com.javasrc.webservices.age;
public class Age_Imp
     public String age( String name, Integer age )
          return name + " is " + age + " years old!";
when i am invoking using the client progrmme i am getting nullpointer exception
ie.
java.lang.NullPointerException
     at org.apache.axis.client.Call.getTypeMapping(Call.java:2402)
     at org.apache.axis.client.Call.setReturnType(Call.java:1230)
     at org.apache.axis.client.Call.setOperation(Call.java:1412)
     at org.apache.axis.client.AxisClientProxy.invoke(AxisClientProxy.java:369)
     at $Proxy0.age(Unknown Source)
     at com.javasrc.webservices.age.AgeClient.main(AgeClient.java:35)
Exception in thread "main"
**this is my client programm**
package com.javasrc.webservices.age;
import javax.xml.rpc.Service;
import javax.xml.rpc.ServiceFactory;
import com.javasrc.webservices.age.Age;
import javax.xml.namespace.QName;
import java.net.URL;
public class AgeClient
public static void main( String[] args ) throws Exception {
if( args.length < 3 )
System.out.println( "Usage: AgeClient urlstr name age" );
System.exit( 0 );
String urlstr = args[ 0 ];
String argument = args[ 1 ];
String argument2 = args[ 2 ];
System.out.println( "Contacting webservice at " + urlstr );
URL url = new URL(urlstr);
QName qname = new QName("http://age.webservices.javasrc.com/",
"AgeService");
ServiceFactory factory = ServiceFactory.newInstance();
Service service = factory.createService( url, qname );
Age age = ( Age ) service.getPort( Age.class );
System.out.println( "age.age(" + argument + ", " + argument2 + ")" );
String result = age.age(argument,new Integer( argument2 ));//here i am getting error
System.out.println( "output:" + result );
pls help in resolving this

Assuming this is for Oracle BPM 11g.
I'm a novice at this and sure others will have infinitely better ideas (have I lowered your expectations enough?), but here are two thoughts. Both of these ideas assume that your child process was invoked by an Oracle BPM parent process.
When you expose a process as a web service and invoke it asynchronously from a parent process, there is a call back service available. I've yet to figure out exactly how to get it to work, but if you look at the "Start" event's property in the composite (it's the service) you will see the callback information in the bottom dropdown. I believe what this means is that from your child process, you can use a Service activity to invoke a service that invokes the callback service back to the parent process's Service activity.
My other idea (you're not going to like this one) would be to to invoke the subprocess using a Message Start Event activity instead of the Service activity you're currently using. If you go this route, then you could have your parent process kick off the child subprocess using a Message Start Event activity and then immediately after this have a Message Catch Event activity. The child process could have a Message Throw Event activity immediately after its Start Message Event activity that sends a notification to the parent process. The good part about this is that I've actually gotten this to work.
You can send argument information back to the parent process, but (sorry) I don't yet know how to capture the process id.
Wish I could be of more help and hope this helps a little.

Properties of Web Services generated from Application services in CAF

Hi to all,
first sorry for posting one question twice (in CAF and CE forums) but I am not sure where exactly it belongs.
I experience problems with exposing web services from application service in CE 7.1 (trial version).
I want to add fault elements or use document literal instead of RPC binding. I do it from the design page for web services. The problem is that after saving and regenerating the application, the changed information gets lost.
Is it possible to expose these services while changing some information?
And another question that would arise if this is possible. How can I catch the faults in VC? Is there e possibility to show different panels according to the value returned (from the data service, which is a web service with fault element).
Thank You in advance!
V S

Hi,
Please check note 1004108.
Methods of Application and/or Entity Services (Business Objects) of CAF of SAP NetWeaver CE 7.1 cannot be exposed in document style, only RPC/literal is possible. Sorry.
It's a restriction that is planned to be solved in one of the next releases.
Regards,
Jan

Problem in using the Web Service generated from BAPI_FLIGHT_GETLIST

Similar Messages

Maybe you are looking for