-
1. In JBOSS AS 6 Is there any option for disabling verifyDeployments for EJB3
jaikiran Jan 23, 2011 12:10 PM (in response to search4mahesh)What kind of verifications do you want to disable for EJB3?
-
2. In JBOSS AS 6 Is there any option for disabling verifyDeployments for EJB3
search4mahesh Jan 24, 2011 5:02 AM (in response to jaikiran)I am getting error as
Deployment "vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/daytrader-ear-2.2.
1.ear/" is in error due to the following reason(s): java.lang.RuntimeException:
message-destination has no jndi-name/resolved-jndi-name MessageDestinationRefere
nceMetaData{name=jms/TradeStreamerTopic,type=javax.jms.Topic,link=jms/TradeStrea
merTopic,ignore-dependecy=false,jndi-name=null,resolvoed-jndi-name=null,usage=Pr
oduces}
Is there any kind of option that can avoid this JNDI lookup and error?
(Note: I am trying apache geronimo daytrader v 2.2.1 application against JbossAS 5)
Please suggest.
Thanks,
Mahesh
-
3. In JBOSS AS 6 Is there any option for disabling verifyDeployments for EJB3
nickarls Jan 24, 2011 5:09 AM (in response to search4mahesh)It's probably missing its JMS destination.
Ignoring missing dependencies is not a good idea is most cases because even if you manage to supress the lookup, sooner or later it's going to be used and then you have a NPE.
-
4. In JBOSS AS 6 Is there any option for disabling verifyDeployments for EJB3
search4mahesh Jan 26, 2011 11:11 PM (in response to nickarls)Hi Nick,
Thanks for reply.
Looks like message destination is in another module(EJB jar) but in same application. The application was origionally intended for Websphere they have syntax as
<message-destination-ref>
<message-destination-ref-name>jms/TradeStreamerTopic</message-destination-ref-name>
<message-destination-type>javax.jms.Topic</message-destination-type>
<message-destination-usage>Produces</message-destination-usage>
<message-destination-link>daytrader-ejb-1.0-SNAPSHOT.jar#TradeStreamerTopic<
/message-destination-link>
</message-destination-ref>
Do Jboss also need same kind of syntax or JNDI is resolved at global application level?
Thanks,
Mahesh
-
5. In JBOSS AS 6 Is there any option for disabling verifyDeployments for EJB3
nickarls Jan 27, 2011 2:01 AM (in response to search4mahesh)Probably since the deploy fails. Google around, it might be in jboss.xml.
-
6. Re: In JBOSS AS 6 Is there any option for disabling verifyDeployments for EJB3
search4mahesh Jan 27, 2011 10:28 PM (in response to nickarls)Hi,
Above syntax is for one of client module which is outside the EJB module but in same application.
So jboss.xml won't help.
Also When I see Jboss console I can see the the JNDI name for TradeStreamerTopic.That means it has been deployed successfully.
But only remaining problem is JMS destination resolution for client module.Because it looks like JMS destination has module level scope rather than application level(I may be wrong here)
daytrader-ejb-1.0-SNAPSHOT.jar#TradeStreamerTopic
So above syntax or similar one it may need.
Above syntax is Websphere,What is syntax in case of Jboss to resolve message destination located in other jar(module)?
Please suggest and please correct me if I am wrong.(I am newbie to Jboss AS).