[JBoss Getting Started Documentation] - Newbie Questions
by jej2003
I am trying to understand how EJB components (SLSB, SFSB, MDB) work. If I have an MDB that has a reference to a SLSB and a SFSB like:
| public class TestMDB implements MessageListener {
| @EJB
| private TestSLSB slsb;
| @EJB
| private TestSFSB sfsb;
| public void onMessage(Message msg){
| ...
|
I had thought that the SLSB was pulled from a pool of available objects (so could be the same instance but not necessary) while the SFSB would always be the same instance no matter how many times the onMessage was called so long as the MDB remained in memory, is this not the case? One of the developers I work with was telling me that the SLSB and SFSB would both be the same instances no matter how many times the onMessage was called. If this were the case I am not sure I completely understand what the difference between a SLSB and SFSB would be. Additionally it would help to understand when injection occurs and for SFSB vs SLSB.
If anyone can help me figure out these questions I'd greatly appreciate it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177763#4177763
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177763
17 years, 9 months
[Beginners Corner] - problem with upgrading to JBoss 4.2.3
by MikePhoenix
OK, I am trying to upgrade from 4.0.1 to 4.2.3. i am now getting the error:
java.lang.IllegalStateException: Cannot obtain target bean for: JuniperLNServlet
I have searched extensively for this error both on Google and the JBoss site search function and cannot find anything. Any help would be appreciated.
15:31:55,752 INFO [DefaultWebAppDesciptorModifierImpl] Ignore servlet: lingonet.webservices.JuniperLNServlet
15:31:55,752 INFO [DefaultWebAppDesciptorModifierImpl] Ignore servlet: lingonet.webservices.ConnectorLNServlet
15:31:55,752 INFO [DefaultWebAppDesciptorModifierImpl] Ignore servlet: lingonet.webservices.ExampleResponseLNServlet
15:31:55,768 INFO [DefaultWebAppDesciptorModifierImpl] Ignore servlet: lingonet.LoginServlet
15:31:55,768 INFO [DefaultWebAppDesciptorModifierImpl] Ignore servlet: lingonet.EDSLoginServlet
15:31:55,768 INFO [DefaultWebAppDesciptorModifierImpl] Ignore servlet: lingonet.UserCommander
15:31:55,768 INFO [DefaultWebAppDesciptorModifierImpl] Ignore servlet: lingonet.ProjectCommander
15:31:55,768 INFO [DefaultWebAppDesciptorModifierImpl] Ignore servlet: lingonet.SystemSettingsCommander
15:31:55,768 INFO [DefaultWebAppDesciptorModifierImpl] Ignore servlet: lingonet.reports.ReportImageServlet
15:31:55,768 INFO [DefaultWebAppDesciptorModifierImpl] Ignore servlet: javax.faces.webapp.FacesServlet
15:31:55,830 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.2.3.GA/server/default/tmp/deploy/tmp24788app.ear-contents/web.war
java.lang.IllegalStateException: Cannot obtain target bean for: JuniperLNServlet
at org.jboss.wsf.container.jboss42.ModifyWebMetaDataDeploymentAspect.create(ModifyWebMetaDataDeploymentAspect.java:58)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118)
at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy45.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177762#4177762
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177762
17 years, 9 months
[JBoss Messaging] - @MessageDriven annotation
by bfach
Hello,
I am attempting to find a workaround for @MessageDriven annotation issue. If you put @MessageDriven and want to add more deployments using the deployment descriptors in the ear, you will have an error saying that the destination type is not configured for <<default bean name>>.
This is due to the @MessageDriven annotation. If i do not use this annotation and describe all my beans in the xml deployment descriptors, the problem disappears. I would like to use the @MessageDriven annotation if possible.
The idea is to have multiple types of MDBs in one deployable ear file that can be updated to deploy different types. For example.
<enterprise-beans>
<message-driven>
<ejb-name>MDBA</ejb-name>
<ejb-class>main.MDBA</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
<message-driven>
<ejb-name>MDBB</ejb-name>
<ejb-class>main.MDBB</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
The idea here is that both classes use common framework provided to it within the same deployable.
Both classes would have the @MessageDriven annotation however I would like to remove the error that is deplayed if you do not add in configuration here for a bean that is automatically deployed due to the @MessageDriven annotation in the event that you do not want to deploy MDBA.
Thanks for the help. I hope it isn't too confusing.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177755#4177755
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177755
17 years, 9 months
[JCA/JBoss] - Setting up JBoss 4.2.2 so MDBs can subscribe to Topic on rem
by gortman
Hope this is the right forum for asking my question. If not, I'd appreciate it if you could point me in the right direction.
We have a an EJB3 MDB deployed to our JBoss server that needs to subscribe to a Topic on a remote WebLogic server. I'm having difficulty finding much documentation (an example would be best) of how exactly to establish the connectivity to the topic. Based on my web search it seems like I need to update jms-ds.xml, possibly jboss-service.xml, and perhaps include wlclient.jar in the JBoss classpath.
I've tried a variety of ways to make the connection so far with no success. On the JBoss wiki I found the article "HowDoIConfigureAnEJB3MDBToTalkToARemoteQueue" but that only addresses JBoss-to-JBoss. The other web search hits were mostly people asking the same question I am but with no resolution attached.
Any help you could give would be appreciated. Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177754#4177754
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177754
17 years, 9 months