-
1. Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile
dmlloyd Nov 15, 2006 11:17 AM (in response to jeffdelong)Why don't I just bundle these two libraries in the console regardless of AS version. At worst it just means that there'll be an extra library loaded.
-
2. Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile
tom.baeyens Nov 15, 2006 11:19 AM (in response to jeffdelong)i consider that an option. let's try it after the alpha 2 release.
-
3. Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile
jeffdelong Nov 15, 2006 11:23 AM (in response to jeffdelong)I think it would be nice to understand why they are needed by the console app, if there are siimilar jars that could provide the same or replacement classes that the console could use, why they are being removed by the EJB3 profile, etc. Otherwise we risk having classloader issues, or at the very least a bloated dsitribution.
-
4. Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile
tom.baeyens Nov 15, 2006 2:14 PM (in response to jeffdelong)the jsf implementation we use is written for java 5 and david backported it to 1.4 with jboss retro. jboss retro requires 2 jars at runtime, which are in the 4.0.4.GA distro, but not in the 4.0.4 patch 1 EJB profile.
depending on where you deploy you have to add the libs to our web app. to make it more convenient, david proposed to add them anyway. the alternative is that we start creating web apps with various kinds of libraries included for deployment on different versions of each server. -
5. Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile
jeffdelong Nov 15, 2006 2:19 PM (in response to jeffdelong)EJB 3 profile probably removes them because EJB3 assumes Java 5.
So if the console app is run with Java 5, are the retro jars still required? -
6. Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile
dmlloyd Nov 15, 2006 3:04 PM (in response to jeffdelong)Yes and no... We could produce a JDK 5 version that skips the "retro" phase, and a separate 1.4 version that does the jbossretro bit and requires the two jars. This is what the JBossWS guys do, and other projects are doing it as well I believe. JBossAS ships with the 1.4 version. Of course for them it's a matter of spec compliance - they have to be able to run on the 1.4 JDK to be compliant with j2ee 1.4.
I'm open to this possibility if Tom agrees. -
7. Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile
jeffdelong Nov 15, 2006 4:10 PM (in response to jeffdelong)Well I would not want to see having to maintain two versions that would require two different downloads, etc.
-
8. Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile
dmlloyd Nov 15, 2006 4:48 PM (in response to jeffdelong)It's really more a question of build.xml spitting out two war files instead of one... it's very easily accomplished.
-
9. Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile
tom.baeyens Nov 16, 2006 3:45 AM (in response to jeffdelong)i'm definitely open to having a .war for 1.4 and a .war for 5.0.
BUT the thing to take into account is that i want the war files to have the same name. because when deploying wars, the filename is used as the context root.
the way i'm heading now is that 1 version is being produced in the deploy folder of the distro's. Then there is a build script that can build all kinds of (currently only 1) variations with different library combinations.
The one customized version that this script now produces is a version that runs on tomcat 6.0.0.
Would that be a good approach ? starting with one base file in the download + an ant script that can generate the other variations.