Parent application and EJB

Hi,
I have several ears that contain jars with EJBs. Just now, I define the classpath for these EJBs in the META-INF/Manifest.mf of their jars, ant I put the jars they need in root path of the ears.
The classpaths for the EJBs are very similar. For this reason I want to create a parent application that contains all the jars that my EJBs share. The ears with the EJBs will be child of my parent application.
So, I try to do this but I don't achieve that the ears with my EJBs will be deployed. OC4J says that several classes are not found. These classes are part of the jars contained in my parent application.
It is possible that an EJB in a child application can access classes in the parent application? If affirmative answer, how can I do this?
Thanks in advance,
Jose

Please take a look at this thread:
Re: ejb lookup between ejb's in different ear files fails
Or alternatively use the following:
ou can group your client applications together. Here is what you need to do:
1. Deploy your EJB's
2. When you deploy your client applications, under parent application choose the name of your EJB application. This way OC4J knows that the client application is a trusted source (i.e. a child of the parent) and it will not ask you for the credentials. You can then use the JNDI name of the resource that you are looking up.
When you choose the parent application, your server.xml will change and it will get a parent attribute:
<application name="clientapp" path="../applications/clientapp.ear" parent="EJBAppName" auto-start="true" />Hope this help.
Deepak

Similar Messages

Strut and EJB

Hi guys,
I am trying to call EJB in my strut action classes using @EJB and got the error java.lang.NullPointerException while I use InitialContext to lookup for the EJB manually it works. The error indicates, to me that the container did not inject the EJB object at the run time. Can anyone explain to me why using annotation to inject the EJB in action classes would not work? Am I doing something wrong?
Some environment info:
** Both my web application and EJB are on the same glassfish server
** The web application and EJB are not in the same .ear file, meaning they are separate applications
thanks in advance, Kenny
Edited by: user13433552 on 7/12/2010 16:36
Edited by: user13433552 on 7/12/2010 16:36

As far as I know, the JEE server can only inject into resources it "knows about", which are servlets, other EJBs, MDBs and for example JSF backing beans. Struts is not part of the JEE spec, so I guess it won't scan those classes.
But perhaps Struts itself has a mechanism to inject EJBs into an action class?

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

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

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

Servlet jndi lookup to remote EJB, servlet and EJB not in the same application

Hi,
I think that the subject explain my problem.
I have Oracle IAS9i 9.0.2.0.0, and JDeveloper 9.0.2.829
I have deployed and EJB in IAS9i and i want to use from the developer machines, which have JDeveloper.
how can i to do remote calls from JDeveloper?.
I have modifed the orion-application.xml, and added remote=true.
I have modifed the rmi.xml and added the hosts where the Jdeveloper placed.
Any ideas?
Thanks and cheers
P.D The app server and jdeveloper are in the same net.
if it is posible replys me to [email protected] too.

Steps to access a remote EJB from within OC4J
++++++++++++++++++++++++++++++++++++++++++++++
1) Deploy EJB application (ApplicationRemote) to remote container (REMOTE)
"java -jar admin.jar -deploy ormi://REMOTE.hostname:REMOTE.port REMOTE.username REMOTE.password -deploy -file ApplicationRemote.ear
-deploymentName ApplicationRemote"
2) Ensure that local application (ApplicationLocal) has ejb-ref tags for remote EJBs accessed (in web.xml or ejb-jar.xml)
3) Deploy to local container (LOCAL) an empty application (ApplicationEmpty) with the same name as the remote application (ApplicationRemote)
"java -jar admin.jar -deploy ormi://LOCAL.hostname:LOCAL.port LOCAL.username LOCAL.password -deploy -file ApplicationEmpty.ear -deploymentName
ApplicationRemote"
5) Deploy local application (ApplicationLocal) to local container (LOCAL)
"java -jar admin.jar -deploy ormi://LOCAL.hostname:LOCAL.port LOCAL.username LOCAL.password -deploy -file ApplicationLocal.ear -deploymentName
ApplicationLocal"
4)Restart local container
ApplicationEmpty should consist of just an application.xml file - no modules. The same file can be deployed with different application names for all the remote
applications that must be accessed.
ApplicationLocal should access the remote EJB by using the following JNDI properties
java.naming.factory.initial = "com.evermind.server.rmi.RMIInitialContextFactory"
java.naming.provider.url = "ormi://REMOTE.hostname:REMOTE.port/ApplicationRemote"
java.naming.security.principal = "REMOTE.username"
java.naming.security.credentials = "REMOTE.password"
regards
Debu Panda

Parent application

Hi,
How can I set the parent application in Oracle 9iAS? I could not see the option during the deployment.

Francesco,
The best way is to make a remote call when accessing an EJB belonging to different application. For session beans the code is as follows (replace BeanHome and Bean with your actual interface classnames):
String hostname = "127.0.0.1"; // replace with your IP address
String application = "test"; // replace with the target application name under which it was deployed
String prinicipal = "admin"; // replace with the user name; not needed for "localhost" calls
String credentials = "welcome"; // replace with the user password, not needed for "localhost" calls
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.PROVIDER_URL,"ormi://" + hostname + "/" + application);
env.put(Context.SECURITY_PRINCIPAL, principal);
env.put(Context.SECURITY_CREDENTIALS, credentials);
Context ctx = new InitialContext(env);
BeanHome home = (BeanHome) PortableRemoteObject.narrow(ctx.lookup(name), BeanHome.class);
Bean bean = (Bean) PortableRemoteObject.narrow(home.create(), Bean.class);
After that, you may invoke the EJB calls via the "bean" variable. For other EJB types the code is analogous; the most important part of the above example code is the creation of proper InitialContext.
For more information look into "Enterprise JavaBeans Developer's Guide and Reference". Chapter 2 of "Servlet Developer's Guide" is also a good reference.
Daniel.

Parent Applications with Eclipse WTP

Hello,
I have an question upon Eclipse WTP and Oracle 10.1.3.
In my project we have 4 EJB Modules which are in 4 EAR Files and are deployed on the Oracle 10.1.3 application server. One EAR is the parent for all the others. So I configured the server.xml like this:
<application name="Server" path="server.ear" />
<application name="Server2" parent="Server" path="server2.ear" />
<application name="Server3" parent="Server" path="server3.ear" />
<application name="Server4" parent="Server" path="server4.ear" />
What must I do to tell Eclipse WTP that the projects depend from "Server" when they are deployed by Eclipse to the application server?
Anyone any ideas?
Greetings
Marcel

The deployment task doesn't expose the parent attribute as an out of the box capability in WTP.
Under the covers it's invoking an Ant build script which uses the <oracle:deploy> Ant task. This Ant task does expose the parent attribute for the application being deployed.
I just mucked around with a little and have a 'sorta' solution.
The OC4J WTP plugin is defined in a file called: servers\oracle.10.1.3.serverdef.
This defines the details for an OC4J server definition.
What I did was to add a new property called application.parent.
     <property id="application.parent"
          label="%label.application.parent"
          type="string"
          context="server"
          default="default" />
And in plugin.properties added the label text
label.application.parent=Parent Application:
Then I modified the buildfiles\oracle.10.1.3.xml file and added the parent attribute to the deploy.j2ee.ear target:
<target name="deploy.j2ee.ear" depends="check.skip.ear.deploy"
unless="skip.deploy">
<antcall target="package.module.ear"/>
     <oracle:deploy
          deployerUri="${deployer.uri}"
          userId="${oc4j.admin.user}"
          password="${oc4j.admin.password}"
          file="${server.publish.dir}/${module.name}.ear"
          deploymentName="${module.name}"
          parent="${application.parent}"
          bindAllWebApps="${oc4j.bind.website}"/>
</target>
Now fire up eclipse.
What you should now see is when you define an OC4J 10.1.3 instance you can set the "Application Parent:" value and this is then supplied to application when it is deployed.
Voila!
Now the small usage wrinkle here is that this property is set per OC4J server instance definition -- so in your case, you'd need define 2 OC4J server instances. One server definition where the parent is the "default" application and use that deploy "Server" and another where the parent application is set to "Server" and use that to deploy Server 2-4.
If you want the changes I made to the file, then send me an email at steve dot button at oracle dot com and I'll send them to you.
I put a few screen shots and a bit of a discussion here:
http://buttso.blogspot.com/2006/11/hacking-eclipse-wtp-oc4j-to-add-parent.html
cheers
-steve-

In Adobe Bridge when I try to open my camera raws, I get a pop up box stating "Bridges parent application is not active. Bridge requires that a qualifying product has been launched at least once to enable this feature" What do I do? Please advise

In Adobe Bridge, when I try to open my camera raws, I get a pop up stating"Bridges parent application is not active. Bridge requires that a qualifying product has been launced at least once to enable this feature." What the heck? I have a PC and haven't had problems before.. I have adobe cloud and pay my monthly bill...

Have you opened Photoshop or any other Adobe app that Bridge works with? You need to do this if you've upgraded PS or just signed up for CC.

Diff b/w bc4j model and ejb model in adf11g

hi all,
iam murali iam new for adf 11g i have some dout's in adf11g ,can u please solve my probleam
what is the difference b/w bc4j componet and ejb componet,how to develop ejb application in adf11g.

,how to develop ejb application in adf11gTake a look at this tutorial for starters:
http://st-curriculum.oracle.com/obe/jdev/obe11jdev/ps1/ejb/ejb.html

Move and redeploy application- and web-servers for Planing?

Hi, all!
Have Hyperion Planing ability to move application- and web-servers from unix-machine to another win-machine and after redeploy existing unix-installed planing on it?

They are actually for for 2 different things. The Sun WAS is for enterprise applications, EJBs and the like.
Tomcat is for simpler Servlet/JSP hosting.
The Sun WAS actually uses the Tomcat server as its Servlet/JSP engine then adds EJBs on top.

How can I develop a web application using EJB design pattern?

I have searched over the web and found quite a lot of tutorials on how to use the EJB design pattern.
I know that there will be a home interface, EJB object interface and a SessionBean.
But the tutorials often only cover a single class, this made me unable to get a complete picture of how EJB design pattern can be implemented into a whole system.
I am now required to devleop an online shopping web application using EJB and JSP page.
I think I will need to create a lot of classes: Member, ShoppingCart, Product...etc.
What I want to ask is that, do I need to create a home interface, EJB object interface and a SessionBean for each of these classes?
I really need some ideas on how to develop this system using EJB + JSP pages.
Many thanks to you all.

For every EJB that you want to create, you will need to code a home and remote interface and a bean class.
You could start getting your ideas here
http://www.theserverside.com/books/wiley/masteringEJB/
http://www.coreservlets.com

Error 500 running a tutorial application and other issues

While I am following a tutorial at Oracle JDeveloper 12c (12.1.2) Tutorials - Building a Web Application Using EJB, JPA, and JavaServer Faces it is refusing to run more than once.
When I re-run the application after making changes, it throws error 500 with the below exception stack until it is un-deployed. Once un-deployed, it runs once fine. Why does it have to be terminated and re-deployed?
In Part 3, Step 1 i cannot follow 'p. 7 In the Applications Navigator, right-click HRFacadeBean.java and select Edit Session Facade from context.' as the tree does not have Employees branch.
Why is there no Employees under the session facade?
Error 500 exception:
java.lang.ClassCastException: oracle.adfinternal.view.faces.webapp.rich.RichWindowManagerFactory$WindowIdProviderAdapter cannot be cast to org.apache.myfaces.trinidad.event.WindowLifecycleListener
at oracle.adfinternal.view.faces.webapp.rich.RichWindowManagerFactory$ApplicationWindowListeners.processWindowLifecylce(RichWindowManagerFactory.java:244)
at oracle.adfinternal.view.faces.webapp.rich.RichWindowManager._fireWindowLifecycleEvent(RichWindowManager.java:362)
at oracle.adfinternal.view.faces.webapp.rich.RichWindowManager._handleWindowOpened(RichWindowManager.java:398)
at oracle.adfinternal.view.faces.webapp.rich.RichWindowManager.beginRequest(RichWindowManager.java:924)
at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl._beginWindowManagerRequest(GlobalConfiguratorImpl.java:657)
at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.beginRequest(GlobalConfiguratorImpl.java:225)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:174)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:137)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:120)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:217)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:81)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:225)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3367)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3333)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2220)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2146)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2124)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1564)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:254)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

I thought he prematurely hit Post, thanks for clarification.
The method kind of works. It worked for a few times, then I got this. Of course property b6 does exist. Undeploying and re-deploying fixed the issue, as previously.
javax.el.PropertyNotFoundException: //D:/Users/user0/AppData/Roaming/JDeveloper/system12.1.2.0.40.66.68/o.j2ee/drs/OracleDemoWeb/ViewControllerWebApp.war/customerOrders.jsf @25,100 binding="#{backingBeanScope.backing_untitled1.b6}": The class 'oracledemo.view.backing.Untitled1' does not have the property 'b6'.
at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:111)
at com.sun.faces.application.ApplicationImpl.createComponentApplyAnnotations(ApplicationImpl.java:1941)
at com.sun.faces.application.ApplicationImpl.createComponent(ApplicationImpl.java:1144)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.createComponent(ComponentTagHandlerDelegateImpl.java:518)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:168)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at com.sun.faces.facelets.tag.jsf.core.FacetHandler.apply(FacetHandler.java:104)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at oracle.adfinternal.view.faces.facelets.rich.RichDocumentHandler.applyNextHandler(RichDocumentHandler.java:69)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at com.sun.faces.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:182)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:86)
at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:152)
at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:774)
at org.apache.myfaces.trinidad.view.ViewDeclarationLanguageWrapper.buildView(ViewDeclarationLanguageWrapper.java:94)
at org.apache.myfaces.trinidad.view.ViewDeclarationLanguageWrapper.buildView(ViewDeclarationLanguageWrapper.java:94)
at org.apache.myfaces.trinidadinternal.application.ViewDeclarationLanguageFactoryImpl$ChangeApplyingVDLWrapper.buildView(ViewDeclarationLanguageFactoryImpl.java:322)
at oracle.adfinternal.view.faces.lifecycle.ResponseRenderManager._processViewDefinitionLanguage(ResponseRenderManager.java:105)
at oracle.adfinternal.view.faces.lifecycle.ResponseRenderManager.runRenderView(ResponseRenderManager.java:41)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:1104)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:389)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:255)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:254)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:136)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:341)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:192)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:478)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:478)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:303)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:208)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at weblogic.servlet.utils.FastSwapFilter.doFilter(FastSwapFilter.java:64)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:137)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:120)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:217)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:81)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:225)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3367)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3333)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2220)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2146)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2124)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1564)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:254)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

JDBC, JMS and EJB transactions - possible problem?

Hello,
          I am using Oracle 9, Weblogic 8.1 SP 4, MyEclipse and
          XDoclet.
          In my current project I have the following piece of code
          in one of my message driven beans (code cited as pseudocode
          without unnecessary details):
          * @ejb.bean name="MyMessageProcessor"
          * display-name="Display name for a MyMessageProcessor"
          * jndi-name="ejb/MyMessageProcessor"
          * description="Bean MyMessageProcessor"
          * destination-type="javax.jms.Queue"
          * transaction-type="Container"
          * acknowledge-mode="Auto-acknowledge"
          * subscription-durability="Durable"
          * generate="false"
          * @ejb.transaction type="Required"
          public class MyMessageProcessor implements MessageDrivenBean, MessageListener {
          public void onMessage(Message msg) {
               try {
                    //obtaining connections to two different databases via JNDi
                    java.sql.Connection connOne =
                    ((DataSource)ctx.lookup("DataSourceOne")).getConnection();
                    java.sql.Connection connTwo =
                         ((DataSource)ctx.lookup("DataSourceTwo")).getConnection();
                    // performing some UPDATEs and INSERTs on connOne and connTwo
                    // calling some other methods of this bean
                    //creating the reply JMS message and sending it to another JMS queue
                    Message msgTwo = this.createReplyMessage(msg)
                    this.queueSender.send(msgTwo);
                    //commiting everything
                    this.queueSession.commit();
               } catch (Exception ex) {
               try {
                    if (this.queueSession!=null) this.queueSession.rollback();
               } catch (JMSException JMSEx) {};
               this.context.setRollbackOnly();
          Some days ago (before the final remarks from my client) there used to be only one DataSource configurated on the basis of the
          connection pool with non-XA jdbc driver. Everything worked fine
          including the transactions (if anything wrong happend not only wasn't the replymessage sent, but also no changes were written
          to database and the incomming message was thrown back to the my bean's
          queue).
          When I deployed the second DataSource I was informed by an error message, that only one non-transactional resource may
          participate in a global transaction. When I changed both datasources
          to depend on underlying datasources with transatcional (XA) jdbc drivers, everything stopped working. Even if
          EJB transaction was theoretically successfully rolledbacked, the changed were written to the database
          and the JMS message wasn't resent to the JMS queue.
          So here are my questions:
               1. How to configure connection pools to work in such situations? What JDBC drivers should I choose?
               Are there any global server configurations, which may influence this situation?
               2. Which jdbc drivers should I choose so that the container was able to rollback the database transactions
               (of course, if necessary)?
               3. Are there any JMS Queue settings, which would disable the container to send message back to the
               queue in case of setRollbackOnly()? How should be the Queue configurated?
          As I am new to the topic and the deadline for the project seems to be too close I would be grateful
          for any help.
          This message was sent to EJB list and JDBC list.
          Sincerely yours,
          Marcin Zakidalski

Hi,
          I found these information extremely useful and helpful.
          The seperate transaction for sending messages was, of course, unintentional. Thanks a lot.
          Anyway, I still have some problems. I have made some changes to the
          code cited in my previous mail. These changes included changing QueueSessions
          to non-transactional. I also set the "Honorate global transactions" to true.
          I am using XA JDBC driver. After setting "Enable local transactions" to false
          (I did it, because I assume that JDBC transactions should be part on the global
          EJB transaction) I got the following error:
          java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA
          driver supports performing SQL operations with no global transaction, explicitly allow it by setting
          "SupportsLocalTransaction" JDBC connection pool property to true. In this case, also remember to complete the local
          transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To
          complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
          I have also inspected the calls of methods of bean inside of onMessage() method just to check, whether
          the transactions are correctly initialized (using the weblogic.transaction.Transaction class).
          My questions are as follows:
          1. Any suggestions how to solve it? I have gone through the google answers on that problem and only
          thing I managed to realize that JDBC must start its own transaction. Is there any way to prohibit it
          from doing that? Can using setAutocommit(true/false) change the situation for better?
          2. How to encourage the JDBC driver to be a part of EJB transaction?
          3. As I have noticed each of ejb method has its own transactions (transactions have different
          Xid). Each method of the bean has "required" transaction attribute. Shouldn't it work in such
          way that if already started transaction exists it is used by the called method?
          4. The DataSources are obtained in my application via JNDI and in the destination environment I will have slight
          impact on the configuration of WebLogic. What is least problematic and most common WebLogic configuration which would
          enable JDBC driver to participate in the EJB transaction? Is it the WebLogic configuration problem or can it be
          solved programmically?
          Currently my module works quite fine when "enable local transactions" for DataSources is set to true, but this way
          I am loosing the ability to perform all actions in one transaction.
          Any suggestions / hints are more than welcomed. This message was posted to jdbc list and ejb list.
          Marcin

OC4J 9.0.3 and EJB 1.1 deployments???

I can not deploy my ejb1.1 beans on 9.0.3 container.
OC4J crashes with an XML parse error as a null pointer exception.
If I remove my O-R mappings from my orion-ejb-jar.xml file, the container starts up ok (app wont run as it needs the mappings)
9.0.3 docs claim I should be able to use my 1.1 ejb in this ejb 2.0 container.
Solaris release notes for 9.0.3 claim I must migrate to ejb2.0
Someone else posted this same question but got no replies.
Anyone else deployed ejb1.1 with OR mappings in 9.0.3 successfully yet?
thanks

I have tried migrating to an ejb2.0 set of beans and ejb-jar.xml file.
With no <query> tags installed for my finders I notice that a typical finder produces this:

This is vastly different from the 1.1 orion-ejb-jar.xml which would list ALL column names in the finder - hence how am I going to do a findAll? The currently generated sql is way off. Deployment of the "ormap" demo also shows a lack of column names in the generated SQL finder methods in orion-ejb-jar.xml.
Further, as soon as I introduce the query in the 2.0 version of ejb-jar.xml, the container dies with a null pointer exception. Removing this from the ejb-jar and bean deploys. Useless, cause theres no finders though.
Also, attempts to add to the <finder-method query=...> tag yield container crashes with null pointers too.
This is not very robust to say the least. Can you provide names of jar files that would cause such exceptions?
When NO query tag is inserted in the ejb-jar file, attempts to run a sample client using findByPrimaryKey return successfully but use of findAll causes timeouts similar to whats described in
"finders giving "timeout expired waiting for an instance" after 0, 1, or 2 calls" in this same forum.
Heres the query out of the ejb-jar.xml file...
<query>
<query-method>
<method-name>findAll</method-name>
<method-params></method-params>
</query-method>
<ejb-ql>
SELECT OBJECT(o) from IspTb o
</ejb-ql>
</query>
IspTb is the <abstract-schema-name> Tables exist in db.
The full error...which prevents deployment of the ejbs and hence no rewrite of the orion-ejb-jar file.
=========
10/23/02 1:54 PM: javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
10/23/02 1:54 PM: java.lang.NullPointerException
10/23/02 1:54 PM: at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
10/23/02 1:54 PM: at java.lang.ClassLoader.loadClass(ClassLoader.java:287)
10/23/02 1:54 PM: at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:135)
10/23/02 1:54 PM: at java.lang.ClassLoader.loadClass(ClassLoader.java:287)
10/23/02 1:54 PM: at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:135)
10/23/02 1:54 PM: at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getClass(PersistenceDescriptor.java:767)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getStateClass(PersistenceDescriptor.java:753)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getCMPFieldType(PersistenceDescriptor.java:1302)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.initializeFieldInfo(PersistenceDescriptor.java:1052)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getPersistentFieldInfo(PersistenceDescriptor.java:805)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.<init>(SQLGenerator.java:151)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.generateSQL(SQLGenerator.java:360)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.generateSQL(SQLGenerator.java:309)
10/23/02 1:54 PM: at com.evermind.server.ejb.deployment.EJBPackage.translateEjbqlQeries(EJBPackage.java:2100)
10/23/02 1:54 PM: at com.evermind.server.ejb.compilation.Compilation.translateEjbqlQeries(Compilation.java:140)
10/23/02 1:54 PM: at com.evermind.server.ejb.compilation.Compilation.compile(Compilation.java:178)
10/23/02 1:54 PM: at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:551)
10/23/02 1:54 PM: at com.evermind.server.Application.postInit(Application.java:431)
10/23/02 1:54 PM: at com.evermind.server.Application.setConfig(Application.java:136)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1635)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.initializeApplications(ApplicationServer.java:1585)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1240)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:93)
10/23/02 1:54 PM: at java.lang.Thread.run(Thread.java:479)
10/23/02 1:54 PM: javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getClass(PersistenceDescriptor.java:770)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getStateClass(PersistenceDescriptor.java:753)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getCMPFieldType(PersistenceDescriptor.java:1302)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.initializeFieldInfo(PersistenceDescriptor.java:1052)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getPersistentFieldInfo(PersistenceDescriptor.java:805)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.<init>(SQLGenerator.java:151)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.generateSQL(SQLGenerator.java:360)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.generateSQL(SQLGenerator.java:309)
10/23/02 1:54 PM: at com.evermind.server.ejb.deployment.EJBPackage.translateEjbqlQeries(EJBPackage.java:2100)
10/23/02 1:54 PM: at com.evermind.server.ejb.compilation.Compilation.translateEjbqlQeries(Compilation.java:140)
10/23/02 1:54 PM: at com.evermind.server.ejb.compilation.Compilation.compile(Compilation.java:178)
10/23/02 1:54 PM: at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:551)
10/23/02 1:54 PM: at com.evermind.server.Application.postInit(Application.java:431)
10/23/02 1:54 PM: at com.evermind.server.Application.setConfig(Application.java:136)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1635)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.initializeApplications(ApplicationServer.java:1585)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1240)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:93)
10/23/02 1:54 PM: at java.lang.Thread.run(Thread.java:479)

Bridge's Parent Application is Not Active, Bridge Requires That a Qualifying Product Has Been Launch

Has anyone figured out how to fix this? Tried fixes & I still can not open RAW files from Bridge or Photoshop CS5. I upgraded the Camera RAW plug-in and downloaded all fixes for Photoshop CS5 ( done automatically through Adobe updater) so program is up to date. I can open RAW files from mini bridge if I right click the photo BUT if I take the photo back to Bridge I can not open it there. ( I could do this before the upgrades so this is not different ). I have windows 7 professional 32 bit. I tried DNG files & .cr2 files.
In Photoshop CS4 I had the same problem ( almost the same error message...bridge requires a qualify product to be launched at least once... Camera RAW) and it was never fixed but I didn't understand the advantages of working in camera RAW. So it may be the same glich if I had it in CS4 & CS5. Thanks in advance for your help.

i ran into the same issue just this last week....and i finally found (at least in my case) the SOLUTION...i'd D/Led the trial version of adobe illustrator...something in that download, or the preference choices that followed afterward, KICKED my "Parent Application," which had always been photoshop CS4, to the curb! realizing, as i've had to in the past, that i should "look back to what you'd done just prior to the change (with its resulting ERROR message) and UNDO it." ergo: i dumped the trial version of illustrator, and VOILA! i can now, once again, open jpgs by opting for "open in camera raw" directly from the BRIDGE again...hope this helps! too bad newly added ADOBE programs don't ask you to actually ESTABLISH which of their programs you would LIKE to designate as the PARENT APPLICATION when you're loading said new software!

Bridge's parent application is not active

Hi,
I've suddenly come across a problem with Adobe Bridge where it isn't allowing me to open .CR2 files into Camera Raw. When I right click on an image in Bridge, an error message pops up:
"Bridge's parent application is not active. Bridge requires that a qualifying product has been launched at least once to enable this feature."
Originally, I opened Photoshop CS6, then File > Browse in Bridge. I've have opened ACR hundreds of times on this computer so I don't understand why it wants me to open it to be able to use it. I've opened a RAW file from Windows explorer, but when going back to Bridge, the same error occurs.
Does anyone know what the problem is here and how to fix it?
Running Windows 7, Photoshop CS6 64-bit, ACR 7.1, Bridge CS6 64-bit.
Thank you!

Then, in Bridge, I get the dreaded "Camera Raw blah blah blah" message when trying to open files in ACR by pressing 'cmd-R' or going to File > Open in Camera Raw.
This seems related to an old thread and I'm using email to read and write to the forum. Can you clarify a bit more about the blahblah?
You stated that it happened suddenly this morning and also mention a subscription trouble with the creative cloud. Did you use Bridge after the trouble was solved and it worked but stopped this morning or was it directly after you reinstalled everything?
Did you already try the obvious restart Bridge holding down option key and choose reset preferences? The Clean tool is not deleting everything Adobe has installed before.
And double check on the updates, the application manager sometimes has a mind of its own, especially when having multiple language versions installed, it only updates the language version set in preferences.
And check PS the About Menu
for about PS it should say 13.1.2 x64
and about plug in / camera raw it should say 7.3.0.71.
And in Bridge About Bridge it should say 5.0.2.4
Can you confirm this and can you also report what other applications you have installed from the creative cloud.
And since I changed to OSX 10.8 I can't check myself, is 10.7.5 the latest update?

Parent application and EJB

Similar Messages

Maybe you are looking for