Make use of new Java EE new predefined JNDI name java:comp/InAppClientContainer

ari-ban / glassfish-genericjmsra

0 stars 0 forks source link

Make use of new Java EE new predefined JNDI name java:comp/InAppClientContainer #52

Closed arinban closed 6 years ago

arinban commented 12 years ago

In the draft Java EE 7 platform spec, section EE.5.17 "Application Client Container Property" states that "An application may determine whether it is executing in a Java EE application client container by using the pre-defined JNDI name java:comp/InAppClientContainer."

This means that when GenericJMSRA is deployed in a Java EE 7 application server it does not need to rely on the deployer setting the undocumented system property genericra.inAppClientContainer.

Affected Versions

[2.1a]

arinban commented 6 years ago

Issue Imported From: https://github.com/javaee/glassfish-genericjmsra/issues/52
Original Issue Raised By:@glassfishrobot
Original Issue Assigned To: @glassfishrobot

arinban commented 12 years ago

@glassfishrobot Commented Reported by nigeldeakin

arinban commented 12 years ago

@glassfishrobot Commented nigeldeakin said: Adding dependency on GLASSFISH-19052

arinban commented 11 years ago

@glassfishrobot Commented ebratt said: Removed tag indicating this is needed for the JMS 2 RI, as this is not strictly required for the JMS 2 RI. However this will be required, once this RA is upgraded to support JMS 2.0 specification.

arinban commented 12 years ago

@glassfishrobot Commented Issue-Links: depends on GLASSFISH-19052

arinban commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA GENERICJMSRA-52

arinban commented 6 years ago

Closing this as this issue is migrated to https://github.com/ari-ban/test1/issues/52