On Fri, Mar 21, 2008 at 3:12 AM, David J. M. Karlsen
<[EMAIL PROTECTED]> wrote:
> Hi folks!
>
>  The was6-maven-plugin has just graduated, and released as version
>  1.0-alpha-1.
>
>  The plugin can be used to start and stop websphere 6.1 containers (ND or
>  standalone installations) and applications,
>  generate WAS specific bindings, generate EJB deployment code (stubs),
>  and run arbitrary scripts (JCAL/Jython) against WAS.
>  It's implemented as a wrapper around ws_ant - WAS's own wrapper around
>  ant and WAS ant tasks, which ensures the correct setup of environment.

Thanks for this, David. I tried it now, and I can start and stop the
server, but have some problems installing ear files into websphere via
the wsInstallApp goal. Some of the log output;

INFO] The ' characters around the executable and arguments are
[INFO] not part of the command.
[INFO]   [wsadmin] WASX7357I: By request, this scripting client is not
connected to any server process. Certain configuration and application
operations will be available in local mode.
[INFO]   [wsadmin] WASX7017E: Exception received while running file
"/tmp/wsant46650jacl"; exception information:
com.ibm.ws.scripting.ScriptingException: WASX7280E: An application
with name "cargoear" does not exist.
[INFO]
[ERROR]
[ERROR] BUILD FAILED
[ERROR] 
/usr/local/src/testcargo/testcargo/target/was6plugin/was6plugin-build.xml:23:
Java returned: 105

..and my configuration;

                        <configuration>
                            <wasHome>/usr/local/WebSphere/AppServer</wasHome>
                            <host>rohnny-laptop</host>
                            <applicationName>cargoear</applicationName>
                            <username>system</username>
                            <password>...</password>
                            <profileName>AppSrv02</profileName>

<earFile>/usr/local/src/testcargo/cargoear/target/cargoear.ear</earFile>
                            <verbose>true</verbose>
                        </configuration>

I am also curious why you want to create your own plugin for
websphere, instead of patching up cargo? As you know cargo is a nice
framework for this, and it shouldnt be much work integrating websphere
with cargo; I even think it is 90% done already.

Kind regards,
Rohnny

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to