I don't think that there is anything wrong with having a
platform-specific descriptor where the spec allows. You can still deploy
the same EAR file on multiple platforms. For instance I am doing this
now with WebLogic and WebSphere. WebLogic pays attention to
weblogic-ejb-jar.xml and WebSphere
I beleive that the EAR/WAR structure is defined in the servlet spec.
Denes wrote:
Can you tell me where in the specs is an ear file defined? I overlooked
the 1.4 spec and EJB 2.0 spec and can´t find it.
I think this should be implemented within the VM as well. Imagine the
overhead of having another copy of the server running for every
application. I also think that you shouldn't have to have the server
installed twice to run a separate VM. With a large server (with
clustering support) it can m
I think this is a good idea. One thing that sys admin people that I work
with like about WebSphere 4 is the centralized config repository that
can be managed from any machine in the cluster. There is no need for a
special admin server. This could make clustering easier. No need to
replicate con
Wouldn't having a separate server configuration require a separate
runtime? It seems like a mistake to require another runtime for every
application that you have. There is nothing precluding you from running
multiple applications in a runtime but you have to be wary of
collisions. This is part
AFAIK the spec doesn't outline how classloaders must work. In fact I
think the word classloader only appears 2 times in the 1.3 spec and
doesn't have anything to do with how a container must implement
classloaders. However, there are requirements for enterprise
applications to remain separate a
