Jerome Dochez wrote:
> are you changing any Config objects ? up to now, the domain tree was
> unchanged when deploying, has this changed ?
This is a good time to decide what we should do here. My feeling is
that since config access has been improved in V3, we should have
an app/module entry created in domain.xml during deployment
and removed during undeployment.
This also facilitates the target based deployment/undeployment.
What do you think?
>
> 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).
>>
>> 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.
>>
>> 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
>