Re: File locations: EAR, WAR, XML datasource
On Sat, Dec 29, 2007 at 04:32:54PM +0100, Daniel Pocock wrote:
>
>>> I've looked in the Debian Java FAQ (EJB and Servlet sections) and also
>>> the Wiki (link below) and couldn't find an existing answer to this
>>> question.
>>>
>>> http://wiki.debian.org/FileSetsAndLocations
>>>
>>> Also, defining such a directory would probably mean we need to define
>>> some dependencies, such as `j2ee-war-container', and
>>> `j2ee-ejb-container'. These dependencies would be satisfied by packages
>>> such as Tomcat, and could be used to ensure that two conflicting
>>> containers were not installed.
>>>
>>
>> We dont have such a directory (yet). I wonder if its possible to have
>> some. There are still small differences/incompatibilities between
>> different containers. Sure, there is a small common denominator. But
>> does really worlds applications only use this common denominator?
>>
>>
> There is a saying: `build it and they will come'
>
> In practice, many applications built for one container don't always work in
> others. Some vendors focus on two containers rather than just one.
>
> However, if Debian can show a mature approach to this situation, then at
> least some application vendors may consider the portability of their
> applications.
Okay, let us discuss this a bit further. This dir should be independant
of /usr/share/java and all containers, tomcat, jetty, glassfish, jboss
need to be configured/patched to use this directory. Does all these
containers recognize new jars, ears, wars automatically? does some need
to be restart or triggered in another way?
> Maybe we should go one step further: a deployment directory for packaged
> EAR files, and a deployment directory for locally created EAR files
> (/usr/local/share/java/deploy).
Thats a good idea. Thats then a directory that can be created on
installation of a certain package like java-common as it may not be
included in some package directly.
Cheers,
Michael
Reply to: