 | 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
|
|
|
| | | J2EE packaging | J2EE packaging 2003-12-23 - By Katz Guy
Back
hi;
your remarks are not very clear so I don't really understand what you are
trying to say. but I will add the following:
1. what do you mean don't worry about portability? - obviously you never had
to produce an application that runs over more than one app server. packaging
your application according to the recommendations and best practices will
get you quite a long way to portability - using app server specific features
wont!.
2. J2EE classloading hierarchy is a subject that is not mandated by the J2EE
spec. there are several recommendations but that's it. there is a big hole
there and the result is a different classloading hierarchy for almost every
App server (allthough may share the same logic).
thanks.
-- --Original Message-- --
From: ashraf galal [mailto:ashrafwg@(protected)]
Sent: Tuesday, December 23, 2003 3:28 AM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Re: J2EE packaging
To Katz Guy :
Application servers are totally different. so there is no need to wary about
portability between them.
class loader is J2EE specification used for packing and deploying
applications while JNDI used for creating, adding, removing, searching and
modifying directory objects.
so I think this ides is not valid.
Ashraf Galal
(416)804-8359
>From: Katz Guy >Reply-To: An interest list for Sun Java Center J2EE Pattern
Catalog >To: J2EEPATTERNS-INTEREST@(protected) >Subject: Re: J2EE packaging
>Date: Sun, 21 Dec 2003 08:09:40 +0200 > >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)
__ __
Add photos to your messages with MSN 8.
<http://g.msn.com/8HMAENCA/2749??PS=> Get 2 months FREE*.
====================================================================
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 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859 (See http://iso-8859.ora-code.com)-1">
<TITLE>Message</TITLE>
<META content="MSHTML 5.00.3809.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=893291008-23122003>hi;</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=893291008-23122003>your
remarks are not very clear so I don't really understand what you are trying to
say. but I will add the following:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=893291008-23122003>1.
what do you mean don't worry about portability? - obviously you never had to
produce an application that runs over more than one app server. packaging your
application according to the recommendations and best practices will get you
quite a long way to portability - using app server specific features
wont!.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=893291008-23122003>2.
J2EE classloading hierarchy is a subject that is not mandated by the J2EE spec.
there are several recommendations but that's it. there is a big hole there and
the result is a different classloading hierarchy for almost every App server
(allthough may share the same logic).</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=893291008-23122003>thanks.</SPAN></FONT></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV align=left class=OutlookMessageHeader dir=ltr lang=en-us><FONT
face=Tahoma size=2>-- --Original Message-- --<BR><B>From:</B> ashraf galal
[mailto:ashrafwg@(protected)] <BR><B>Sent:</B> Tuesday, December 23, 2003 3:28
AM<BR><B>To:</B> J2EEPATTERNS-INTEREST@(protected)<BR><B>Subject:</B> Re:
J2EE packaging<BR><BR></FONT></DIV>
<DIV>
<P><BR><BR></P>
<DIV>
<P>To Katz Guy :</P>
<P>Application servers are totally different. so there is no need to wary
about portability between them.</P>
<P>class loader is J2EE specification used for packing and deploying
applications while JNDI used <FONT face="Times New Roman" size=3>for
creating, adding, removing, searching and modifying directory objects.
</FONT></P>
<P><FONT face="Times New Roman" size=3>so I think this ides is not
valid.</FONT></P>
<P><GUY_KATZ@(protected)><BR><BR></P><BR><BR><BR>
<DIV>Ashraf Galal <BR>(416)804-8359</DIV>>From: Katz Guy
<GUY_KATZ@(protected)>>Reply-To: An interest list for Sun Java Center
J2EE Pattern Catalog <J2EEPATTERNS-INTEREST@(protected)>>To:
J2EEPATTERNS-INTEREST@(protected) >Subject: Re: J2EE packaging >Date:
Sun, 21 Dec 2003 08:09:40 +0200 > >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) </DIV></DIV><BR clear=all>
<HR>
Add photos to your messages with <A
href="http://g.msn.com/8HMAENCA/2749??PS=">MSN 8. </A>Get 2 months FREE*.
==================================================================== 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)
*****************************************************************************
**************************<BR>This
footnote confirms that this email message has been scanned by PineApp
Mail-SeCure for the presence of malicious code, vandals & computer
viruses.<BR>*****************************************************************
**************************************<BR></BLOCKQUOTE></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)
|
|
|
