Just an update. I specified the default host as you outlined and that seemed to
work. However, I needed to specify some ejb settings so I needed to specify a
bindings file which I did. Unfortunately, it looks like no matter what was
specified in my file that by default the wsDefaultBindings goal generated
default activation spec entries. My binding file looks like the following:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE dfltbndngs SYSTEM "dfltbndngs.dtd">
<dfltbndngs>
<module-bindings>
<ejb-jar-binding>
<jar-name>opscenter-ejb.jar</jar-name>
<ejb-bindings>
<ejb-binding>
<ejb-name>Gateway</ejb-name>
<listener-port>Gateway</listener-port>
</ejb-binding>
<ejb-binding>
<ejb-name>LoadProfile</ejb-name>
<listener-port>LoadProfile</listener-port>
</ejb-binding>
</ejb-bindings>
</ejb-jar-binding>
<war-binding>
<jar-name>opscenter-web.war</jar-name>
<virtual-host>opscenter</virtual-host>
<resource-ref-bindings>
<resource-ref-binding>
<resource-ref-name>TimerManagerRef</resource-ref-name>
<jndi-name>tm/default</jndi-name>
</resource-ref-binding>
</resource-ref-bindings>
</war-binding>
</module-bindings>
</dfltbndngs>
Even though I'm specifying a listener-port for my message driven beans an
additional default activation spec target resource jndi name of eis.Gateway is
being created and when my app starts it fails with an error saying it can't
find that resource (my listener-port is being created). I don't think this is
an error with the was6-maven-plugin. It looks like the wsDefaultBindings goal
is specifying things correctly from what I can tell. It looks like this is a
problem with the IBM WebSphere DefaultBindings ant task. I was curious if
anyone else had run into this problem?
Thanks,
Matt
________________________________
From: Matt Goodwin [[email protected]]
Sent: Monday, August 16, 2010 6:17 PM
To: [email protected]
Subject: RE: [mojo-user] was6 maven plugin
Ok. Thanks for confirming. I did that and I ran into some issues where jndi
lookups were failing. Looks like I had some IBM bindings in my project. I
think I'm on the right track now.
Thanks,
Matt
________________________________
From: quints quad [[email protected]]
Sent: Monday, August 16, 2010 3:49 PM
To: [email protected]
Subject: Re: [mojo-user] was6 maven plugin
That argument is set when you create the default bindings for the ear. Your
execution would look something like the following:
<properties>
<property>
<VirtualHost>default_host</VirtualHost>
</property>
</properties>
...
<execution>
<id>deploy-snapshot</id>
<phase>deploy</phase>
<goals>
<goal>wsDefaultBindings</goal>
<goal>installApp</goal>
</goals>
<configuration>
<virtualHost>${VirtualHost}</virtualHost>
<forceBindings>true</forceBindings>
</configuration>
</execution>
You can look at more here:
http://mojo.codehaus.org/was6-maven-plugin/wsDefaultBindings-mojo.html
On Mon, Aug 16, 2010 at 2:11 PM, Matt Goodwin
<[email protected]<mailto:[email protected]>> wrote:
How do you pass parameters to the was6:installApp goal. I would like to pass
the -MapWebModToVH argument to the installApp goal.
Thanks,
Matt
