Deployment of VisualAge EJBs into iAS

I want to deploy EJBs (1.1) developed using IBM VisualAge 3.5.3 into ORACLE iAS (the one you can download from ORACLE's web site at the moment). My experiences in a former project were that due some incompatibilites between IBM's and ORACLE's EJB specifications I had to use JDeveloper when I want to deploy EJBs into ORACLE software. Has anyone out there some experiences with the deployment of EJBs developed with VisualAge 3.5.3 into the newest ORACLE iAS, and can you give some tips on what to do (Stay away from deployment, or: you can do this or that to get around the tricky things etc etc) ???

We actually deployed moost of the samples from IBM websphere/VisualAge to OC4J. We also have customers who smoothly migrated from Websphere/VisualAge to OC4J.
However in some cases you need to change code if are using any custom features.
There are a few issues you need to consider while migrating EJB code developed on VAJ3.5.3 to OC4J:
1. Aceess Beans: If you code is using Visual ages/websphere specific access beans you need to copy ivjejb35.jar file to $OC4J_HOME\j2ee\home\lib directory
2. Client Code changes:
In the client applications if you are using IBM specific JNDI server and RMI over IIOP to look up EJBs you need change you code to use OC4J ORMI and OC4J JNDI contextFactory.
3. Changes to EJB code :
The main thing you have to keep in mind is VAJ3.5.3 is not fully EJB 1.1 compliant and it uses 'finderhelper' classes to define custom finder methods. Most of the cases OC4J generates these finder. In case if you have custom finders defined in finderhelper classes you can easily customzie the OC4J generated deployment descriptors: orion-ejb-jar.xml to define your custom finders.
4.Finally you need to generate ejb-jar.xml and ejb.jar files since WebSphere/Visual age only supports serialized deployment descriptors. You can use Jdeveloper or Ant tool to do that.
Otherwise it is fairly straight forward.If you still till have any specific migration issue you can contact me:[email protected]. Note: We are in the process of releasing websphere 3.5.3 migration guide soon, which will give a step by step migration path from websphere 3.5.x to OC4J.
thanks
V
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by hdcordes2:
I want to deploy EJBs (1.1) developed using IBM VisualAge 3.5.3 into ORACLE iAS (the one you can download from ORACLE's web site at the moment). My experiences in a former project were that due some incompatibilites between IBM's and ORACLE's EJB specifications I had to use JDeveloper when I want to deploy EJBs into ORACLE software. Has anyone out there some experiences with the deployment of EJBs developed with VisualAge 3.5.3 into the newest ORACLE iAS, and can you give some tips on what to do (Stay away from deployment, or: you can do this or that to get around the tricky things etc etc) ???<HR></BLOCKQUOTE>
null

Similar Messages

  • Deploy Websphere built ejb on 9ias (r2)

    Anyone had any experience of deploying WebSphere built EJB's to OC4J. The .xml files differ and I would like to know if there are any tools/utilities/experiences out there. The development environment is WASAD, the Server is Oracle9iAS release 2 (+patches) on Solaris (64bit).

    You deploy BC4J as EJB on iAS exactly the same as deploying it on database, same iiop connection,etc... You are really deploying BC4J as EJB to database 8.1.7, named databse cache.

  • Deployment wizard (OAS EJB)

    Why do I get
    There is nothing to process in jar file I:\\ows_4082\\ows\\upload\\691MyOASAppSource.jar.
    Compilation of idl interfaces for I:\\ows_4082\\ows\\upload\\691MyOASAppSource.jar failed!
    if I try to deploy my bc4j appmodule to an oas 4.0.8.2 as EJB?
    thx,
    Tib

    Hi
    edit the file svwww.cfg file in
    ORAWEB_HOME/admin/websitename/httpd_machinename/www.
    In the [Server] portion of parameters change the 'FileCaching'
    parameter to "OFF".
    regards
    raghu
    Albert (guest) wrote:
    : Trying to deploy an EJB into OAS 4.0.8.1 using
    : JD3 deployment wizard.
    : If the EJB already exists there, then an exception arises
    : in the wizard:
    : Creating client jar...
    : java.io.FileNotFoundException: E:\dev32\ows\4.0
    : \..\apps\ejb\MyAccount\_client.jar
    : at java.lang.Throwable.<init>(Compiled Code)
    : at java.io.FileNotFoundException.<init>(Compiled Code)
    : at java.io.FileOutputStream.<init>
    : (FileOutputStream.java:69)
    : at sun.tools.jar.Main.run(Main.java:76)
    : at sun.tools.jar.Main.main(Main.java:524)
    : at oracle.oas.tools.util.JarGenerator.createJar(Compiled
    : Code)
    : at oracle.oas.tools.util.CreateJars.main(Compiled Code)
    : Creation of client jar for E:\\dev32
    : \\ows\\upload\\194MyAccountSource.jar failed!
    : As I've found, the _client.jar is actually present there,
    : but it is locked by someone, so the wizard cannot overwrite it.
    : If I stop the OAS Node Manager, then the file is released.
    : After deleting the _client.jar and starting OAS Node Manager
    : again, the wizard works.
    : What Oracle has to comment on that ?
    null

  • Re-deploying replica aware EJBs

              How does one update an app server with a new EJB when the app server
              is running in a cluster? Doing a re-deploy on the EJB in a single instance
              can even be a problem. First, you can have beans that are cached and
              in use. locking the server and waiting until the last client has completed
              it's operation until you do the redeploy should work. With clustered SLSBs
              the replica aware stubs get distributed by JNDI so until all the servers
              in the cluster have the update the classes are out of sync.
              It seems like you have to bounce all the app servers in the cluster. Not
              a very amicable solution.
              

    In article <[email protected]>, [email protected] says...
              >
              > How does one update an app server with a new EJB when the app server
              > is running in a cluster? Doing a re-deploy on the EJB in a single instance
              > can even be a problem. First, you can have beans that are cached and
              > in use. locking the server and waiting until the last client has completed
              > it's operation until you do the redeploy should work. With clustered SLSBs
              > the replica aware stubs get distributed by JNDI so until all the servers
              > in the cluster have the update the classes are out of sync.
              >
              > It seems like you have to bounce all the app servers in the cluster. Not
              > a very amicable solution.
              >
              >
              >
              Mike,
              This is a toughy and something I've been trying to figure out for a
              while. Maybe together we'll devise a strategy so here's what I've come
              up with so far:
              Maintain a set of "upgrade servers" on another network line (using a
              switch). When upgrading, bring them online into the main cluster and
              then start kiling the main machines. When they're all dead, unplug them
              from the network and begin the upgrade. Test the upgrade after bringing
              the new main cluster back up. Once confirmed, start locking out
              transactions, etc from the backup cluster and have the web front end
              give a "down for X minutes message to all new requests". Once the
              backup app servers have no more requests, unplug them from the network
              and plug the new app servers in. Reopen the flood gates at the front
              end. You'll still lose some sessions, but this should be in a service
              level agreement and be understood by customers.
              Some variations, in case the switch isn't manageable and being
              physically there is not on option would be to bring various interfaces
              up and down to meet the needs described above.
              It's not perfect; uptime is still purposely limited, but these are thing
              that should be defined in any agreement you make with customers. Even
              NASDAQ goes down. I'm currently working on a strategy for WebLogic 6.0
              JT
              

  • Error in deploying a simple EJB 3.0

    Hi ,
    I am getting the following error while deploying my simple ejb of version 3.0 in Weblogic 9.2.
    Exception preparing module: EJBModule(build) [EJB:011023]An error occurred while reading the deployment descriptor. The error was: Error processing annotations: java.lang.NullPointerException.
    During my evaluation of Weblogic 9.2 for EJB 3.0 , I have got the following questions.
    EJB Specification states that EJB's in EJB 3.0 can be developed and deployed without the need of deployment descriptors. I have created a simple EJB with two file Env.java and EnvBean.java and the source code is given below.
    a) I just complied these class files and when I was trying to deploy without ejb-jar.xml and weblogic-ejb-jar.xml, the console was not at all allowing me to deploy.Why is this so?
    b) After I created a META-INF file under root of classes directory by placing ejb-jar.xml with empty <enterprise-beans> element, console was allowing me to deploy with errors in parsing ejb-jar.xml. The error was either session/entity/mdb is a required under <enterprise-beans> element. Why is this required when there are several examples stating <enterprise-beans> element can be empty.
    c) Later I updated ejb-jar.xml with <session> element under <enterprise-beans> with the following values. I got the above error when deployed with this change.
    I had been struggling to deploy this simple bean for almost a day.Pleas point me if there is any documentation that solves my stated problem or if there is a solution.Thanks in advance.
    regards
    Karim
    ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" version="3.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
    <enterprise-beans>
    <session>
    <description>This is the stateless ejb</description>
    <display-name>Env Bean</display-name>
    <ejb-name>EnvBean</ejb-name>
    </session>
    </enterprise-beans>
    </ejb-jar>
    Env.java
    package examples ;
    public interface Env {
    public void display();
    EnvBean.java
    package examples;
    import javax.ejb.Remote;
    import javax.ejb.Stateless;
    @Stateless
    @Remote(Env.class)
    public class EnvBean implements Env {
    public void display() {
    System.out.println("Welcome to EJB 3.0");
    }

    Presumably you're using the EJB3 tech preview, and not a vanilla WebLogic 9.2 install, right?
    Can you post the full stack trace?
    -Patrick

  • Error while deploying a JAR-File into 8i !

    Hello to all Oracle experts,
    At the attempt to deploy a Jar file into the 8i the following
    error message comes onto Shell level:
    initialization complete
    loading : com/sun/xml/tree/XmlDocumentBuilder
    ORA-01536: space quota exceeded for tablespace 'PROCON_DATA'
    Error while loading com/sun/xml/tree/XmlDocumentBuilder
    ORA-06502: PL/SQL: numeric or value error
    ORA-06512: at "SYS.DBMS_LOB", line 700
    ORA-06512: at "PROCON.LOADLOBS", line 1
    ORA-06512: at line 1
    creating : com/sun/xml/tree/XmlDocumentBuilder
    Error while creating class com/sun/xml/tree/XmlDocumentBuilder
    ORA-29509: incorrectly formed Java binary class definition
    The command was:
    loadjava -user procon/procon@t2srv1:1521:PROCON -thin -verbose -schema PROCON xml_un.jar
    It would please me if somebody has an idea to this error !
    null

    Hi Olivier,
    you could try the following approach:
    1. Package your JAR files as J2EE Engine libraries and deploy them on it as described here: <a href="http://help.sap.com/saphelp_nw04/helpdata/en/9f/2ade3fc6c6ec06e10000000a1550b0/frameset.htm">Working with J2EE Libraries</a>.
    2. Set reference to this library from the application that use them. Depending on your application, refer to the appropriate documentation:
    -- reference from a J2EE app -> see <a href="http://help.sap.com/saphelp_nw04/helpdata/en/15/d5d93fe80fed06e10000000a1550b0/frameset.htm">Referencing Libraries in Applications</a>
    -- reference from a portal app -> see <a href="http://help.sap.com/saphelp_nw04/helpdata/en/02/788540ae1dbb4de10000000a1550b0/frameset.htm">Referencing Elements</a>
    Hope that helps!

  • Problems deploying a simple EJB

    I am trying to deploy a simple EJB on the 8.1.5. The bean only owns a single method that needs a unique parameter.
    No problems with compilation of source bean, home and remote interfaces, whatever the type of this parameter is.
    But when I try to deploy the jar on the server, I only succeed if the parameter of my method is a simple type (int, String ...).
    If I try the same passing a complex type (here a oracle.xml.parser.v2.XMLDocument type), I encounter this message from the deployejb tool :
    Generating EJBHome and EJBObject on the server...
    Compilation errors in oracle/aurora/ejb/gen/test_myFluxInsert/EjbObject_FluxInsert:ORA-29535: source requires recompilationjava/lang/Object: Authorization error for referenced class Oracle/xml/parser/v2/XMLDocument.java/lang/Object: Authorization error for referenced class oracle/xml/parser/v2/XMLDocument.oracle/aurora/ejb/gen/test_myFluxInsert/EjbObject_FluxInsert:50: Class oracle.xml.parser.v2.XMLDocument not found in type declaration.
    public java.lang.String insereFlux (oracle.xml.parser.v2.XMLDocument arg0)
    ^ Info: 3 errors
    And if I use an int instead of the XMLDocument parameter, everithing's right.
    Can anybody submit a no-paranormal solution ?
    Thanks.
    GH

    Parameter passing in EJB must implement Serializable. One way to solve this is:
    1. Define a new class which implements
    Serializable.
    2. Place whatever you want to pass inside
    this class.
    3. Now use the new class as your parameter.
    eg.
    public class Params implements java.io.Serializable {
    String p1;
    XmlDocmuent xdoc;,
    etc, etc
    Your program now have to use the class Params for parameter passing.
    Hope this helps.
    Tam
    null

  • Error - In deploying the web services into axis

    Hello,
    I am working on deploying a webservices into axis. I have an deploy.wsdd file and I have an ant script (build.xml) for deploying that web service into axis (axis is in tomcat). After deploying I can see the services
    [http://localhost:8080/axis/servlet/AxisServlet] at this link. But when I run my web project which uses the deployed service, I am getting an InstatiationException as shown below.
    {color:#ff0000}SEVERE: Remote Connect Failure:
    AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
    faultSubcode:
    faultString: java.lang.InstantiationException: myexample.HelloWS
    faultActor:
    faultNode:
    faultDetail:
    {http://xml.apache.org/axis/}hostname:Personal
    java.lang.InstantiationException: myexample.HelloWS
    at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
    at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
    at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
    at org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1403)
    at org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator.java:1550)
    at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1149)
    at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
    at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
    at javax.xml.parsers.SAXParser.parse(Unknown Source)
    at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
    at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
    at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
    at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
    at org.apache.axis.client.Call.invoke(Call.java:2767)
    at org.apache.axis.client.Call.invoke(Call.java:2443)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)
    at mypackage.HelloImpl.getSiteMenu(RDMInterfaceWSSoapBindingStub.java:1589)
    at mypackage.HelloImpl.getSiteMenu(RDMWebserviceImpl.java:443)
    at mypackage.HelloImplServiceClient.getSiteMenu(RDMInterfaceWSServiceClient.java:123)
    at mypackage.ApplicationBean.init(ApplicationBean.java:98)
    at com.sun.rave.web.ui.appbase.servlet.LifecycleListener.attributeAdded(LifecycleListener.java:132)
    at org.apache.catalina.core.ApplicationContext.setAttribute(ApplicationContext.java:777)
    at org.apache.catalina.core.ApplicationContextFacade.setAttribute(ApplicationContextFacade.java:335)
    at com.sun.faces.context.ApplicationMap.put(ExternalContextImpl.java:496)
    at com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:287)
    at com.sun.faces.el.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:78)
    at com.sun.rave.web.ui.appbase.faces.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:96)
    at com.sun.faces.el.impl.NamedValue.evaluate(NamedValue.java:125)
    at com.sun.faces.el.impl.ComplexValue.evaluate(ComplexValue.java:146)
    at com.sun.faces.el.impl.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:243)
    at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:173)
    at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:154)
    at com.sun.rave.web.ui.component.SelectorBase.getItems(SelectorBase.java:114)
    at com.sun.rave.web.ui.component.ListSelector.getOptions(ListSelector.java:168)
    at com.sun.rave.web.ui.component.ListSelector.getListItems(ListSelector.java:113)
    at com.sun.rave.web.ui.renderer.ListRendererBase.renderList(ListRendererBase.java:363)
    at com.sun.rave.web.ui.renderer.ListRendererBase.renderListComponent(ListRendererBase.java:164)
    at com.sun.rave.web.ui.renderer.DropDownRenderer.encodeEnd(DropDownRenderer.java:73)
    at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:720)
    at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:443)
    at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:233)
    at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:701)
    at com.sun.rave.web.ui.util.RenderingUtilities.renderComponent(RenderingUtilities.java:80)
    at com.sun.rave.web.ui.renderer.AbstractRenderer.encodeChildren(AbstractRenderer.java:194)
    at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:701)
    at com.sun.rave.web.ui.util.RenderingUtilities.renderComponent(RenderingUtilities.java:80)
    at com.sun.rave.web.ui.renderer.AbstractRenderer.encodeChildren(AbstractRenderer.java:194)
    at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:701)
    at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:435)
    at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:233)
    at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:701)
    at javax.faces.webapp.UIComponentTag.encodeChildren(UIComponentTag.java:607)
    at javax.faces.webapp.UIComponentTag.doEndTag(UIComponentTag.java:544)
    at com.sun.faces.taglib.html_basic.PanelGridTag.doEndTag(PanelGridTag.java:460)
    at org.apache.jsp.Home_jsp._jspx_meth_h_005fpanelGrid_005f0(Home_jsp.java:541)
    at org.apache.jsp.Home_jsp._jspx_meth_ui_005fform_005f0(Home_jsp.java:368)
    at org.apache.jsp.Home_jsp._jspx_meth_ui_005fbody_005f0(Home_jsp.java:329)
    at org.apache.jsp.Home_jsp._jspx_meth_ui_005fhtml_005f0(Home_jsp.java:250)
    at org.apache.jsp.Home_jsp._jspx_meth_ui_005fpage_005f0(Home_jsp.java:223)
    at org.apache.jsp.Home_jsp._jspx_meth_f_005fview_005f0(Home_jsp.java:170)
    at org.apache.jsp.Home_jsp._jspService(Home_jsp.java:138)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
    at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
    at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
    at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
    at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
    at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
    at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:311)
    at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
    at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)
    at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at com.sun.rave.web.ui.util.UploadFilter.doFilter(UploadFilter.java:194)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Unknown Source){color}
    Please help me how to resolve this problem.
    Thx
    Chaitanya

    Hello,
    I am working on deploying a webservices into axis. I have an deploy.wsdd file and I have an ant script (build.xml) for deploying that web service into axis (axis is in tomcat). After deploying I can see the services
    [http://localhost:8080/axis/servlet/AxisServlet] at this link. But when I run my web project which uses the deployed service, I am getting an InstatiationException as shown below.
    {color:#ff0000}SEVERE: Remote Connect Failure:
    AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
    faultSubcode:
    faultString: java.lang.InstantiationException: myexample.HelloWS
    faultActor:
    faultNode:
    faultDetail:
    {http://xml.apache.org/axis/}hostname:Personal
    java.lang.InstantiationException: myexample.HelloWS
    at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
    at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
    at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
    at org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1403)
    at org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator.java:1550)
    at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1149)
    at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
    at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
    at javax.xml.parsers.SAXParser.parse(Unknown Source)
    at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
    at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
    at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
    at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
    at org.apache.axis.client.Call.invoke(Call.java:2767)
    at org.apache.axis.client.Call.invoke(Call.java:2443)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)
    at mypackage.HelloImpl.getSiteMenu(RDMInterfaceWSSoapBindingStub.java:1589)
    at mypackage.HelloImpl.getSiteMenu(RDMWebserviceImpl.java:443)
    at mypackage.HelloImplServiceClient.getSiteMenu(RDMInterfaceWSServiceClient.java:123)
    at mypackage.ApplicationBean.init(ApplicationBean.java:98)
    at com.sun.rave.web.ui.appbase.servlet.LifecycleListener.attributeAdded(LifecycleListener.java:132)
    at org.apache.catalina.core.ApplicationContext.setAttribute(ApplicationContext.java:777)
    at org.apache.catalina.core.ApplicationContextFacade.setAttribute(ApplicationContextFacade.java:335)
    at com.sun.faces.context.ApplicationMap.put(ExternalContextImpl.java:496)
    at com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:287)
    at com.sun.faces.el.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:78)
    at com.sun.rave.web.ui.appbase.faces.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:96)
    at com.sun.faces.el.impl.NamedValue.evaluate(NamedValue.java:125)
    at com.sun.faces.el.impl.ComplexValue.evaluate(ComplexValue.java:146)
    at com.sun.faces.el.impl.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:243)
    at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:173)
    at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:154)
    at com.sun.rave.web.ui.component.SelectorBase.getItems(SelectorBase.java:114)
    at com.sun.rave.web.ui.component.ListSelector.getOptions(ListSelector.java:168)
    at com.sun.rave.web.ui.component.ListSelector.getListItems(ListSelector.java:113)
    at com.sun.rave.web.ui.renderer.ListRendererBase.renderList(ListRendererBase.java:363)
    at com.sun.rave.web.ui.renderer.ListRendererBase.renderListComponent(ListRendererBase.java:164)
    at com.sun.rave.web.ui.renderer.DropDownRenderer.encodeEnd(DropDownRenderer.java:73)
    at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:720)
    at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:443)
    at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:233)
    at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:701)
    at com.sun.rave.web.ui.util.RenderingUtilities.renderComponent(RenderingUtilities.java:80)
    at com.sun.rave.web.ui.renderer.AbstractRenderer.encodeChildren(AbstractRenderer.java:194)
    at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:701)
    at com.sun.rave.web.ui.util.RenderingUtilities.renderComponent(RenderingUtilities.java:80)
    at com.sun.rave.web.ui.renderer.AbstractRenderer.encodeChildren(AbstractRenderer.java:194)
    at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:701)
    at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:435)
    at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:233)
    at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:701)
    at javax.faces.webapp.UIComponentTag.encodeChildren(UIComponentTag.java:607)
    at javax.faces.webapp.UIComponentTag.doEndTag(UIComponentTag.java:544)
    at com.sun.faces.taglib.html_basic.PanelGridTag.doEndTag(PanelGridTag.java:460)
    at org.apache.jsp.Home_jsp._jspx_meth_h_005fpanelGrid_005f0(Home_jsp.java:541)
    at org.apache.jsp.Home_jsp._jspx_meth_ui_005fform_005f0(Home_jsp.java:368)
    at org.apache.jsp.Home_jsp._jspx_meth_ui_005fbody_005f0(Home_jsp.java:329)
    at org.apache.jsp.Home_jsp._jspx_meth_ui_005fhtml_005f0(Home_jsp.java:250)
    at org.apache.jsp.Home_jsp._jspx_meth_ui_005fpage_005f0(Home_jsp.java:223)
    at org.apache.jsp.Home_jsp._jspx_meth_f_005fview_005f0(Home_jsp.java:170)
    at org.apache.jsp.Home_jsp._jspService(Home_jsp.java:138)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
    at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
    at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
    at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
    at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
    at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
    at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:311)
    at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
    at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)
    at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at com.sun.rave.web.ui.util.UploadFilter.doFilter(UploadFilter.java:194)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Unknown Source){color}
    Please help me how to resolve this problem.
    Thx
    Chaitanya

  • How to deploy and run  EJB in eclipse without XDoclet

    Hi Friends
    I am new in j2ee.In my academic project i want to do some ejb programming.
    For that purpose i want to write some ejb's.I have written all required class for ejb,created ejb-jar.xml file manually,weblogic .xml file manually. I am using weblogic8 as an server for deployment.
    I know deployment with xdoclet but i want to know hoe to deploy ejb without xdoclet.
    If u have saple code or useful link regarding this please send it as soon as possible.
    Thanks in advance
    How to deploy and run EJB in eclipse without XDoclet

    HI Welcome to J2ee...
    I am also new to this...But i ll share my ideas with you...
    In EJB 3.0 No need of any Deployment Descriptors....
    And If you are using Eclipse You can Deploy(as jar) using Export in File tab...
    XDoclet is not mandatory...
    Gopal V

  • Strange exception when deploying BC4J as EJB in 8i CORBA.BAD_PARAM: null Strings are

    I am trying to deploy BC4J as Ejb to 8i (8.1.6). I use the following deployment method with j: my Jdev root.
    setjboenv j: ejb8i
    loadjava - u user/passwd@host:port:sid - thin -v - r grant "SYS,PUBLIC" j:lib\xmlparserv2.jar
    loadjava - u user/passwd@host:port:sid - thin -v - r grant "SYS,PUBLIC" j:lib\jbomt.zip
    loadjava - u user/passwd@host:port:sid - thin -v - r grant "SYS,PUBLIC" j:lib\jboejb.jarI then create a deployment profile for ejb 8i with the ide. (Without deploying)
    I then use loadjava outside the IDE to deploy the 2 jar files created
    MyProject1CommonEJB.jar
    and
    Myproject1.jar
    I then use the ide again to deploy the bean profile
    Package1ModuleServerEJB.prf
    The last step fails with the error :
    Publishing EJBHome...org.omg.CORBA.BAD_PARAM: null Strings are illegal in IIOP. Please correct your application or run the ORB in backward compatibility mode. minor code: 0 completed: No
    void oracle.aurora.ejb.deployment.GenerateEjb.invoke()
    void oracle.aurora.server.tools.sess_iiop.ToolImpl.invoke(java.lang.String[], java.io.InputStream, java.io.PrintStream, java.io.PrintStream)
    void oracle.aurora.ejb.deployment.GenerateEjb.main(java.lang.String[])
    Exception in thread main
    Strangely, when I test this EJB with the tester (middle tier = remote ejb) it works, but from JSP's I get an application error : "Unknown Exception"
    I am using Jdev 3.1
    Also using the deploy option when creating the deployment profile fails apparantly due to the missing grant "SYS,PUBLIC" when loading classes to the database before deploying the bean.
    What can be done ?
    null

    Hi Blaise
    Thanks for the reply. I have tried to do the complete deployment from within Jdev, but now I get the following error right at the end of the deployment.
    /BC4J1AppModuleEjb/EjbObject_RemoteBC4J1AppModuleEjb:ORA-29535: source requires recompilationjava.lang.NullPointerException at sun.tools.java.Environment.error(Environment.java) at sun.tools.java.Environment.error(Environment.java) at sun.tools.java.Environment.error(Environment.java) ..... etc.
    I have tried to deploy to a clean schema with the java privilages granted as described in the Jdev release notes.
    I included the following libraries in my project :
    JBO JDBC816 PATCH
    JBO OSQL Domains
    JDeveloper Runtime
    Oracle 8.1.6 JDBC
    Connection Manager
    JBO Runtime
    JBO VB Runtime
    JBO 8i Runtime
    SQLJ Runtime
    JBO 8i Client
    JBO Vanilla Domains
    JBO EJB Runtime
    JServer
    Oracle XML SQL Utility
    ORACLE XML Parser 2.0
    Then I just used the deployment wizzard
    null

  • Dependecy injection EJB into a jsp

    Hello,
    How can I do a dependency injection of and EJB into a jsp?
    When Iu2019m trying to used it (see below), It doesnu2019t work, What Iu2019m doing wrong?
    Also I tried to do a lookup, but I canu2019t do a cast because the classe returned by the lookup is some Proxy class and the only way that Iu2019ve find to access the EJBu2019s methods is through reflection.
    Regards,
    Janeth
    @EJB (name = "crystal.com.co/captura_produccion_ear/CapturaPrimeraEjbBean")
         private CapturaPrimeraEjbRemote capPrimeraEjbRemote;
    if (capPrimeraEjbRemote != null) {
           capPrimeraEjbRemote.test();
    else{
              out.println("null");

    Thank both for the answer, about the lookup:
    Vladimir you are right about implementation, actually I print trough reflection the interfaces of Proxy class, and I obtain this:
    co.com.crystal.eficiencia.primera.CapturaPrimeraEjbRemote
    javax.ejb.EJBObject
    com.sap.engine.services.ejb3.runtime.ComponentInterface com.sap.engine.services.ejb3.runtime.ReplaceableProxy
    The common code is:
    Properties props = new Properties();
         props.put(Context.INITIAL_CONTEXT_FACTORY,
                   "com.sap.engine.services.jndi.InitialContextFactoryImpl");
         props.put(Context.PROVIDER_URL, "localhost:50004");
         InitialContext ctx = new InitialContext(props);
         Object object = ctx.lookup("crystal.com.co/captura_produccion_ear/REMOTE/CapturaPrimeraEjbBean/co.com.crystal.eficiencia.primera.CapturaPrimeraEjbRemote");
         out.println(object.getClass());
    If I do injection, itu2019s work correctly:
    Method findAll = object.getClass().getMethod("test", null);
         String listaTurnos = (String) findAll.invoke(object, null);
         out.print(listaTurnos);
    But if I use narrow or cast, it doesnu2019t work (I get a java.lang.ClassCastException):
    co.com.crystal.eficiencia.primera.CapturaPrimeraEjbRemote capPrimera = (co.com.crystal.eficiencia.primera.CapturaPrimeraEjbRemote)PortableRemoteObject.narrow(object, co.com.crystal.eficiencia.primera.CapturaPrimeraEjbRemote.class);
         String listaTurnos = capPrimera.test
         out.print(listaTurnos);
    or the cast:
    co.com.crystal.eficiencia.primera.CapturaPrimeraEjbRemote capPrimera = (co.com.crystal.eficiencia.primera.CapturaPrimeraEjbRemote)object;
    What I have to do to check the correctly way to do the cast or the narrow? What Iu2019m doing wrong?
    Thanks
    Janeth

  • Calling from an EJB into a JSF Backing Bean

    Hello all,
    I'm looking for some help in making calls from an EJB into a Backing Bean (the converse is fairly straightforward). My basic question is: what is regarded as the best way to do this?
    However, for anybody who's interested, I'll describe what I've been trying...
    Here's my situation (I'm working with OC4J 10.1.3.2). I have a simple application-scoped backing bean:
       public class BackingBean implements SimpleInterface, Serializable {
           private String greeting = "Hello, World";
           private SessionEJBRemote blBeanRemote = null;
           public BackingBean() {
               // get hold of EJB
               // [ ... code to obtain EJB's remote interface snipped ... ]
               // set the callback with the EJB       
               try {
                   blBeanRemote.setCallback(this);
               } catch (Exception ex) {
                   ex.printStackTrace();
           // methods to manipulate the greeting string
           public String getGreeting() {
               return greeting;
           public void setGreeting(String greeting) {
               this.greeting = greeting;
       }SimpleInterface, which my Backing Bean implements is, well, a simple interface:
       public interface SimpleInterface {
           public void setGreeting(String greeting);
       }And my EJB is also pretty straightforward:
       @Stateful(name="SessionEJB")
       public class SessionEJBBean implements SessionEJBRemote, SessionEJBLocal {
           private SimpleInterface callback = null;
           public void setCallback(SimpleInterface callback) {
               this.callback = callback;
               callback.setGreeting("Goodbye, World");
       }Now, by using SimpleInterface, my intention was to ensure a one-way dependency: i.e. the JSF-level code would depend on the EJB-level code, but not vice versa.
    However, my experimentation has shown that when I make the call to blBeanRemote.setCallback, the parameter appears to be passed by value rather than by reference. This means firstly that, at runtime, by EJB needs to have access to my backing bean class and secondly, that the call to callback.setGreeting has no effect.
    Can anybody suggest how to work around this? Is it possible to pass the backing bean by reference? Is there a better way to achieve this callback? I appreciate that these questions might be more general Java/AppServer queries rather than JSF-specific ones - but hopefully this is something that all you JSF experts have encountered before.
    (Incidentally, I realise that what I'm doing in this example is pointless - what I'm building towards is using the ICEFaces framework to have the EJBs prod a backing bean which will in turn cause a user's browser to rerender.)
    Many thanks - any help very much appreciated!
    Alistair.

    Hi Raymond - yes, you've pretty much got that spot on: an event occurs (say receipt of a JMS message - which is spontaneous, as far as the users are concerned). As a result of that event, the client's view (in their browser) needs to be re-rendered.
    ICEFaces uses the AJAX technique to allow server-pushes, and rather than refreshing the whole page it uses "Direct-to-DOM" rendering to maninpulate the page components. If you've not come across it, and you're interested, then there are some pretty interesting demos here: http://www.icefaces.org/main/demos/ - the "chat" feature of the Auction Monitor demo (if you open it up in two browsers) is the nearest to the effect I'm looking for.
    The Auction Monitor demo uses a number of session-scoped beans, each implementing the ICEFaces "Renderable" interface, and each of which registers itself with an application-scoped bean. The application-scoped bean can thus iterate through each of the session-scoped beans and cause the corresponding browser to refresh.
    Unfortunately, in the Auction Monitor demo, the entry point is always from a browser - albeit the result is then mirrored across all connected browsers. I haven't found any examples of this processing being driven by an external event, hence my experimentation in this area!

  • Error after deploying my OA Pages into apps instance

    Hi,
    I deployed all my pages into instance, i attached them to functions, and those functions to a menu and menu to a responsibility. When i try to open them am getting an error saying
    The application pool failed to checkout an application module due to the following exception: oracle.jbo.JboException: JBO-29000: Unexpected exception caught: java.lang.NoClassDefFoundError, msg=oracle/apps/xxoc/server/XXalActivityDetailsVOImpl at oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:1610) at oracle.jbo.common.ampool.ApplicationPoolImpl.useApplicationModule(ApplicationPoolImpl.java:2357) at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:427) at oracle.jbo.http.HttpSessionCookieImpl.useApplicationModule(HttpSessionCookieImpl.java:214) at oracle.apps.fnd.framework.webui.OAHttpSessionCookieImpl.useApplicationModule(OAHttpSessionCookieImpl.java:473) at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:398) at oracle.apps.fnd.framework.webui.OAJSPApplicationRegistry.registerApplicationModule(OAJSPApplicationRegistry.java:208) at oracle.apps.fnd.framework.webui.OAJSPApplicationRegistry.registerApplicationModule(OAJSPApplicationRegistry.java:78) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1166) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:497) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:418) at oa_html._OA._jspService(_OA.java:88) at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119) at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417) at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267) at oracle.jsp.JspServlet.internalService(JspServlet.java:186) at oracle.jsp.JspServlet.service(JspServlet.java:156) at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) at oracle.jsp.provider.Jsp20RequestDispatcher.forward(Jsp20RequestDispatcher.java:162) at oracle.jsp.runtime.OraclePageContext.forward(OraclePageContext.java:187) at oa_html._RF._jspService(_RF.java:102) at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119) at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417) at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267) at oracle.jsp.JspServlet.internalService(JspServlet.java:186) at oracle.jsp.JspServlet.service(JspServlet.java:156) at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456) at org.apache.jserv.JServConnection.run(JServConnection.java:294) at java.lang.Thread.run(Thread.java:534)
    Any suggestions, what can be the problem
    Thanks

    hi,
    That problem got resolved. yes i dont have that file...Now am getting another error..
    oracle.apps.fnd.framework.OAException: oracle.jbo.NoDefException: JBO-25002: Definition oracle.apps.xxoc.schema.server.XXalActivityDetailsEO of type Entity Definition not found at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:888) at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:862) at oracle.apps.fnd.framework.OAException.wrapperInvocationTargetException(OAException.java:985) at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:210) at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:152) at oracle.apps.fnd.framework.server.OAApplicationModuleImpl.invokeMethod(OAApplicationModuleImpl.java:721) at oracle.apps.xxoc.webui.ViewDiagnosticsCO.processRequest(ViewDiagnosticsCO.java:48) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:581) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:247) at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processRequest(OAPageLayoutHelper.java:1095) at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processRequest(OAPageLayoutBean.java:1569) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:932) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:899) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:640) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:247) at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processRequest(OAFormBean.java:385) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:932) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:899) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:640) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:247) at oracle.apps.fnd.framework.webui.beans.OABodyBean.processRequest(OABodyBean.java:353) at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2298) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1711) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:497) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:418) at oa_html._OA._jspService(_OA.java:88) at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119) at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417) at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267) at oracle.jsp.JspServlet.internalService(JspServlet.java:186) at oracle.jsp.JspServlet.service(JspServlet.java:156) at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) at oracle.jsp.provider.Jsp20RequestDispatcher.forward(Jsp20RequestDispatcher.java:162) at oracle.jsp.runtime.OraclePageContext.forward(OraclePageContext.java:187) at oa_html._RF._jspService(_RF.java:102) at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119) at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417) at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267) at oracle.jsp.JspServlet.internalService(JspServlet.java:186) at oracle.jsp.JspServlet.service(JspServlet.java:156) at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456) at org.apache.jserv.JServConnection.run(JServConnection.java:294) at java.lang.Thread.run(Thread.java:534)
    Thanks

  • Deploying JSR168 Portlet's into Portal

    Hi,
    I developed a simple ADF portlet's in Jdev 11g. I also deployed into integrated WLS (as shown in Oracle's developer guide) and the URL http://host:port/context-root/portlets/wsrp2?WSDL shows WDSL correctly
    Now I want to deploy the same portlet into an external Weblogic Server 10.3. I created and uploaded the .war file and deployed via weblogic console.
    The deploy seemed to finish correctly because I see in the console my web application deployed but I don't see the wsdl (in http://externawlshost:port/context-root/portlets/wsrp2?WSDL).
    Until the WSDL is visible I can't add the producer to Oracle Portal.
    Do I need to do something else in the deploy process?
    Thank You,
    Andre

    Hi All,
    I am facing the same issue. My ADF portlet application got deployed successfully into integrated weblogic server and can access the WSDL end point also.
    But when I am trying to deploy it to an external weblogic through weblogic console, could not able to access the WSDL url.
    Can anbody tell me what could be the issue. Do I need to have a WSRP container in my weblogic? If so, how to install it?
    --Abhijit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Problems deployment servlet and ejb

    Hello,
              I'm Having the following problem hopefully someone can help me.
              I'm working in a visualcafe 4.5 project and I have to external jar
              files
              one containing an EJB the other cotaining some classes.
              testservlet.war : deployed by VC
              ejb.jar
              xxx.jar
              Deploying from VC is no problem but when I want to start the
              server it can not find some classes which are in the xxx.jar file
              containing the classes. But when I open the xxx.jar I see that they
              are located in WEB-INF/classes.
              My first Idea is that it could be a classloader problem
              In the startweblogic.cmd I add the testservlet.war to the classpath
              (Project options)
              In the ejbc additional classpath entrys of the testservlet.jar I add
              the xxx.jar.
              In the server additional classpath I added both ejb.jar and the
              xxx.jar
              can someone tell me where it is going wrong???
              Thanks
              Oskar
              

    Depoly them both in an EAR file. You will have to edit the Class-Path: property in each of the MANIFEST.MF files to make the proper path to the Singleton visible to all three, as well.

Maybe you are looking for