Is EJB3.0 Supported ?

Hi All,
Is EJB3.0 is supported in weblogic 8.1 . If so do they provide any backward compatiblity for earlier EJB versions.
Thanks
Bala.J

No, it is not. They only just produced the first draft of the specification. There are no implementations of it. It will be a long way off. Read the specification if you want to understand how it supports backwards compatibility (which I believe it does).

Similar Messages

Will Kodo EJB3 support SQL queries standard?

Hello,
Will Kodo EJB3 support SQL queries (via
EntityManager.createNativeQuery(...))
in the Standard Edition since native queries are part of the API? Or will
that functionality require Enterprise Edition or Performance Pack?
thanks and good luck in the new year,
dave

Currently, SQL queries require the enterprise edition. Whether this
will change for Kodo 4 final has not been decided. The safest route
would be to assume that it will not change.

Availaibility of EJB3 support in JDeveloper 10g

Hi,
I found online demos such as this one http://www.oracle.com/technology/products/jdev/101/viewlets/101/ejb30entitybeanviewlet_viewlet_swf.htm impressive. Excactly what I need !
I'd love to test it in real life but I can not access the EJB3 related features in the most recent JDeveloper 10g 10.1.3 I found on the web site.
Is there someting to configure or an addon to install ? Do I have to wait for another release (when) ?
Bernard

Hello Bernard,
The support of EJB 3.0 development/deployment inside Oracle JDeveloper will be in the release 10.1.3 production that should go out in Summer 2005.
Regards
Tugdual Grall

Support for EJB3 with JDK1.4?

Are there any plans for support of EJB3 with JDK 1.4?
I see from the release notes for Kodo 4 that it currently requires JDK 1.5
for EJB3 support. The primary driver here is the use of WebSphere, which
doesn't support JDK 1.5. [And, NO, Weblogic is NOT an option. :)]
Thanks,
-Toby Reyelts

Toby Reyelts wrote:
Abe White wrote:
Are there any plans for support of EJB3 with JDK 1.4?
No. The spec itself relies heavily on Java 5 features.I understand that EJB3 makes use of JDK 1.5 language features, but that's
nothing that couldn't be fairly easily worked around. I've got a pretty
good handle on what's involved - I did write Retroweaver,
http://retroweaver.sf.net
Is there any hope of a re-evaluation of this position?We'd love to take an approach like that, but if we did, the entirety of
Sun's legal team would come after us. Basically, according to the JCP
rules, we can't ship anything but the official JCP-approved EJB3 jars.
We certainly can't prevent you from taking that sort of approach in your
own code base, but from a legal standpoint, we're not allowed to
officially support anything that's not the official jars.
-Patrick

JDeveloper vs OC4J DP4

I just noticed that OC4J developer preview 4 was released, including OPMN, HTTP Server, AS Control and EJB3 support. Sounds great news, maybe the production release is finally getting closer... With the release of Weblogic 9, Oracle is now last in line with a production quality J2EE 1.4!
However, the readme states that there will be no corresponding JDeveloper release, and that it won't be possible to deploy on DP4 with the current JDeveloper.
Why is this? How long do we have to wait for JDev 10.1.3 final? And how long do we have to wait for an official ADF Faces release?

There should be nothing to stop you building an EAR file manually deploying, either by setting up an autodeploy directory in OC4J or by using Ant.

Entity beans - cascade delete doesn't work

Hi,
Could anyone show me a working example where cascade delete implemented with EJB3 entity beans?
If the database not created with cascade delete I can't do it..
I use JDeveloper 10.1.3.0 and it's embedded OC4J and Oracle 8i database.
My session bean doesn't catch any exception during remove an entity that has child entity. The exception will be thrown only at the end of the transaction, when the container calls the concrete SQL. And my client receives SQL exception: child record found.
Why can I define: cascade={CascadeType.REMOVE} if the container doesn't check it and doesn't throw exception when I want to delete an entity that has childs?
Thanks
Kati

Kati,
The EJB3 support in 10.13.0 JDeveloper is a preview implementation released prior to the completion of the EJB3 specification. I do not believe the cascade functionality was complete for that preview. I would recommend either switching to the 10.1.3.1 preview or downloading and using TopLink Essentials, which is the compliant implementation of EJB3 Java Persistence API (JPA).
http://otn.oracle.com/jpa
Doug

JDO future

Hi,
I was wondering what the commitment to JDO of Solarmetric is. Has the
company made any statements as to how long it will continue to offer JDO
support in addition to the new EJB3 support ?
Thanks, Luc.

SolarMetric is committed to both the JDO and EJB specifications. We
have no plans to drop JDO support. JDO 2 is a great spec.

Does WebLogic9.1 support EJB3?

i've found a package named ejb3 in the weblogic.jar of WebLogic9.1, but failed in deploying some case which were succeed in Jboss4 on.
does Ver9.1 support EJB3, and where can i find some examples of that?
bow?:|

now i want to use the ejb3 tech preview version to deploy a stateless bean. when i add the annotation of "@Remote" to the bean, deployment failed. but without the annotation, deployment success. why? if without the annotation of "@Remote", how can the client call the bean?

EJB3 - More than one remote interface for Session Bean?

Hi,
Is it possible in EJB3 to have more than one remote interface for a SessionBean?
I have seen it posetd on here that it is possible but never been able to find any other information.
Using JBoss as my App Server, I have deployed an App, where a SessionBean is defined as implementing 2 interfaces, both of which are annotated using @remote.
However when I examine the JBoss JMX Console, Global JNDI Namespace only one remote interface is listed, and indeed it is the first one defined in the SessionBean.
Considering I use a String similar to (MyApp/MyBean/remote) to do the JNDI lookup, this would indicate that it is not possible to have more than one remote interface.
1. Is this a JBoss specific limitation?
2. Is there another way of performing the JNDI lookup?
Thanks,
Alan.

Hi,
Thanks for prompt response! I tried the suggestion in my application, and the output from JBoss JMX Console was
+- XXXBean (class: org.jnp.interfaces.NamingContext)
| | +- remote (proxy: $Proxy291 implements No ClassLoaders found for: xxx.xxx.xxx.xxx.xxx.Remote1 (no security manager: RMI class loader disabled))Again only displaying the remote interface that is first in the @remote ({ Remote1.class , Remote2.class}) list. This would lead me to believe that JBoss does not support this.
Can anyone confirm this?
Alan.

How to do batchreading of collections in EJB3

Hi!
I'm trying to migrate a small example from using ordinary toplink mapping in the mapping workbench to EJB3. There are some collections in that example that I want to be read as batch. (It's a check box called "Batch Reading" in the mapping workbench). Is it possible to do this in EJB3 and how? It would be very useful as it has proven to me to be a very effective way of limiting the number of roundtrips to the database.
Regards,
Bjorn Boe

Beautiful!
One other thing that I've noticed is the lack of support for configuring caching on the mappings. The closest I've come to documentation on this has been to configure bean instance pool timeout in the orion-ejb-jar.xml, which I hope was documentation on something else. Do you know if there are any plans on doing something there or other ways to get around this that won't involve using the mapping workbench for mappings?
Regards,
Bjorn Boe

Javax.naming.NameNotFoundException using Spring with EJB3 and Weblogic 10

I'm deploying an EAR application from Weblogic 10 Administration Console... This
EAR has two modules: an EJB3 module, and a Web module. The deploy process finish,
but the status of the application is "Failed"... then in the log I get the
following error:
User defined listener
org.springframework.web.context.ContextLoaderListener failed:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'gruposUnidadesServiceFacade' defined in class path resource
[http://applicationContext.xml]: Invocation of init method failed; nested exception is
javax.naming.NameNotFoundException: Unable to resolve
'GruposUnidadesService'. Resolved ''; remaining name 'GruposUnidadesService'.
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'gruposUnidadesServiceFacade' defined in class path resource
[http://applicationContext.xml]: Invocation of init method failed; nested exception is
javax.naming.NameNotFoundException: Unable to resolve 'GruposUnidadesService'. Resolved
''; remaining name 'GruposUnidadesService' at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1260)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:438)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383)
at java.security.AccessController.doPrivileged(Native Method) at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:394)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source) at
weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
at
weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at
weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at
weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at
weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at
weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at
weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at
weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at
weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
javax.naming.NameNotFoundException: Unable to resolve 'GruposUnidadesService'. Resolved
''; remaining name 'GruposUnidadesService' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) at
weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380) at
javax.naming.InitialContext.lookup(InitialContext.java:392) at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:132)
at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:88) at
org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:130) at
org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:155) at
org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:93)
at
org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105)
at org.springframework.ejb.access.AbstractRemoteSlsbInvokerInterceptor.lookup(AbstractRemoteSlsbInvokerInterceptor.java:97)
at
org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.refreshHome(AbstractSlsbInvokerInterceptor.java:105)
at org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.afterPropertiesSet(AbstractSlsbInvokerInterceptor.java:92)
at
org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean.afterPropertiesSet(SimpleRemoteStatelessSessionProxyFactoryBean.java:99)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1288)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1257)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:438)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383)
at java.security.AccessController.doPrivileged(Native Method) at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:394)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source) at
weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at
weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at
weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at
weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at
weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at
weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
This my EJB3 bean code:
@Stateless(name="GruposUnidadesService",
mappedName="GruposUnidadesService")
public
class GruposUnidadesServiceBean implements GruposUnidadesService,
GruposUnidadesServiceLocal {
In the mappedName I have tried different ways like: "ejb/GruposUnidadesService"
but I always get the same exception.
This is my weblogic-ejb-jar.xml
<?xml version = '1.0' encoding =
'windows-1252'?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA
Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>GruposUnidadesService</ejb-name>
<enable-call-by-reference>true</enable-call-by-reference>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
In the web module, I have Spring with MyFaces, in my applicationContext.xml
I have:
<?xml version="1.0"
encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD
BEAN//EN"
"http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
<bean id="gruposUnidadesServiceFacade" class="org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean">
<property name="jndiName"
value="GruposUnidadesService"/>
<property name="businessInterface" value="penoles.infraestructura.web.servicesfacades.gruposunidades.GruposUnidadesServiceFacade"/>
</bean>
<bean
id="gruposUnidadesServiceFacadeBean" class="penoles.infraestructura.web.servicesfacades.gruposunidades.GruposUnidadesServiceFacadeBean">
<property name="gruposUnidadesServiceFacade"
ref="gruposUnidadesServiceFacade"/>
</bean>
</beans>
Here, I have tried adding the resourceRef property set
to true and to false and always I get the exception.
Finally, in my web.xml I have:
<ejb-ref>
<ejb-ref-name>GruposUnidadesService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<remote>penoles.infraestructura.business.services.gruposunidades.GruposUnidadesService</remote>
</ejb-ref>
And in my weblogic.xml:
<?xml version = '1.0' encoding =
'windows-1252'?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA
Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>GruposUnidadesService</ejb-ref-name>
<jndi-name>ejb/GruposUnidadesService</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
My environment is: Weblogic 10.3.0.0 on Linux Redhat 4
thnks
Edited by: user501097 on 08-oct-2008 8:29

Well I Think it was a beginner mistake…
I added to the following to my web.xml
<ejb-ref>
<ejb-ref-name>SeguridadService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<remote>penoles.infraestructura.business.services.seguridad.SeguridadService</remote>
<ejb-link>SeguridadService</ejb-link>
</ejb-ref>
And change the applicationContext.xml
<bean id="gruposUnidadesServiceFacade" class = "org.springframework.jndi.JndiObjectFactoryBean">
<property name="resourceRef" value="true"/>
<property name="proxyInterface" value="penoles.infraestructura.web.servicesfacades.gruposunidades.GruposUnidadesServiceFacade"/>
<property name = "jndiName" value = "GruposUnidadesService"/>
</bean>
thnks!

EJB3 MessageDriven not de-queueing the message

Hi,
I've got a problem setting up a MessageDriven Bean (EJB3) on default JMS Queue in OC4J (10130).
If I open up the enterprise manager, I can see that the bean has been deployed, I can see the Queue contains messages, but it seems like the messages are not being read.
If I look at the MDB properties in the em, the only property that disturbs me is the destination type property, which seems unavailable, however I did configure it in the @MessageDriven annotation properties.
What am I doing wrong here?
Kind regards,
Bert
Here's my code:
Message Driven Bean
@MessageDriven(
          activationConfig = {
               @ActivationConfigProperty(propertyName="connectionFactoryJndiName",propertyValue="jms/RefacQueueConnectionFactory"),
               @ActivationConfigProperty(propertyName="destinationName",propertyValue="jms/MyQueue"),
               @ActivationConfigProperty(propertyName="destinationType",propertyValue="javax.jms.Queue"),
               @ActivationConfigProperty(propertyName="messageSelector",propertyValue="RECIPIENT = 'MDB'") } )
public class TestMDB implements MessageListener, TimedObject {
          public void onMessage(Message message) {
                    System.out.println("onMessage() - " + message);
          public void ejbTimeout(Timer timer) {
               System.out.println("EJB 3.0: Timer with MDB");
               System.out.println("ejbTimeout() called at: " + new Date(System.currentTimeMillis()));
Client putting a test message on the queue
          ConnectionFactory factory = (ConnectionFactory) context.lookup("jms/RefacQueueConnectionFactory");
          Queue queue = (Queue) context.lookup("jms/MyQueue");
          Connection connection = factory.createConnection();
          Session session = connection.createSession(true, Session.AUTO_ACKNOWLEDGE);
          MessageProducer sender = session.createProducer(queue);
          connection.start();
          System.out.println("Sending Message to the queue");
sender.send(session.createTextMessage("HelloWorld"));
session.commit();
View from the Enterprise manager
Message Driven Bean: "TestMDB"
General
Name "TestMDB"
State Up
Start Time Jul 7, 2006 7:25:40 AM CEST
Messaging Type javax.jms.MessageListener
Transactions Container
Transaction Support NotSupported
Performance
Messages Dequeued 0
Messages Rolled Back 0
Average Message Processing Time (seconds) 0.00
Number of Available Instances 0
Number of Used Instances 0
Message Properties
Uses Resource Adapter as Listener False
Destination Type Unavailable
Destination JNDI Location jms/MyQueue
Connection Factory JNDI Location jms/RefacQueueConnectionFactory
Subscription Type NonDurable
Subscription Name Unavailable
Listener Threads 1
Message Selector RECIPIENT = 'MDB'
Acknowledgement Mode AUTO_ACKNOWLEDGE

Well, I got the problem myself.
Just for the record, here's what I did wrong:
I forgot to put the RECIPIENT parameter on the message before sending it to the destination
Message message = session.createMessage();
message.setStringProperty("RECIPIENT", "MDB");
publisher.send(message);
I have no idea if this property is JMS spec, or Oracle specific... in my previous experience with jms, I never had to set this property (if I recall correctly). (this is the first time I'm using jms in an OC4J container.)
grtz

Which application server supports EJB 3 and Java EE 5?

Hi all,
I want to develop an application using EJB 3.
I was planning on using JBOSS 4.0.4 as application server, but I am not sure whether EJB 3 is fully supported.
Which application server supports EJB 3 and Java EE 5?
Thanks

Just install it using the EJB3 profile in the installer. Don't use the "All" profile
and think EJB3 is included in it :)

JMS Sender with ejb3 container managed transaction

Hi all,
I refer to the following link http://download.oracle.com/docs/cd/E11035_01/wls100/jms/trans.html#wp1035937
I found that JTA support JMS.
But I dont' want to use JTA explicitly, I want to use container manage transaction. eg. inside ejb3 stateless session bean.
does it support JMS?
With Regards,
wp

Hi,
Yes, WebLogic JMS supports JTA (a.k.a XA, a.k.a global) transactions such as container managed transactions. There are two requirements for CMTs on SSB:
(1) use an XML descriptor setting or EJB annotation to enable CMT for the SSB
(2) use a WebLogic JMS connection factory that is configured to have "global (XA) transactions enabled"
And I usually also recommend:
(3) Consider using a JEE "res-ref" for the connection factory to enable pooling of JMS resources. See "Enhanced Support for Using WebLogic JMS with EJBs and Servlets" (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13727/j2ee.htm#g1329180), and the "Integrating Remote JMS Providers" FAQ (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13727/interop.htm#JMSPG553).
(4) Avoid using SSBs to receive messages. MDBs are specifically designed for processing incoming messages.
It's also possible to have WebLogic automatically enlist foreign (non-WebLogic) vendors in WebLogic transactions. See the "Integrating Remote JMS Providers" FAQ for details (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13727/interop.htm#JMSPG553).
Regards,
tom

Design Patterns Support in Jdev 10.1.3?

Is Design Patterns Support included as part of JDev 10.1.3. I have seen this support in SAP NetWeaver Developer Studio where you have the option of converting existing classes to implement a certain J2EE/J2SE Design Pattern or create a new class(es) to implement a Design Pattern. I believe TogetherSoft has this support.
Any chances this request is consider in the next major release of JDev 10.1.3?

Dear Shmeltzer,
My company just begins the migration from Oracle Form-based application to pure Java EE one. We will be using JDeveloper v10.1.3, persuaded by it fast GUI building, data-binding features. Before that, we have been trying out Eclipse & JBoss.
We are going to use Swing & JSF for client, and JavaEE 5 for midtier. Persistence layer, will be JPA (EJB3 entity bean persistence) and Spring Framework DAO support. Spring DAO is interesting bcos it gives a consistent style of API (we want to support both JDBC & JPA) and consistent Exception hierarchy too. So our midtier will be partitioned (roughly according to Fowler's patterns) into 3 layers: Service, Domain/Biz Object, Data Access. Thus far is pretty standard.
We are still pretty new to this ADF, and are still exploring.
Now, my initial impression with ADF is that it seems to interfere too much with the kind of pattern we had in mind. The fact that ADF hides too much details from us programmers scares me -- it becomes restrictive and we are helpless as to what are going on inside (with those xml, dcx, etc). For e.g. talk about Service Locator pattern, and we cannot seem to figure out how/where it is implemented. Using ADF Data Control and Biz Components will make all the design patterns "disappear" -- we dont see DAO classes anymore bcos it has been automated. It looks more like 2-tier client-server pattern to me. :-)
We are interested to use ADF data-binding features, so
1) Is it still advisable to use Spring DAO layer?
2) Is it possible to just use ADF in the Client / web tier, while the EJB container remains free of ADF technologies?
Regards.

Is EJB3.0 Supported ?

Similar Messages

Maybe you are looking for