They are needed and they are being generated for my EJB project. On Jan 18, 2008 11:55 AM, Jeff Mutonho <[EMAIL PROTECTED]> wrote:
> On Jan 18, 2008 12:25 PM, Thomas Tardy <[EMAIL PROTECTED]> wrote: > > > Hello > > > > I'm not using a standalone WAS, I'm using the installation from the RSA7 > > installation. And the property is looking like yours, just applied to > the > > RSA7 installation structure. I'm not facing any problems with the > Windows > > 'Program Files' directory. > > > > I have defined the property in my settings.xml looking like this: > > > > <settings xmlns="http://maven.apache.org/POM/4.0.0"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > > http://maven.apache.org/xsd/settings-1.0.0.xsd";> > > > > <localRepository>C:\repos\maven</localRepository> > > > > <profiles> > > <profile> > > <id>default</id> > > <activation> > > <activeByDefault>true</activeByDefault> > > </activation> > > > > <properties> > > <custom.was.home>C:\Program > > Files\IBM\SDP70\runtimes\base_v61</custom.was.home> > > </properties> > > </profile> > > </profiles> > > </settings> > > > > Hope this helps! > > > > Kind Regards, > > Thomas > > > > > > On Jan 18, 2008 11:15 AM, Jeff Mutonho <[EMAIL PROTECTED]> wrote: > > > > > On Jan 18, 2008 11:43 AM, Thomas Tardy <[EMAIL PROTECTED]> wrote: > > > > > > > Hello, > > > > > > > > I haven't managed to get the example from Peter Pilgrim's blog > > working. > > > In > > > > the example they use the ant task. The problem I faced was, that you > > > have > > > > to > > > > initialize the runtime with lot of properties and I wasn't feeling > > like > > > > finding all the required properties. > > > > > > > > Therefore I'm unsing the bat-file or shellscript included in each > > > > websphere > > > > installation. It's setting up all the requiered properties. And in > the > > > > poms > > > > of my ejb projects it's looking like this. > > > > > > > > <plugins> > > > > <plugin> > > > > <artifactId>maven-antrun-plugin</artifactId> > > > > <executions> > > > > <execution> > > > > <phase>verify</phase> > > > > <configuration> > > > > <tasks> > > > > <property name="mvn.classpath" > refid=" > > > > maven.runtime.classpath" /> > > > > <exec > > > > executable="${custom.was.home}/bin/ejbdeploy.bat" > > > > failonerror="true" os="Windows XP"> > > > > <arg value="${ > > project.build.directory > > > > }/${project.artifactId}-${project.version}.jar" /> > > > > <arg > > > > value="${project.build.directory}/ejbdeply-working" > > > > /> > > > > <arg value="${ > > project.build.directory > > > > }/${project.artifactId}-${project.version}-OUTPUT.jar" /> > > > > <arg value="-cp" /> > > > > <arg value="${mvn.classpath}" /> > > > > </exec> > > > > <exec > > > > executable="${custom.was.home}/bin/ejbdeploy.sh" > > > > failonerror="true" os="Linux"> > > > > <arg value="${ > > project.build.directory > > > > }/${project.artifactId}-${project.version}.jar" /> > > > > <arg > > > > value="${project.build.directory}/ejbdeply-working" > > > > /> > > > > <arg value="${ > > project.build.directory > > > > }/${project.artifactId}-${project.version}-OUTPUT.jar" /> > > > > <arg value="-cp" /> > > > > <arg value="${mvn.classpath}" /> > > > > </exec> > > > > <move file="${project.build.directory > > }/${ > > > > project.artifactId}-${project.version}.jar" tofile="${ > > > > project.build.directory}/${project.artifactId}-${project.version}- > > > > INPUT.jar" > > > > /> > > > > <move file="${project.build.directory > > }/${ > > > > project.artifactId}-${project.version}-OUTPUT.jar" tofile="${ > > > > project.build.directory}/${project.artifactId}-${project.version > }.jar" > > > /> > > > > </tasks> > > > > </configuration> > > > > <goals> > > > > <goal>run</goal> > > > > </goals> > > > > </execution> > > > > </executions> > > > > </plugin> > > > > </plugins> > > > > > > > > It's working fine. The only condition you have is that you have > access > > > to > > > > a > > > > Websphere installation on the machine you are building the ejb. > > > > The ${custom.was.home} property is the path to the root directory of > > > your > > > > Websphere installation. > > > > > > > > Hope this helps! > > > > > > > > Kind Regards, > > > > Thomas > > > > Thanks Thomas.It worked finally. I , however noticed that the final ejb > jar > has EJSxyz.class files , but not the _EJBSxyv.class files.It seems like > they're not being generated , where's creating the jar using RAD does > generate the those _EJBxyz class files. > Arent these _EJSxyz.class files needed? > > > > > > "Don't take the name of root in vain." > > Jeff Mutonho > Cape Town > South Africa > > GoogleTalk : ejbengine > Skype : ejbengine > Registered Linux user number 366042 >
