[JBoss JIRA] Created: (JBAS-3630) JMSTransportSupport is not portable across different JMS providers.
by Darran Lofthouse (JIRA)
JMSTransportSupport is not portable across different JMS providers.
-------------------------------------------------------------------
Key: JBAS-3630
URL: http://jira.jboss.com/jira/browse/JBAS-3630
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: JBossAS-4.0.4.GA
Reporter: Darran Lofthouse
Assigned To: Thomas Diesler
Fix For: JBossAS-4.0.6.CR1
JMSTransportSupport is not portable across different JMS providers, the queue name is retrieved using the following code: -
String fromName = null;
Destination destination = message.getJMSDestination();
if (destination instanceof Queue)
fromName = "queue/" + ((Queue)destination).getQueueName();
if (destination instanceof Topic)
fromName = "topic/" + ((Topic)destination).getTopicName();
For JBossMQ this is fine and it results in a name that matches the JNDI name of the queue, for WebSphereMQ this returns the name of the queue as configured on WebSphere not the JNDI name the queue is bound to in JBoss.
The Javadoc for Queue describes the getQueueName as not being suitable for portable clients: -
http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Queue.html
A more portable solution could be to lookup a variable in the ENC that contains the name of the web service, this could either be provided by the user deploying the MDB or the web service deployer could bind a value to the ENC of the message driven bean as the web service is deployed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (EJBTHREE-1074) Circular @EJB3 references in session beans fail to deploy.
by Gunnar Grim (JIRA)
Circular @EJB3 references in session beans fail to deploy.
----------------------------------------------------------
Key: EJBTHREE-1074
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1074
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.1.GA
Reporter: Gunnar Grim
The following circular references makes the application undeployable:
In ArchiveBrokerBean:
@EJB
private SeriesBrokerLocal itsSeriesBroker;
In SeriesBrokerBean
@EJB
private ArchiveBrokerLocal itsArchiveBroker;
Circular references like these work fine in Glassfish but JBoss shows the following error message:
ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
State: NOTYETINSTALLED
I Depend On:
jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveTypeBroker,service=EJB3
persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
Depends On Me:
jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3
jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3
State: NOTYETINSTALLED
I Depend On:
jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
State: NOTYETINSTALLED
I Depend On:
jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
Depends On Me:
jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3
ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3
State: NOTYETINSTALLED
I Depend On:
jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (EJBTHREE-1045) Improve error message when binding fails
by Carlo de Wolf (JIRA)
Improve error message when binding fails
----------------------------------------
Key: EJBTHREE-1045
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1045
Project: EJB 3.0
Issue Type: Feature Request
Affects Versions: AS 4.2.1.GA
Reporter: Carlo de Wolf
Fix For: AS 4.2.2.GA, EJB 3.0 RC11 - FD
2007-09-03 14:58:50,737 WARN [org.jboss.system.ServiceController] Problem starting service jboss.j2
ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
at org.jboss.util.naming.Util.rebind(Util.java:125)
at org.jboss.util.naming.Util.rebind(Util.java:113)
at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens.
It should say an error message in the likes of:
"Can't bind ItemSession/remoteHome, because ItemSession is already bound"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBAS-4810) mail-ra.rar make SSL configurable
by Kurt Stam (JIRA)
mail-ra.rar make SSL configurable
---------------------------------
Key: JBAS-4810
URL: http://jira.jboss.com/jira/browse/JBAS-4810
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Kurt Stam
Assigned To: Weston Price
Attachments: mail-ra-patch.txt
We are using it in JBossESB now, but in my (test) case I did not want SSL with my IMAP
connection, so I'm suggesting to make this setting configurable in the
connector/src/main/org/jboss/resource/adapter/mail/inflow/MailFolder.java
- sessionProps.setProperty("mail.imap.starttls.enable", "true");
+ sessionProps.setProperty("mail.imap.starttls.enable", starttls + "");
I have attached the patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months