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>

Similar Messages

OMWB under Linux redhat AS 3 : Java 1.4 not found

Hi,
I have already used the oracle migration workbench under Windows with a total sucess.
But passing to Linux Redhat AS 3; Trying to launch the migration workbench by the ./omwb.sh ... the stressing error follows :
Java 1.4 not found. Java 1.4 requiered
I installed the j2re and j2sdk rpms without any changes
please help ! thinks

Hello All,
I solved the problem by executing the following commands :
$ java -version
... placeholder message ...
$ su -
# alternatives --remove java /usr/share/java/libgcj-java-placeholder.sh
# alternatives --remove javac /usr/share/java/libgcj-javac-placeholder.sh
# alternatives --remove jar /usr/bin/fastjar
# alternatives --remove jar.1.gz /usr/share/man/man1/fastjar.1.gz
# cd /usr/bin
# ln -s /usr/java/jre1.5.0/bin/java java
... also set the links for javac etc ...
# exit
$ java -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing)
$
Procedure of JDK is similar to J2RE...
It seems that it wasn't a difficult problem
sorry and thinks
Tchao

Deployment of a WebService on WLS that uses PAPI code

I have a web-service that uses PAPI code..
We need to deploy it I am guessing on the WLS server.. Where do we deploy it inside WLS? Is it under deployments or services?
Do we make a WAR or an EAR file?
We need to give the exact path for the directory.xml which is used in our code ...Where can we find this path on WLS or Enterprise Server?
i.e.
configuration.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE,
Also once we deploy it on WLS, what would be the WSDL path to access and make a client out of it?
http://testServer:1234/testTicket/services/CallPAPI?wsdl
does not work..

Hi,
Assuming you context to be..
Context
--Request_PedidoAutorizacao (node)
PedidoAutorizacao (node)
RefPagamento (attribute)
<i>You are invalidating Request_PedidoAutorizacao which is your main node.This node contians subnode PedidoAutorizacao</i>
<i>which has the input attribute RefPagamento</i>.
// try the following
WS_PagamentoVisa model = new WS_PagamentoVisa();
Request_PedidoAutorizacao req = new Request_PedidoAutorizacao(model);
PedidoAutorizacao input = new PedidoAutorizacao(model);
req.setPedidoAutorizacao(input);
wdContext.nodeRequest_PedidoAutorizacao().bind(req);
wdContext.currentPedidoAutorizacaoElement.setRefPagamento("12321321323");
wdContext.currentRequest_PedidoAutorizacaoElement().modelObject().execute();
wdContext.nodeResponse.invalidate(); // invalidate your response node

WLS 10.3.2 error - specific file not found system-jazn-data.xml

I don't want to use this on my stand alone server. Does anyone know how to get around it asking for the file upon deployment? Is there a setting in the WLS console to disable this feature?

hi,
1)Is this error occured at leat one secutity enable app installed?(Without application server works well?)
2)Is your app file base secutty enabled one(jazn-dat.xml) then what is the jazn-data.xml file size?
3)All ways keep a backup of newely created domain system-jazan-data.xml. Then you can replace the original one in case.
4)What is tha pllication? If it is an ADF app what is the version?
Nilum.

WLS started as NT service: javai.dll not found

Hi,
I have just installed WLS 5.1 SP8 as NT Service. After trying to start the
service from the console I get the message "The dynamic link library
javai.dll could not be found in the specified path ...".
But the WLS seems to work anyway (what I have tested so far).
I do not get this error if I start the WLS from the command line.
I checked on another machine and found the javai.dll in the jdk 1.1.8 bin
directory but I installed the JDK 1.3.0 on the new machine.
Does anybody else experienced this before?
Do I need to install the JDK 1.1.8?
Any feedback is very appreciated.
Thanks in advance,
Fleming Frese

In the unzipped SP8, there is sub-directory win32_12 under bin, which has
WLService.exe and some other files, copy them to your <wl-home>/bin
directory and try it again.
"Fleming Frese" <[email protected]> wrote in message
news:3a838fcb$[email protected]..
Michael,
Thanks for this information.
Does this mean, that WLS 5.1 SP9 kann run with JDK1.3, especially as NT
service then?
I interpreted the information in the "WebLogic Platform Support Summary"
website
(http://www.weblogic.com/platforms/index.html#winnt)
as if JDK 1.3 is generally not recommended to use with WLS 5.1.
I just want to sort out if we should wait for SP 9 or if we shut restrict
our development on JDK 1.2.2.
Thanks for any comments and recommendation
Fleming
Michael Girdley <----> wrote in message
news:3a80ff93$[email protected]..
This is a bug to be fixed in SP9.
Bug #: CR031853
Thanks,
Michael
Michael Girdley
BEA Systems
Learning WebLogic? http://learnweblogic.com
"Fleming Frese" <[email protected]> wrote in message
news:3a7ff4f3$[email protected]..
Hi,
I have just installed WLS 5.1 SP8 as NT Service. After trying to start
the
service from the console I get the message "The dynamic link library
javai.dll could not be found in the specified path ...".
But the WLS seems to work anyway (what I have tested so far).
I do not get this error if I start the WLS from the command line.
I checked on another machine and found the javai.dll in the jdk 1.1.8bin
directory but I installed the JDK 1.3.0 on the new machine.
Does anybody else experienced this before?
Do I need to install the JDK 1.1.8?
Any feedback is very appreciated.
Thanks in advance,
Fleming Frese

Calling webservice - meta-inf/services/javax.xml.ws.spi.provider not found

Hi,
I have created an applet. Its running well in standalone application. But it is not getting referred in some other localhost. The JAXWS is not getting referred by the JRE. I'm getting the exception as invocation exception, and cannot find the META-INF/services/javax.xml.ws.spi.provider.
Anyone can solve, pls reply me.

your problem is too stuffed to understand properly..could you elobarate a lil bit

Deploying a webservice on WLS 9.1 and got an wsdl error.

Hi,
I hoped it is then right usergroup to publish the following question.
I'm trying to deploy a EJB webservice on a WLS 9.1.
But I got the following error message:
[java] port component "SystemServiceEndpointPort" 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,
jaxrpc-mapping-SystemService.xml, SystemService.wsdl) works fine under JBoss 4.0, but not with
WLS 9.1. Maybe it's a simple configuration error and I hope someone can help.
I haved remembered the namespace in the webservices.xml file: <wsdl-port>wsdl:SystemServiceEndpointPort</wsdl-port> and also defined et in the top of the file.
Regards
Torben
<b>webservices.xml</b>
<webservices
xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wsdl="http://www.organisator.dk"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_web_services_1_1.xsd"
version="1.1">
<webservice-description>
<icon></icon>
<webservice-description-name>SystemService</webservice-description-name>
<wsdl-file>META-INF/wsdl/SystemService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/jaxrpc-mapping-SystemService.xml</jaxrpc-mapping-file>
<port-component>
<icon></icon>
<port-component-name>SystemServiceEndpointPort</port-component-name>
<wsdl-port>wsdl:SystemServiceEndpointPort</wsdl-port>
<service-endpoint-interface>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint-interface>
<service-impl-bean>
<ejb-link>SCSystem</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
<b>weblogic-webservices.xml</b>
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<webservice-description>
<webservice-description-name>SystemService</webservice-description-name>
<port-component>
<port-component-name>SystemServiceEndpointPort</port-component-name>
<service-endpoint-address>
<webservice-contextpath>/winnie</webservice-contextpath>
<webservice-serviceuri>/SystemService</webservice-serviceuri>
</service-endpoint-address>
</port-component>
</webservice-description>
</weblogic-webservices>
<b>ejb-jar.xml</b>
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar 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://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd" version="2.1">
<description><![CDATA[No Description.]]></description>
<display-name>Generated by XDoclet</display-name>
<enterprise-beans>

<session >
<description><![CDATA[System information handler]]></description>
<display-name>SCSystem</display-name>
<ejb-name>SCSystem</ejb-name>
<home>dk.organisator.winnie.system.ejbsystem.services.SCSystemHome</home>
<remote>dk.organisator.winnie.system.ejbsystem.services.SCSystemRemote</remote>
<service-endpoint>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint>
<ejb-class>dk.organisator.winnie.system.ejbsystem.services.SCSystemBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
<b>SystemService.wsdl</b>
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="SystemService" targetNamespace="http://organisator.dk/winnie/wsdl" xmlns:tns="http://organisator.dk/winnie/wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns2="http://organisator.dk/winnie/types" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<schema targetNamespace="http://organisator.dk/winnie/types" xmlns:tns="http://organisator.dk/winnie/types" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="getXxxxxxxxx">
<sequence>
<element name="String_1" type="string" nillable="true"/></sequence></complexType>
<complexType name="getXxxxxxxxxResponse">
<sequence>
<element name="result" type="string" nillable="true"/></sequence></complexType>
<complexType name="ping">
<sequence/></complexType>
<complexType name="pingResponse">
<sequence>
<element name="result" type="int"/></sequence></complexType>
<complexType name="setXxxxxxxx">
<sequence>
<element name="String_1" type="string" nillable="true"/></sequence></complexType>
<complexType name="setXxxxxxxxResponse">
<sequence/></complexType>
<element name="getXxxxxxxxx" type="tns:getXxxxxxxxx"/>
<element name="getXxxxxxxxxResponse" type="tns:getXxxxxxxxxResponse"/>
<element name="ping" type="tns:ping"/>
<element name="pingResponse" type="tns:pingResponse"/>
<element name="setXxxxxxxx" type="tns:setXxxxxxxx"/>
<element name="setXxxxxxxxResponse" type="tns:setXxxxxxxxResponse"/></schema></types>
<message name="SystemServiceEndpoint_getXxxxxxxxx">
<part name="parameters" element="ns2:getXxxxxxxxx"/></message>
<message name="SystemServiceEndpoint_getXxxxxxxxxResponse">
<part name="result" element="ns2:getXxxxxxxxxResponse"/></message>
<message name="SystemServiceEndpoint_ping">
<part name="parameters" element="ns2:ping"/></message>
<message name="SystemServiceEndpoint_pingResponse">
<part name="result" element="ns2:pingResponse"/></message>
<message name="SystemServiceEndpoint_setXxxxxxxx">
<part name="parameters" element="ns2:setXxxxxxxx"/></message>
<message name="SystemServiceEndpoint_setXxxxxxxxResponse">
<part name="result" element="ns2:setXxxxxxxxResponse"/></message>
<portType name="SystemServiceEndpoint">
<operation name="getXxxxxxxxx">
<input message="tns:SystemServiceEndpoint_getXxxxxxxxx"/>
<output message="tns:SystemServiceEndpoint_getXxxxxxxxxResponse"/></operation>
<operation name="ping">
<input message="tns:SystemServiceEndpoint_ping"/>
<output message="tns:SystemServiceEndpoint_pingResponse"/></operation>
<operation name="setXxxxxxxx">
<input message="tns:SystemServiceEndpoint_setXxxxxxxx"/>
<output message="tns:SystemServiceEndpoint_setXxxxxxxxResponse"/></operation></portType>
<binding name="SystemServiceEndpointBinding" type="tns:SystemServiceEndpoint">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="getXxxxxxxxx">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation>
<operation name="ping">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation>
<operation name="setXxxxxxxx">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation></binding>
<service name="SystemService">
<port name="SystemServiceEndpointPort" binding="tns:SystemServiceEndpointBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
<b>jaxrpc-mapping-SystemService.xml</b>
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1" 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>dk.organisator.winnie.system.ejbsystem.services</package-type>
<namespaceURI>http://organisator.dk/winnie/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>dk.organisator.winnie.system.ejbsystem.services</package-type>
<namespaceURI>http://organisator.dk/winnie/wsdl</namespaceURI>
</package-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_ping_ResponseStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:pingResponse</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>result</java-variable-name>
<xml-element-name>result</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_getXxxxxxxxx_RequestStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:getXxxxxxxxx</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>String_1</java-variable-name>
<xml-element-name>String_1</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_setXxxxxxxx_ResponseStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:setXxxxxxxxResponse</root-type-qname>
<qname-scope>complexType</qname-scope>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_setXxxxxxxx_RequestStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:setXxxxxxxx</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>String_1</java-variable-name>
<xml-element-name>String_1</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_ping_RequestStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:ping</root-type-qname>
<qname-scope>complexType</qname-scope>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_getXxxxxxxxx_ResponseStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:getXxxxxxxxxResponse</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>result</java-variable-name>
<xml-element-name>result</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<service-interface-mapping>
<service-interface>dk.organisator.winnie.system.ejbsystem.services.SystemService</service-interface>
<wsdl-service-name xmlns:serviceNS="http://organisator.dk/winnie/wsdl">serviceNS:SystemService</wsdl-service-name>
<port-mapping>
<port-name>SystemServiceEndpointPort</port-name>
<java-port-name>SystemServiceEndpointPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint-interface>
<wsdl-port-type xmlns:portTypeNS="http://organisator.dk/winnie/wsdl">portTypeNS:SystemServiceEndpoint</wsdl-port-type>
<wsdl-binding xmlns:bindingNS="http://organisator.dk/winnie/wsdl">bindingNS:SystemServiceEndpointBinding</wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>getXxxxxxxxx</java-method-name>
<wsdl-operation>getXxxxxxxxx</wsdl-operation>
<wrapped-element/>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_getXxxxxxxxx</wsdl-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://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_getXxxxxxxxxResponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
<service-endpoint-method-mapping>
<java-method-name>ping</java-method-name>
<wsdl-operation>ping</wsdl-operation>
<wrapped-element/>
<wsdl-return-value-mapping>
<method-return-value>int</method-return-value>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_pingResponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
<service-endpoint-method-mapping>
<java-method-name>setXxxxxxxx</java-method-name>
<wsdl-operation>setXxxxxxxx</wsdl-operation>
<wrapped-element/>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_setXxxxxxxx</wsdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>

the problem is with the xmlns:wsdl="http://www.organisator.dk" line in your webservices.xml. It does not match the namespace of the corresponding PortType in your wsdl: targetNamespace="http://organisator.dk/winnie/wsdl"

Modify service endpoint in webservices.xml throws class not found for link

Hello, we had a problem for serveral days and have not found any solutions googling. We read the documentation and seems ok, so we are a little desesperate.
We have a WebService project in Oracle Eclipse included in Weblogic 10.3.5 with the following classes:
- An EJB (org.test.TestWSImpl) with the @WebService annotation:
@WebService(serviceName = "TestService", portName = "testService", targetNamespace = "testNameSpace",
endpointInterface = "test.TestWS", wsdlLocation = "/wsdls/test.wsdl")
- When deploying the ear all runs ok. Now, for serveral business reasons, we need to change the defalut service URI so we added a webservices.xml and weblogic-webservices.xml.
The webservices.xml:
<?xml version='1.0' encoding='UTF-8'?>
<webservices xmlns="http://java.sun.com/xml/ns/javaee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2">
     <webservice-description>
          <webservice-description-name>TestService</webservice-description-name>
          <port-component>
               <port-component-name>testService</port-component-name>
               <wsdl-port xmlns:tns="testNameSpace">tns:testDataService</wsdl-port>
               <service-endpoint-interface>test.TestWS</service-endpoint-interface>
               <service-impl-bean>
                    <ejb-link>TestWSImpl</ejb-link>
               </service-impl-bean>
          </port-component>
     </webservice-description>
</webservices>
In the weblogic-webservices.xml we define the new endpoint:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices
xmlns="http://xmlns.oracle.com/weblogic/weblogic-webservices"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-webservices http://xmlns.oracle.com/weblogic/weblogic-webservices/1.1/weblogic-webservices.xsd">
<webservice-description>
<webservice-description-name>IE3SEnvironmentalMasterDataService</webservice-description-name>
<webservice-type>JAXWS</webservice-type>
<port-component>
<port-component-name>e3sEnvironmentalMasterDataService</port-component-name>
<service-endpoint-address>
<webservice-contextpath>/E3S</webservice-contextpath>
<webservice-serviceuri>/e3sEnvironmentalMasterDataService</webservice-serviceuri>
</service-endpoint-address>
</port-component>
</webservice-description>
We apreciate any help
Thanks in advance!
Edited by: 960518 on 21/09/2012 02:42
Sorry for the copy; a browser error. Please delete this thread

We have found a solution removing the eclipse webservice project and adding the EJB inside the EJB project module.
greetings.

Hypervisor: Create Standalone Real-Time Application (Error at deploying: File not found)

Hello,
I am using Hypservisor. With "Build Specifications" in the project explore I want to create a standalone real-time application.
In my first try I only want to print some texts onto the real-time console (HyperTerminal) using the function "RT Debug String.vi". I built the real-time application successfully and got the rtexe-file locally on the windows system. But as I tried to deploy the application to the target system, I got the error: "File not found". Please check the attached file "error.txt" for details.
I don't understand which file is not found. Or I used "\" as path separators. Is it wrong? I'd appreciate if you'd have any idea of the problem. Thank you very much.
Regards,
Scarletice
Solved!
Go to Solution.
Attachments:
ERROR.txt ‏1 KB
builds.zip ‏153 KB

Hello Casey,
Thank you very much for your reply and your interest in our project. We are using Real-Time Hypervisor for the setup of our test stand. We use the Windows system to show the GUI and the Real-Time system for the real-time machine control and online data storage. We use shared variables and shared memory for the data exchange between the two systems.
The system works generally quite fine now. But we still have to face new problems at each step forwards. I'm sure, I'll have more questions. I'd appreciate your advices. Thanks sincerely.
Best regards,
Scarletice

Cannot deploy a EJB 3.0 Session bean to the OAS 10.1.3.4

Hi All,
I am unable to deploy a EJB 3.0 Session bean with no deployment descriptors to OAS 10.1.3.4 App server.This Session bean is also exposed as a web service using annotations. I am able to deploy this bean to a standalone oc4j 10.1.3.x containers and test it successfully.
i have written a simple stateless session bean ( exposed as webservice) and every bean is having issues with deployment having the same exception stated below
Can some one please help as i need to deploy this urgently.
below is the session bean code:
import javax.ejb.Stateless;
@Stateless(name="SiebelQuoteEJB")
public class SiebelQuoteEJBBean implements SiebelQuoteEJBLocal,
SiebelQuoteEJBWebService {
public SiebelQuoteEJBBean() {
public String publishMessage(String message,String type) throws java.rmi.RemoteException {
client.publishMessage(message,type);
return "SUCCESS";
Below is the error while deploying:
11/01/06 15:03:49 WARNING: Application.setConfig Application: javasso is in failed state as initialization failed.
java.lang.NullPointerException
11/01/06 15:03:50 WARNING: Application.setConfig Application: SiebelQuoteEJB is in failed state as initialization failed.
java.lang.InstantiationException: Error initializing ejb-modules: null Error parsing application-server config file: null
11/01/06 15:03:50 java.lang.NullPointerException
at com.evermind.server.ObjectReferenceCleaner.cleanupApplicationLogLevels(ObjectReferenceCleaner.java:166)
at com.evermind.server.ObjectReferenceCleaner.loaderDestroyed(ObjectReferenceCleaner.java:88)
at oracle.classloader.EventDispatcher.loaderDestroyed(EventDispatcher.java:248)
at oracle.classloader.PolicyClassLoader.close(PolicyClassLoader.java:1113)
at oracle.classloader.PolicyClassLoader.close(PolicyClassLoader.java:1041)
at com.evermind.server.ApplicationStateRunning.destroyClassLoaders(ApplicationStateRunning.java:1171)
at com.evermind.server.Application.stateCleanUp(Application.java:3635)
at com.evermind.server.Application.setConfig(Application.java:506)
at com.evermind.server.Application.setConfig(Application.java:355)
at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1895)
at com.evermind.server.ApplicationServer.initializeDeployedApplications(ApplicationServer.java:1651)
at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1034)
at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
at java.lang.Thread.run(Thread.java:736)

which jdk version? Had this with 1.6 and had to install an up-to-date jdbc.

No longer able to build ejb using appc (WLS 8.1)

I'm in the process of re-writing some build files to make use of the new
appc compiler, but I started to get a rather confusing error. Although
the EJB builds (using ejbc) and deploys fine on WLS 7, when I try to
build using appc I get a slew of messages such as "In EJB MyEJB, the
bean class must implement directly or indirectly the
javax.ejb.SessionBean interface" (which it does), or "In EJB MyEJB,
method remove() defined in the local interface either does not exist in
the bean class, or it is not a public method in the bean class". A
portion of the error message is listed below. I'm sure it must be some
kind of problem with my configuration...has anyone seen this before?
Any suggestions?
Thanks in advance,
Tim
weblogic.utils.compiler.ToolFailureException: [J2EE:160121]Errors
encountered wh
ile compiling module 'D:\workspace\TRIPS\deployment\build':
In EJB VASKeyGeneratorEJB, the bean class must implement directly or
indirectly
the javax.ejb.SessionBean interface.
In EJB VASKeyGeneratorEJB, method remove() defined in the local
interface either
does not exist in the bean class, or it is not a public method. Each
method in
the local interface must have a corresponding public method in the bean
class.
In EJB VASKeyGeneratorEJB, method getEJBHome() defined in the local
interface ei
ther does not exist in the bean class, or it is not a public method.
Each method
in the local interface must have a corresponding public method in the
bean clas
s.
In EJB VASKeyGeneratorEJB, method getPrimaryKey() defined in the local
interface
either does not exist in the bean class, or it is not a public method.
Each met
hod in the local interface must have a corresponding public method in
the bean c
lass.
In EJB VASKeyGeneratorEJB, method getHandle() defined in the local
interface eit
her does not exist in the bean class, or it is not a public method. Each
method
in the local interface must have a corresponding public method in the
bean class
In EJB VASKeyGeneratorEJB, method isIdentical(javax.ejb.EJBObject)
defined in th
e local interface either does not exist in the bean class, or it is not
a public
method. Each method in the local interface must have a corresponding
public met
hod in the bean class.
In EJB VASKeyGeneratorEJB, method remove() defined in the local
interface either
does not exist in the bean class, or it is not a public method. Each
method in
the local interface must have a corresponding public method in the bean
class.
In EJB VASKeyGeneratorEJB, method getPrimaryKey() defined in the local
interface
either does not exist in the bean class, or it is not a public method.
Each met
hod in the local interface must have a corresponding public method in
the bean c
lass.
In EJB VASKeyGeneratorEJB, method isIdentical(javax.ejb.EJBLocalObject)
defined
in the local interface either does not exist in the bean class, or it is
not a p
ublic method. Each method in the local interface must have a
corresponding publi
c method in the bean class.
In EJB VASKeyGeneratorEJB, method getEJBLocalHome() defined in the local
interfa
ce either does not exist in the bean class, or it is not a public
method. Each m
ethod in the local interface must have a corresponding public method in
the bean
class.
- with nested exception:
In EJB VASKeyGeneratorEJB, the bean class must implement directly or
indirectly
the javax.ejb.SessionBean interface.
In EJB VASKeyGeneratorEJB, method remove() defined in the local
interface either
does not exist in the bean class, or it is not a public method. Each
method in
the local interface must have a corresponding public method in the bean
class.
In EJB VASKeyGeneratorEJB, method getEJBHome() defined in the local
interface ei
ther does not exist in the bean class, or it is not a public method.
Each method
in the local interface must have a corresponding public method in the
bean clas
s.
In EJB VASKeyGeneratorEJB, method getPrimaryKey() defined in the local
interface
either does not exist in the bean class, or it is not a public method.
Each met
hod in the local interface must have a corresponding public method in
the bean c
lass.
In EJB VASKeyGeneratorEJB, method getHandle() defined in the local
interface eit
her does not exist in the bean class, or it is not a public method. Each
method
in the local interface must have a corresponding public method in the
bean class
In EJB VASKeyGeneratorEJB, method isIdentical(javax.ejb.EJBObject)
defined in th
e local interface either does not exist in the bean class, or it is not
a public
method. Each method in the local interface must have a corresponding
public met
hod in the bean class.
In EJB VASKeyGeneratorEJB, method remove() defined in the local
interface either
does not exist in the bean class, or it is not a public method. Each
method in
the local interface must have a corresponding public method in the bean
class.
In EJB VASKeyGeneratorEJB, method getPrimaryKey() defined in the local
interface
either does not exist in the bean class, or it is not a public method.
Each met
hod in the local interface must have a corresponding public method in
the bean c
lass.
In EJB VASKeyGeneratorEJB, method isIdentical(javax.ejb.EJBLocalObject)
defined
in the local interface either does not exist in the bean class, or it is
not a p
ublic method. Each method in the local interface must have a
corresponding publi
c method in the bean class.
In EJB VASKeyGeneratorEJB, method getEJBLocalHome() defined in the local
interfa
ce either does not exist in the bean class, or it is not a public
method. Each m
ethod in the local interface must have a corresponding public method in
the bean
class.
at weblogic.appc.compileEJB(appc.java:714)
at weblogic.appc.compileInput(appc.java:446)
at weblogic.appc.runBody(appc.java:167)
at weblogic.utils.compiler.Tool.run(Tool.java:146)
at weblogic.utils.compiler.Tool.run(Tool.java:103)
at weblogic.appc.main(appc.java:961)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain
(CompilerTask.java:
275)
at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at org.apache.tools.ant.taskdefs.CallTarget.execute
(CallTarget.java:143)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at org.apache.tools.ant.taskdefs.CallTarget.execute
(CallTarget.java:143)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at org.apache.tools.ant.taskdefs.CallTarget.execute
(CallTarget.java:143)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.Project.executeTargets
(Project.java:1255)
at org.apache.tools.ant.Main.runBuild(Main.java:609)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
Total time: 11 seconds

Hello Tim,
Which version of WLS 8.1 are you using (beta or GA) ?
Also, make sure that you don't have any jar files from WLS 7 still on your classpath,
so that appc doesn't get confused. Also, how are you invoking appc?
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
Tim Perrigo <[email protected]> wrote:
I'm in the process of re-writing some build files to make use of the
new
appc compiler, but I started to get a rather confusing error. Although
the EJB builds (using ejbc) and deploys fine on WLS 7, when I try to
build using appc I get a slew of messages such as "In EJB MyEJB, the
bean class must implement directly or indirectly the
javax.ejb.SessionBean interface" (which it does), or "In EJB MyEJB,
method remove() defined in the local interface either does not exist
in
the bean class, or it is not a public method in the bean class". A
portion of the error message is listed below. I'm sure it must be some
kind of problem with my configuration...has anyone seen this before?
Any suggestions?
Thanks in advance,
Tim
weblogic.utils.compiler.ToolFailureException: [J2EE:160121]Errors
encountered wh
ile compiling module 'D:\workspace\TRIPS\deployment\build':
In EJB VASKeyGeneratorEJB, the bean class must implement directly or
indirectly
the javax.ejb.SessionBean interface.
In EJB VASKeyGeneratorEJB, method remove() defined in the local
interface either
does not exist in the bean class, or it is not a public method. Each
method in
the local interface must have a corresponding public method in the bean
class.
In EJB VASKeyGeneratorEJB, method getEJBHome() defined in the local
interface ei
ther does not exist in the bean class, or it is not a public method.
Each method
in the local interface must have a corresponding public method in the
bean clas
s.
In EJB VASKeyGeneratorEJB, method getPrimaryKey() defined in the local
interface
either does not exist in the bean class, or it is not a public method.
Each met
hod in the local interface must have a corresponding public method in
the bean c
lass.
In EJB VASKeyGeneratorEJB, method getHandle() defined in the local
interface eit
her does not exist in the bean class, or it is not a public method. Each
method
in the local interface must have a corresponding public method in the
bean class
In EJB VASKeyGeneratorEJB, method isIdentical(javax.ejb.EJBObject)
defined in th
e local interface either does not exist in the bean class, or it is not
a public
method. Each method in the local interface must have a corresponding
public met
hod in the bean class.
In EJB VASKeyGeneratorEJB, method remove() defined in the local
interface either
does not exist in the bean class, or it is not a public method. Each
method in
the local interface must have a corresponding public method in the bean
class.
In EJB VASKeyGeneratorEJB, method getPrimaryKey() defined in the local
interface
either does not exist in the bean class, or it is not a public method.
Each met
hod in the local interface must have a corresponding public method in
the bean c
lass.
In EJB VASKeyGeneratorEJB, method isIdentical(javax.ejb.EJBLocalObject)
defined
in the local interface either does not exist in the bean class, or it
is
not a p
ublic method. Each method in the local interface must have a
corresponding publi
c method in the bean class.
In EJB VASKeyGeneratorEJB, method getEJBLocalHome() defined in the local
interfa
ce either does not exist in the bean class, or it is not a public
method. Each m
ethod in the local interface must have a corresponding public method
in
the bean
class.
- with nested exception:
In EJB VASKeyGeneratorEJB, the bean class must implement directly or
indirectly
the javax.ejb.SessionBean interface.
In EJB VASKeyGeneratorEJB, method remove() defined in the local
interface either
does not exist in the bean class, or it is not a public method. Each
method in
the local interface must have a corresponding public method in the bean
class.
In EJB VASKeyGeneratorEJB, method getEJBHome() defined in the local
interface ei
ther does not exist in the bean class, or it is not a public method.
Each method
in the local interface must have a corresponding public method in the
bean clas
s.
In EJB VASKeyGeneratorEJB, method getPrimaryKey() defined in the local
interface
either does not exist in the bean class, or it is not a public method.
Each met
hod in the local interface must have a corresponding public method in
the bean c
lass.
In EJB VASKeyGeneratorEJB, method getHandle() defined in the local
interface eit
her does not exist in the bean class, or it is not a public method. Each
method
in the local interface must have a corresponding public method in the
bean class
In EJB VASKeyGeneratorEJB, method isIdentical(javax.ejb.EJBObject)
defined in th
e local interface either does not exist in the bean class, or it is not
a public
method. Each method in the local interface must have a corresponding
public met
hod in the bean class.
In EJB VASKeyGeneratorEJB, method remove() defined in the local
interface either
does not exist in the bean class, or it is not a public method. Each
method in
the local interface must have a corresponding public method in the bean
class.
In EJB VASKeyGeneratorEJB, method getPrimaryKey() defined in the local
interface
either does not exist in the bean class, or it is not a public method.
Each met
hod in the local interface must have a corresponding public method in
the bean c
lass.
In EJB VASKeyGeneratorEJB, method isIdentical(javax.ejb.EJBLocalObject)
defined
in the local interface either does not exist in the bean class, or it
is
not a p
ublic method. Each method in the local interface must have a
corresponding publi
c method in the bean class.
In EJB VASKeyGeneratorEJB, method getEJBLocalHome() defined in the local
interfa
ce either does not exist in the bean class, or it is not a public
method. Each m
ethod in the local interface must have a corresponding public method
in
the bean
class.
at weblogic.appc.compileEJB(appc.java:714)
at weblogic.appc.compileInput(appc.java:446)
at weblogic.appc.runBody(appc.java:167)
at weblogic.utils.compiler.Tool.run(Tool.java:146)
at weblogic.utils.compiler.Tool.run(Tool.java:103)
at weblogic.appc.main(appc.java:961)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain
(CompilerTask.java:
275)
at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at org.apache.tools.ant.taskdefs.CallTarget.execute
(CallTarget.java:143)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at org.apache.tools.ant.taskdefs.CallTarget.execute
(CallTarget.java:143)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at org.apache.tools.ant.taskdefs.CallTarget.execute
(CallTarget.java:143)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.Project.executeTargets
(Project.java:1255)
at org.apache.tools.ant.Main.runBuild(Main.java:609)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
Total time: 11 seconds

Steps to deploy an ejb application and running an ejb client in weblogic server6.1

steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
if the client is an simple java application and if the client is a servlet

Hi.
Check out the beanManaged example that ships with WLS and read the accompanying docs. This
is a simple EJB with a servlet that invokes it.
Michael
shekhar sachdev wrote:
steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
if the client is an simple java application and if the client is a servlet--
Michael Young
Developer Relations Engineer
BEA Support

Deployed PAR file webservices are not displayed in SOAP admin

Hi,
we were facing the problem with customized PAR file deployment and
associated webservices.We have deployed the the PAR file on two
different versions of EP as given below.
EP6.0(WAS620)-SP2(J2EE and Portal versions are identical)
EP6.0(WAS640)-SP13(J2EE and Portal versions are identical)
The problem was the webservices has been shown in the case of
EP6.0(WAS620)-SP2 under SOAP Administration and not shown in case
of EP6.0(WAS640)-SP13.Is there any specific version made PAR files are
required for each of above portal versions or any other way to
check the webservcies in EP6.0(SP13).
Kindly help us to resolve this issue.

Hi Swetha ,
in Bypass scenario if you are fetching a flat file from source to target some time you are not able to view the file in payload .However it does not make any difference as you are simply tunnling the file not doing any transformation with it .
If it is a flat file in sender CC just make 1 .file type as bin or 2 . file type as text and encoding as UTF-8 and then check you can view the file content or not .check with both bin and text ( one by one ) .might be you will able to view payload in MONI with any one of that setting in sender CC .
Regards,
Saurabh

Error initializing ejb-module; Exception javac.exe not found under

Dear all,
I got followings error after i had tried to doing some lab.I had checked the folder "C:\Program Files\Oracle\jre\1.3.1" exists but missed but missing javac.exe. Could anyone can advice me what is going wrong?
04/04/14 16:44:20 Auto-deploying - web/WEB-INF/classes (No previous deployment found)...
04/04/14 16:44:20 Error instantiating application 'lab04' at file:/C:/share/oc4j
/labs/lab04/: Error initializing ejb-module; Exception javac.exe not found under
C:\Program Files\Oracle\jre\1.3.1, please use a valid jdk or specify the locati
on of your java compiler in server.xml using the <java-compiler .../> tag
Thanks in advance!
Best Regards,
Chris CHIU

Dear Chris,
The answer lies in the error message you got, namely:
please use a valid jdkAccording to your post, you don't have a JDK, you only have a JRE. The javac compiler is part of the JDK, it is not part of the JRE.
You can download the JDK from the J2SE Download Web page. Look for the Download J2SE SDK link -- do not choose the Download J2SE JRE link!
Good Luck,
Avi.

WL8.1 crashed during deployment of EJB from ear file

Hello,
WL8.1 crashed during deployment of EJB from ear file on SunOs 5.8:
error: Invalid class file format in /export/home/bea/j2sdk1.4.1_03/jre/lib/rt.jar(java/lang/AssertionError.class).
The major.minor version '48.0' is too recent for this tool to understand.
/export/home/mydomain/./ep1/.wlnotdelete/EJBCompilerCache/1xd25ws3hwp86/mydomain/facade/payroll/PayrollFL_vww01c_HomeImpl.java:83:
Class java.lang.AssertionError not found.
throw new AssertionError("Unable to find expected "+
Thanks,
Oleg.

Thank you Mark,
It works now.
Oleg.
"Mark Griffith" <[email protected]> wrote:
I don't think though that _03 is the problem, you should have compatability
between minor versions of a VM release. How did you deploy the ear?
Did
you copy over from a 7.0 domain? It looks like the EJB was built on
a
previous version of WLS, or has not had "ejbc" run on it prior to
deployment. Try running weblogic.appc foo.ear or fooExplodedEar. And
then
try redeploying. To be sure everything is clean rm -rf .wldonotdelete
after
you shut the server down.
cheers
mbg
"Oleg" <[email protected]> wrote in message
news:3ef54653$[email protected]..
Hello,
WL8.1 crashed during deployment of EJB from ear file on SunOs 5.8:
error: Invalid class file format in/export/home/bea/j2sdk1.4.1_03/jre/lib/rt.jar(java/lang/AssertionError.class
The major.minor version '48.0' is too recent for this tool to understand.
/export/home/mydomain/./ep1/.wlnotdelete/EJBCompilerCache/1xd25ws3hwp86/mydo
main/facade/payroll/PayrollFL_vww01c_HomeImpl.java:83:
Class java.lang.AssertionError not found.
throw new AssertionError("Unable to find expected "+
Thanks,
Oleg.

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

Similar Messages

Maybe you are looking for