Jerome Dochez wrote:
>
> On Feb 8, 2008, at 9:08 AM, Tim Quinn wrote:
>
>> Hi.
>>
>> If I start the server successfully using java -jar <the-main-jar> and
>> then I deploy a web app, and the domain.xml file is renamed to
>> domain.bak. It is never renamed back to .xml nor is a new domain.xml
>> created - at least not anywhere I have found and I've looked. The
>> same thing happens if I restart the server with a web app deployed
>> already (having renamed the domain.bak back to domain.xml or else the
>> server will not start).
>
> I traced the code. Web container is creating WebModule's in the
> configuration. Amy, JF, why is this happening, the deployment should
> do that...
Not sure what you mean. Web container was creating WebModule always
when invoked by WebDeployer?
Let's talk off line about this.
Thanks,
Amy
>
>
>> Interestingly, using java -jar to start the server I do not see the
>> class not found exceptions for
>> com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
>> that I see when I run using mvn gf:run.
> looks like the domain.xml that is being used when doing gf:run still
> has the jvmOption to set the MBeanServer like in V2. I have removed
> that jvm option from the nucleus-base.zip's domain.xml since we will
> be using the JDK MBeanServer in v3, so I am not sure why you still
> have the old one.
>>
>>
>> Further, if I run with mvn gf:run then I see the exceptions I wrote
>> about last night but I *do *get a new domain.xml in the domain's
>> config directory!
>>
>> Odd. Any ideas?
>>
>> - Tim
>