Note the deploying things moves them to the services data directory - and they are referenced from there.
You could use the Maven plugin to deploy to production, however you might want to use the generated SA's and Installers to provide control - since you could copy these ZIP's to your UAT/Integration environment and then use the exact same deployables in your production environment. Cheers P On 10/23/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
FYI, the maven jbi plugin uses the JBI standard way of deploying JBI artifacts. They are copied into servicemix workspace. On 10/23/06, moraleslos <[EMAIL PROTECTED]> wrote: > > Just curious, is this the preferred way of automatically deploying an SA in a > production environment? I can see this projectDeploy useful for testing but > I'm just not used to having something deployed and not reside in the > server's own directory in production. Any suggestions on this? Thanks in > advance. > > -los > > > Philip Dodds-2 wrote: > > > > Great - thanks > > > > the SA actually gets deployed from the copy in the target directory > > under your project, since this is where the SA was built by Maven. > > > > Thanks > > > > P > > > > On 10/23/06, moraleslos <[EMAIL PROTECTED]> wrote: > >> > >> Ok, will do once JIRA is back up and running. > >> > >> BTW, regarding projectDeploy, I was curious as to how the SA gets > >> deployed. > >> I can see that smx picks it up via the console window but I do not see a > >> physical deployment of the SA anywhere. For example, the > >> %smx_home%\deploy > >> or %smx_home%\install are still empty even though my SA is up and > >> running. > >> I'm curious since I want to be able to know where my SAs are in > >> production... Thanks in advance. > >> > >> -los > >> > >> > >> Philip Dodds-2 wrote: > >> > > >> > I don't believe this is possible right now - but it does sound like an > >> > interesting feature - can you raise a JIRA for it :) > >> > > >> > P > >> > > >> > On 10/20/06, moraleslos <[EMAIL PROTECTED]> wrote: > >> >> > >> >> My bad... It works completely. I accidently removed a <dependency> > >> from > >> >> my > >> >> SU POM when I did a copy/paste... It finally works!!! > >> >> > >> >> I do have another question though. When I do this from the command > >> line, > >> >> i.e. mvn jbi:projectDeploy, I need to go all the way to my jbi > >> directory. > >> >> For example, here is how my project structure is set up: > >> >> > >> >> -->/core > >> >> --> pom.xml > >> >> -->/integration > >> >> -->pom.xml > >> >> -->/integration-common > >> >> -->pom.xml > >> >> -->/integration-servicemix > >> >> -->pom.xml > >> >> -->/integration-servicemix-jbi > >> >> -->pom.xml > >> >> > >> >> Now, when I do my mvn clean/compile/..., I do this at the root > >> directory, > >> >> i.e. /core. When I do mvn:projectDeploy, I can not do it at the root > >> >> (complains about not finding jbi-service-assembly). I have to go down > >> to > >> >> the integration-servicemix-jbi and run the projectDeploy command. Is > >> >> there > >> >> a way to have this done at the root and recurse to all the JBI-related > >> >> directories? Therefore, if I have more than one SA to deploy, I can > >> >> still > >> >> do it from the root directory where maven will recurse and deploy all > >> of > >> >> the > >> >> SAs... Thanks in advance. > >> >> > >> >> -los > >> >> > >> >> > >> >> moraleslos wrote: > >> >> > > >> >> > Hi Philip, > >> >> > > >> >> > Thanks for the reply. Looks like your suggestion got me very far > >> now. > >> >> I > >> >> > changed everything you said and looks like it tries to deploy to > >> >> > servicemix but I'm getting this error: > >> >> > > >> >> > ********************************** > >> >> > Caused by: org.springframework.beans.FatalBeanException: Unable to > >> >> resolve > >> >> > classpath location lib/test-integration-common-1.0-SNAPSHOT.jar > >> >> > at > >> >> > > >> >> > >> org.apache.xbean.server.spring.configuration.ClassLoaderXmlPreprocessor.preprocess(ClassLoaderXmlPreprocessor.java:117) > >> >> > at > >> >> > > >> >> > >> org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.preprocess(XBeanXmlBeanDefinitionReader.java:93) > >> >> > at > >> >> > > >> >> > >> org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.registerBeanDefinitions(XBeanXmlBeanDefinitionReader.java:78) > >> >> > at > >> >> > > >> >> > >> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:406) > >> >> > ... 50 more > >> >> > ************************************* > >> >> > > >> >> > My servicemix.xml in my SU-- called test-integration-servicemix-- > >> has a > >> >> > classpath referencing the test-integration-common.jar since the SU > >> has > >> >> a > >> >> > dependence on it: > >> >> > > >> >> > <classpath> > >> >> > <location>.</location> > >> >> > > >> >> <location>lib/test-integration-common-1.0-SNAPSHOT.jar</location> > >> >> > </classpath> > >> >> > > >> >> > So running maven, all the clean/compile/install/package/install > >> works > >> >> > successfully, and hence I think all the dependencies in the POMs > >> check > >> >> out > >> >> > ok. Now its when I run mvn jbi:packageDeploy that I'm running into > >> >> this > >> >> > issue. Got anymore ideas? I appreciate it. Thanks! > >> >> > > >> >> > -los > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > Philip Dodds-2 wrote: > >> >> >> > >> >> >> Can you try using something like the following : > >> >> >> > >> >> >> <?xml version="1.0" encoding="UTF-8"?> > >> >> >> <!-- > >> >> >> > >> >> >> Licensed to the Apache Software Foundation (ASF) under one or > >> more > >> >> >> contributor license agreements. See the NOTICE file > >> distributed > >> >> with > >> >> >> this work for additional information regarding copyright > >> >> ownership. > >> >> >> The ASF licenses this file to You under the Apache License, > >> >> Version > >> >> >> 2.0 > >> >> >> (the "License"); you may not use this file except in compliance > >> >> with > >> >> >> the License. You may obtain a copy of the License at > >> >> >> > >> >> >> http://www.apache.org/licenses/LICENSE-2.0 > >> >> >> > >> >> >> Unless required by applicable law or agreed to in writing, > >> >> software > >> >> >> distributed under the License is distributed on an "AS IS" > >> BASIS, > >> >> >> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or > >> >> >> implied. > >> >> >> See the License for the specific language governing permissions > >> >> and > >> >> >> limitations under the License. > >> >> >> > >> >> >> --> > >> >> >> <project 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/maven-v4_0_0.xsd";> > >> >> >> <modelVersion>4.0.0</modelVersion> > >> >> >> <groupId>org.mycompany</groupId> > >> >> >> <artifactId>my-lw-su</artifactId> > >> >> >> <packaging>jbi-service-unit</packaging> > >> >> >> <version>1.0-SNAPSHOT</version> > >> >> >> <name>A LWContainer Service Unit</name> > >> >> >> <url>http://www.myorganization.org</url> > >> >> >> <pluginRepositories> > >> >> >> <pluginRepository> > >> >> >> <id>apache.snapshots</id> > >> >> >> <name>Maven Central Plugins Development Repository</name> > >> >> >> > >> >> <url>http://people.apache.org/repo/m2-incubating-repository/</url> > >> >> >> <snapshots> > >> >> >> <enabled>true</enabled> > >> >> >> </snapshots> > >> >> >> <releases> > >> >> >> <enabled>true</enabled> > >> >> >> </releases> > >> >> >> </pluginRepository> > >> >> >> </pluginRepositories> > >> >> >> <repositories> > >> >> >> <repository> > >> >> >> <id>apache.snapshots</id> > >> >> >> <name>Maven Central Plugins Development Repository</name> > >> >> >> > >> >> <url>http://people.apache.org/repo/m2-incubating-repository/</url> > >> >> >> <snapshots> > >> >> >> <enabled>true</enabled> > >> >> >> </snapshots> > >> >> >> <releases> > >> >> >> <enabled>true</enabled> > >> >> >> </releases> > >> >> >> </repository> > >> >> >> </repositories> > >> >> >> <properties> > >> >> >> > >> >> <servicemix-version>3.1-incubating-SNAPSHOT</servicemix-version> > >> >> >> </properties> > >> >> >> <dependencies> > >> >> >> <dependency> > >> >> >> <groupId>org.apache.servicemix</groupId> > >> >> >> <artifactId>servicemix-lwcontainer</artifactId> > >> >> >> <version>3.0-incubating</version> > >> >> >> </dependency> > >> >> >> <dependency> > >> >> >> <groupId>org.apache.servicemix</groupId> > >> >> >> <artifactId>servicemix-core</artifactId> > >> >> >> <version>3.0-incubating</version> > >> >> >> <scope>provided</scope> > >> >> >> </dependency> > >> >> >> </dependencies> > >> >> >> <build> > >> >> >> <resources> > >> >> >> <resource> > >> >> >> <directory>src/main/resources</directory> > >> >> >> <includes> > >> >> >> <include>**/*</include> > >> >> >> </includes> > >> >> >> </resource> > >> >> >> </resources> > >> >> >> <plugins> > >> >> >> <plugin> > >> >> >> <groupId>org.apache.servicemix.tooling</groupId> > >> >> >> <artifactId>jbi-maven-plugin</artifactId> > >> >> >> <version>3.0-incubating</version> > >> >> >> <extensions>true</extensions> > >> >> >> </plugin> > >> >> >> </plugins> > >> >> >> </build> > >> >> >> </project> > >> >> >> > >> >> >> > >> >> >> There are a couple of things - first its best to reference the > >> final > >> >> >> release for 3.0 and also you'll probably need to add the > >> repositories > >> >> >> to pick it up :) > >> >> >> > >> >> >> Thanks > >> >> >> > >> >> >> P > >> >> >> > >> >> >> On 10/19/06, moraleslos <[EMAIL PROTECTED]> wrote: > >> >> >>> > >> >> >>> that was a copy/paste typo... its correct for SA, but in the SU > >> its > >> >> >>> > >> >> >>> <dependency> > >> >> >>> <groupId>com.test.integration.common</groupId> > >> >> >>> <artifactId>test-integration-common</artifactId> > >> >> >>> <version>1.0-SNAPSHOT</version> > >> >> >>> </dependency> > >> >> >>> > >> >> >>> The SU has dependencies on the common package, and the SA depends > >> on > >> >> the > >> >> >>> SU... > >> >> >>> > >> >> >>> -los > >> >> >>> > >> >> >>> > >> >> >>> Philip Dodds-2 wrote: > >> >> >>> > > >> >> >>> > Just to clarify what is this other dependency? > >> >> >>> > > >> >> >>> > <dependency> > >> >> >>> > <groupId>com.test.integration.servicemix</groupId> > >> >> >>> > > >> <artifactId>test-integration-servicemix</artifactId> > >> >> >>> > <version>1.0-SNAPSHOT</version> > >> >> >>> > <scope>runtime</scope> > >> >> >>> > </dependency> > >> >> >>> > > >> >> >>> > P > >> >> >>> > > >> >> >>> > > >> >> >>> > On 10/19/06, moraleslos <[EMAIL PROTECTED]> wrote: > >> >> >>> >> > >> >> >>> >> These class not found issues I'm getting does not seem to be > >> >> related > >> >> >>> to > >> >> >>> >> how > >> >> >>> >> the dependencies are added in the pom. I've added this > >> >> dependency: > >> >> >>> >> > >> >> >>> >> <dependency> > >> >> >>> >> <groupId>org.apache.servicemix</groupId> > >> >> >>> >> <artifactId>servicemix-jbi</artifactId> > >> >> >>> >> <version>3.0-incubating-SNAPSHOT</version> > >> >> >>> >> </dependency> > >> >> >>> >> > >> >> >>> >> in all of my pom files and I still get this error: > >> >> >>> >> > >> >> >>> >> ************************************************* > >> >> >>> >> [INFO] Unable to deploy project, Error accessing ServiceMix > >> >> >>> >> administration > >> >> >>> >> > >> >> >>> >> javax/jbi/management/LifeCycleMBean > >> >> >>> >> [INFO] > >> >> >>> >> > >> >> >>> > >> >> > >> ------------------------------------------------------------------------ > >> >> >>> >> [DEBUG] Trace > >> >> >>> >> org.apache.maven.lifecycle.LifecycleExecutionException: Unable > >> to > >> >> >>> deploy > >> >> >>> >> project > >> >> >>> >> , Error accessing ServiceMix administration > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > >> >> >>> >> ultLifecycleExecutor.java:559) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > >> >> >>> >> Goal(DefaultLifecycleExecutor.java:488) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > >> >> >>> >> ltLifecycleExecutor.java:458) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > >> >> >>> >> dleFailures(DefaultLifecycleExecutor.java:306) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > >> >> >>> >> ts(DefaultLifecycleExecutor.java:273) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > >> >> >>> >> fecycleExecutor.java:140) > >> >> >>> >> at > >> >> >>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > >> >> >>> >> at > >> >> >>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > >> >> >>> >> at > >> org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > >> >> >>> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > >> >> >>> Method) > >> >> >>> >> at > >> >> >>> >> > >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > >> >> >>> >> java:39) > >> >> >>> >> at > >> >> >>> >> > >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > >> >> >>> >> sorImpl.java:25) > >> >> >>> >> at java.lang.reflect.Method.invoke(Method.java:585) > >> >> >>> >> at > >> >> >>> >> > >> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > >> >> >>> >> at > >> >> >>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > >> >> >>> >> at > >> >> >>> >> > >> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > >> >> >>> >> > >> >> >>> >> at > >> >> org.codehaus.classworlds.Launcher.main(Launcher.java:375) > >> >> >>> >> Caused by: org.apache.maven.plugin.MojoExecutionException: > >> Unable > >> >> to > >> >> >>> >> deploy > >> >> >>> >> proj > >> >> >>> >> ect, Error accessing ServiceMix administration > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.servicemix.maven.plugin.jbi.JbiProjectDeployerMojo.deployP > >> >> >>> >> roject(JbiProjectDeployerMojo.java:146) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.servicemix.maven.plugin.jbi.JbiProjectDeployerMojo.execute > >> >> >>> >> (JbiProjectDeployerMojo.java:75) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > >> >> >>> >> nManager.java:412) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > >> >> >>> >> ultLifecycleExecutor.java:534) > >> >> >>> >> ... 16 more > >> >> >>> >> Caused by: Error accessing ServiceMix administration > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.jav > >> >> >>> >> a:272) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.servicemix.maven.plugin.jbi.JbiProjectDeployerMojo.isDeplo > >> >> >>> >> yed(JbiProjectDeployerMojo.java:194) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.servicemix.maven.plugin.jbi.JbiProjectDeployerMojo.deployP > >> >> >>> >> roject(JbiProjectDeployerMojo.java:120) > >> >> >>> >> ... 19 more > >> >> >>> >> Caused by: java.lang.NoClassDefFoundError: > >> >> >>> >> javax/jbi/management/LifeCycleMBean > >> >> >>> >> at java.lang.ClassLoader.defineClass1(Native Method) > >> >> >>> >> at > >> java.lang.ClassLoader.defineClass(ClassLoader.java:620) > >> >> >>> >> at > >> >> >>> >> > >> >> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 > >> >> >>> >> 4) > >> >> >>> >> at > >> >> >>> java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > >> >> >>> >> at > >> >> java.net.URLClassLoader.access$100(URLClassLoader.java:56) > >> >> >>> >> at > >> java.net.URLClassLoader$1.run(URLClassLoader.java:195) > >> >> >>> >> at java.security.AccessController.doPrivileged(Native > >> >> Method) > >> >> >>> >> at > >> >> java.net.URLClassLoader.findClass(URLClassLoader.java:188) > >> >> >>> >> at > >> java.lang.ClassLoader.loadClass(ClassLoader.java:306) > >> >> >>> >> at > >> >> >>> >> > >> >> org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassL > >> >> >>> >> oader.java:195) > >> >> >>> >> at > >> >> >>> >> > >> >> org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassReal > >> >> >>> >> m.java:255) > >> >> >>> >> at > >> >> >>> >> > >> >> org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader. > >> >> >>> >> java:214) > >> >> >>> >> at > >> java.lang.ClassLoader.loadClass(ClassLoader.java:251) > >> >> >>> >> at > >> >> >>> java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > >> >> >>> >> at java.lang.Class.forName0(Native Method) > >> >> >>> >> at java.lang.Class.forName(Class.java:164) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.servicemix.jbi.management.task.JbiTask.class$(JbiTask.java > >> >> >>> >> :123) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.servicemix.jbi.management.task.JbiTask.getAdminCommandsSer > >> >> >>> >> vice(JbiTask.java:123) > >> >> >>> >> at > >> >> >>> >> > >> >> org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.jav > >> >> >>> >> a:268) > >> >> >>> >> ... 21 more > >> >> >>> >> ************************************* > >> >> >>> >> > >> >> >>> >> Funny thing is that the servicemix-jbi-3.0-incubating.jar is in > >> >> the > >> >> >>> >> %smx_home%\lib directory so I don't really know how to continue > >> >> >>> debugging > >> >> >>> >> this. > >> >> >>> >> > >> >> >>> >> -los > >> >> >>> >> > >> >> >>> >> > >> >> >>> >> Philip Dodds-2 wrote: > >> >> >>> >> > > >> >> >>> >> > Can you try using the following? > >> >> >>> >> > > >> >> >>> >> > <packaging>jbi-service-unit</packaging> > >> >> >>> >> > <version>1.0-SNAPSHOT</version> > >> >> >>> >> > <dependencies> > >> >> >>> >> > <dependency> > >> >> >>> >> > <groupId>org.apache.servicemix</groupId> > >> >> >>> >> > > >> <artifactId>servicemix-lwcontainer</artifactId> > >> >> >>> >> > <version>3.0-incubating-SNAPSHOT</version> > >> >> >>> >> > </dependency> > >> >> >>> >> > <dependency> > >> >> >>> >> > > >> >> <groupId>com.test.integration.servicemix</groupId> > >> >> >>> >> > > >> >> <artifactId>test-integration-servicemix</artifactId> > >> >> >>> >> > <version>1.0-SNAPSHOT</version> > >> >> >>> >> > <scope>runtime</scope> > >> >> >>> >> > </dependency> > >> >> >>> >> > </dependencies> > >> >> >>> >> > <properties> > >> >> >>> >> > <componentName>servicemix-lwcontainer</componentName> > >> >> >>> >> > </properties> > >> >> >>> >> > > >> >> >>> >> > I'm not sure why you have a dependency on > >> >> >>> test-integration-servicemix > >> >> >>> >> > in both your SU and you SA? > >> >> >>> >> > > >> >> >>> >> > Cheers > >> >> >>> >> > P > >> >> >>> >> > > >> >> >>> >> > On 10/19/06, moraleslos <[EMAIL PROTECTED]> wrote: > >> >> >>> >> >> > >> >> >>> >> >> I'm running smx 3.0. As for component dependencies, I'm not > >> >> >>> exactly > >> >> >>> >> sure > >> >> >>> >> >> what you are describing so I'll just post my poms: > >> >> >>> >> >> > >> >> >>> >> >> SU pom: > >> >> >>> >> >> ********************************* > >> >> >>> >> >> ..... > >> >> >>> >> >> <packaging>jbi-service-unit</packaging> > >> >> >>> >> >> <version>1.0-SNAPSHOT</version> > >> >> >>> >> >> <dependencies> > >> >> >>> >> >> <dependency> > >> >> >>> >> >> <groupId>org.apache.servicemix</groupId> > >> >> >>> >> >> <artifactId>servicemix-core</artifactId> > >> >> >>> >> >> <version>3.0-incubating-SNAPSHOT</version> > >> >> >>> >> >> <scope>provided</scope> > >> >> >>> >> >> </dependency> > >> >> >>> >> >> <dependency> > >> >> >>> >> >> <groupId>org.apache.servicemix</groupId> > >> >> >>> >> >> <artifactId>servicemix-jbi</artifactId> > >> >> >>> >> >> <version>3.0-incubating-SNAPSHOT</version> > >> >> >>> >> >> <scope>provided</scope> > >> >> >>> >> >> </dependency> > >> >> >>> >> >> <dependency> > >> >> >>> >> >> <groupId>geronimo-spec</groupId> > >> >> >>> >> >> <artifactId>geronimo-spec-activation</artifactId> > >> >> >>> >> >> <version>1.0.2-rc4</version> > >> >> >>> >> >> <scope>provided</scope> > >> >> >>> >> >> </dependency> > >> >> >>> >> >> <dependency> > >> >> >>> >> >> > >> >> <groupId>com.test.integration.servicemix</groupId> > >> >> >>> >> >> > >> >> >>> <artifactId>test-integration-servicemix</artifactId> > >> >> >>> >> >> <version>1.0-SNAPSHOT</version> > >> >> >>> >> >> <scope>runtime</scope> > >> >> >>> >> >> </dependency> > >> >> >>> >> >> </dependencies> > >> >> >>> >> >> <properties> > >> >> >>> >> >> > >> <componentName>servicemix-lwcontainer</componentName> > >> >> >>> >> >> </properties> > >> >> >>> >> >> ... > >> >> >>> >> >> ********************************** > >> >> >>> >> >> > >> >> >>> >> >> > >> >> >>> >> >> SA pom: > >> >> >>> >> >> ********************************* > >> >> >>> >> >> ... > >> >> >>> >> >> <packaging>jbi-service-assembly</packaging> > >> >> >>> >> >> <version>1.0-SNAPSHOT</version> > >> >> >>> >> >> <dependencies> > >> >> >>> >> >> <dependency> > >> >> >>> >> >> > >> >> <groupId>com.test.integration.servicemix</groupId> > >> >> >>> >> >> > >> >> >>> <artifactId>test-integration-servicemix</artifactId> > >> >> >>> >> >> <version>1.0-SNAPSHOT</version> > >> >> >>> >> >> </dependency> > >> >> >>> >> >> </dependencies> > >> >> >>> >> >> ... > >> >> >>> >> >> *********************************** > >> >> >>> >> >> > >> >> >>> >> >> Is this what you were looking for? > >> >> >>> >> >> > >> >> >>> >> >> -los > >> >> >>> >> >> > >> >> >>> >> >> > >> >> >>> >> >> Philip Dodds-2 wrote: > >> >> >>> >> >> > > >> >> >>> >> >> > The Maven plugin should be able to deploy in the example > >> you > >> >> >>> gave, > >> >> >>> >> in > >> >> >>> >> >> > fact you can also run ServiceMix under Maven using > >> >> >>> jbi:servicemix > >> >> >>> >> >> > which would work - as long as your Service Units have a > >> >> >>> dependency > >> >> >>> >> to > >> >> >>> >> >> > their Components (since it uses this to ensure the > >> components > >> >> >>> are > >> >> >>> >> >> > deployed). > >> >> >>> >> >> > > >> >> >>> >> >> > I'm wondering if you are hitting a problem with either the > >> >> >>> >> ServiceMix > >> >> >>> >> >> > versions (which version of smx are you running against) or > >> >> have > >> >> >>> you > >> >> >>> >> >> > added servicemix-core as provided maybe? > >> >> >>> >> >> > > >> >> >>> >> >> > Thanks > >> >> >>> >> >> > > >> >> >>> >> >> > P > >> >> >>> >> >> > > >> >> >>> >> >> > On 10/19/06, moraleslos <[EMAIL PROTECTED]> wrote: > >> >> >>> >> >> >> > >> >> >>> >> >> >> Well, looks like it can't find the LifeCycleMBean class: > >> >> >>> >> >> >> > >> >> >>> >> >> >> *********************************************** > >> >> >>> >> >> >> [INFO] Unable to deploy project, Error accessing > >> ServiceMix > >> >> >>> >> >> >> administration > >> >> >>> >> >> >> > >> >> >>> >> >> >> javax/jbi/management/LifeCycleMBean > >> >> >>> >> >> >> [INFO] > >> >> >>> >> >> >> > >> >> >>> >> >> > >> >> >>> >> > >> >> >>> > >> >> > >> ------------------------------------------------------------------------ > >> >> >>> >> >> >> [DEBUG] Trace > >> >> >>> >> >> >> org.apache.maven.lifecycle.LifecycleExecutionException: > >> >> Unable > >> >> >>> to > >> >> >>> >> >> deploy > >> >> >>> >> >> >> project > >> >> >>> >> >> >> , Error accessing ServiceMix administration > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > >> >> >>> >> >> >> ultLifecycleExecutor.java:559) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > >> >> >>> >> >> >> Goal(DefaultLifecycleExecutor.java:488) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > >> >> >>> >> >> >> ltLifecycleExecutor.java:458) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > >> >> >>> >> >> >> dleFailures(DefaultLifecycleExecutor.java:306) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > >> >> >>> >> >> >> ts(DefaultLifecycleExecutor.java:273) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > >> >> >>> >> >> >> fecycleExecutor.java:140) > >> >> >>> >> >> >> at > >> >> >>> >> >> > >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > >> >> >>> >> >> >> at > >> >> >>> >> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > >> >> >>> >> >> >> at > >> >> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > >> >> >>> >> >> >> at > >> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native > >> >> >>> >> Method) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > >> >> >>> >> >> >> java:39) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > >> >> >>> >> >> >> sorImpl.java:25) > >> >> >>> >> >> >> at > >> java.lang.reflect.Method.invoke(Method.java:585) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> > >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > >> >> >>> >> >> >> at > >> >> >>> >> org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > >> >> >>> >> >> >> > >> >> >>> >> >> >> at > >> >> >>> >> org.codehaus.classworlds.Launcher.main(Launcher.java:375) > >> >> >>> >> >> >> Caused by: > >> org.apache.maven.plugin.MojoExecutionException: > >> >> >>> Unable > >> >> >>> >> to > >> >> >>> >> >> >> deploy > >> >> >>> >> >> >> proj > >> >> >>> >> >> >> ect, Error accessing ServiceMix administration > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.servicemix.maven.plugin.jbi.JbiProjectDeployerMojo.deployP > >> >> >>> >> >> >> roject(JbiProjectDeployerMojo.java:146) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.servicemix.maven.plugin.jbi.JbiProjectDeployerMojo.execute > >> >> >>> >> >> >> (JbiProjectDeployerMojo.java:75) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > >> >> >>> >> >> >> nManager.java:412) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > >> >> >>> >> >> >> ultLifecycleExecutor.java:534) > >> >> >>> >> >> >> ... 16 more > >> >> >>> >> >> >> Caused by: Error accessing ServiceMix administration > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.jav > >> >> >>> >> >> >> a:272) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.servicemix.maven.plugin.jbi.JbiProjectDeployerMojo.isDeplo > >> >> >>> >> >> >> yed(JbiProjectDeployerMojo.java:194) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.servicemix.maven.plugin.jbi.JbiProjectDeployerMojo.deployP > >> >> >>> >> >> >> roject(JbiProjectDeployerMojo.java:120) > >> >> >>> >> >> >> ... 19 more > >> >> >>> >> >> >> Caused by: java.lang.NoClassDefFoundError: > >> >> >>> >> >> >> javax/jbi/management/LifeCycleMBean > >> >> >>> >> >> >> at java.lang.ClassLoader.defineClass1(Native > >> Method) > >> >> >>> >> >> >> at > >> >> >>> java.lang.ClassLoader.defineClass(ClassLoader.java:620) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 > >> >> >>> >> >> >> 4) > >> >> >>> >> >> >> at > >> >> >>> >> >> java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > >> >> >>> >> >> >> at > >> >> >>> >> java.net.URLClassLoader.access$100(URLClassLoader.java:56) > >> >> >>> >> >> >> at > >> >> >>> java.net.URLClassLoader$1.run(URLClassLoader.java:195) > >> >> >>> >> >> >> at > >> >> java.security.AccessController.doPrivileged(Native > >> >> >>> >> Method) > >> >> >>> >> >> >> at > >> >> >>> >> java.net.URLClassLoader.findClass(URLClassLoader.java:188) > >> >> >>> >> >> >> at > >> >> >>> java.lang.ClassLoader.loadClass(ClassLoader.java:306) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassL > >> >> >>> >> >> >> oader.java:195) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassReal > >> >> >>> >> >> >> m.java:255) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader. > >> >> >>> >> >> >> java:214) > >> >> >>> >> >> >> at > >> >> >>> java.lang.ClassLoader.loadClass(ClassLoader.java:251) > >> >> >>> >> >> >> at > >> >> >>> >> >> > >> java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > >> >> >>> >> >> >> at java.lang.Class.forName0(Native Method) > >> >> >>> >> >> >> at java.lang.Class.forName(Class.java:164) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.servicemix.jbi.management.task.JbiTask.class$(JbiTask.java > >> >> >>> >> >> >> :123) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.servicemix.jbi.management.task.JbiTask.getAdminCommandsSer > >> >> >>> >> >> >> vice(JbiTask.java:123) > >> >> >>> >> >> >> at > >> >> >>> >> >> >> > >> >> >>> >> > >> >> org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.jav > >> >> >>> >> >> >> a:268) > >> >> >>> >> >> >> ... 21 more > >> >> >>> >> >> >> **************************************************** > >> >> >>> >> >> >> > >> >> >>> >> >> >> All I want to do is have a convenient build/deploy > >> process > >> >> >>> using > >> >> >>> >> >> Maven. > >> >> >>> >> >> >> Not > >> >> >>> >> >> >> sure what is the appropriate way to do this. With Ant, > >> I'm > >> >> >>> used to > >> >> >>> >> >> >> creating > >> >> >>> >> >> >> a deploy task which copies the jar/war/ear to the > >> >> appServer's > >> >> >>> >> deploy > >> >> >>> >> >> >> directory. So that is what I was *hoping* to accomplish > >> >> with > >> >> >>> Maven > >> >> >>> >> >> and > >> >> >>> >> >> >> deploying the SA onto ServiceMix. Now if there is a much > >> >> >>> better > >> >> >>> >> way > >> >> >>> >> >> of > >> >> >>> >> >> >> deploying SAs after a build, I would like your suggestion > >> on > >> >> >>> this. > >> >> >>> >> >> >> Thanks! > >> >> >>> >> >> >> > >> >> >>> >> >> >> -los > >> >> >>> >> >> >> > >> >> >>> >> >> >> > >> >> >>> >> >> >> Philip Dodds-2 wrote: > >> >> >>> >> >> >> > > >> >> >>> >> >> >> > The maven JBI plugins uses the JMX infrastructure to > >> >> deploy > >> >> >>> the > >> >> >>> >> >> >> > service assemblies from the target directory to the > >> server > >> >> - > >> >> >>> it > >> >> >>> >> >> >> > doesn't copy the files to the deploy or install > >> directory. > >> >> >>> >> >> >> > > >> >> >>> >> >> >> > Can you re-run with a -X to get the details of the > >> failure > >> >> :) > >> >> >>> >> >> >> > > >> >> >>> >> >> >> > Thanks > >> >> >>> >> >> >> > > >> >> >>> >> >> >> > P > >> >> >>> >> >> >> > > >> >> >>> >> >> >> > On 10/19/06, moraleslos <[EMAIL PROTECTED]> wrote: > >> >> >>> >> >> >> >> > >> >> >>> >> >> >> >> The final step in my build/deploy of my SA is to copy > >> the > >> >> SA > >> >> >>> >> >> created > >> >> >>> >> >> >> in > >> >> >>> >> >> >> >> my > >> >> >>> >> >> >> >> repo into the %servicemix_home%\deploy directory. I > >> was > >> >> >>> looking > >> >> >>> >> at > >> >> >>> >> >> >> the > >> >> >>> >> >> >> >> jbi:projectDeploy but don't really understand how this > >> >> >>> works. > >> >> >>> >> When > >> >> >>> >> >> I > >> >> >>> >> >> >> >> tried > >> >> >>> >> >> >> >> it, I get this message: > >> >> >>> >> >> >> >> > >> >> >>> >> >> >> >> ************************************** > >> >> >>> >> >> >> >> [INFO] > >> >> >>> >> >> >> >> > >> >> >>> >> >> >> > >> >> >>> >> >> > >> >> >>> >> > >> >> >>> > >> >> > >> ------------------------------------------------------------------------ > >> >> >>> >> >> >> >> [ERROR] BUILD ERROR > >> >> >>> >> >> >> >> [INFO] > >> >> >>> >> >> >> >> > >> >> >>> >> >> >> > >> >> >>> >> >> > >> >> >>> >> > >> >> >>> > >> >> > >> ------------------------------------------------------------------------ > >> >> >>> >> >> >> >> [INFO] Unable to deploy project, Error accessing > >> >> ServiceMix > >> >> >>> >> >> >> >> administration > >> >> >>> >> >> >> >> > >> >> >>> >> >> >> >> javax/jbi/management/LifeCycleMBean > >> >> >>> >> >> >> >> ************************************** > >> >> >>> >> >> >> >> > >> >> >>> >> >> >> >> Basically all I want to do is copy or move the zip > >> file > >> >> >>> >> >> respresenting > >> >> >>> >> >> >> my > >> >> >>> >> >> >> >> SA > >> >> >>> >> >> >> >> stored in my local repo into the /deploy directory of > >> >> >>> >> ServiceMix. > >> >> >>> >> >> How > >> >> >>> >> >> >> >> can I > >> >> >>> >> >> >> >> accomplish this with maven and/or corresponding jbi > >> >> goals? > >> >> >>> >> Thanks > >> >> >>> >> >> in > >> >> >>> >> >> >> >> advance. > >> >> >>> >> >> >> >> > >> >> >>> >> >> >> >> -los > >> >> >>> >> >> >> >> -- > >> >> >>> >> >> >> >> View this message in context: > >> >> >>> >> >> >> >> > >> >> >>> >> >> >> > >> >> >>> >> >> > >> >> >>> >> > >> >> >>> > >> >> > >> http://www.nabble.com/maven-jbi%3AprojectDeploy-question-tf2473814.html#a6897988 > >> >> >>> >> >> >> >> Sent from the ServiceMix - User mailing list archive > >> at > >> >> >>> >> Nabble.com. > >> >> >>> >> >> >> >> > >> >> >>> >> >> >> >> > >> >> >>> >> >> >> > > >> >> >>> >> >> >> > > >> >> >>> >> >> >> > >> >> >>> >> >> >> -- > >> >> >>> >> >> >> View this message in context: > >> >> >>> >> >> >> > >> >> >>> >> >> > >> >> >>> >> > >> >> >>> > >> >> > >> http://www.nabble.com/maven-jbi%3AprojectDeploy-question-tf2473814.html#a6898382 > >> >> >>> >> >> >> Sent from the ServiceMix - User mailing list archive at > >> >> >>> Nabble.com. > >> >> >>> >> >> >> > >> >> >>> >> >> >> > >> >> >>> >> >> > > >> >> >>> >> >> > > >> >> >>> >> >> > >> >> >>> >> >> -- > >> >> >>> >> >> View this message in context: > >> >> >>> >> >> > >> >> >>> >> > >> >> >>> > >> >> > >> http://www.nabble.com/maven-jbi%3AprojectDeploy-question-tf2473814.html#a6899085 > >> >> >>> >> >> Sent from the ServiceMix - User mailing list archive at > >> >> >>> Nabble.com. > >> >> >>> >> >> > >> >> >>> >> >> > >> >> >>> >> > > >> >> >>> >> > > >> >> >>> >> > >> >> >>> >> -- > >> >> >>> >> View this message in context: > >> >> >>> >> > >> >> >>> > >> >> > >> http://www.nabble.com/maven-jbi%3AprojectDeploy-question-tf2473814.html#a6901854 > >> >> >>> >> Sent from the ServiceMix - User mailing list archive at > >> >> Nabble.com. > >> >> >>> >> > >> >> >>> >> > >> >> >>> > > >> >> >>> > > >> >> >>> > >> >> >>> -- > >> >> >>> View this message in context: > >> >> >>> > >> >> > >> http://www.nabble.com/maven-jbi%3AprojectDeploy-question-tf2473814.html#a6902587 > >> >> >>> Sent from the ServiceMix - User mailing list archive at > >> Nabble.com. > >> >> >>> > >> >> >>> > >> >> >> > >> >> >> > >> >> > > >> >> > > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> http://www.nabble.com/maven-jbi%3AprojectDeploy-question-tf2473814.html#a6925348 > >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. > >> >> > >> >> > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/maven-jbi%3AprojectDeploy-question-tf2473814.html#a6953162 > >> Sent from the ServiceMix - User mailing list archive at Nabble.com. > >> > >> > > > > > > -- > View this message in context: http://www.nabble.com/maven-jbi%3AprojectDeploy-question-tf2473814.html#a6961826 > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet
