I checked with Tim, follow is his reply. Looks like user needs to do
some setup in order for OpenCMS to run through on GlassFish. Jim, would you
please look into Tim's detail analysis, please try it out and let us
know. Thanks Tim, it is a big help :-) --Judy
-------
A few things.
1. I downloaded OpenCMS 7.0.4, expanded it into a directory as specified
in the directions and tried to deploy it and saw the same errors.
2. One Google search for the error message found that this seems to be
an "expected" error during deployment. Apparently, if I understand
correctly, the deployment is to be followed by invoking a particular URL
within the web app to do some initialization. This follow-up step is
described in the install.html in the OpenCMS distribution and it seems
that this error message, logged by the servlet initialization, is
intended to remind the user to run the additional set-up step after
deployment.
3. The link which Jim pointed to in his problem (2) discussion says that
there are source code changes required in OpenCMS in order for it to
work on GlassFish. Do we know if those changes were made in this case?
I suspect not, based on what the instructions at that link say to do,
but I do not have the time to chase through all these steps myself.
4. I also tried deploying the expanded app in a disabled state. The
deployment succeeded, but when I tried to enable it after that the
enable failed (not surprisingly) with the same error and the app remains
disabled so I cannot invoke the additional set-up URL the instructions
describe.
5. It is not completely clear to me, but it is possible that openCMS
does NOT expect the server to reject the deployment because of the
servlet initialization exception that is thrown. Yet because v3 is
doing just that, there is no way to run the additional set-up step
because the app is never available. My quick reading of the link Jim
cited below is that a GlassFish user needs to prevent the exception from
being thrown by editing the openCMS source and rebuilding it. Because
Jim's report includes this error I assume he has not followed the
directions in the link he mentioned in (2).
- Tim
Judy Tang wrote:
> Thanks Adam !
>
> Hi Jim, Could you please help to log an issue for problem (1), for
> problem (2) we will add a comment to the
> following bug Adam filed which is fail to run Liferay on v3 prelude
> but it works in v3 TP2. Thanks Jim !
>
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=5980
>
> Judy
>
> Adam Bien wrote:
>
>> Hi Jim,
>>
>> it look similarly to my bug. Checkout GF logs. In my case I found
>> NoClassDefFound errors,
>>
>> hope it helps!,
>>
>> adam
>> Jim Jiang schrieb:
>>
>>> Problem (1): OpenCMS(http://www.opencms.org/en/) is the web app for
>>> content managerment.
>>> When try to deploy OpenCms 7.04 (download from here
>>> <http://www.opencms.org/en/modules/downloads/begindownload.html?id=14f9c938-e77b-11dc-ad81-b7a33137a728>)
>>> on GlassFish v3 but got following error:
>>> Exception while deploying the app : java.lang.Exception:
>>> java.lang.IllegalStateException: ContainerBase.addChild: start:
>>> LifecycleException: javax.servlet.ServletException: Critical error
>>> during OpenCms initialization: The OpenCms setup wizard is still
>>> enabled.
>>>
>>> Problem (2): There is a doc about App server relate topic for
>>> reference:
>>> http://opencms-wiki.org/App_server_related_topics#Glassfish_V2
>>>
>>> Another issue with OpenCMS is sometimes meet the error "PWC6033:
>>> Unable to compile class for JSP" on "2008-07-15_235420.png" , see
>>> attached snapshot
>>> It seems the best way to solve this problem is to "reboot" the whole
>>> server. When we tried to stop-domain after error reported, lots of
>>> glassfish processes would come out.
>>>
>>> Looking forward to getting your help.
>>>
>>> Thanks,
>>> Jim
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>