• Post Reply Bookmark Topic Watch Topic
  • New Topic

Using shared Libraries in JSF projects  RSS feed

 
Arsineh Keshishian
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
HI,

I'd like to deploy a jar as a shared lib in weblogic.
This jar should be used by several jsf projects.
The shared lib is purposed to deliver dynamic content to the jsf projects.
Will this idea work? Do I have to extend the faces-config with the shared lib or where to note the shared lib?
Thanks in advice.
 
Tim Holloway
Bartender
Posts: 18531
61
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The paradigm for a J2EE web application (whether JSF or otherwise) is that each and every web application should be self-contained. So sharing a single copy of a library is discouraged.

Sharing resources (and related code) is a somewhat different matter. For example, a database Connection pool might be shared between multiple webapps. In cases like that, the pool object is constructed and owned by the webapp server (container) and access to the resource is provided via JNDI. EJBs are another case. When an EJB is defined with Remote accessibility (which was the standard up until about EJB3), then the client apps could share EJBs, with the EJBs also being located via JNDI.

Then there are the more complex forms of functionality, such as having the webapps invoke shared Web Services, interact with RMI or CORBA servers, or messaging systems such as JMS.

Since WebLogic is a full-featured J2EE stack implementation, all of these and more are available options.

And finally, if the "shared resources" are simply things like common JavaScript, images, and/or CSS, you can simply designate one webapp to server them up and use its URLs as the reference for these resources in your other webapps.
 
Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!