J2EE packaging

Google

Mailing List

Home

Forum Home

JBoss - Java Application Server

Struts - A MVC web framework

Tomcat - JSP/Servlet container

iText - An open source PDF Java Library

JDOM - JDOM XML Parser

J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition

J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog

Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology

JSP - A mailing list about Java Server Pages specification and reference

Struts & Hibernate

Subjects

•	JSP editor plugin for eclipse ?
•	org apache jasper JasperException: Unable to compile class for JSP
•	Tomcat: Connection reset by peer: socket write error
•	Cannot retrieve definition for form bean null
•	Struts Tiles Tutorial (free Struts training)
•	Where do I download Tomcat 4 0 6?
•	Data Access Object (DAO) pattern, example DAO 's
•	Where to download Tomcat v 4 1 24 from?
•	Tomcat 5 0 16 Requested resource not available
•	Oracle Connection Pooling in 3 2 2
•	Servlet : Session invalidate
•	Servlet action is currently unavailable
•	Tomcat/Struts Unicode Encoding/Decoding problems
•	Tomcat and webapplication specific java library path
•	Running a Simple JMS Example
•	Mapping in workers2 properties
•	org apache jasper JasperException
•	Cannot find message resources under key org apache struts action MESSAGE
•	problem with html:text bean throwing exception
•	Cannot find message resources under key org apache struts action MESSAGE
•	invalid direct reference problem with solution
•	Tool for jsp debug Try Sysdeo Eclipse Plugin
•	Tomcat 5 Cannot load JDBC driver class 'null ' SQL state: null
•	weblogic ejbc
•	java properties file
•	Jboss 3 2 3 Coyote Can 't re
•	Tomcat 5, Apache2 and mod jk2 integration problem
•	JBoss example problem new to J2EE
•	url string for connecting jboss to oracle
•	Value attribute of <html:checkbox
•	javax servlet ServletException: BeanUtils populate
•	HTTP Status 404 The requested resource is not available
•	5 0 18: Windows XP Pro vs Windows 2000

J2EE packaging

J2EE packaging

2003-12-21 - By Katz Guy

Back

Reply: 1 2 3 4 5 6 7 8 9 10

Hi;
I think messing with the classloaders defaults is not a good idea. You will
eventually have portability problems cause the hierarchies are different
between app servers..
You should think of a more creative idea such as putting this object
(singleton) in the JNDI tree and access it from both apps
Also, sometimes its not that bad to have two instances of your object (even
though it's a singleton), especially if it holds read only data, if this
does not compromise your application logically, it will just cause some form
of duplication in caching of data.

-- --Original Message-- --
From: joe@(protected) [mailto:joe@(protected)]
Sent: Friday, December 19, 2003 10:07 AM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Re: J2EE packaging

Sachin,

Your problem can be solved by modifying your EAR settings in WSAD. Like you
say, each war module has by default its own classloader and is isolated from
the rest of the application. This means that calling ejb modules from the
war is ok but calling one war from another is not possible.

To allow calls into the war from another war, you need to change the War
classloader policy from MODULE to APPLICATION in the Server (WebSphere Test
environment) configuration.

You find this in the server perspective (I assume you use WSAD 5.x), from
the Server Configuration view, select the test server you are running on and
open it. In the Applications tab at the far right of the configuration you
will find the Application Options. Select the EAR you are running and change
the War classloader policy.

Hope this solves your problem.

Best regards,
J�rn �lmheim
SCEA
Statoil ASA

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
listserv@(protected)
****************************************************************************
***************************
This footnote confirms that this email message has been scanned by PineApp
Mail-SeCure for the presence of malicious code, vandals & computer viruses.
****************************************************************************
***************************

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859 (See http://iso-8859.ora-code.com)-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2655.35">
<TITLE>RE: J2EE packaging</TITLE>
</HEAD>
<BODY>

Hi;
 I think messing with the classloaders defaults is not a good
idea. You will eventually have portability problems cause the hierarchies are
different between app servers..

You should think of a more creative idea such as putting this
object (singleton) in the JNDI tree and access it from both apps

Also, sometimes its not that bad to have two instances of your
object (even though it's a singleton), especially if it holds read only data,
if this does not compromise your application logically, it will just cause some
form of duplication in caching of data.

-- --Original Message-- --
 From: joe@(protected) [<A HREF="mailto:joe@(protected)">mailto
:joe@(protected)</A>] 
 Sent: Friday, December 19, 2003 10:07 AM
 To: J2EEPATTERNS-INTEREST@(protected)
 Subject: Re: J2EE packaging

 

Sachin,


Your problem can be solved by modifying your EAR settings in
WSAD. Like you
 say, each war module has by default its own classloader and is
isolated from
 the rest of the application. This means that calling ejb
modules from the
 war is ok but calling one war from another is not possible.


To allow calls into the war from another war, you need to
change the War
 classloader policy from MODULE to APPLICATION in the Server
(WebSphere Test
 environment) configuration.


You find this in the server perspective (I assume you use WSAD
5.x), from
 the Server Configuration view, select the test server you are
running on and
 open it. In the Applications tab at the far right of the
configuration you
 will find the Application Options. Select the EAR you are
running and change
 the War classloader policy.


Hope this solves your problem.


Best regards,
 J�rn �lmheim
 SCEA
 Statoil ASA


===============================================================
=====
 Companion Site: <A HREF="http://www.corej2eepatterns.com"
TARGET="_blank">http://www.corej2eepatterns.com</A>
 J2EE BluePrints: <A HREF="http://java.sun.com/blueprints
/corej2eepatterns" TARGET="_blank">http://java.sun.com/blueprints
/corej2eepatterns</A>
 List Archive: <A HREF="http://archives.java.sun.com/archives
/j2eepatterns-interest.html" TARGET="_blank">http://archives.java.sun.com
/archives/j2eepatterns-interest.html</A>
 Unsubscribing: email "signoff J2EEPATTERNS-INTEREST"
to listserv@(protected)
 **************************************************************
*****************************************
 This footnote confirms that this email message has been
scanned by PineApp Mail-SeCure for the presence of malicious code, vandals &amp
; computer viruses.

***************************************************************
****************************************


</BODY>
</HTML>
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)