[jboss-user] [JBoss Seam] - Re: Exadel, JBoss and Seam
anonymous wrote : insanely productive development environment that is comparable to Microsoft's .Net. I don't know how well you know MS VS .NET, but from what I've seen from it, I can tell you that if RHDS resembles VS, I'm surely not going to use it. Eclipse and NetBeans are insanely more productive than VS, IMHO. :-) My expectations are high concerning RHDS, I've been waiting a long time to get an IDE with good JSF and Seam support. Personally, I think it would be nive to have a feature that allows to build the projects without IDE (yes,indeed, for building on a continuous integration server). Currently I haven't seen a solution for that, so I'm always doing double work: keeping the Ant build files and the Eclipse project files in sync. (If someone knows of an existing solution I'd appreciate to be pointed at it ;-)) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037886#4037886 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037886 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - @EJB annotation doesn't lookup globally JBoss
Hi,
I have 2 ear's, say earA and earB. I have a session bean (say SessionA) that
needs to call a method on a session bean (say SessionB) in earB.
I implemented this like this:
| @Stateless
| public class SessionBeanA implements SessionBeanALocal {
| @EJB(mappedName=earB/SessionBeanB/local)
| SessionBeanB beanB;
| ...
|
which is exactly how it appears in the JNDI view.
However, during execution, the beanB variable is always null.
I have tried all possible formats for the mapped name, it never works:
SessionBeanB/local
earB/SessionBeanB
SessionBeanB
...
It works fine if beanB is in the same ear as beanA. It also works fine if I do
a classical lookup :
| InitialContext initCtx = new InitialContext();
| SessionBeanB beanB= (SessionBeanB)initCtx.lookup(earB/SessionBeanB/local);
|
If I understand the EJB3 docs well, it should be no issue that the beanB is in
another ear, or is it?
anonymous wrote :
| Rules for the @EJB annotation
|
| * The @EJB annotation also has a mappedName() attribute. The
specification leaves this a vendor specific metadata, but JBoss recognizes
mappedName() as the global JNDI name of the EJB you are referencing. If you
have specified a mappedName(), then all other attributes are ignored and this
global JNDI name is used for binding.
| * If you specify @EJB with no attributes defined:
|
| @EJB ProcessPayment myEjbref;
|
| Then the following rules apply:
| o The EJB jar of the referencing bean is contained in is search
for another EJB with the same interface. If there are more than one EJB that
publishes same business interface, throw an exception, if there is one, use
that one.
| o Search the EAR for EJBs that publish that interface. If there
are duplicates, throw an exception, otherwise return that one.
| o Search globally in JBoss for an EJB of that interface. Again,
if duplicates, throw an exception
| * @EJB.beanName() corresponds to ejb-link. If the beanName() is
defined, then use the same algorithm as @EJB with no attributes defined except
use the beanName() as a key in the search. An exception to this rule is if you
use the ejb-link '#' syntax. The '#' syntax allows you to put a relative path
to a jar in the EAR where the EJB you are referencing lives. See spec for more
details
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4034937#4034937
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034937
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS JBossMQ] - Howto connect a EJB3 MDB to a remote queue?
Hi, I need to make a EJB3 MDB that listens for messages coming from another JBoss server. I'm pretty new to JBoss and an intense googling for examples and tutorials wasn't very helpful for me. Especially the possibility of doing things several different ways is confusing. Also it looks like it changes quite a lot between minor versions? (I'm currently using JBoss 4.0.5) Anyway, so far I configured a JMSProviderLoader in jms-ds.xml: mbean code=org.jboss.jms.jndi.JMSProviderLoader | name=jboss.mq:service=JMSProviderLoader,name=RemoteMQProvider,server=192.168.100.10 | attribute name=ProviderNameISJMSProvider/attribute | attribute name=ProviderAdapterClassorg.jboss.jms.jndi.JNDIProviderAdapter/attribute | attribute name=QueueFactoryRefXAConnectionFactory/attribute | attribute name=TopicFactoryRefXAConnectionFactory/attribute | attribute name=Properties |java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory |java.naming.factory.url.pkgs=org.jnp.interfaces |java.naming.provider.url=192.168.100.10:25199 | /attribute | /mbean and an invoker proxy in the ejb jboss.xml: |message-driven | ejb-nameTestMDB/ejb-name | destination-jndi-namequeue/remotequeue/destination-jndi-name | invoker-bindings | invoker | invoker-proxy-binding-nameTextMDBInvoker/invoker-proxy-binding-name | /invoker | /invoker-bindings | /message-driven | /enterprise-beans | | invoker-proxy-bindings | invoker-proxy-binding | nameTextMDBInvoker/name | invoker-mbeandoes-not-matter/invoker-mbean | proxy-factoryorg.jboss.ejb.plugins.jms.JMSContainerInvoker/proxy-factory | proxy-factory-config | JMSProviderAdapterJNDIISJMSProvider/JMSProviderAdapterJNDI | ServerSessionPoolFactoryJNDIStdJMSPool/ServerSessionPoolFactoryJNDI | MinimumSize1/MinimumSize | MaximumSize15/MaximumSize | KeepAliveMillis3/KeepAliveMillis | MaxMessages1/MaxMessages | MDBConfig | ReconnectIntervalSec5/ReconnectIntervalSec | DLQConfig | DestinationQueuequeue/DLQ/DestinationQueue | MaxTimesRedelivered10/MaxTimesRedelivered | TimeToLive0/TimeToLive | /DLQConfig | /MDBConfig | /proxy-factory-config | /invoker-proxy-binding | /invoker-proxy-bindings | But now, how do I configure my EJB3 MDB to connect to this remote queue? Also the remote JBoss server is version 3. I have been told that this should be no problem. But is it really no problem when using EJB3? All tips and hints are greatly appreciated. D. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3995806#3995806 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3995806 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS JBossMQ] - Re: Howto connect a EJB3 MDB to a remote queue?
I think I found the solution http://www.jboss.com/index.html?module=bbop=viewtopict=88899 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3995824#3995824 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3995824 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
