Re: JSR-88 Q.

[Dain Sundstrom <da...@iq80.com>]

Before, you spend a lot of time working on 88 related stuff.... I  
heard a rumor that 88 was going to be "no longer required" in the next  
JEE spec.  If true, my guess a lot of vendors will drop it (for lots  
of different reasons).

-dain

On Nov 18, 2008, at 5:54 AM, Steve Loughran wrote:

> David Jencks wrote:
>> On Nov 17, 2008, at 6:49 AM, Steve Loughran wrote:
>>>
>>> I have some queries about JSR-88, the deployment API that  
>>> WebSphere and Geronimo -and maybe others- implement
>>>
>>> -which JAR should apps use if they want to builld against this?
>>>
>>> I see some references to geronimo-spec-j2ee-deployment-1.1 but  
>>> that stops at RC4 in 2005. Is that a compatible version to build  
>>> against? Is there an official version somewhere?
>>>
>>> - how do people test their client apps compliance?
>> The latest geronimo spec jar is available at
>> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-javaee-deployment_1.1MR3_spec/1.0/geronimo-javaee-deployment_1.1MR3_spec-1.0.jar 
>>  There are source and javadoc jars there too.
>> The source is at
>> https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javaee-deployment_1.1MR3_spec-1.0 
>>  There are some tests of some of the mandated functionality in the  
>> javaee tck.  As far as I know there is no standalone tck, but  
>> perhaps it is available if you know the right people at sun.
>> My impression is that this spec has not been enthusiastically  
>> adopted by any vendors other than geronimo, but I don't have much  
>> to base this on.
>> There's a fair amount of implementation in various parts of  
>> geronimo that you might or might not find useful.  Ask on the  
>> geronimo dev list with more details of what you are trying to do  
>> for more info.
>
> Thanks - i'll have a look. Everything other than WebSphere seems  
> quite happy with deploy-by-copy operations, but JSR-88 adds a lot of  
> bonus complexity. I can't help thinking it would be easier if we  
> could just add a separate config file alongside every WAR/EAR, but  
> then I've never been part of a Java EE JSR and obviously don't  
> understand why the only deployment model that makes sense is a gui  
> with property sheets...
>
>

Re: JSR-88 Q.

[Steve Loughran <st...@apache.org>]

Dain Sundstrom wrote:
> Before, you spend a lot of time working on 88 related stuff.... I heard 
> a rumor that 88 was going to be "no longer required" in the next JEE 
> spec.  If true, my guess a lot of vendors will drop it (for lots of 
> different reasons).
> 
> -dain

Excellent! deploy-by-copy is the only thing anyone needs. What JSR-88 
added to that was the ability to set some env variables above and beyond 
facts hard-coded into the WAR/EAR file, which means you can actually 
have WAR/EAR files that will deploy into different environments without 
them implementing their own custom post-install configuration GUI (as 
things like JIRA end up doing)