Yeah it sounds like it should work. The libraries referenced by the
--libraries option during deployment should be available to the
application. However, as v2.* code base is no longer been actively
worked on (you would need to go through support channel for bug fixes in
v2.1), would you be able to move to glassfish 3.1.* to try to see how
things look there?
Thanks,
- Hong
On 11/28/2011 10:26 PM, forums_at_java.net wrote:
> hi all
>
> have a question with support jar file placement.
>
> I am using
>
> glassfish version
>
> Sun GlassFish Enterprise Server v2.1.1 ((v2.1 Patch06)(9.1_02 Patch12))
> (build b31g-fcs)
>
> An EAR application can be deployed and run sucessfully if I put the
> support
> jar files in $domain/lib but I think because of the very old
> xerces.jar file
> that was used, the admin console would not come up:
>
> [#|2011-11-29T11:21:34.882+0800|INFO|sun-appserver2.1|javax.enterprise.resource.webcontainer.jsf.config|_ThreadID=20;_ThreadName=httpWorkerThread-4848-0;;|Initializing
>
> Mojarra (1.2_13-b01-FCS) for context ''|#]
>
> [#|2011-11-29T11:21:35.012+0800|INFO|sun-appserver2.1|javax.enterprise.system.container.web|_ThreadID=20;_ThreadName=httpWorkerThread-4848-0;|PWC1412:
>
> WebModule[] ServletContext.log():PWC1409: Marking servlet FacesServlet as
> unavailable|#]
>
> so i tried to move all the jar files in the applibs directory and deploy
> using
>
> /opt/SUNWappserver/bin/asadmin deploy --libraries xerces.jar,xml4j.jar
> --user
> admin --passwordfile pwd file app.ear
>
> the deployment was successful but the apps could not start,
> complaining class
> missing (from xerces.jar) file.
>
> From what I read this is the way to do it , but what am I doing wrong?
>
>
>
> thanks
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> [Message sent by forum member 'zerocooler']
>
> View Post: http://forums.java.net/node/868882
>
>