I guess that depends on what kind of resources you're using. JMS seems a little bit heavyweight way to deal with this issue.
Why not simply have the resources returned from a Session Bean on the appserver? Regards, Will Hartung ([EMAIL PROTECTED]) ----- Original Message ----- From: "Keith Wannamaker" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Wednesday, July 10, 2002 9:52 PM Subject: RE: JNDI - What resources are loaded? > Portability is an issue, so it seems the best way > to effect global parms in J2EE is to designate them > for one component (say a web app), then use JMS to > communicate the values to the other components > (web apps). Does this seem like the portable way > to attack this problem? > > Keith > > | -----Original Message----- > | From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > | Sent: Wednesday, July 10, 2002 5:53 PM > | To: Tomcat Users List > | Subject: RE: JNDI - What resources are loaded? > | > | > | > | > | J2EE specs don't require the ability to share resources in this way, so > | there's no portability guarantee. But Tomcat 4.1.x supports this. In > | server.xml, you put the resources in a <GlobalNamingResources> section at > | the top of the file (or use the admin tool to configure them). > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
