Hi Ian,
Thanks for sending me the required files. Since you pass the custom
domain.xml, you can set http-listener to 9090 in your domain.xml. Or
modify your pom.xml like this:
diff -uw pom.xml.orig pom.xml
--- pom.xml.orig 2011-03-04 21:21:23.000000000 +0530
+++ pom.xml 2011-03-04 21:22:14.000000000 +0530
@@ -402,7 +402,10 @@
<configuration>
<goalPrefix>embedded-glassfish</goalPrefix>
<app>${project.build.directory}/${project.build.finalName}.war</app>
- <port>9090</port>
+ <ports>
+ <http-listener>9090</http-listener>
+ </ports>
+
<contextRoot>jee6webapp</contextRoot>
<autoDelete>true</autoDelete>
<configFile>${basedir}/glassfish/domains/domain1/config/domain.xml</configFile>
HTH,
Bhavanishankar
Sun, an Oracle Company
http://www.oracle.com
On 03/04/2011 04:17 PM, Bhavanishankar wrote:
> Could you send me your pom.xml and domain.xml?
>
> Bhavanishankar
> Sun, an Oracle Company
> http://www.oracle.com
>
>
> On 03/04/2011 03:34 PM, Ian Smith wrote:
>> I have since converted my plugin configuration in the POM to 3.1
>> standard, and am using the 3.1 default domain.xml (mentioned in the
>> docs) with the addition of my datasource.
>>
>> This has made no difference at all, the failure mode is exactly the
>> same as before (no server listening on HTTP port, maven output
>> indicates that server is working and that app is deployed), but the
>> strange thing is, if I go back to version 3.0.1 everything works
>> again, even with the updated configs.
>>
>> So, I now have a project that can be rendered useless simply by
>> deleting the two characters ".0" in my POM, with all source and config
>> otherwise untouched.
>>
>> I can only conclude that the maven-embedded-glassfish-plugin is
>> broken in 3.1.
>>
>> Anyone disagree with my analysis?
>>
>> Ian.