well yes, I would recommend having a GlassFish v3 install handy.
It can be useful to troubleshoot whether a particular issue is related to the "embedded" facet or to the "core" v3 part.
For instance you could run GlassFish v3 embedded using the implanted mode using glassfish/lib/embedded/glassfish-embedded-static-shell.jar in you classpath (see
http://blogs.sun.com/alexismp/entry/glassfish_embedded_reloaded).
cheers,
-Alexis
On 20 janv. 2010, at 16:13, Joey Jarosz wrote:
> I guess I will have to install a full v3 in order to give this a try....
>
> -----Original Message-----
> From: Alexis.Moussine-Pouchkine_at_sun.com [mailto:Alexis.Moussine-Pouchkine_at_sun.com] On Behalf Of Alexis Moussine-Pouchkine
> Sent: Wednesday, January 20, 2010 2:10 AM
> To: Bobby Bissett; Joey Jarosz
> Cc: embedded_at_glassfish.dev.java.net; Justin Lee
> Subject: Re: [embedded] Cannot seem to get embedded to work with domain.xml that specifies the http-listeners
>
> thanks Bobby.
> explicitly adding Joey (not sure he subscribes to this mailing list).
> -Alexis
>
> On 19 janv. 2010, at 18:37, Bobby Bissett wrote:
>
>> Yes, a v3 prelude domain isn't compatible with v3 final, and I don't recommend trying to hack it manually. However, if you start up a v3 instance with this domain it *should* recognize the domain as needing an upgrade and do that for you (or you can run asupgrade manually). When starting the server with "asadmin start-domain" you should see some output like this:
>>
>> hostname% ../bin/asadmin start-domain <domain name here>
>> Domain needs to be upgraded before it can be started.
>> Attempting upgrade now...
>> Upgrade was successful, starting domain...
>> [...]
>>
>> Did you see that text? I'd recommend making a copy of your original prelude domain, then copy that over to the gfv3/domains directory and start the server normally. You should see the "attempting upgrade" message above and it should all happen for you. Check the server log to see if there were any errors.
>>
>> After that, if you're still having troubles, then there could be a bug somewhere in the glassfish upgrade service code.
>>
>> Cheers,
>> Bobby
>>
>> On Jan 17, 2010, at 4:12 PM, Alexis Moussine-Pouchkine wrote:
>>
>>> You may also want to look at the glassfish/bin/asupgrade tool.
>>> -Alexis
>>>
>>> On 17 janv. 2010, at 21:44, Alexis Moussine-Pouchkine wrote:
>>>
>>>> Joey,
>>>>
>>>> domain.xml no longer has a DTD and its structure has changed in v3.
>>>> Please read http://www.antwerkz.com/documenting-the-glassfish-v3-schema/
>>>> Cc'ing Justin.
>>>>
>>>> hth,
>>>> -Alexis
>>>>
>>>> On 17 janv. 2010, at 21:37, Joey Jarosz wrote:
>>>>
>>>>> I've been working for weeks on this problem and am stumped. I am trying to move from the v3-prelude version of embedded over to the latest and greatest, but can't seem to get my existing domain.xml to work. To remove some variables I took the domain.xml from the glassfish jar file as a starting point, only change being that I add the http-listener entries in the domain.xml instead of setting the port programmatically.
>>>>>
>>>>> My domain.xml file needs to support multiple listeners, my original working file is attached as "old-domain.xml". The modified file pulled from glassfish is attached as "GFdomain.xml"
>>>>>
>>>>> It's like the code does not even try to recognize the http-listener defined in the domain.xml
>>>>>
>>>>> joey
>>>>>
>>>>> --------------------------------------------
>>>>> Joey Jarosz
>>>>> Senior Architect
>>>>> Chip Planning Solutions
>>>>> Cadence Design Systems, Inc.
>>>>> (408) 914-6269
>>>>>
>>>>> Need some IP? Check out www.chipestimate.com
>>>>>
>>>>> <GFdomain.xml><old-domain.xml>---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: embedded-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: embedded-help_at_glassfish.dev.java.net
>>>>
>>>
>>
>