Ejb webservice..wsdl file

hi all,
i have created a product table in the database and then i created an entity product class from the table,
after that i created session bean and publish this session bean as a web service.
During creating session bean --> i chose Business tier00--> session bean --> include Web Service Endpoint Interface-->
i got the interface ProductSessionWeb Service (java file) but i am wondering why in the class i need to import and do anotation @WebMethod on my own the tool does do this for me.
After adding anotation @WebMethod for an operation (selectAll) in order to select product table.
i deployed this web service on oracle application server. it was sucessful and i tested this web service . it returned the product data that i expected.
1. However, i can not find WSDL file in the directory that i created.
2. i can only see wsdl file from my address location on (Explorer)
3. How can i generate WSDL file from this application
please help

Hi Ashutosh,
I am not using web dynpro. I am using EJB for consuming webservice. Now, in visual admin I stopped Web service security service and again started it again
Now its giving me following error:
<b>java.lang.Exception: Call to {remote server url} returned http code 500 with unacceptable content type (text/html).
<HTML>
<HEAD><TITLE>500 Server Error</TITLE></HEAD>
<BODY>
<H1>Server Error</H1>
<H4>
The following error occurred:<P>
[code=SERVER_RESPONSE_CLOSE] The server closed the connection while reading the response. Contact your system administrator.
</H4>
<HR>
Please contact the administrator.
</BODY>
</HTML></b>

Similar Messages

Regarding Webservice WSDL file

Hello experts,
Please help me by clarifying the below mentioned issue.
I have cretaed a interactive form and placed one button on the form to submit the form data to the webservice.
Now, in the properties of the button(Execute Type) i got the new dataconnection name by choosing the path EDIT-->New Data Connection
and by uploading the WSDL file which was saved on my desktop.
Now, it is working fine and iam able to do the bindings to webservice importing fields.
But the problem is if i remove the WSDL file from the location where it was while creating new data connection in the form.
The interfacing parameters of webservice in the DATA VIEW of the form are going OFF and if i reopen the form it is saying that "the file XXXXXXXXXXXXXXXX not exist".
I tried with giving http URL in creating New data connection, but it is not accepting that URL and saying that "the URL : YYYYYYYYYYYYYYYYYYYYYYYY is invalid"
Iam just following the standard procedure for taking the WSDL file or http UTL.
Am i need to do any thing extra in taking WSDL file or URL?
Regards,
Ram

No you are doing it right ....if you enter the url for the wsdl in a browser to you get the wsdl showing up? Are there any dialogs that pop up?
Paul

Error creating Webservice Client in JAVA for ABAP Webservice(WSDL file)

Hi all,
I have created a webservice from a funtion module in the backend.
Using soamanger I downloaded the wsdl file using "Open WSDL document for selected binding" link.
I tested this web service in backend and it is working fine.
Now I am trying to generate JAVA cilent for this webservice using Eclipse and Axis,but getting the following error
IWAB0399E Error in generating Java from WSDL: WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy):
faultCode=INVALID_WSDL: Encountered unexpected element '{http://schemas.xmlsoap.org/ws/2004/09/policy}Policy'.:
    WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element
'{http://schemas.xmlsoap.org/ws/2004/09/policy}Policy'.:
    at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
    at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
    at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
    at java.lang.Thread.run(Unknown Source)
Please let me know,wat needs to be done for this error to get resolved
Thanks
Santhosh

Hi,
I am also getting the same error while generating the client class from IBM Rational Application Developer IDE.
Here is the error I get.
WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
     [java] at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
     [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
     [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
     [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
     [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
     [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
     [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
     [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
     [java] at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
     [java] at java.lang.Thread.run(Thread.java:571)
Did you find out the cause of this issue?
Thanks & Regards,
Vijay

Have a requirement to consume a SOAP webservice (wsdl file) using apex

Hi,
I am using Application Express 4.2.2.00.11.
My requirement is to consume a soap web service (wsdl file).
I am pasting the wsdl fille.
<wsdl:message name="FulfillOrderResponseRequestMessage">
<wsdl:part name="payload" element="ffebm:ProcessFulfillmentOrderNotificationEBM"/>
</wsdl:message>
<wsdl:message name="FulfillOrderResponseResponseMessage">
<wsdl:part name="payload" element="ffebm:ProcessFulfillmentOrderNotificationResponseEBM"/>
</wsdl:message>
<wsdl:portType name="FulfillOrderResponse">
<wsdl:operation name="process">
<wsdl:input message="client:FulfillOrderResponseRequestMessage"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="FulfillOrderResponseCallback">
<wsdl:operation name="processResponse">
<wsdl:input message="client:FulfillOrderResponseResponseMessage"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="FulfillOrderResponseBinding" type="client:FulfillOrderResponse">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
<wsp:PolicyReference URI="#wss11_saml_or_username_token_with_message_protection_service_policy" wsdl:required="false"/>
<wsp:PolicyReference URI="#wsaddr_policy" wsdl:required="false"/><wsdl:operation name="process">
and the xml file looks like this
<FulfillOrderResponseRequestMessage>
<part name="payload">
<coreforderrocessFulfillmentOrderNotificationEBM>
<corecom:EBMHeader>
<corecom:EBMID>2d383135353332303931343330383630</corecom:EBMID>
<corecom:EBMName>{_http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/FulfillmentOrder/V1}ProcessFulfillmentOrderNotificationEBM</corecom:EBMName>
<corecom:EBOName>{_http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/FulfillmentOrder/V1}ProcessFulfillmentOrderNotificationEBO</corecom:EBOName>
<corecom:CreationDateTime>2013-12-27T13:29:04.530+05:30</corecom:CreationDateTime>
<corecom:VerbCode>Update</corecom:VerbCode>
<corecom:MessageProcessingInstruction>
<corecom:EnvironmentCode>PRODUCTION</corecom:EnvironmentCode>
</corecom:MessageProcessingInstruction>
<corecomender>
<corecom:ID schemeAgencyID="GPR">EBSVIS</corecom:ID>
<corecomenderMessageID/>
<corecom:CallingServiceName>{_http://xmlns.oracle.com/ApplicationBusinessFlow/OrderToCash/ProcessFulfillmentOrderNotificationEbizToFusionDOOABF/V1}ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</corecom:CallingServiceName>
<corecom:WSAddress>
<ns1:ReplyTo>
<ns1:Address/>
<ns1ortType>ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</ns1ortType>
<ns1erviceName>ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</ns1erviceName>
</ns1:ReplyTo>
<ns1:FaultTo>
<ns1:Address/>
<ns1ortType>ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</ns1ortType>
<ns1erviceName>ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</ns1erviceName>
</ns1:FaultTo>
</corecom:WSAddress>
</corecomender>
<corecom:Target>
<corecom:ID schemeAgencyID="GPR">GPR</corecom:ID>
</corecom:Target>
<corecom:BusinessScope/>
<corecom:EBMTracking>
<corecomequenceNumber>1</corecomequenceNumber>
<corecom:ExecutionUnitName>ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</corecom:ExecutionUnitName>
<corecom:ImplementationCode>BPEL</corecom:ImplementationCode>
<corecom:ActivityDateTime>2013-12-27T13:29:04.531+05:30</corecom:ActivityDateTime>
</corecom:EBMTracking>
<xacml-context:Request/>
</corecom:EBMHeader>
<coreforderataArea>
<corecomrocess operation="ProcessFulfillmentOrderNotification"/>
<coreforderrocessFulfillmentOrderNotification>
<corecom:Identification>
<corecom:BusinessComponentID/>
<corecom:ID schemeID="ORDER_NUMBER" schemeAgencyID="EBSVIS">66498</corecom:ID>
<corecom:ApplicationObjectKey>
<corecom:ID schemeID="HEADER_ID" schemeAgencyID="EBSVIS">228338</corecom:ID>
</corecom:ApplicationObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeAgencyID="GPR">300000030196926</corecom:ID>
</corecom:AlternateObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeID="ExternalInteractionKey">228338</corecom:ID>
</corecom:AlternateObjectKey>
</corecom:Identification>
<coreforder:CurrencyCode listAgencyID="EBSVIS">USD</coreforder:CurrencyCode>
<coreforder:TypeCode listAgencyID="GPR">ORDER</coreforder:TypeCode>
<corecom:BusinessUnitReference>
<corecom:BusinessUnitIdentification>
<corecom:BusinessComponentID/>
<corecom:ApplicationObjectKey>
<corecom:ID schemeID="ORG_ID" schemeAgencyID="EBSVIS">204</corecom:ID>
</corecom:ApplicationObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeAgencyID="GPR">300000028235904</corecom:ID>
</corecom:AlternateObjectKey>
</corecom:BusinessUnitIdentification>
</corecom:BusinessUnitReference>
<coreforder:FulfillmentOrderLine actionCode="UPDATE">
<corecom:Identification>
<corecom:BusinessComponentID/>
<corecom:ID schemeID="LINE_NUMBER" schemeAgencyID="EBSVIS">1</corecom:ID>
<corecom:ApplicationObjectKey>
<corecom:ID schemeID="LINE_ID" schemeAgencyID="EBSVIS">419300</corecom:ID>
</corecom:ApplicationObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeAgencyID="GPR">300000030196928</corecom:ID>
</corecom:AlternateObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeID="ExternalInteractionKey">419300</corecom:ID>
</corecom:AlternateObjectKey>
</corecom:Identification>
<coreforderrderQuantity>2</coreforderrderQuantity>
<coreforder:CurrencyCode listAgencyID="EBSVIS">USD</coreforder:CurrencyCode>
<corecomtatus>
<corecom:Code listAgencyID="GPR">AWAIT_SHIP</corecom:Code>
</corecomtatus>
<corecom:ItemReference>
<corecom:ItemIdentification>
<corecom:BusinessComponentID/>
<corecom:ApplicationObjectKey>
<corecom:ID schemeAgencyID="EBSVIS">225</corecom:ID>
</corecom:ApplicationObjectKey>
</corecom:ItemIdentification>
<corecom:TypeCode listAgencyID="GPR">4</corecom:TypeCode>
</corecom:ItemReference>
<coreforder:FulfillmentOrderSchedule actionCode="UPDATE">
<corecom:Identification>
<corecom:BusinessComponentID/>
<corecom:ApplicationObjectKey>
<corecom:ID schemeID="LINE_ID" schemeAgencyID="EBSVIS">419300</corecom:ID>
</corecom:ApplicationObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeID="FulfillLineId" schemeAgencyID="GPR">300000030196928</corecom:ID>
</corecom:AlternateObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeID="ExternalInteractionKey">419300</corecom:ID>
</corecom:AlternateObjectKey>
</corecom:Identification>
<coreforder:FreightTermCode listAgencyID="EBSVIS">Paid</coreforder:FreightTermCode>
<coreforderrderQuantity>2</coreforderrderQuantity>
<coreforderromisedShipDateTime>2013-12-27T19:30:00.000+00:00</coreforderromisedShipDateTime>
<corefordercheduledShipDateTime>2013-12-27T19:30:00.000+00:00</corefordercheduledShipDateTime>
<corecomtatus>
<corecom:Code listAgencyID="GPR">AWAIT_SHIP</corecom:Code>
</corecomtatus>
<corecom:UnitListPrice>
<corecom:Amount>100</corecom:Amount>
</corecom:UnitListPrice>
<corecom:UnitSalePrice>
<corecom:Amount>100</corecom:Amount>
</corecom:UnitSalePrice>
<corecom:CarrierPartyReference>
<corecomartyIdentification>
<corecom:ApplicationObjectKey>
<corecom:ID schemeAgencyID="EBSVIS"/>
</corecom:ApplicationObjectKey>
</corecomartyIdentification>
</corecom:CarrierPartyReference>
<coreforder:FulfillmentOrderScheduleTax>
<corecom:Tax>
<corecom:Amount>0</corecom:Amount>
</corecom:Tax>
</coreforder:FulfillmentOrderScheduleTax>
<coreforder:FulfillmentOrderItem>
<corecom:ItemReference>
<corecom:ItemIdentification>
<corecom:BusinessComponentID/>
<corecom:ApplicationObjectKey>
<corecom:ID schemeAgencyID="EBSVIS">225</corecom:ID>
</corecom:ApplicationObjectKey>
</corecom:ItemIdentification>
<corecom:TypeCode listAgencyID="GPR">4</corecom:TypeCode>
</corecom:ItemReference>
</coreforder:FulfillmentOrderItem>
</coreforder:FulfillmentOrderSchedule>
</coreforder:FulfillmentOrderLine>
</coreforderrocessFulfillmentOrderNotification>
</coreforderataArea>
</coreforderrocessFulfillmentOrderNotificationEBM>
</part>
</FulfillOrderResponseRequestMessage>
I need to pass few of the above parameters from database using apex.
Any help will be very thankfull.
Please if anything more is required to be provided from my side
Thanks
Nilesh

I nee to pass values to few of the above parameters.
Please inform if anything more is required from my end.

Need PAPI WebService WSDL files - INPUT & OUTPUT schema will do

Dear Friends,
I need all the wsdl files or atleast input and output schema for all PAPI Web Services. Currently I dont have access to development env but need to put this in a document. The Oracle documents related to PAPI WS does not include this. They just show a few examples and code snippets.
Thanks,
Som
Edited by: user10880245 on Sep 20, 2010 9:44 PM

Try using SoapUI to view the PAPI-WS... It will list out all the methods that are available, and should allow you get what you need. You can even do this from studio, so a DEV environment isn't needed.
HTH,
-Kevin

How to get values of complex data type specified in webservice wsdl file

I'm trying to retreive cid from a complex data type[b] course which I'm getting as response from the webservice, it throwing that cid is not valid .
<course>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="payload">
<syncbpelResponse xmlns="http://acm.org/samples">
<course>
<startDate xmlns="urn:cms_soa">2005-12-11T18:30:00.000Z</startDate>
<materialid xmlns="urn:cms_soa">234</materialid>
<cdescription xmlns="urn:cms_soa">learn spoken english</cdescription>
<instructorid xmlns="urn:cms_soa">145</instructorid>
<regEndDate xmlns="urn:cms_soa">2005-11-30T18:30:00.000Z</regEndDate>
<cid xmlns="urn:cms_soa">12222</cid>
<cfee xmlns="urn:cms_soa">1000.0</cfee>
<strength xmlns="urn:cms_soa">20</strength>
<currentStrength xmlns="urn:cms_soa">2</currentStrength>
<endDate xmlns="urn:cms_soa">2005-12-30T18:30:00.000Z</endDate>
<cvenue xmlns="urn:cms_soa">ELNET</cvenue>
<cname xmlns="urn:cms_soa">english</cname>
</course>
</syncbpelResponse>
</part>
</course>
I tried using
<from variable="course" part="payload" query="/tns:syncbpelRespons/tns:course/@cid"/>
but not at all accepting....
I 'll be thankfull if u send me a response

Hi
This can not be done Vc only "sees" the returned data in the webservice, it can not access the meta data from the webservice.
Jarrod

How to combine multiple webservices into one WSDL file

Gurus,
I have 4 four webservices(ws1,ws2,ws3 & ws4) defined in XI. Normally in XI when we define webservice ,WSDL file will be generated for each interface. Now I have 4 related interfaces, so 4 WSDL files will generated. Suppose if I have 100 webservices then 100 WSDL files need to be generated & need to send to other party to consume our services, which is very tedious task & to track also. So is it possible to combine related webservices into one WSDL file? Your inputs will be highly appreciated.
Regards,
Santhosh

Hi,
Instead of trying to combine the interfaces, you can try to define your interface mapping with 4 sender interfaces with in one interface mapping . I think this may give you the result you are expecting.
If you want entire content to be in one interface , then, define single interface which can accomadate, all message ocntent of all 4 interfaces.Means your sender message to contain the 4 datatypes internally.
Regards,
Reyaz

Deploying an EJB WebService under WLS 9.1 - port component "Hello" is not found in wsdl.

Hi,
I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
compile works fine, but the server deployment throw the following error
message:
[java] port component "Hello" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but not with
WLS 9.1. Maybe it's a simple configuration error and someone can help.
Regards
Guido
Appendix
webservice.xml
<webservices xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
version="1.1">
<webservice-description>
<webservice-description-name>HelloService</webservice-description-name>
<wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>Hello</port-component-name>
<wsdl-port>HelloPort</wsdl-port>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<service-impl-bean>
<ejb-link>HelloBean</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping version="1.1" xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
</package-mapping>
<service-interface-mapping>
<service-interface>com.jcoffee.components.ws.HelloService</service-interface
>
<wsdl-service-name
xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
wsdl-service-name>
<port-mapping>
<port-name>HelloPort</port-name>
<java-port-name>HelloPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<wsdl-port-type
xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
port-type>
<wsdl-binding
xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>hello</java-method-name>
<wsdl-operation>hello</wsdl-operation>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
sdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
ponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>
HelloService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://ws.components.jcoffee.com/"
xmlns:tns="http://ws.components.jcoffee.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="Hello_hello">
<part name="String_1" type="xsd:string"/>
</message>
<message name="Hello_helloResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="Hello">
<operation name="hello" parameterOrder="String_1">
<input message="tns:Hello_hello"/>
<output message="tns:Hello_helloResponse"/>
</operation>
</portType>
<binding name="HelloBinding" type="tns:Hello">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="hello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</input>
<output>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloPort" binding="tns:HelloBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
and last but not least the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>JCoffee web service sample</display-name>
<enterprise-beans>
<session>
<ejb-name>HelloBean</ejb-name>
<service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
<ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<method-permission>
<unchecked/>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Hi again,
I got it - i've forgot the namespace prefix for the wsdl-port.
Now it works.
Thanks!
"Ben" <[email protected]> schrieb im Newsbeitrag
news:[email protected]...
Hi,
I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
compile works fine, but the server deployment throw the following error
message:
[java] port component "Hello" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but notwith
WLS 9.1. Maybe it's a simple configuration error and someone can help.
Regards
Guido
Appendix
webservice.xml
<webservices xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
version="1.1">
<webservice-description>
<webservice-description-name>HelloService</webservice-description-name>
<wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>Hello</port-component-name>
<wsdl-port>HelloPort</wsdl-port>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<service-impl-bean>
<ejb-link>HelloBean</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping version="1.1" xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
</package-mapping>
<service-interface-mapping>
<service-interface>com.jcoffee.components.ws.HelloService</service-interface
>>
<wsdl-service-name
xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
wsdl-service-name>
<port-mapping>
<port-name>HelloPort</port-name>
<java-port-name>HelloPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<wsdl-port-type
xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
port-type>
<wsdl-binding
xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>hello</java-method-name>
<wsdl-operation>hello</wsdl-operation>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
sdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
ponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>
HelloService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://ws.components.jcoffee.com/"
xmlns:tns="http://ws.components.jcoffee.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="Hello_hello">
<part name="String_1" type="xsd:string"/>
</message>
<message name="Hello_helloResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="Hello">
<operation name="hello" parameterOrder="String_1">
<input message="tns:Hello_hello"/>
<output message="tns:Hello_helloResponse"/>
</operation>
</portType>
<binding name="HelloBinding" type="tns:Hello">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="rpc"/>
>
>
<operation name="hello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</input>
<output>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloPort" binding="tns:HelloBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
and last but not least the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>JCoffee web service sample</display-name>
<enterprise-beans>
<session>
<ejb-name>HelloBean</ejb-name>
<service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
<ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<method-permission>
<unchecked/>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Consume WSDL file in EJB Causes the Error while running in NWDI 7.2

Hi Experts,
I have WSDL File its working in the Portal.I have checked the WSDL file WS Navigator.
Importing the WSDL File:
I have follow these steps:
1. I have select the EJB Project and import the WSDL File.
2. Once the WSDL File is import in EJB Project i have right click the WSDL File and select the Create Web Service Client.
3. The Below Java Class File is created.
    i) Package-info.java
    ii) ObjectFactory.Java
   iii) Request.java
   iv) Response.java
   v) Remote.java
   vi) Service.java
4. And then i have create one client.java and Main.java File to execute the WSDL File.
5. Run the Main.java file and at the time it shows the below error
Exception in thread "main" java.lang.NoClassDefFoundError: com/sap/engine/interfaces/sca/logtrace/CallEntry$TraceLevel
at com.sap.engine.services.webservices.espbase.client.bindings.ConfigurationUtil.getTransportBinding(ConfigurationUtil.java:249)
at com.sap.engine.services.webservices.espbase.client.bindings.ConfigurationUtil.createClientConfiguration(ConfigurationUtil.java:109)
at com.sap.engine.services.webservices.espbase.client.jaxws.metadata.InterfaceMetadata.createClientConfigurationContext(InterfaceMetadata.java:178)
at com.sap.engine.services.webservices.espbase.client.jaxws.metadata.InterfaceMetadata.getProxy(InterfaceMetadata.java:70)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.getPort(SAPServiceDelegate.java:258)
at javax.xml.ws.Service.getPort(Service.java:92)
at com.sap.tutorial.testwebser1ejb.TestAddService.getTestAddPort(TestAddService.java:38)
at com.sap.tutorial.testwebser1ejb.TestAddClient.testAdd(TestAddClient.java:12)
at com.sap.tutorial.testwebser1ejb.MainClass.main(MainClass.java:12)
Caused by: java.lang.ClassNotFoundException: com.sap.engine.interfaces.sca.logtrace.CallEntry$TraceLevel
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
... 9 more
Please reply if there is a problem in Importing and calling the WSDL file.Reply will help me a lot.
Thanks & Regards,
SatheshKumar R

Are you using the same version for both NWDS and your target SAP NetWeaver system?

How to assosciate webservice to a WSDL file

Hi
I tried developing webservice(EJB as RPC) in weblogic server and installed and its working fine if i call it from client.
I am using java2WSDL(axis) tool to create a WSDL file and WSDL2Java to create stubs for client to call.I am struck in linking webservice to use the wsdl file which i have created.
I manually tried to add my WSDL file to the WAR file of my application and also Updated the web.xml file of the Web application adding a mime-mapping.
I am able to access the WSDL file in browser as http://bt885094:7001/webservice/user.wsdl
But my client tries to access the service "http://bt885094:7001/webservice/C2PUserService" which has an associated WSDL file defined as http://bt885094:7001/webservice/C2PUserService?WSDL which needs to be checking for http://bt885094:7001/webservice/user.wsdl
Could anyone tell me how to assosciate webservice to a WSDL file.
thanks in advance

Thank you everyone for your help. As a complete newbie I found this nice walkthrough tutorial in onjava(i dont mean to spam).
1. View: Take a peek at the existing Fibonacci code.
2. Java2WSDL: Generate the WSDL file for the given Fibonacci interface.
3. WSDL2Java: Generate the server side wrapper code, and stubs for easy client access.
4. FibonacciSoapBindingImpl: Fill in wrapper to call the existing Fibonacci code.
5. Deploy: Deploy the service to Apache Axis.
6. Client: Write a client that uses the generated stubs, to easily access the Web service.
Given the webservice endpoint and the method name, I think I can now consume the web service using steps 3,4, and 6.

ERROR IN LOADING WSDL FILE in adaptive webservice model

Hi
i made my bapi as WDSL file and saved on to my desktop when i try to browse that wsdl file from front end it is saying ERROR IN LOADING WDSL FILE what might be the actual problem.could you please help me.
Thanks
Rahul

HI
try to save it once again and try or you can use the wsdl url directly . or other option you can do is
use the webservice model(deprecated) . maybe this could solve your problem .

Error in creating Adaptive Webservice model from local wsdl file

hi ,
     I am working on Netweaver7.1 CE. I am creating adaptive webservice model from local wsdl file which i have saved at location D:/subordinate WSDL WSDL By Raju/Manager.wsdl on my pc. I am able to bind context , build and deploy. But when i am running that webdynpro project m getting following error
java.io.FileNotFoundException: /D:/subordinate WSDL WSDL By Raju/Manager.wsdl (No such file or directory)
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(name=encryptappl.EncryptAppl, id=25f1f2e1a96411dd9d240050569630a5). The causing exception is nested. RID=25ef0cb0a96411dd91ce0050569630a5
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:650)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:225)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
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:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'file:/D:/subordinate WSDL By Raju/Manager.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:1034)
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.apl.model.manager.Manager.<init>(Manager.java:44)
at encryptappl.comp.EncryptApplComp.wdDoInit(EncryptApplComp.java:112)
at encryptappl.comp.wdp.InternalEncryptApplComp.wdDoInit(InternalEncryptApplComp.java:126)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:160)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:230)
at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:249)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:209)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:513)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1228)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoPreprocessing(AbstractExecutionContextDispatcher.java:150)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppPreprocessing.doService(DispatchHandlerForAppPreprocessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoPreprocessing(ExecutionContextDispatcher.java:100)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:75)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:507)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:527)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:233)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:647)
... 41 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. [Problem with WSDL file parsing. See nested message.]
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:247)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:131)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:124)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:420)
... 67 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Problem with WSDL file parsing. See nested message.
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:585)
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:341)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.loadProxy(DGenericServiceImpl.java:130)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:65)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:240)
... 70 more
Caused by: com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: /D:/subordinate WSDL By Raju/Manager.wsdl (No such file or directory)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:140)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:579)
... 74 more
Caused by: java.io.FileNotFoundException: /D:/subordinate WSDL By Raju/Manager.wsdl (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
at java.net.URL.openStream(URL.java:1007)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:201)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)
at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:282)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:293)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:146)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:132)
... 77 more

hi ,
i tried to create model using url in address tab , but i am getting error. This webservice is having authentication ,is this error bcoz of authentication????
I am posting error below
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://172.25.30.195:80/WebService/WebServiceApp.nsf/wsGetSuperior?OpenAgent' and service factory configuration '{DynamicProxy.ClassPath=D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.tc.cmi_10.0.0.080222130515/lib/com.sap.tc.cmi_api.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.exception_2.0.0.080222130515/lib/sap.comtcexceptionimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.engine.webservices_2.0.0.080222130515/lib/sap.comtcblbasewebservices_libimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.engine.webservices_2.0.0.080222130515/lib/sap.comtcbliqlibimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.engine.webservices_2.0.0.080222130515/lib/sap.comtcbljkernel_bootimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.engine.webservices_2.0.0.080222130515/lib/sap.comtcbljkernel_utilimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.engine.webservices_2.0.0.080222130515/lib/sap.comtcjewebservices_apiimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.engine.webservices_2.0.0.080222130515/lib/sap.comtcjewebservices_libimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.engine.webservices_2.0.0.080222130515/lib/sap.comtcjewebservicesimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.engine.webservices_2.0.0.080222130515/lib/sap.comtcsecwssecclientimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.engine.webservices_2.0.0.080222130515/lib/sap.comtcsecwsseclibimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.engine.webservices_2.0.0.080222130515/lib/sap.comtcsecwssecsrtlibimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.dictionary.runtime_10.0.0.080222130515/lib/com.sap.dictionary.runtime.mod_api.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.dictionary.runtime_10.0.0.080222130515/lib/com.sap.dictionary.runtime.mod_core.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.dictionary.runtime_10.0.0.080222130515/lib/dictionary_mdi_util_api.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.dictionary.runtime_10.0.0.080222130515/lib/dictionary_mdi_util_core.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.dictionary.runtime_10.0.0.080222130515/lib/dictionary_runtime_mdi_api.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.dictionary.runtime_10.0.0.080222130515/lib/dictionary_runtime_mdi_core.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.dictionary.services_10.0.0.080118105715/lib/com.sap.dictionary.services_api.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0.080222130515/lib/sap.comtcloggingjavaimpl.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0.080222130515/lib/sap.comtcsapxmltoolkitsapxmltoolkit.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0.080222130515/lib/activation.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0.080222130515/lib/jaxm-api.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0.080222130515/lib/jaxrpc-api.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0.080222130515/lib/jnet.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0.080222130515/lib/jsse.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0.080222130515/lib/mail.jar;D:/Program Files/SAP/IDE/CE/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0.080222130515/lib/saaj-api.jar;, DynamicProxy.HTTPPassword=, DynamicProxy.HTTPUserName=, DynamicProxy.Javac.path=D:\Program Files\java\jdk1.5.0_12\bin\javac, DynamicProxy.TempDir=C:\DOCUME1\kavita\LOCALS~1\Temp\}'
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:414)
     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:306)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:316)
     at com.sap.tc.webdynpro.model.webservice.modeltype.importer.ui.PageAWSRename.loadNameSpacesAndModelClasses(PageAWSRename.java:996)
     at com.sap.tc.webdynpro.model.webservice.modeltype.importer.ui.PageAWSLocalFileClient$5$1.run(PageAWSLocalFileClient.java:283)
     at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
     at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
     at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:158)
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:326)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
     at com.sap.tc.webdynpro.model.webservice.modeltype.importer.ui.PageAWSLocalFileClient.getNextPage(PageAWSLocalFileClient.java:299)
     at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813)
     at com.sap.ide.cmi.core.internal.newmodelwizard.NewModelWizardDialog.nextPressed(NewModelWizardDialog.java:66)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
     at com.sap.ide.cmi.core.internal.newmodelwizard.NewModelWizardDialog.buttonPressed(NewModelWizardDialog.java:88)
     at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
     at org.eclipse.jface.window.Window.open(Window.java:796)
     at com.sap.ide.cmi.core.internal.services.CreationServiceUI.createModel(CreationServiceUI.java:76)
     at com.sap.ide.cmi.core.browser.actions.CreateModelAction.run(CreateModelAction.java:60)
     at com.sap.ide.tools.core.viewerfwk.internal.actions.BaseSelectionSingleAction.run(BaseSelectionSingleAction.java:39)
     at com.sap.ide.tools.core.viewerfwk.internal.actions.BaseSelectionAction.runInternal(BaseSelectionAction.java:78)
     at com.sap.ide.tools.core.viewerfwk.internal.actions.BaseSelectionAction.run(BaseSelectionAction.java:70)
     at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
     at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
     at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
     at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
     at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
     at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
     at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
     at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
     at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
     at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
     at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
     at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
     at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. [Problem with WSDL file parsing. See nested message.]
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:247)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:91)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:84)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:412)
     ... 60 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Problem with WSDL file parsing. See nested message.
     at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:585)
     at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:341)
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.loadProxy(DGenericServiceImpl.java:130)
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:65)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:240)
     ... 63 more
Caused by: com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad Attribute value: ' or " expected!(http://172.25.30.195:80/WebService/WebServiceApp.nsf/wsGetSuperior?OpenAgent, row:3, col:96)
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:140)
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)
     at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:579)
     ... 67 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad Attribute value: ' or " expected!(http://172.25.30.195:80/WebService/WebServiceApp.nsf/wsGetSuperior?OpenAgent, row:3, col:96)(http://172.25.30.195:80/WebService/WebServiceApp.nsf/wsGetSuperior?OpenAgent, row=3, col=96) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad Attribute value: ' or " expected!(http://172.25.30.195:80/WebService/WebServiceApp.nsf/wsGetSuperior?OpenAgent, row:3, col:96)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:130)
     ... 70 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad Attribute value: ' or " expected!(http://172.25.30.195:80/WebService/WebServiceApp.nsf/wsGetSuperior?OpenAgent, row:3, col:96)
     at com.sap.engine.lib.xml.parser.XMLParser.scanAttValue(XMLParser.java:1402)
     at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1576)
     at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1719)
     at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2449)
     at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1848)
     at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2449)
     at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1848)
     at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2449)
     at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1848)
     at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2449)
     at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1848)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2852)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
     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.parse_DTDValidation(Parser.java:282)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:293)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
     ... 72 more

"Error in loading WSDL file" --- Adaptive Webservice Model

Hi All,
I have been using Deprecated web service model. But now my application is moving to Test. So in order not to change the URL of the webservice model in the Test, i tried with the Adaptive webservice model. But when i try to import the model its saying " Error in loading WSDL file. Check the error log for more details." Please help me out in this.
Thanks in advance,
Pranesh.

Hi Pranesh,
Please refer to this thread for similar issue and check the log file for NWDS for more details
Error in loading the WSDL file. Check the error log for more details
Hope it helps
Regards
Arun

Adaptive Webservice Model: Error in loading the WSDL file in NWDS 7.1 CE

Hi All,
I am trying to import WSDL using Adaptive Webservice Model into my webdynpro application. But I am unable to do so and it throws up an error as " Error in loading WSDL file. Check the error log for more details". The Content of log files has the following details
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Can not create SerializationFactoryImpl with 'null' params
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:247)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:91)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:84)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:412)
... 60 more
Caused by: java.lang.IllegalArgumentException: Can not create SerializationFactoryImpl with 'null' params !
at com.sap.engine.services.webservices.jaxrpc.encoding.SerializationFactoryImpl.<init>(SerializationFactoryImpl.java:171)
at com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingImpl.fromXml(TypeMappingImpl.java:495)
at com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingRegistryImpl.<init>(TypeMappingRegistryImpl.java:183)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.initTypeMappingRegistry(DGenericServiceImpl.java:108)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:66)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:240)
... 63 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Problem with WSDL file parsing. See nested message.
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:247)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:91)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:84)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:412)
     ... 60 more
Caused by: com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: Invalid Response Code: (500) Internal Server Error. The requested URL was:"http://10.15.8.97:5555/soap/rpc"
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:140)
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)
     at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:579)
     ... 67 more
Any pointer on this would be of great help.
Thanks and Regards,
Vishweshwara P.K.M

Solved. Issue was with the xml schema of the web service.

Can I include 2 diff strctures in d same wsdl file in a webservice scenario

Hii all,
We are using webservice to webservice scenario in which sender shld b able to send all the new rquest to the target and receive any updations or modifications from the receiver.
Few fields are different for request and modification structures. so i created 2 diff structures for source and target.
can any one suggest me who can i use single wsdl file for both the msgs( Creation and modifications) mean how to implement multi maping ( 1 to many) using wsdl
Regards
Anu

A simple way to include the 2 structures in one WSDL would be to create a combined structure similar to the one below:
<RequestPackage> (1 occurrence)
   <Request> (0 to n occurrence)
      <Create> (0 to 1 occurrence)
         ... Create Fields u2026
      </Create>
      <Modify> (0 to 1 occurrence)
         u2026 Modify Fields u2026
      </Modify>
   </Request>
</RequestPackage>
This is more complex than using 2 wsdls but it would allow you to easily send multiple create and modify records in the same message.
- Craig

Ejb webservice..wsdl file

Similar Messages

Maybe you are looking for