Install is successful after replacing pom in local repositary . Thanx . Gert Vanthienen <[EMAIL PROTECTED]> wrote: Kumar,
This is probably the same problem as is mentioned in http://www.nabble.com/Failed-to-run-the-Loan-Broker-BPEL-example-tf4090764s12049.html and https://issues.apache.org/activemq/browse/SM-997. For the moment, the only solution would be to use the workaround mentioned in the first thread or update the pom.xml file in your local repository with the one you can find at http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.1.1/pom.xml Gert kumar k wrote: > I created a su for jms component as consumer. When I do mvn install I am > getting following error. I am using 3.1.1. > > > [INFO] Error building POM (may not be this project's POM). > > Project ID: org.apache.servicemix.tooling:tooling:pom:3.1.1-incubating > Reason: Cannot find parent: org.apache.servicemix:servicemix for project: > org.apache.servicemix.tooling:tooling:pom:3.1.1-incubating for project > org.apache.servicemix.tooling:tooling:pom:3.1.1-incubating > > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build > project for plugin 'org.apache.servicemix.tooling:jbi-maven-plugin': Cannot > find parent: org.apache.servicemix:servicemix for project: > org.apache.servicemix.tooling:tooling:pom:3.1.1-incubating for project > org.apache.servicemix.tooling:tooling:pom:3.1.1-incubating > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeHandlers(DefaultLifecycleExecutor.java:1176) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:178) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:141) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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.InvalidPluginException: Unable to build > project for plugin 'org.apache.servicemix.tooling:jbi-maven-plugin': Cannot > find parent: org.apache.servicemix:servicemix for project: > org.apache.servicemix.tooling:tooling:pom:3.1.1-incubating for project > org.apache.servicemix.tooling:tooling:pom:3.1.1-incubating > at > org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:276) > at > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:192) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:171) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1257) > ... 14 more > Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find > parent: org.apache.servicemix:servicemix for project: > org.apache.servicemix.tooling:tooling:pom:3.1.1-incubating for project > org.apache.servicemix.tooling:tooling:pom:3.1.1-incubating > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1261) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1278) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:747) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236) > at > org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:260) > ... 17 more > Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error > reading POM. Reason: end tag name must match start tag name from line 819 > (position: TEXT seen ...\n ... @820:18) for project > org.apache.servicemix:servicemix at C:\Documents and > Settings\KumarA\.m2\repository\org\apache\servicemix\servicemix\3.1.1-incubating\servicemix-3.1.1-incubating.pom > at > org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1422) > at > org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1379) > at > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:530) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1257) > ... 21 more > Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag > name must match start tag name from line 819 (position: TEXT seen ...\n ... > @820:18) > at org.codehaus.plexus.util.xml.pull.MXParser.parseEndTag(MXParser.java:1686) > at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1128) > at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090) > at org.codehaus.plexus.util.xml.pull.MXParser.nextTag(MXParser.java:1077) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseDependency(MavenXpp3Reader.java:1162) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseDependencyManagement(MavenXpp3Reader.java:1297) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2356) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4422) > at > org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1418) > ... 24 more > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: < 1 second > [INFO] Finished at: Wed Jul 18 18:11:30 GMT+05:30 2007 > [INFO] Final Memory: 1M/2M > > Gert Vanthienen wrote: > Kumar, > > If you take a look in the repository (at > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/tooling/servicemix-bean-service-unit/), > > you'll notive that this archetype is only available since version > 3.1.1-incubating... > > Gert > > kumar k wrote: >> I am trying to create a su for servicemix-bean with following arguments but >> it gives an error saying can't get from specified repository. Probably value >> of DarchetypeArtifactId is not correct. Please advise. >> >> mvn archetype:create \ >> -DarchetypeGroupId=org.apache.servicemix.tooling \ >> -DarchetypeArtifactId=servicemix-bean-service-unit \ >> -DarchetypeVersion=3.1-incubating \ >> -DgroupId=com.mycompany \ >> -DartifactId=my-processor-su \ >> -DremoteRepositories=http://people.apache.org/repo/m2-incubating-repository >> >> >> Bruce Snyder > wrote: On 7/17/07, kumar k wrote: >>> I want to write a class which can receive messages from my jms >>> component i.e. messages put on this jms queue should be delivered to my >>> class >>> which will do processing for messages. My question is how do I tell >>> xbean configuration that which class/method should receive the message for >>> processing?Is it decided by service and end point?Has it to be a web >>> service?If I want it to be a POJO what I need to specify for service and >>> end point? Or something else is needed altogether? >>> >>>> endpoint="jms" >>> targetService="test:MyConsumerService" >>> targetEndpoint="myConsumer" >>> role="consumer" >>> destinationStyle="queue" >>> jmsProviderDestinationName="queue/A" >>> jndiConnectionFactoryName="ConnectionFactory" >>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; >>> defaultOperation="test:Echo" /> >> The service is the name of this service whereas the targetService >> should be the name of the service to which you would like to send the >> messages consumed from the queue. If you'd like to write your own POJO >> to process the messages, I would suggest looking at using the >> servicemix-bean component. This component allows you to use a POJO to >> process JBI messages by implementing the MessageExchangeListener >> interface. >> >> Bruce > > > > --------------------------------- > Sucker-punch spam with award-winning protection. > Try the free Yahoo! Mail Beta. --------------------------------- Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. --------------------------------- Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us.
