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

Similar Messages

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

  • How to test Siebel webservice in Jdeveloper that uses Authentication?

    Hi..
    I am testing siebel webservice in Jdeveloper 11.1.1.5 by right clicking on WSDL n using "Test webService".But it is giving 500:internal server error..I tried everything..basically i have to pass username password in authentication.I have tried "Authorization-basic" and also tried vis "SOAP Headers > :WS-Security:Header" but of no use.I also tried the above mentioned way.."security-role-assignment" in web.xml and weblogic.xml but that is also not working.The webservice is working fine on SOAPUI but not wroking on Jdeveloper.Is there anything that Iam missing in configuration part...or in HTTP analyzer?? Please help.
    Thanks!

    In transaction SICF  you could enter a (system) user for your webservices so that you won't require authentication. (However, you should check if this is a good and valid option in the context of your application.)
    In addition, you can provide your SAP credentials (username, password) within Adobe Flex itself. Read more about the "URLRequestHeader" function.

  • How to open Crytal report deployed in Business Objects 3.1 CMC using C# cod

    WE designed the report using Crystal report 2008 and then deployed the reports in Business Objects 3.1
    The deployment server has below details
    BO:   BO 3.1 no fix packs
    OS:   AIX 5.3
    WebSphere: 6.1.0.25
    Now we have an Intraday website devveloped with ASP.net 3.5 hosted on a Windows 2003 server. the backend is SQL server 2005. I need  sample C# code  that can be used to open the crystal report deployment in Business Object 3.1 UNIX server as mentioned above.
    Any assistance is highly appreciated.
    P:S I didn't find any documentation/sample in this website.
    Regards,
    Ashok

    The developer library documentation can be found at:
    http://www.sdn.sap.com/irj/boc/sdklibrary
    Look for "Business Objects Enterprise .NET SDK - Developer Guide and API references" links.
    There are tutorials and code snippets in developer guide.
    The samples can be found at:
    http://www.sdn.sap.com/irj/boc/index?rid=/webcontent/uuid/706de3ab-8186-2b10-15aa-e4c5e73283f1 [original link is broken]

  • Does Firefox support sites that use captcha codes? Captcha's come blank for me.

    Several sites that I use require the use of "Captchas", coded words that prove you are a human and not a computer answering a question. I am unable to take advantage of these sites, or offers, because it seems that Firefox does not allow the use of Captcha's, or at least I have not found out how to enable it yet. A good example is that the SF Giants use Captcha's in special circumstances and when that happens, I am unable to participate in whatever is offered and lose out. I am hopeful that someone out there can help me solve this issue. Thank you.

    Start Firefox in [[Safe Mode]] to check if one of the add-ons is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
    * Don't make any changes on the Safe mode start window.
    See:
    * [[Troubleshooting extensions and themes]]
    * http://kb.mozillazine.org/Images_or_animations_do_not_load

  • Error while deploying application that uses  adobe forms

    Hi ,
    When i deploy an a web dynpro application that uses web dynpro I receive the following error .Please assist
    java.net.UnknownHostException: pwdf3102
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:153)
    at java.net.Socket.connect(Socket.java:452)
    at java.net.Socket.connect(Socket.java:402)
    at java.net.Socket.<init>(Socket.java:309)
    at java.net.Socket.<init>(Socket.java:124)

    Hi Amit
    As per Subject of ur post u told ur using Adobe forms in ur Web Dynpro Application so Hope u insured that Ur WAS is 7.0 ie  2004s or if its 6.4 then u have got Adobe document services deployed on Was and some configuration required are done on WAS  else your Application wont run and also u must make sure that u do not forget to set PdfSource property of Adobe forms set to BINARY context element before u deploy ur application
    Regards
    ASIF

  • How to notify a Notification Wait activity using PAPI

    I am trying to use Papi code to release an instance waiting in the notification wait activity of a process deployed in the enterprise server .... for this I am running the papi code from main method of a java class running in eclipse using the notify.send(........) method ........but when the code hits the notify.send(.......) method it is giving the following error :
    Exception in thread "main" java.lang.IllegalStateException: The component must be invoked on a server-side method.
         at fuego.components.ProcessInstance.getCurrent(ProcessInstance.java:590)
         at fuego.components.Notification.send(Notification.java:229)
         at PapiCode.main(PapiCode.java:61
    Can someone point out the error and how to resolve it ??

    Hi,
    I am a little confused with the package name of the classes and components you are invoking. If you are using the Client API PAPI, then the package name should be fuego.papi.*.
    I think you are using the internal components that should be used within a process implementation that assume running in the context of the Engine instead of a pure client application.
    Unless I am interpreting this incorrectly, you should use a client Java Application using PAPI to connect to a deployed process into an OBPM Engine.
    I would recommend you take a look at the very good introduction document that talks about PAPI, explains how to compile a program and also talks about how to write your first PAPI program client. It will also outline all the needed jar files need to include from a client application perspective. The link is: http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/papi/index.html.
    You may alternatively like to check the main Oracle BPM 10gR3 Documentation page through this link: http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/index.html
    HTH,
    eduardoc.

  • ADFBindingFilter error while deploying a war to WLS server using jdev 12c

    I've a OSB Server setup using XBUS_MAIN_GENERIC_120131.1402.S which is using JDEVADF_MAIN_GENERIC_120102.0032.6211.
    Launched the 12c Jdev and created a simple adfc web application with a test.jspx page and deployed in the OSB Server. The web app deployed and could launch the test page.
    I have added the page definition for that test page by 'Go to Page Definition' option.
    Now, If I try to deploy this web app war to the OSB Server, I'm getting the following exception in the jdev (Error1) and in the server log I could see the error (Error2).
    Any Idea how to resolve this issue?
    Error1 ( on Jdev )
    [03:15:08 AM] ---- Deployment started. ----
    [03:15:08 AM] Target platform is (Weblogic 10.3).
    [03:15:09 AM] Retrieving existing application information
    [03:15:09 AM] Running dependency analysis...
    [03:15:09 AM] Building...
    [03:15:15 AM] Deploying profile...
    [03:15:16 AM] Wrote Web Application Module to /scratch/sansrini/OSB_DEV/OSBMgmtTestApp/OSBMgmtTaskflowsTestApp/deploy/newosb2.war
    [03:15:16 AM] Deploying Application...
    [03:15:18 AM] [Deployer:149193]Operation "deploy" on application "newosb2" has failed on "AdminServer".
    [03:15:18 AM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application newosb2 on AdminServer.: [HTTP:101371]There was a failure when processing annotations for application /scratch/sansrini/view_storage/sansrini_xbus2/xbus/build/MW_HOME/user_projects/domains/base_domain/servers/AdminServer/upload/newosb2/app/newosb2.war. Ensure that the annotations are valid. The error is oracle.adf.model.servlet.ADFBindingFilter.
    [03:15:18 AM] weblogic.application.ModuleException: [HTTP:101371]There was a failure when processing annotations for application /scratch/sansrini/view_storage/sansrini_xbus2/xbus/build/MW_HOME/user_projects/domains/base_domain/servers/AdminServer/upload/newosb2/app/newosb2.war. Ensure that the annotations are valid. The error is oracle.adf.model.servlet.ADFBindingFilter
    [03:15:18 AM] Deployment cancelled.
    [03:15:18 AM] ---- Deployment incomplete ----.
    [03:15:18 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    Error2 ( on wls log )
    <Feb 3, 2012 3:15:18 AM PST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: [HTTP:101371]There was a failure when processing annotations for application /scratch/sansrini/view_storage/sansrini_xbus2/xbus/build/MW_HOME/user_projects/domains/base_domain/servers/AdminServer/upload/newosb2/app/newosb2.war. Ensure that the annotations are valid. The error is oracle.adf.model.servlet.ADFBindingFilter
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:732)
    at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
    at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:93)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
    at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:172)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.adf.model.servlet.ADFBindingFilter
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
    Truncated. see log file for complete stacktrace

    I guess you should be asking on an internal forum somewhere, because we, the unwashed masses, don't have access to JDev 12c.
    John

  • 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 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"

  • [svn] 1590: Updating WebService RPC tests that previously used external endpoints at whitemesa . net to now use internal endpoints accessed through Tomcat server on localhost :8400/qa-regress/axis/services/{SERVICE_NAME}?wsdl

    Revision: 1590
    Author: [email protected]
    Date: 2008-05-07 08:49:22 -0700 (Wed, 07 May 2008)
    Log Message:
    Updating WebService RPC tests that previously used external endpoints at whitemesa.net to now use internal endpoints accessed through Tomcat server on localhost:8400/qa-regress/axis/services/{SERVICE_NAME}?wsdl
    Endpoints built from Axis SOAPBuilder tests in Perforce's /depot/axis/xml-axis/java/tests/
    Modified Paths:
    blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/server-config.wsdd
    blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/web.xml
    blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/flexunit/src/tests/flexunit/wscl/int erop/SOAPBuilderRound3Import1_WhiteMesaTest.as
    blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/flexunit/src/tests/flexunit/wscl/int erop/SOAPBuilderRound3Import3_WhiteMesaTest.as
    blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/flexunit/src/tests/flexunit/wscl/int erop/SOAPBuilderRound3RPCEncoded.as
    Added Paths:
    blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/lib/
    blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/lib/javax_mail.jar
    blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/lib/qa-services-wm.jar
    blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/flexunit/src/tests/flexunit/wscl/int erop/SOAPBuilderRound3Compound1.as

  • Failure When Deploying EJB Project That Uses Library Onto Glassfish

    <font size=4>Hi,
    I have a multi project application that I am developing and I am having issues testing it. I have set up a EAR, WAR, EJB, and two library JARs. The EJB contains classes that use components from the library JARs or implement abstract classes from the library JARs. I have added the library JARs to the compile-time libraries of the EJB. I then also added the library JARs to the libraries of the EAR. However when I then go to deploy the EAR onto the Glassfish server I get this error, displayed in the Glassfish log:</font><br>
    <font size=2><font color="red">WARNING: Error in annotation processing: java.lang.NoClassDefFoundError: com/foo/sdk/core/AbstractClass</font><br>
    <font color="red">WARNING: Error in annotation processing: java.lang.NoClassDefFoundError: com/foo/sdk/core/AbstractClass</font><br>
    <font color="red">WARNING: Error in annotation processing: java.lang.NoClassDefFoundError: com/foo/sdk/core/AbstractClass</font><br>
    <font color="red">WARNING: Error in annotation processing: java.lang.NoClassDefFoundError: com/foo/sdk/core/AbstractClas</font><br>
    <font color="red">SEVERE: Class [ com/foo/sdk/core/InterfaceClass ] not found. Error while loading [ class com.foo2.BeanFooClass ]</font><br>
    <font color="red">SEVERE: Exception while deploying the app [FooEAR]</font><br>
    <font color="red">SEVERE: Invalid ejb jar [BeanFoo.jar]: it contains zero ejb. </font><br>
    Note:
    1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean.
    2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
    3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), please check server.log to see whether the annotations were processed properly.
    java.lang.IllegalArgumentException: Invalid ejb jar [BeanFoo.jar]: it contains zero ejb.
    Note:
    1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean.
    2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
    3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), please check server.log to see whether the annotations were processed properly.
         at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:76)
         at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:128)
         at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:730)
         at com.sun.enterprise.deployment.Application.visit(Application.java:1768)
         at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:799)
         at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openWith(ApplicationArchivist.java:277)
         at com.sun.enterprise.deployment.archivist.ApplicationFactory.openWith(ApplicationFactory.java:240)
         at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:170)
         at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:93)
         at com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:826)
         at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:768)
         at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:368)
         at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
         at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:370)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1067)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1247)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
         at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:465)
         at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:222)
         at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
         at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
         at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234)
         at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
         at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
         at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
         at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
         at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
         at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
         at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
         at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
         at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
         at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
         at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
         at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
         at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
         at java.lang.Thread.run(Thread.java:679)
    <font color="red">SEVERE: Exception while deploying the app [FooEAR] : Invalid ejb jar [FooBean.jar]: it contains zero ejb. </font><br>
    Note:
    1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean.
    2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
    3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), please check server.log to see whether the annotations were processed properly.</font><br>
    <font size=4>I am using these technologies:
    NetBeans IDE 7.0 for Java EE
    Glassfish 3.1
    I did read that putting the libraries in this directory: <glassfish_home>/domains/domain1/lib may resolve the problem, however there must be a better way.
    Any help would be greatly appreciated!</font>
    Edited by: 866180 on Jun 15, 2011 2:32 PM

    First of all, use a normal font when posting a question. This is just terrible to read.
    You have multiple failures here. Did you actually read and try to understand the error?
    java.lang.NoClassDefFoundError: com/foo/sdk/core/AbstractClassJava is not going to lie, this class is not on the classpath of the application. Either the jar is missing, the class is missing from the jar or you put the jar in the wrong place. Open up the ear using your favorite zip tool and check out its structure. What is the path to the jar inside it?
    Also, open up the META-INF/manifest.mf file inside the EJB jar. Is there a class-path line in there? There shouldn't be!
    A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean. Apparently your EJB jar contains not a single EJB or MDB class. Did you forget some annotations perhaps?
    Seems to me that your application compiles, but other than that it is very much broken.

  • Deploying an app that uses freeTTS

    I'll get the hang of this soon :-)
    I'm trying to deploy an application that uses the FreeTTS Text to speech. I'm using Netbeans IDE. The program runs fine locally, but when I run it via Web Start, it closes with an exception at the point it initialises the FreeTTS, so I guess I'm missing a .jar in the deployment?
    I've included 5 .jar files that were included with the FreeTTS download, (and these match the ones I have added to the list of libraries in Netbeans).. the important bits of the exception are:
    myapp.Main.StartVoice(Main.java:83) <<- this is my function that initialises
    myapp.Main.main(Main.java:45)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    java.lang.reflect.Method.invoke(Unknown Source)
    com.sun.javaws.Launcher.executeApplication(Unknown Source)
    com.sun.javaws.Launcher.executeMainClass(Unknown Source)
    com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
    com.sun.javaws.Launcher.run(Unknown Source)
    java.lang.Thread.run(Unknown Source)
    So, I guess the first question would be what .jar files do I need to include for a simple program that uses the Kevin16 voice to say "hello", and is the above exception telling me It is missing a .jar file?
    Thanks in advance for any help.
    Message was edited by:
    Forgeuk

    After a couple of days of 'dicking around' with WebStart, I finally stumbled on an answer.
    So, here it is for anyone else getting stuck on distributing a freeTTS application via webstart, it doesn't seem to mention this in any of the FAQs very clearly, it mentions something similar for the webstart clock app.
    I was simply missing a line in the JNLP file:
    <property name="freetts.voices" value="com.sun.speech.freetts.en.us.cmu_us_kal.KevinVoiceDirectory"/>
    Not entire sure what it does, but it now works!

  • How to deploy a J2ME app in actual device that uses RMS?

    Hi,
    Apologies if the post is in the wrong place.
    I have a MIDlet suite that uses RMS. The application would use certain data that comes from those .db files. The cliche is that the data should pre-exist in a .db file (I enter the data in the .db file through a separate MIDlet and close the RecordStore) prior to running the application for the first time in the device. Now I cannot understand how should I ship the .db file along with the .jar. Should I bundle it with the jar? And is there any device specific implementations?
    Thanks in advance.
    Regards,
    Kalyan

    Thank you for your answer, I am now creating the record store within the startApp() of my MIDlet. would you please read the following article
    at
    http://www.javaworld.com/javaworld/jw-05-2005/jw-0502-midp_p.html
    Can you please explain which data files are they talking about?

  • How do you deploy an Event view to a cluster using the RDBMS 1.0 adapter in WLI7?

    Hi ,
    We are trying to deploy an application view representing a database event in a
    table to a cluster consisting of 2 WLI servers.
    When you get the deploy screen in the wlai console it prompts you for a url for
    the event Router.
    On a single instance of WLI this is simply http://localhost:7001/BEA_RDBMS_1_0_EventRouter/EventRouter
    but what should this be in the case when the adapter is deployed to a cluster
    of 2 machines??
    We have tried replacing localhost:7001 with the ip and ports of either of the
    two WLI servers as well as trying the admin server ip and port but always get
    the error show below.
    has anyone succesfully done this?
    any ideas greatly appreciated
    Adam
    com.bea.wlai.client.DeploymentException: ConnectionFactoryDeployer on cscw00336440:
    Failed to upload weblogic-ra.xml descriptor for connection factory OrderDetails_connectionFactory
    due to a communication problem with the Admin server; Unexpected exception in
    com.bea.wlai.admin.RARUploadSessionBean.upload(): java.net.ConnectException: Tried
    all: '1' addresses, but could not connect over HTTP to server: 'www.bea.com',
    port: '80' at weblogic.net.http.HttpClient.openServer(HttpClient.java:222) at
    weblogic.net.http.HttpClient.openServer(HttpClient.java:274) at weblogic.net.http.HttpClient.(HttpClient.java:126)
    at weblogic.net.http.HttpClient.New(HttpClient.java:168) at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:111)
    at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:281)
    at java.net.URL.openStream(URL.java:793) at weblogic.apache.xerces.readers.DefaultReaderFactory.createReader(DefaultReaderFactory.java:149)
    at

    Try downloading the DTD from BEA to your filesystem and change the XML
    so it points to it.
    Ricardo
    Adam Finlayson wrote:
    Hi Chris,
    Thanks for that bit of info. We have pinned the eventgenerator to just one managed
    server now but are still getting the same error when trying to deploy an event
    application view.
    The admin server appears to be trying to contact the bea website for some reason
    as part of the deployment.
    I am guessing this must be trying to access some DTD or something but this system
    sits behind a firewall so any http requests would need to go through a proxy.
    Any idea why it may be contacting www.bea.com or how to set up WLS to use a proxy
    server?
    Chris Stead <[email protected]> wrote:
    Hi Adam,
    Due to the nature of the the event generator Web application (WAR) URL,
    you have to pin the war file to a single server in your cluster. Here
    is some information about deploying adapters in a cluster:
    http://e-docs.bea.com/wli/docs70/deploy/cluster.htm#1454929
    I hope this helps with your deployment.
    Cheers,
    Chris
    Adam Finlayson wrote:
    Hi ,
    We are trying to deploy an application view representing a database
    event in a
    table to a cluster consisting of 2 WLI servers.
    When you get the deploy screen in the wlai console it prompts you for
    a url for
    the event Router.
    On a single instance of WLI this is simply http://localhost:7001/BEA_RDBMS_1_0_EventRouter/EventRouter
    but what should this be in the case when the adapter is deployed to
    a cluster
    of 2 machines??
    We have tried replacing localhost:7001 with the ip and ports of either
    of the
    two WLI servers as well as trying the admin server ip and port but
    always get
    the error show below.
    has anyone succesfully done this?
    any ideas greatly appreciated
    Adam
    com.bea.wlai.client.DeploymentException: ConnectionFactoryDeployer
    on cscw00336440:
    Failed to upload weblogic-ra.xml descriptor for connection factory
    OrderDetails_connectionFactory
    due to a communication problem with the Admin server; Unexpected exception
    in
    com.bea.wlai.admin.RARUploadSessionBean.upload(): java.net.ConnectException:
    Tried
    all: '1' addresses, but could not connect over HTTP to server: 'www.bea.com',
    port: '80' at weblogic.net.http.HttpClient.openServer(HttpClient.java:222)
    at
    weblogic.net.http.HttpClient.openServer(HttpClient.java:274) at weblogic.net.http.HttpClient.(HttpClient.java:126)
    at weblogic.net.http.HttpClient.New(HttpClient.java:168) at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:111)
    at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:281)
    at java.net.URL.openStream(URL.java:793) at weblogic.apache.xerces.readers.DefaultReaderFactory.createReader(DefaultReaderFactory.java:149)
    at

  • How to Invoke bpel process which is deployed in weblogic using java code

    Hi
    I want to invoke a BPEL Process which is deployed in Weblogic server using Java code. Please provide me the code snnipet which will be used to connect and then invoke a BPEL Process.

    The simple way would be creating a java client to consume the SOAP webservice interface exposed by the bpel process.
    If you have Oracle Service Registry you can also use UDDI to discover the endpoint at runtime.
    But you can also use direct binding to do that.
    If you search on internet you will find many blog entries about this as well as many related posts here on OTN.
    I can't suggest a specific one, but looking on Google this one seems quite ok: Managing Oracle SOA Environment [10g/11g]: Invoking SOA11g Composite Using Direct Binding Invocation API

Maybe you are looking for