tag:old.nabble.com,2006:forum-12049
Nabble - ServiceMix
2009-11-09T14:27:10Z
tag:old.nabble.com,2006:post-26274812
Re: Generating Camel SU with Maven
2009-11-09T14:27:10Z
2009-11-09T14:27:10Z
Kenneth H
Hi Willem,
<br><br>It finally works! I can now run the simple camel tutorial on the Servicemix homepage.
<br><br>It was not the spring-remoting-2.0.8.jar but the spring-support-2.0.6.jar that was something wrong with. In the directory where this jar is located the following files somehow was missing (don't know why):
<br><br>spring-support-2.0.6.jar.md5
<br>spring-support-2.0.6.pom.md5
<br>spring-support-2.0.6.pom
<br>spring-support-2.0.6.jar.sha1
<br>spring-support-2.0.6.pom.sha1
<br><br>I downloaded these files from <a href="http://repo1.maven.org/maven2" target="_top" rel="nofollow">http://repo1.maven.org/maven2</a> and ran mvn install again. Some new files were then missing and again I downloaded them from <a href="http://repo1.maven.org/maven2" target="_top" rel="nofollow">http://repo1.maven.org/maven2</a>. This happened 7 times and then it worked. Now time will show if this solution works for more complex configurations.
<br><br>Thanks for your time and effort Willem.
<br><br>Kind regards, Kenneth
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26273319
[jira] Commented: (SMXCOMP-638) NotSerializableException with JMSFlow when camel returns an exception.
2009-11-09T12:41:52Z
2009-11-09T12:41:52Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SMXCOMP-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55244#action_55244" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55244#action_55244</a> ]
<br><br>Giovani Seben commented on SMXCOMP-638:
<br>---------------------------------------
<br><br>@Gertv,
<br>I like your suggestion too, specially the serialization=strict, since there could be non-serializable objects aside from exceptions that are sent over the bus.
<br><br>-Gio
<br><div class='shrinkable-quote'><br>> NotSerializableException with JMSFlow when camel returns an exception.
<br>> -----------------------------------------------------------------------
<br>>
<br>> Key: SMXCOMP-638
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SMXCOMP-638" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-638</a><br>> Project: ServiceMix Components
<br>> Issue Type: Bug
<br>> Components: servicemix-camel
<br>> Affects Versions: servicemix-camel-2009.01
<br>> Reporter: Giovani Seben
<br>> Assignee: Gert Vanthienen
<br>> Attachments: fix.patch, JbiCamelExceptionsTest.java, MOD_testcase.patch, SMXCOMP-638.patch, smxcomp638.patch
<br>>
<br>>
<br>> In servicemix when a camel route handles an exception that is then returned to the NMR it will attempt to return the exception object with the exchange. Using JMSFlow if the exception object is not serializable, it will fail to be sent back with a NotSerializableException. This is similar to SMXCOMP-18, but instead the problem here happens with the CamelProviderEndpoint.
<br>> Below is the full exception stack trace:
<br>> {code}
<br>> java.lang.RuntimeException: org.apache.servicemix.camel.JbiExchange
<br>> at org.apache.activemq.command.ActiveMQObjectMessage.storeContent(ActiveMQObjectMessage.java:104)
<br>> at org.apache.activemq.command.ActiveMQObjectMessage.setObject(ActiveMQObjectMessage.java:155)
<br>> at org.apache.activemq.ActiveMQSession.createObjectMessage(ActiveMQSession.java:319)
<br>> at org.apache.activemq.pool.PooledSession.createObjectMessage(PooledSession.java:149)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.doRouting(AbstractJMSFlow.java:480)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.doSend(AbstractJMSFlow.java:435)
<br>> at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.send(AbstractFlow.java:126)
<br>> at org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(DefaultBroker.java:283)
<br>> at org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket(SecuredBroker.java:88)
<br>> at org.apache.servicemix.jbi.container.JBIContainer.sendExchange(JBIContainer.java:882)
<br>> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:396)
<br>> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:432)
<br>> at org.apache.servicemix.common.EndpointDeliveryChannel.send(EndpointDeliveryChannel.java:79)
<br>> at org.apache.servicemix.common.endpoints.SimpleEndpoint.send(SimpleEndpoint.java:70)
<br>> at org.apache.servicemix.common.endpoints.SimpleEndpoint.fail(SimpleEndpoint.java:94)
<br>> at org.apache.servicemix.camel.CamelProviderEndpoint.handleActiveProviderExchange(CamelProviderEndpoint.java:128)
<br>> at org.apache.servicemix.camel.CamelProviderEndpoint.process(CamelProviderEndpoint.java:73)
<br>> at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:540)
<br>> at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:492)
<br>> at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
<br>> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:623)
<br>> at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:183)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.access$401(AbstractJMSFlow.java:63)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow$4.run(AbstractJMSFlow.java:517)
<br>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
<br>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
<br>> at java.lang.Thread.run(Thread.java:595)
<br>> Caused by: java.io.NotSerializableException: org.apache.servicemix.camel.JbiExchange
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
<br>> at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
<br>> at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
<br>> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
<br>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
<br>> at java.util.HashMap.writeObject(HashMap.java:1039)
<br>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
<br>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
<br>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
<br>> at java.lang.reflect.Method.invoke(Method.java:585)
<br>> at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
<br>> at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
<br>> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
<br>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
<br>> at org.apache.servicemix.jbi.messaging.ExchangePacket.writeExternal(ExchangePacket.java:404)
<br>> at org.apache.servicemix.jbi.messaging.MessageExchangeImpl.writeExternal(MessageExchangeImpl.java:605)
<br>> at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
<br>> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
<br>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
<br>> at org.apache.activemq.command.ActiveMQObjectMessage.storeContent(ActiveMQObjectMessage.java:98)
<br>> {code}
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26269847
Re: Can't send 2000 messages into the NMR : ESB is stuck after 1000...
2009-11-09T09:01:51Z
2009-11-09T09:01:51Z
jcamus
Ok. Three questions then :
<br>1) Why the file component is not taking into account the global parameters?
<br>2) How I can set up such values for file component in xbean.xml ? The example you gave is about sm:container.
<br>3) Why some messages are lost? When I restart the ESB, 1000 messages are definitely lost! I
<br>though by default every message into the NRM were managed by JMS with data persistence!
<br><br><br>Regards.
<br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Jean-Baptiste Onofré wrote:</div>
<div class="quote-message shrinkable-quote">Hi,
<br><br>have you just defined the global corePoolSize, maximumPoolSize and
<br>queueSize properties in the conf/servicemix.properties file or do you
<br>have defined component specific configuration ?
<br><br>For your information, you can define the thread/queue configuration on
<br>one component depending of the flow type used.
<br><br>For example, for the file component, you can define something like:
<br><br> <entry key="flow.seda.servicemix-file">
<br> <bean
<br>class="org.apache.servicemix.executors.impl.ExecutorConfig">
<br> <property name="corePoolSize" value="32"/>
<br> <property name="maximumPoolSize" value="-1"/>
<br> <property name="queueSize" value="1024"/>
<br> </bean>
<br><br>I think that in your case, the global thread/queue configuration is
<br>enough the CXF components (largely enough :)) but maybe not enough for
<br>the file component.
<br><br>Try to decrease the global properties values and define the thread
<br>configuration specific for the servicemix-file component.
<br><br>You can find more information about this here:
<br><a href="http://servicemix.apache.org/thread-pools.html" target="_top" rel="nofollow">http://servicemix.apache.org/thread-pools.html</a><br><br>Regards
<br>JB
<br><br>jcamus wrote:
<br>> Hi!
<br>> I am trying to send into the NMR 2000 messages in a row but ESB seems stuck
<br>> after 1000 messages.
<br>> My design is the following :
<br>> CXF-BC -> CXF-SE -> FileSender
<br>>
<br>> So a SOAP Client is sending 2000 times the same request (in a simple loop,
<br>> so no multithread) and in the CXF-SE here is method called :
<br>>
<br>> Here is the code :
<br>>
<br>> public void sendFile(String filename, byte[] fileContent, String deviceCode,
<br>> int operatorCode) {
<br>> filename = operatorCode + "-" + deviceCode + "-" + filename;
<br>> try {
<br>> InOnly exchange = getClient().createInOnlyExchange();
<br>> exchange.setService(m_incomingService);
<br>> ServiceEndpoint endPoint =
<br>> getClient().getContext().getEndpoint(m_incomingService,
<br>> m_incomingSenderEndpoint);
<br>> exchange.setEndpoint(endPoint);
<br>> NormalizedMessage messageToSend = exchange.getInMessage();
<br>> messageToSend.setProperty(DefaultFileMarshaler.FILE_NAME_PROPERTY,
<br>> filename);
<br>> DataSource fileSource = new ByteDataSource(fileContent);
<br>> DataHandler handler = new DataHandler(fileSource);
<br>> messageToSend.addAttachment(DefaultFileMarshaler.FILE_CONTENT,
<br>> handler);
<br>> getClient().send(exchange);
<br>> } catch (Exception e) {
<br>> m_gLogger.error("Error sendfile : filename " + filename + " deviceCode
<br>> = " + deviceCode + " operatorCode = " + operatorCode, e);
<br>> }
<br>> }
<br>>
<br>> private ServiceMixClient getClient() throws Exception {
<br>> if (m_client == null) {
<br>> ClientFactory factory = (ClientFactory) new
<br>> InitialContext().lookup(ClientFactory.DEFAULT_JNDI_NAME);
<br>> m_client = factory.createClient();
<br>> }
<br>> return m_client;
<br>> }
<br>>
<br>>
<br>>
<br>> I tried to change the values into servicemix.conf like this (without
<br>> success) :
<br>>
<br>> servicemix.corePoolSize = 64
<br>> servicemix.maximumPoolSize = 1280
<br>> servicemix.queueSize = 2560
<br>>
<br>> Can you explain me why the ESB freezes? When it happens I have to restart
<br>> the ESB.. and all the messages pending are lost...
<br>> Where am I wrong? Did I forget to free a resource?
<br>>
<br>> If I replace the code above but a simple copyFile into the CXF-SE it works
<br>> fine...
<br>>
<br>>
<br>>
</div>
</div></blockquote>
<p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26269752
Re: Camel 2.0 / servicemix-camel 2009.02
2009-11-09T08:55:31Z
2009-11-09T08:55:31Z
Jean-Baptiste Onofré
OK good Markus,
<br><br>I think it was a classloader issue due some cache (especially if you
<br>made several osgi:install/delete/stop/start).
<br><br>Regards
<br>JB
<br><br>Markus Wolf wrote:
<div class='shrinkable-quote'><br>> -----BEGIN PGP SIGNED MESSAGE-----
<br>> Hash: SHA1
<br>>
<br>> Hi Jean-Baptiste,
<br>>
<br>> I restarted the servicemix and removed the data/cache contents. After
<br>> that I had to reinstall all dependencies (:() and now it does work.
<br>> There must be something gone wrong in the first try.
<br>>
<br>> But thanks for your help. :)
<br>> Markus
<br>>
<br>> Jean-Baptiste Onofré schrieb:
<br>>> Hi again Markus,
<br>>>
<br>>> could you attach the result of osgi:headers osgi:list commands and the
<br>>> complete stack trace ?
<br>>> It can be a classloader issue.
<br>>>
<br>>> Regards
<br>>> JB
<br>>>
<br>>> Markus Wolf wrote:
<br>>> Hello again,
<br>>>
<br>>> I managed to install all required dependencies on SMX4 (from Fuse).
<br>>> But now when I deploy our component I get this exception:
<br>>>
<br>>> 17:30:02,938 | ERROR | xtenderThread-88 |
<br>>> OsgiBundleXmlApplicationContext | gatedExecutionApplicationContext 366
<br>>> | Post refresh error
<br>>> org.apache.camel.ResolveEndpointFailedException: Failed to resolve
<br>>> endpoint: jetty://<a href="http://0.0.0.0:8888/track-view?matchOnUriPrefix=true" target="_top" rel="nofollow">http://0.0.0.0:8888/track-view?matchOnUriPrefix=true</a><br>>> due to: No component found with scheme: jetty
<br>>> at
<br>>> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:421)
<br>>>
<br>>> at
<br>>> org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:52)
<br>>>
<br>>> at
<br>>> org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:138)
<br>>>
<br>>> at
<br>>> org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:99)
<br>>>
<br>>> at
<br>>> org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:105)
<br>>>
<br>>> at
<br>>> org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72)
<br>>>
<br>>> at
<br>>> org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:74)
<br>>>
<br>>> at
<br>>> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:432)
<br>>>
<br>>>
<br>>>
<br>>> I check that the camel-jetty component is installed and osgi/list
<br>>> displays it as active.
<br>>> Anyone has an idea was I could have done wrong?
<br>>>
<br>>> Thanks for any help
<br>>> Markus Wolf
<br>>>
<br>>>
<br>>> Jean-Baptiste Onofré schrieb:
<br>>>>>> Hi Markus,
<br>>>>>>
<br>>>>>> we're preparing a 2009.02 release of components. We need to fix some
<br>>>>>> issues first.
<br>>>>>>
<br>>>>>> I think that we will be able to release the new components set in the
<br>>>>>> following week.
<br>>>>>>
<br>>>>>> Regards
<br>>>>>> JB
<br>>>>>>
<br>>>>>> Markus Wolf wrote:
<br>>>>>> Hi there,
<br>>>>>>
<br>>>>>> are there any plans to release servicemix-camel 2009.02 in the near
<br>>>>>> future? We have a component requiring camel 2.0 and use servicemix 3.3.1
<br>>>>>> and noticed that camel 2.0 is not supported currently.
<br>>>>>>
<br>>>>>> Thanks
<br>>>>>> Markus Wolf
<br>>
<br>> - --
<br>> NMMN - New Media Markets & Networks GmbH
<br>> Langbehnstrasse 6, 22761 Hamburg
<br>> Geschäftsführung: Kfm. Michael Schütt
<br>> Finanzamt HH-Altona - UStID DE 812 699 852 - HRB 71102 Hamburg
<br>> HypoVereinsbank - BLZ 200 300 00 - Konto-Nr. 156 29 82
<br>>
<br>> <a href="http://www.nmmn.com" target="_top" rel="nofollow">http://www.nmmn.com</a><br>> Tel.: +49 40 284 118-0 - Fax: +49 40 284118-999
<br>> Softwareentwicklung LLynch: -720
<br>> -----BEGIN PGP SIGNATURE-----
<br>> Version: GnuPG v1.4.9 (GNU/Linux)
<br>> Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_top" rel="nofollow">http://enigmail.mozdev.org</a><br>>
<br>> iEYEARECAAYFAkr4R7sACgkQDBHISU1oEKHYfgCfV+JBBceBOCkVMJc5qJn+W9EV
<br>> O68AoLQP140crP/LPjmh6qCpZbHwdj5T
<br>> =q8a+
<br>> -----END PGP SIGNATURE-----
<br></div><p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26269732
Re: Can't send 2000 messages into the NMR : ESB is stuck after 1000...
2009-11-09T08:54:21Z
2009-11-09T08:54:21Z
Jean-Baptiste Onofré
Hi,
<br><br>have you just defined the global corePoolSize, maximumPoolSize and
<br>queueSize properties in the conf/servicemix.properties file or do you
<br>have defined component specific configuration ?
<br><br>For your information, you can define the thread/queue configuration on
<br>one component depending of the flow type used.
<br><br>For example, for the file component, you can define something like:
<br><br> <entry key="flow.seda.servicemix-file">
<br> <bean
<br>class="org.apache.servicemix.executors.impl.ExecutorConfig">
<br> <property name="corePoolSize" value="32"/>
<br> <property name="maximumPoolSize" value="-1"/>
<br> <property name="queueSize" value="1024"/>
<br> </bean>
<br><br>I think that in your case, the global thread/queue configuration is
<br>enough the CXF components (largely enough :)) but maybe not enough for
<br>the file component.
<br><br>Try to decrease the global properties values and define the thread
<br>configuration specific for the servicemix-file component.
<br><br>You can find more information about this here:
<br><a href="http://servicemix.apache.org/thread-pools.html" target="_top" rel="nofollow">http://servicemix.apache.org/thread-pools.html</a><br><br>Regards
<br>JB
<br><br>jcamus wrote:
<div class='shrinkable-quote'><br>> Hi!
<br>> I am trying to send into the NMR 2000 messages in a row but ESB seems stuck
<br>> after 1000 messages.
<br>> My design is the following :
<br>> CXF-BC -> CXF-SE -> FileSender
<br>>
<br>> So a SOAP Client is sending 2000 times the same request (in a simple loop,
<br>> so no multithread) and in the CXF-SE here is method called :
<br>>
<br>> Here is the code :
<br>>
<br>> public void sendFile(String filename, byte[] fileContent, String deviceCode,
<br>> int operatorCode) {
<br>> filename = operatorCode + "-" + deviceCode + "-" + filename;
<br>> try {
<br>> InOnly exchange = getClient().createInOnlyExchange();
<br>> exchange.setService(m_incomingService);
<br>> ServiceEndpoint endPoint =
<br>> getClient().getContext().getEndpoint(m_incomingService,
<br>> m_incomingSenderEndpoint);
<br>> exchange.setEndpoint(endPoint);
<br>> NormalizedMessage messageToSend = exchange.getInMessage();
<br>> messageToSend.setProperty(DefaultFileMarshaler.FILE_NAME_PROPERTY,
<br>> filename);
<br>> DataSource fileSource = new ByteDataSource(fileContent);
<br>> DataHandler handler = new DataHandler(fileSource);
<br>> messageToSend.addAttachment(DefaultFileMarshaler.FILE_CONTENT,
<br>> handler);
<br>> getClient().send(exchange);
<br>> } catch (Exception e) {
<br>> m_gLogger.error("Error sendfile : filename " + filename + " deviceCode
<br>> = " + deviceCode + " operatorCode = " + operatorCode, e);
<br>> }
<br>> }
<br>>
<br>> private ServiceMixClient getClient() throws Exception {
<br>> if (m_client == null) {
<br>> ClientFactory factory = (ClientFactory) new
<br>> InitialContext().lookup(ClientFactory.DEFAULT_JNDI_NAME);
<br>> m_client = factory.createClient();
<br>> }
<br>> return m_client;
<br>> }
<br>>
<br>>
<br>>
<br>> I tried to change the values into servicemix.conf like this (without
<br>> success) :
<br>>
<br>> servicemix.corePoolSize = 64
<br>> servicemix.maximumPoolSize = 1280
<br>> servicemix.queueSize = 2560
<br>>
<br>> Can you explain me why the ESB freezes? When it happens I have to restart
<br>> the ESB.. and all the messages pending are lost...
<br>> Where am I wrong? Did I forget to free a resource?
<br>>
<br>> If I replace the code above but a simple copyFile into the CXF-SE it works
<br>> fine...
<br>>
<br>>
<br>>
<br></div><p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26269583
Re: Camel 2.0 / servicemix-camel 2009.02
2009-11-09T08:47:55Z
2009-11-09T08:47:55Z
KnisterPeter
-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>Hi Jean-Baptiste,
<br><br>I restarted the servicemix and removed the data/cache contents. After
<br>that I had to reinstall all dependencies (:() and now it does work.
<br>There must be something gone wrong in the first try.
<br><br>But thanks for your help. :)
<br>Markus
<br><br>Jean-Baptiste Onofré schrieb:
<div class='shrinkable-quote'><br>> Hi again Markus,
<br>>
<br>> could you attach the result of osgi:headers osgi:list commands and the
<br>> complete stack trace ?
<br>> It can be a classloader issue.
<br>>
<br>> Regards
<br>> JB
<br>>
<br>> Markus Wolf wrote:
<br>> Hello again,
<br>>
<br>> I managed to install all required dependencies on SMX4 (from Fuse).
<br>> But now when I deploy our component I get this exception:
<br>>
<br>> 17:30:02,938 | ERROR | xtenderThread-88 |
<br>> OsgiBundleXmlApplicationContext | gatedExecutionApplicationContext 366
<br>> | Post refresh error
<br>> org.apache.camel.ResolveEndpointFailedException: Failed to resolve
<br>> endpoint: jetty://<a href="http://0.0.0.0:8888/track-view?matchOnUriPrefix=true" target="_top" rel="nofollow">http://0.0.0.0:8888/track-view?matchOnUriPrefix=true</a><br>> due to: No component found with scheme: jetty
<br>> at
<br>> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:421)
<br>>
<br>> at
<br>> org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:52)
<br>>
<br>> at
<br>> org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:138)
<br>>
<br>> at
<br>> org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:99)
<br>>
<br>> at
<br>> org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:105)
<br>>
<br>> at
<br>> org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72)
<br>>
<br>> at
<br>> org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:74)
<br>>
<br>> at
<br>> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:432)
<br>>
<br>>
<br>>
<br>> I check that the camel-jetty component is installed and osgi/list
<br>> displays it as active.
<br>> Anyone has an idea was I could have done wrong?
<br>>
<br>> Thanks for any help
<br>> Markus Wolf
<br>>
<br>>
<br>> Jean-Baptiste Onofré schrieb:
<br>>>>> Hi Markus,
<br>>>>>
<br>>>>> we're preparing a 2009.02 release of components. We need to fix some
<br>>>>> issues first.
<br>>>>>
<br>>>>> I think that we will be able to release the new components set in the
<br>>>>> following week.
<br>>>>>
<br>>>>> Regards
<br>>>>> JB
<br>>>>>
<br>>>>> Markus Wolf wrote:
<br>>>>> Hi there,
<br>>>>>
<br>>>>> are there any plans to release servicemix-camel 2009.02 in the near
<br>>>>> future? We have a component requiring camel 2.0 and use servicemix 3.3.1
<br>>>>> and noticed that camel 2.0 is not supported currently.
<br>>>>>
<br>>>>> Thanks
<br>>>>> Markus Wolf
<br>>
</div><br>- --
<br>NMMN - New Media Markets & Networks GmbH
<br>Langbehnstrasse 6, 22761 Hamburg
<br>Geschäftsführung: Kfm. Michael Schütt
<br>Finanzamt HH-Altona - UStID DE 812 699 852 - HRB 71102 Hamburg
<br>HypoVereinsbank - BLZ 200 300 00 - Konto-Nr. 156 29 82
<br><br><a href="http://www.nmmn.com" target="_top" rel="nofollow">http://www.nmmn.com</a><br>Tel.: +49 40 284 118-0 - Fax: +49 40 284118-999
<br>Softwareentwicklung LLynch: -720
<br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.9 (GNU/Linux)
<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_top" rel="nofollow">http://enigmail.mozdev.org</a><br><br>iEYEARECAAYFAkr4R7sACgkQDBHISU1oEKHYfgCfV+JBBceBOCkVMJc5qJn+W9EV
<br>O68AoLQP140crP/LPjmh6qCpZbHwdj5T
<br>=q8a+
<br>-----END PGP SIGNATURE-----
<br><p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26269556
Can't send 2000 messages into the NMR : ESB is stuck after 1000...
2009-11-09T08:46:27Z
2009-11-09T08:46:27Z
jcamus
Hi!
<br>I am trying to send into the NMR 2000 messages in a row but ESB seems stuck after 1000 messages.
<br>My design is the following :
<br>CXF-BC -> CXF-SE -> FileSender
<br><br>So a SOAP Client is sending 2000 times the same request (in a simple loop, so no multithread) and in the CXF-SE here is method called :
<br><br>Here is the code :
<br><br><i>public void sendFile(String filename, byte[] fileContent, String deviceCode, int operatorCode) {
<br> filename = operatorCode + "-" + deviceCode + "-" + filename;
<br> try {
<br> InOnly exchange = getClient().createInOnlyExchange();
<br> exchange.setService(m_incomingService);
<br> ServiceEndpoint endPoint = getClient().getContext().getEndpoint(m_incomingService, m_incomingSenderEndpoint);
<br> exchange.setEndpoint(endPoint);
<br> NormalizedMessage messageToSend = exchange.getInMessage();
<br> messageToSend.setProperty(DefaultFileMarshaler.FILE_NAME_PROPERTY, filename);
<br> DataSource fileSource = new ByteDataSource(fileContent);
<br> DataHandler handler = new DataHandler(fileSource);
<br> messageToSend.addAttachment(DefaultFileMarshaler.FILE_CONTENT, handler);
<br> getClient().send(exchange);
<br> } catch (Exception e) {
<br> m_gLogger.error("Error sendfile : filename " + filename + " deviceCode = " + deviceCode + " operatorCode = " + operatorCode, e);
<br> }
<br> }
<br><br> private ServiceMixClient getClient() throws Exception {
<br> if (m_client == null) {
<br> ClientFactory factory = (ClientFactory) new InitialContext().lookup(ClientFactory.DEFAULT_JNDI_NAME);
<br> m_client = factory.createClient();
<br> }
<br> return m_client;
<br> }
<br><br></i><br><br>I tried to change the values into servicemix.conf like this (without success) :
<br><br>servicemix.corePoolSize = 64
<br>servicemix.maximumPoolSize = 1280
<br>servicemix.queueSize = 2560
<br><br>Can you explain me why the ESB freezes? When it happens I have to restart the ESB.. and all the messages pending are lost...
<br>Where am I wrong? Did I forget to free a resource?
<br><br>If I replace the code above but a simple copyFile into the CXF-SE it works fine...
<br><br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26269473
Re: Camel 2.0 / servicemix-camel 2009.02
2009-11-09T08:40:58Z
2009-11-09T08:40:58Z
Jean-Baptiste Onofré
Hi again Markus,
<br><br>could you attach the result of osgi:headers osgi:list commands and the
<br>complete stack trace ?
<br>It can be a classloader issue.
<br><br>Regards
<br>JB
<br><br>Markus Wolf wrote:
<div class='shrinkable-quote'><br>> -----BEGIN PGP SIGNED MESSAGE-----
<br>> Hash: SHA1
<br>>
<br>> Hello again,
<br>>
<br>> I managed to install all required dependencies on SMX4 (from Fuse).
<br>> But now when I deploy our component I get this exception:
<br>>
<br>> 17:30:02,938 | ERROR | xtenderThread-88 |
<br>> OsgiBundleXmlApplicationContext | gatedExecutionApplicationContext 366
<br>> | Post refresh error
<br>> org.apache.camel.ResolveEndpointFailedException: Failed to resolve
<br>> endpoint: jetty://<a href="http://0.0.0.0:8888/track-view?matchOnUriPrefix=true" target="_top" rel="nofollow">http://0.0.0.0:8888/track-view?matchOnUriPrefix=true</a><br>> due to: No component found with scheme: jetty
<br>> at
<br>> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:421)
<br>> at
<br>> org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:52)
<br>> at
<br>> org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:138)
<br>> at
<br>> org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:99)
<br>> at
<br>> org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:105)
<br>> at
<br>> org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72)
<br>> at
<br>> org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:74)
<br>> at
<br>> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:432)
<br>>
<br>>
<br>> I check that the camel-jetty component is installed and osgi/list
<br>> displays it as active.
<br>> Anyone has an idea was I could have done wrong?
<br>>
<br>> Thanks for any help
<br>> Markus Wolf
<br>>
<br>>
<br>> Jean-Baptiste Onofré schrieb:
<br>>> Hi Markus,
<br>>>
<br>>> we're preparing a 2009.02 release of components. We need to fix some
<br>>> issues first.
<br>>>
<br>>> I think that we will be able to release the new components set in the
<br>>> following week.
<br>>>
<br>>> Regards
<br>>> JB
<br>>>
<br>>> Markus Wolf wrote:
<br>>> Hi there,
<br>>>
<br>>> are there any plans to release servicemix-camel 2009.02 in the near
<br>>> future? We have a component requiring camel 2.0 and use servicemix 3.3.1
<br>>> and noticed that camel 2.0 is not supported currently.
<br>>>
<br>>> Thanks
<br>>> Markus Wolf
<br>>
<br>> - --
<br>> NMMN - New Media Markets & Networks GmbH
<br>> Langbehnstrasse 6, 22761 Hamburg
<br>> Geschäftsführung: Kfm. Michael Schütt
<br>> Finanzamt HH-Altona - UStID DE 812 699 852 - HRB 71102 Hamburg
<br>> HypoVereinsbank - BLZ 200 300 00 - Konto-Nr. 156 29 82
<br>>
<br>> <a href="http://www.nmmn.com" target="_top" rel="nofollow">http://www.nmmn.com</a><br>> Tel.: +49 40 284 118-0 - Fax: +49 40 284118-999
<br>> Softwareentwicklung LLynch: -720
<br>> -----BEGIN PGP SIGNATURE-----
<br>> Version: GnuPG v1.4.9 (GNU/Linux)
<br>> Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_top" rel="nofollow">http://enigmail.mozdev.org</a><br>>
<br>> iEYEARECAAYFAkr4RGoACgkQDBHISU1oEKGPoACdFZtA7DvpgX9NacycipoGEJqi
<br>> 2x8AoJ27dLSqpHJdjg1luIWBue3TtEeM
<br>> =8D73
<br>> -----END PGP SIGNATURE-----
<br></div><p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26269353
Re: Camel 2.0 / servicemix-camel 2009.02
2009-11-09T08:33:46Z
2009-11-09T08:33:46Z
KnisterPeter
-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>Hello again,
<br><br>I managed to install all required dependencies on SMX4 (from Fuse).
<br>But now when I deploy our component I get this exception:
<br><br>17:30:02,938 | ERROR | xtenderThread-88 |
<br>OsgiBundleXmlApplicationContext | gatedExecutionApplicationContext 366
<br>| Post refresh error
<br>org.apache.camel.ResolveEndpointFailedException: Failed to resolve
<br>endpoint: jetty://<a href="http://0.0.0.0:8888/track-view?matchOnUriPrefix=true" target="_top" rel="nofollow">http://0.0.0.0:8888/track-view?matchOnUriPrefix=true</a><br>due to: No component found with scheme: jetty
<br> at
<br>org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:421)
<br> at
<br>org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:52)
<br> at
<br>org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:138)
<br> at
<br>org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:99)
<br> at
<br>org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:105)
<br> at
<br>org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72)
<br> at
<br>org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:74)
<br> at
<br>org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:432)
<br><br><br>I check that the camel-jetty component is installed and osgi/list
<br>displays it as active.
<br>Anyone has an idea was I could have done wrong?
<br><br>Thanks for any help
<br>Markus Wolf
<br><br><br>Jean-Baptiste Onofré schrieb:
<div class='shrinkable-quote'><br>> Hi Markus,
<br>>
<br>> we're preparing a 2009.02 release of components. We need to fix some
<br>> issues first.
<br>>
<br>> I think that we will be able to release the new components set in the
<br>> following week.
<br>>
<br>> Regards
<br>> JB
<br>>
<br>> Markus Wolf wrote:
<br>> Hi there,
<br>>
<br>> are there any plans to release servicemix-camel 2009.02 in the near
<br>> future? We have a component requiring camel 2.0 and use servicemix 3.3.1
<br>> and noticed that camel 2.0 is not supported currently.
<br>>
<br>> Thanks
<br>> Markus Wolf
</div><br>- --
<br>NMMN - New Media Markets & Networks GmbH
<br>Langbehnstrasse 6, 22761 Hamburg
<br>Geschäftsführung: Kfm. Michael Schütt
<br>Finanzamt HH-Altona - UStID DE 812 699 852 - HRB 71102 Hamburg
<br>HypoVereinsbank - BLZ 200 300 00 - Konto-Nr. 156 29 82
<br><br><a href="http://www.nmmn.com" target="_top" rel="nofollow">http://www.nmmn.com</a><br>Tel.: +49 40 284 118-0 - Fax: +49 40 284118-999
<br>Softwareentwicklung LLynch: -720
<br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.9 (GNU/Linux)
<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_top" rel="nofollow">http://enigmail.mozdev.org</a><br><br>iEYEARECAAYFAkr4RGoACgkQDBHISU1oEKGPoACdFZtA7DvpgX9NacycipoGEJqi
<br>2x8AoJ27dLSqpHJdjg1luIWBue3TtEeM
<br>=8D73
<br>-----END PGP SIGNATURE-----
<br><p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26269310
[jira] Commented: (SMXCOMP-621) SDO integration
2009-11-09T08:30:52Z
2009-11-09T08:30:52Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SMXCOMP-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55236#action_55236" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55236#action_55236</a> ]
<br><br>Jean-Baptiste Onofré commented on SMXCOMP-621:
<br>----------------------------------------------
<br><br>Thanks for the update Dan.
<br><br>I will take a look on the CXF trunk.
<br><div class='shrinkable-quote'><br>> SDO integration
<br>> ---------------
<br>>
<br>> Key: SMXCOMP-621
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SMXCOMP-621" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-621</a><br>> Project: ServiceMix Components
<br>> Issue Type: New Feature
<br>> Reporter: James Strachan
<br>>
<br>> We could do with an implementation of SDO
<br>> <a href="http://dev2dev.bea.com/wlplatform/commonj/" target="_top" rel="nofollow">http://dev2dev.bea.com/wlplatform/commonj/</a><br>> and integration with SDO as a BindingComponent
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26268837
[jira] Commented: (SMXCOMP-621) SDO integration
2009-11-09T07:58:52Z
2009-11-09T07:58:52Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SMXCOMP-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55235#action_55235" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55235#action_55235</a> ]
<br><br>Daniel Kulp commented on SMXCOMP-621:
<br>-------------------------------------
<br><br><br>On a related note: CXF trunk (targetting 2.3) support an SDO databinding. Thus, when CXF 2.3 comes out, this MIGHT be partially achievable via the cxf-bc/se things.
<br><br><br><div class='shrinkable-quote'><br>> SDO integration
<br>> ---------------
<br>>
<br>> Key: SMXCOMP-621
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SMXCOMP-621" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-621</a><br>> Project: ServiceMix Components
<br>> Issue Type: New Feature
<br>> Reporter: James Strachan
<br>>
<br>> We could do with an implementation of SDO
<br>> <a href="http://dev2dev.bea.com/wlplatform/commonj/" target="_top" rel="nofollow">http://dev2dev.bea.com/wlplatform/commonj/</a><br>> and integration with SDO as a BindingComponent
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26268806
Re: Camel vs. SMX Maven repository
2009-11-09T07:57:03Z
2009-11-09T07:57:03Z
Jean-Baptiste Onofré
Done,
<br><br><a href="http://svn.apache.org/repos/asf/camel/m2-repo" target="_top" rel="nofollow">http://svn.apache.org/repos/asf/camel/m2-repo</a> has been added in the
<br>servicemix-camel component trunk.
<br><br>Regards
<br>JB
<br><br>Martin Krasser wrote:
<div class='shrinkable-quote'><br>> Hi Jean-Baptiste,
<br>>
<br>> seems that there are no objections against uploading the artifacts to
<br>> <a href="https://svn.apache.org/repos/asf/camel/m2-repo" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo</a>. So I'll put them there.
<br>>
<br>> Jean-Baptiste Onofré schrieb:
<br>>> Hi Martin,
<br>>>
<br>>> for my part, I think that we need to consider Camel as a SMX
<br>>> dependency (like CXF, ActiveMQ, etc). So, Camel should upload
<br>>> artifacts and dependencies to
<br>>> <a href="https://svn.apache.org/repos/asf/camel/m2-repo" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo</a> and the ServiceMix
<br>>> Camel component should have this repository in its pom.
<br>>>
<br>>> Let see the feeling of the other guys.
<br>>>
<br>>> Regards
<br>>> JB
<br>>>
<br>>> Martin Krasser wrote:
<br>>>> Hi,
<br>>>>
<br>>>> I started a thread on the Camel dev mailing list discussing which
<br>>>> Maven repo to use for uploading new artifacts needed by Camel.
<br>>>>
<br>>>> <a href="http://old.nabble.com/GAE-API-in-Maven-repo-tt26243221s22882.html" target="_top" rel="nofollow">http://old.nabble.com/GAE-API-in-Maven-repo-tt26243221s22882.html</a><br>>>>
<br>>>> We finally discussed the two options:
<br>>>>
<br>>>> - <a href="https://svn.apache.org/repos/asf/servicemix/m2-repo/" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/servicemix/m2-repo/</a> (ServiceMix
<br>>>> Maven repo)
<br>>>> - <a href="https://svn.apache.org/repos/asf/camel/m2-repo/" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo/</a> (Camel Maven repo)
<br>>>> Camel already uses the ServiceMix repo to download jars. Which option
<br>>>> do you prefer?
<br>>>>
<br>>>> Thanks,
<br>>>> Martin
<br>>>>
<br>>>>
<br>>>
<br>>
<br></div><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26268746
svn commit: r834116 - /servicemix/components/engines/servicemix-camel/trunk/pom.xml
2009-11-09T07:54:30Z
2009-11-09T07:54:30Z
jbonofre
Author: jbonofre
<br>Date: Mon Nov 9 15:54:22 2009
<br>New Revision: 834116
<br><br>URL: <a href="http://svn.apache.org/viewvc?rev=834116&view=rev" target="_top" rel="nofollow">http://svn.apache.org/viewvc?rev=834116&view=rev</a><br>Log:
<br>Add Camel mvn repo.
<br><br>Modified:
<br> servicemix/components/engines/servicemix-camel/trunk/pom.xml
<br><br>Modified: servicemix/components/engines/servicemix-camel/trunk/pom.xml
<br>URL: <a href="http://svn.apache.org/viewvc/servicemix/components/engines/servicemix-camel/trunk/pom.xml?rev=834116&r1=834115&r2=834116&view=diff" target="_top" rel="nofollow">http://svn.apache.org/viewvc/servicemix/components/engines/servicemix-camel/trunk/pom.xml?rev=834116&r1=834115&r2=834116&view=diff</a><br>==============================================================================
<br>--- servicemix/components/engines/servicemix-camel/trunk/pom.xml (original)
<br>+++ servicemix/components/engines/servicemix-camel/trunk/pom.xml Mon Nov 9 15:54:22 2009
<br>@@ -70,6 +70,20 @@
<br> </servicemix.osgi.bundles>
<br> </properties>
<br>
<br>+ <repositories>
<br>+ <repository>
<br>+ <id>camel-repo</id>
<br>+ <name>Apache Camel Repository</name>
<br>+ <url><a href="http://svn.apache.org/repos/asf/camel/m2-repo/" target="_top" rel="nofollow">http://svn.apache.org/repos/asf/camel/m2-repo/</a></url>
<br>+ <releases>
<br>+ <enabled>true</enabled>
<br>+ </releases>
<br>+ <snapshots>
<br>+ <enabled>false</enabled>
<br>+ </snapshots>
<br>+ </repository>
<br>+ </repositories>
<br>+
<br> <dependencies>
<br> <dependency>
<br> <groupId>org.apache.camel</groupId>
<br><br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26268666
[CONF] Apache ServiceMix > Components list
2009-11-09T07:50:00Z
2009-11-09T07:50:00Z
confluence-2
<html>
<head>
<base href="http://cwiki.apache.org/confluence">
<link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=SM&forWysiwyg=true" type="text/css">
</head>
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
<h2><a href="http://cwiki.apache.org/confluence/display/SM/Components+list" target="_top" rel="nofollow">Components list</a></h2>
<h4>Page <b>edited</b> by <a href="http://cwiki.apache.org/confluence/display/~nanthrax" target="_top" rel="nofollow">Jean-Baptiste Onofré</a>
</h4>
<br />
<div class="notificationGreySide">
<p>ServiceMix currently has the following JBI components:</p>
<h2><a name="Componentslist-StandardJBIcomponents" target="_top"></a>Standard JBI components</h2>
<p>The following components ships with ServiceMix distribution:</p>
<ul>
<li><a href="/confluence/display/SM/servicemix-bean" title="servicemix-bean" target="_top" rel="nofollow">servicemix-bean</a> is a JBI component for mapping beans (POJOs) to JBI message exchanges for easy procssing of JBI message exchanges. Note that if you want to support SOAP, type safe business interfaces or JAX-WS / JSR 181 then you should use <a href="/confluence/display/SM/servicemix-jsr181" title="servicemix-jsr181" target="_top" rel="nofollow">servicemix-jsr181</a></li>
<li><a href="/confluence/display/SM/servicemix-bpe" title="servicemix-bpe" target="_top" rel="nofollow">servicemix-bpe</a> (deprecated)</li>
<li><a href="/confluence/display/SM/servicemix-camel" title="servicemix-camel" target="_top" rel="nofollow">servicemix-camel</a></li>
<li><a href="/confluence/display/SM/servicemix-cxf-bc" title="servicemix-cxf-bc" target="_top" rel="nofollow">servicemix-cxf-bc</a></li>
<li><a href="/confluence/display/SM/servicemix-cxf-se" title="servicemix-cxf-se" target="_top" rel="nofollow">servicemix-cxf-se</a></li>
<li><a href="/confluence/display/SM/servicemix-drools" title="servicemix-drools" target="_top" rel="nofollow">servicemix-drools</a></li>
<li><a href="/confluence/display/SM/servicemix-eip" title="servicemix-eip" target="_top" rel="nofollow">servicemix-eip</a> contains several routing patterns based on the great <a href="http://www.enterpriseintegrationpatterns.com/index.html" rel="nofollow" target="_top">EIP</a> book</li>
<li><a href="/confluence/display/SM/servicemix-exec" title="servicemix-exec" target="_top" rel="nofollow">servicemix-exec</a> is a Service Engine that allows to execute system command</li>
<li><a href="/confluence/display/SM/servicemix-file" title="servicemix-file" target="_top" rel="nofollow">servicemix-file</a> is a file system Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-ftp" title="servicemix-ftp" target="_top" rel="nofollow">servicemix-ftp</a> is an FTP Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-http" title="servicemix-http" target="_top" rel="nofollow">servicemix-http</a> is an HTTP/SOAP Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-jms" title="servicemix-jms" target="_top" rel="nofollow">servicemix-jms</a> is a JMS Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-jsr181" title="servicemix-jsr181" target="_top" rel="nofollow">servicemix-jsr181</a> Service Engine can expose annotated POJOs as services</li>
<li><a href="/confluence/display/SM/servicemix-lwcontainer" title="servicemix-lwcontainer" target="_top" rel="nofollow">servicemix-lwcontainer</a> Service Engine can deploy lightweight components</li>
<li><a href="/confluence/display/SM/servicemix-mail" title="servicemix-mail" target="_top" rel="nofollow">servicemix-mail</a> Email Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-osworkflow" title="servicemix-osworkflow" target="_top" rel="nofollow">servicemix-osworkflow</a> OSWorkflow Service Engine</li>
<li><a href="/confluence/display/SM/servicemix-quartz" title="servicemix-quartz" target="_top" rel="nofollow">servicemix-quartz</a></li>
<li><a href="/confluence/display/SM/servicemix-saxon" title="servicemix-saxon" target="_top" rel="nofollow">servicemix-saxon</a></li>
<li><a href="/confluence/display/SM/servicemix-script" title="servicemix-script" target="_top" rel="nofollow">servicemix-script</a> uses Spring Dynamic Language Support</li>
<li><a href="/confluence/display/SM/servicemix-scripting" title="servicemix-scripting" target="_top" rel="nofollow">servicemix-scripting</a> JSR-223 Scripting Engine</li>
<li><a href="/confluence/display/SM/servicemix-smpp" title="servicemix-smpp" target="_top" rel="nofollow">servicemix-smpp</a> SMPP (SMS) Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-snmp" title="servicemix-snmp" target="_top" rel="nofollow">servicemix-snmp</a> SNMP Binding Component</li>
<li><a href="/confluence/pages/createpage.action?spaceKey=SM&title=servicemix-truezip&linkCreation=true&fromPageId=39113" class="createlink" target="_top" rel="nofollow">servicemix-truezip</a></li>
<li><a href="/confluence/display/SM/servicemix-validation" title="servicemix-validation" target="_top" rel="nofollow">servicemix-validation</a> a xml validation engnine</li>
<li><a href="/confluence/display/SM/servicemix-vfs" title="servicemix-vfs" target="_top" rel="nofollow">servicemix-vfs</a> a vfs binding component based on Apache Commons-VFS</li>
<li><a href="/confluence/display/SM/servicemix-wsn2005" title="servicemix-wsn2005" target="_top" rel="nofollow">servicemix-wsn2005</a> is an implementation of WS-Notification</li>
<li><a href="/confluence/display/SM/servicemix-xmpp" title="servicemix-xmpp" target="_top" rel="nofollow">servicemix-xmpp</a> is an XMPP (Jabber) Binding Component</li>
</ul>
<h2><a name="Componentslist-ComponentsRoadmap" target="_top"></a>Components Roadmap</h2>
<p>The following list shows the future components that will be included in ServiceMix distribution :</p>
<table class='confluenceTable'><tbody>
<tr>
<th class='confluenceTh'> Component </th>
<th class='confluenceTh'> Type </th>
<th class='confluenceTh'> Description </th>
<th class='confluenceTh'> Status </th>
<th class='confluenceTh'> Jira </th>
<th class='confluenceTh'> Resource </th>
</tr>
<tr>
<td class='confluenceTd'> servicemix-cache </td>
<td class='confluenceTd'> SE </td>
<td class='confluenceTd'> Provide way for caching sync executions of other components (cxf, http etc) with multiple cache proviers (EHcache, JBoss Cache ..) </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> <a href="https://issues.apache.org/activemq/browse/SMXCOMP-505" rel="nofollow" target="_top">https://issues.apache.org/activemq/browse/SMXCOMP-505</a> </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-ldap </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Poll and send data with a LDAP directory server. </td>
<td class='confluenceTd'> Proto </td>
<td class='confluenceTd'> <a href="https://issues.apache.org/activemq/browse/SMXCOMP-492" rel="nofollow" target="_top">https://issues.apache.org/activemq/browse/SMXCOMP-492</a> </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-atom </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Poll data from RSS/Atom feed. </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-irc </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Send and receive data from IRC channels. </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-jt400 </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Integrates data queues on an AS/400 (aka System i, IBM i5, ...) </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-jcom </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses the Java Communication API (<a href="http://java.sun.com/products/javacomm/" rel="nofollow" target="_top">http://java.sun.com/products/javacomm/</a>) </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> <a href="https://issues.apache.org/activemq/browse/SM-1270" rel="nofollow" target="_top">https://issues.apache.org/activemq/browse/SM-1270</a> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-jdbc </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses JDBC connectivity to poll and send data within a database </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-rmi </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses to get and send marshaled object using RMI-IIOP ORB </td>
<td class='confluenceTd'> Proto </td>
<td class='confluenceTd'> <a href="https://issues.apache.org/activemq/browse/SMXCOMP-586" rel="nofollow" target="_top">https://issues.apache.org/activemq/browse/SMXCOMP-586</a> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-talend </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses to get/put data coming from/to Talend ETL </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> <a href="http://www.talend.com/index.php" rel="nofollow" target="_top">http://www.talend.com/index.php</a> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-asterisk </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses to get/put data coming from/to Asterisk VOIP server </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> <a href="http://www.asterisk.org/" rel="nofollow" target="_top">http://www.asterisk.org/</a> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-sip </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses SIP protocol to get/put data </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-dcom </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses to get/put data using Microsoft's DCOM protocol </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-sap </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Interface with SAP </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-hl7 </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Interface with systems supporting HL7 protocol </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-sdo </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Interface with BEA commonj protocol </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> <a href="http://e-docs.bea.com/wls/docs92/commonj/commonj.html" rel="nofollow" target="_top">http://e-docs.bea.com/wls/docs92/commonj/commonj.html</a> </td>
</tr>
</tbody></table>
<h2><a name="Componentslist-ThirdPartyStandardJBIComponents" target="_top"></a>Third Party Standard JBI Components </h2>
<p>These components are a wonderful benefit of JBI that is a direct result of the JBI spec. Because the JBI spec is open, many vendors provide JBI compliant components that can be deployed in ServiceMix. </p>
<h2><a name="Componentslist-ApacheODE" target="_top"></a>Apache ODE</h2>
<p><a href="http://ode.apache.org" rel="nofollow" target="_top">Apache Ode</a> is a BPEL engine which provides a JBI compliant component that can be easily deployed into ServiceMix.</p>
<h3><a name="Componentslist-SunOpenESBJBIComponents" target="_top"></a>Sun OpenESB JBI Components </h3>
<p>The Sun <a href="https://open-esb.dev.java.net/" rel="nofollow" target="_top">OpenESB</a> is based on JBI and provides <a href="https://open-jbi-components.dev.java.net/" rel="nofollow" target="_top">many JBI compliant components</a> that can also be used in ServiceMix. </p>
<h3><a name="Componentslist-ObjectWebPetalsComponents" target="_top"></a>ObjectWeb Petals Components </h3>
<p>The <a href="http://petals.objectweb.org/" rel="nofollow" target="_top">Petals ESB</a> is also based on JBI and provides <a href="http://petals.objectweb.org/downloads.html#component" rel="nofollow" target="_top">JBI compliant components</a> as well. </p>
<h3><a name="Componentslist-VariousHighlyUsefulJBIComponents" target="_top"></a>Various Highly Useful JBI Components </h3>
<ul>
<li>Support for <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel" rel="nofollow" target="_top">WS-BPEL</a> is provided via <a href="http://ode.apache.org/" rel="nofollow" target="_top">Apache ODE</a></li>
<li><a href="http://www.bpmscript.org" rel="nofollow" target="_top">BpmScript</a> is a Business Process Engine written using Rhino continuations</li>
<li><a href="http://www.sbbi.net/site/jafs/" rel="nofollow" target="_top">JAFS</a> is an FTP server embedded in a JBI component</li>
<li><a href="http://jbi4corba.sourceforge.net/" rel="nofollow" target="_top">JBI4Corba</a> a JBI component for working with CORBA services</li>
<li><a href="http://jbi4cics.sourceforge.net/" rel="nofollow" target="_top">JBI4Cics</a> a JBI component for working with CICS services</li>
<li><a href="http://jbi4ejb.sourceforge.net/" rel="nofollow" target="_top">JBI4Ejb</a> a JBI component for working for existing EJBs</li>
</ul>
<h3><a name="Componentslist-Lightweightcomponents" target="_top"></a>Lightweight components</h3>
<p>ServiceMix also provides some <a href="/confluence/display/SM/Lightweight+components" title="Lightweight components" target="_top" rel="nofollow">Lightweight components</a>, but theses are rather deprecated and the standard JBI components above should be used instead.</p>
</div>
<div id="commentsSection" class="wiki-content pageSection">
<div style="float: right;">
<a href="http://cwiki.apache.org/confluence/users/viewnotifications.action" class="grey" target="_top" rel="nofollow">Change Notification Preferences</a>
</div>
<a href="http://cwiki.apache.org/confluence/display/SM/Components+list" target="_top" rel="nofollow">View Online</a>
|
<a href="http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=39113&revisedVersion=50&originalVersion=49" target="_top" rel="nofollow">View Change</a>
|
<a href="http://cwiki.apache.org/confluence/display/SM/Components+list?showComments=true&showCommentArea=true#addcomment" target="_top" rel="nofollow">Add Comment</a>
</div>
</div>
</div>
</div>
</div>
</body>
</html>
<p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26268643
[CONF] Apache ServiceMix > Components list
2009-11-09T07:49:00Z
2009-11-09T07:49:00Z
confluence-2
<html>
<head>
<base href="http://cwiki.apache.org/confluence">
<link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=SM&forWysiwyg=true" type="text/css">
</head>
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
<h2><a href="http://cwiki.apache.org/confluence/display/SM/Components+list" target="_top" rel="nofollow">Components list</a></h2>
<h4>Page <b>edited</b> by <a href="http://cwiki.apache.org/confluence/display/~nanthrax" target="_top" rel="nofollow">Jean-Baptiste Onofré</a>
</h4>
<br />
<div class="notificationGreySide">
<p>ServiceMix currently has the following JBI components:</p>
<h2><a name="Componentslist-StandardJBIcomponents" target="_top"></a>Standard JBI components</h2>
<p>The following components ships with ServiceMix distribution:</p>
<ul>
<li><a href="/confluence/display/SM/servicemix-bean" title="servicemix-bean" target="_top" rel="nofollow">servicemix-bean</a> is a JBI component for mapping beans (POJOs) to JBI message exchanges for easy procssing of JBI message exchanges. Note that if you want to support SOAP, type safe business interfaces or JAX-WS / JSR 181 then you should use <a href="/confluence/display/SM/servicemix-jsr181" title="servicemix-jsr181" target="_top" rel="nofollow">servicemix-jsr181</a></li>
<li><a href="/confluence/display/SM/servicemix-bpe" title="servicemix-bpe" target="_top" rel="nofollow">servicemix-bpe</a> (deprecated)</li>
<li><a href="/confluence/display/SM/servicemix-camel" title="servicemix-camel" target="_top" rel="nofollow">servicemix-camel</a></li>
<li><a href="/confluence/display/SM/servicemix-cxf-bc" title="servicemix-cxf-bc" target="_top" rel="nofollow">servicemix-cxf-bc</a></li>
<li><a href="/confluence/display/SM/servicemix-cxf-se" title="servicemix-cxf-se" target="_top" rel="nofollow">servicemix-cxf-se</a></li>
<li><a href="/confluence/display/SM/servicemix-drools" title="servicemix-drools" target="_top" rel="nofollow">servicemix-drools</a></li>
<li><a href="/confluence/display/SM/servicemix-eip" title="servicemix-eip" target="_top" rel="nofollow">servicemix-eip</a> contains several routing patterns based on the great <a href="http://www.enterpriseintegrationpatterns.com/index.html" rel="nofollow" target="_top">EIP</a> book</li>
<li><a href="/confluence/display/SM/servicemix-exec" title="servicemix-exec" target="_top" rel="nofollow">servicemix-exec</a> is a Service Engine that allows to execute system command</li>
<li><a href="/confluence/display/SM/servicemix-file" title="servicemix-file" target="_top" rel="nofollow">servicemix-file</a> is a file system Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-ftp" title="servicemix-ftp" target="_top" rel="nofollow">servicemix-ftp</a> is an FTP Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-http" title="servicemix-http" target="_top" rel="nofollow">servicemix-http</a> is an HTTP/SOAP Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-jms" title="servicemix-jms" target="_top" rel="nofollow">servicemix-jms</a> is a JMS Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-jsr181" title="servicemix-jsr181" target="_top" rel="nofollow">servicemix-jsr181</a> Service Engine can expose annotated POJOs as services</li>
<li><a href="/confluence/display/SM/servicemix-lwcontainer" title="servicemix-lwcontainer" target="_top" rel="nofollow">servicemix-lwcontainer</a> Service Engine can deploy lightweight components</li>
<li><a href="/confluence/display/SM/servicemix-mail" title="servicemix-mail" target="_top" rel="nofollow">servicemix-mail</a> Email Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-osworkflow" title="servicemix-osworkflow" target="_top" rel="nofollow">servicemix-osworkflow</a> OSWorkflow Service Engine</li>
<li><a href="/confluence/display/SM/servicemix-quartz" title="servicemix-quartz" target="_top" rel="nofollow">servicemix-quartz</a></li>
<li><a href="/confluence/display/SM/servicemix-saxon" title="servicemix-saxon" target="_top" rel="nofollow">servicemix-saxon</a></li>
<li><a href="/confluence/display/SM/servicemix-script" title="servicemix-script" target="_top" rel="nofollow">servicemix-script</a> uses Spring Dynamic Language Support</li>
<li><a href="/confluence/display/SM/servicemix-scripting" title="servicemix-scripting" target="_top" rel="nofollow">servicemix-scripting</a> JSR-223 Scripting Engine</li>
<li><a href="/confluence/display/SM/servicemix-smpp" title="servicemix-smpp" target="_top" rel="nofollow">servicemix-smpp</a> SMPP (SMS) Binding Component</li>
<li><a href="/confluence/display/SM/servicemix-snmp" title="servicemix-snmp" target="_top" rel="nofollow">servicemix-snmp</a> SNMP Binding Component</li>
<li><a href="/confluence/pages/createpage.action?spaceKey=SM&title=servicemix-truezip&linkCreation=true&fromPageId=39113" class="createlink" target="_top" rel="nofollow">servicemix-truezip</a></li>
<li><a href="/confluence/display/SM/servicemix-validation" title="servicemix-validation" target="_top" rel="nofollow">servicemix-validation</a> a xml validation engnine</li>
<li><a href="/confluence/display/SM/servicemix-vfs" title="servicemix-vfs" target="_top" rel="nofollow">servicemix-vfs</a> a vfs binding component based on Apache Commons-VFS</li>
<li><a href="/confluence/display/SM/servicemix-wsn2005" title="servicemix-wsn2005" target="_top" rel="nofollow">servicemix-wsn2005</a> is an implementation of WS-Notification</li>
<li><a href="/confluence/display/SM/servicemix-xmpp" title="servicemix-xmpp" target="_top" rel="nofollow">servicemix-xmpp</a> is an XMPP (Jabber) Binding Component</li>
</ul>
<h2><a name="Componentslist-ComponentsRoadmap" target="_top"></a>Components Roadmap</h2>
<p>The following list shows the future components that will be included in ServiceMix distribution :</p>
<table class='confluenceTable'><tbody>
<tr>
<th class='confluenceTh'> Component </th>
<th class='confluenceTh'> Type </th>
<th class='confluenceTh'> Description </th>
<th class='confluenceTh'> Status </th>
<th class='confluenceTh'> Jira </th>
<th class='confluenceTh'> Resource </th>
</tr>
<tr>
<td class='confluenceTd'> servicemix-cache </td>
<td class='confluenceTd'> SE </td>
<td class='confluenceTd'> Provide way for caching sync executions of other components (cxf, http etc) with multiple cache proviers (EHcache, JBoss Cache ..) </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> <a href="https://issues.apache.org/activemq/browse/SMXCOMP-505" rel="nofollow" target="_top">https://issues.apache.org/activemq/browse/SMXCOMP-505</a> </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-ldap </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Poll and send data with a LDAP directory server. </td>
<td class='confluenceTd'> Proto </td>
<td class='confluenceTd'> <a href="https://issues.apache.org/activemq/browse/SMXCOMP-492" rel="nofollow" target="_top">https://issues.apache.org/activemq/browse/SMXCOMP-492</a> </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-atom </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Poll data from RSS/Atom feed. </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-irc </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Send and receive data from IRC channels. </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-jt400 </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Integrates data queues on an AS/400 (aka System i, IBM i5, ...) </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-jcom </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses the Java Communication API (<a href="http://java.sun.com/products/javacomm/" rel="nofollow" target="_top">http://java.sun.com/products/javacomm/</a>) </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> <a href="https://issues.apache.org/activemq/browse/SM-1270" rel="nofollow" target="_top">https://issues.apache.org/activemq/browse/SM-1270</a> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-jdbc </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses JDBC connectivity to poll and send data within a database </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-rmi </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses to get and send marshaled object using RMI-IIOP ORB </td>
<td class='confluenceTd'> Proto </td>
<td class='confluenceTd'> <a href="https://issues.apache.org/activemq/browse/SMXCOMP-586" rel="nofollow" target="_top">https://issues.apache.org/activemq/browse/SMXCOMP-586</a> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-talend </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses to get/put data coming from/to Talend ETL </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> <a href="http://www.talend.com/index.php" rel="nofollow" target="_top">http://www.talend.com/index.php</a> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-asterisk </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses to get/put data coming from/to Asterisk VOIP server </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> <a href="http://www.asterisk.org/" rel="nofollow" target="_top">http://www.asterisk.org/</a> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-sip </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses SIP protocol to get/put data </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-dcom </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Uses to get/put data using Microsoft's DCOM protocol </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-sap </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Interface with SAP </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-hl7 </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Interface with systems supporting HL7 protocol </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> </td>
</tr>
<tr>
<td class='confluenceTd'> servicemix-sdo </td>
<td class='confluenceTd'> BC </td>
<td class='confluenceTd'> Interface with BEA commonj protocol </td>
<td class='confluenceTd'> TODO </td>
<td class='confluenceTd'> </td>
<td class='confluenceTd'> <a href="http://e-docs.bea.com/wls/docs92/commonj/commonj.html" rel="nofollow" target="_top">http://e-docs.bea.com/wls/docs92/commonj/commonj.html</a> </td>
</tr>
</tbody></table>
<h2><a name="Componentslist-ThirdPartyStandardJBIComponents" target="_top"></a>Third Party Standard JBI Components </h2>
<p>These components are a wonderful benefit of JBI that is a direct result of the JBI spec. Because the JBI spec is open, many vendors provide JBI compliant components that can be deployed in ServiceMix. </p>
<h2><a name="Componentslist-ApacheODE" target="_top"></a>Apache ODE</h2>
<p><a href="http://ode.apache.org" rel="nofollow" target="_top">Apache Ode</a> is a BPEL engine which provides a JBI compliant component that can be easily deployed into ServiceMix.</p>
<h3><a name="Componentslist-SunOpenESBJBIComponents" target="_top"></a>Sun OpenESB JBI Components </h3>
<p>The Sun <a href="https://open-esb.dev.java.net/" rel="nofollow" target="_top">OpenESB</a> is based on JBI and provides <a href="https://open-jbi-components.dev.java.net/" rel="nofollow" target="_top">many JBI compliant components</a> that can also be used in ServiceMix. </p>
<h3><a name="Componentslist-ObjectWebPetalsComponents" target="_top"></a>ObjectWeb Petals Components </h3>
<p>The <a href="http://petals.objectweb.org/" rel="nofollow" target="_top">Petals ESB</a> is also based on JBI and provides <a href="http://petals.objectweb.org/downloads.html#component" rel="nofollow" target="_top">JBI compliant components</a> as well. </p>
<h3><a name="Componentslist-VariousHighlyUsefulJBIComponents" target="_top"></a>Various Highly Useful JBI Components </h3>
<ul>
<li>Support for <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel" rel="nofollow" target="_top">WS-BPEL</a> is provided via <a href="http://ode.apache.org/" rel="nofollow" target="_top">Apache ODE</a></li>
<li><a href="http://www.bpmscript.org" rel="nofollow" target="_top">BpmScript</a> is a Business Process Engine written using Rhino continuations</li>
<li><a href="http://www.sbbi.net/site/jafs/" rel="nofollow" target="_top">JAFS</a> is an FTP server embedded in a JBI component</li>
<li><a href="http://jbi4corba.sourceforge.net/" rel="nofollow" target="_top">JBI4Corba</a> a JBI component for working with CORBA services</li>
<li><a href="http://jbi4cics.sourceforge.net/" rel="nofollow" target="_top">JBI4Cics</a> a JBI component for working with CICS services</li>
<li><a href="http://jbi4ejb.sourceforge.net/" rel="nofollow" target="_top">JBI4Ejb</a> a JBI component for working for existing EJBs</li>
</ul>
<h3><a name="Componentslist-Lightweightcomponents" target="_top"></a>Lightweight components</h3>
<p>ServiceMix also provides some <a href="/confluence/display/SM/Lightweight+components" title="Lightweight components" target="_top" rel="nofollow">Lightweight components</a>, but theses are rather deprecated and the standard JBI components above should be used instead.</p>
</div>
<div id="commentsSection" class="wiki-content pageSection">
<div style="float: right;">
<a href="http://cwiki.apache.org/confluence/users/viewnotifications.action" class="grey" target="_top" rel="nofollow">Change Notification Preferences</a>
</div>
<a href="http://cwiki.apache.org/confluence/display/SM/Components+list" target="_top" rel="nofollow">View Online</a>
|
<a href="http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=39113&revisedVersion=50&originalVersion=49" target="_top" rel="nofollow">View Change</a>
|
<a href="http://cwiki.apache.org/confluence/display/SM/Components+list?showComments=true&showCommentArea=true#addcomment" target="_top" rel="nofollow">Add Comment</a>
</div>
</div>
</div>
</div>
</div>
</body>
</html>
<p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26268641
[jira] Commented: (SMXCOMP-621) SDO integration
2009-11-09T07:48:52Z
2009-11-09T07:48:52Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SMXCOMP-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55234#action_55234" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55234#action_55234</a> ]
<br><br>Jean-Baptiste Onofré commented on SMXCOMP-621:
<br>----------------------------------------------
<br><br>Hi James,
<br><br>agreed, a SDO BC could be very helpful.
<br><br>I added it in the component roadmap:
<br><a href="http://servicemix.apache.org/components-list.html" target="_top" rel="nofollow">http://servicemix.apache.org/components-list.html</a><br><br>Regards
<br>JB
<br><div class='shrinkable-quote'><br>> SDO integration
<br>> ---------------
<br>>
<br>> Key: SMXCOMP-621
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SMXCOMP-621" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-621</a><br>> Project: ServiceMix Components
<br>> Issue Type: New Feature
<br>> Reporter: James Strachan
<br>>
<br>> We could do with an implementation of SDO
<br>> <a href="http://dev2dev.bea.com/wlplatform/commonj/" target="_top" rel="nofollow">http://dev2dev.bea.com/wlplatform/commonj/</a><br>> and integration with SDO as a BindingComponent
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26268475
[PROPOSAL] Release 2009.02 components set
2009-11-09T07:39:55Z
2009-11-09T07:39:55Z
Jean-Baptiste Onofré
Hi guys,
<br><br>I think that we can prepare and stage a new components 2009.02 release set.
<br><br>I have noticed the following open Jira tasks around components. Could
<br>you confirm that it's not blocking pending issues for the release:
<br><br>Task Component Severity
<br>SMXCOMP-670 JMS
<br>SMXCOMP-667 JMS
<br>SMXCOMP-664 Camel minor (not blocking)
<br>SMXCOMP-661 Drools minor (not blocking)
<br>SMXCOMP-660 CXF-BC minor (not blocking)
<br>SMXCOMP-658 HTTP minor (not blocking)
<br>SMXCOMP-655 CXF-BC good to have
<br>SMXCOMP-654 CXF-BC minor
<br>SMXCOMP-652 HTTP good to have
<br>SMXCOMP-649 CXF-BC good to have
<br>SMXCOMP-647 Test/All minor
<br>SMXCOMP-645 EIP minor
<br>SMXCOMP-643 File minor
<br>SMXCOMP-642 HTTP good to have
<br>SMXCOMP-641 HTTP minor
<br>SMXCOMP-638 JMS minor
<br>SMXCOMP-635 XMPP minor
<br>SMXCOMP-631 All minor
<br>SMXCOMP-625 CXF-BC minor
<br>SMXCOMP-624 JMS minor
<br>SMXCOMP-623 HTTP minor
<br>SMXCOMP-622 HTTP minor
<br><br>If you see other tasks that need to be included in the release, feel
<br>free to add it.
<br><br>I propose to release component-pom 4 this evening and update all
<br>components to use it tonight and I will begin the components release
<br>tomorrow morning (GMT+1 time).
<br>I propose to add the exec and smpp components (with the WSDL support in
<br>the 2009.02 set.
<br><br>Regards
<br>JB
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26268452
[jira] Resolved: (SMXCOMP-615) Servicemix http binding component does not set the content-type header correctly for soap 1.2 to application/soap+xml
2009-11-09T07:38:52Z
2009-11-09T07:38:52Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SMXCOMP-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Jean-Baptiste Onofré resolved SMXCOMP-615.
<br>------------------------------------------
<br><br> Resolution: Fixed
<br> Fix Version/s: servicemix-http-2009.02
<br> Assignee: Jean-Baptiste Onofré
<br><br>Fix on the servicemix-http trunk (2009.02-SNAPSHOT).
<br><div class='shrinkable-quote'><br>> Servicemix http binding component does not set the content-type header correctly for soap 1.2 to application/soap+xml
<br>> ---------------------------------------------------------------------------------------------------------------------
<br>>
<br>> Key: SMXCOMP-615
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SMXCOMP-615" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-615</a><br>> Project: ServiceMix Components
<br>> Issue Type: Bug
<br>> Components: servicemix-http
<br>> Affects Versions: servicemix-http-2008.01
<br>> Reporter: Harsh Marwaha
<br>> Assignee: Jean-Baptiste Onofré
<br>> Fix For: servicemix-http-2009.02
<br>>
<br>>
<br>> The content type header is not set correctly for Soap 1.2. The header needs to be application/soap+xml
<br>> Axis 2 (not sure about others) generated clients verify this header with the SOAP URI in the envelope and therefore do not work with the http BC.
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26268183
Re: Camel 2.0 / servicemix-camel 2009.02
2009-11-09T07:23:33Z
2009-11-09T07:23:33Z
Jean-Baptiste Onofré
Hi Markus,
<br><br>we're preparing a 2009.02 release of components. We need to fix some
<br>issues first.
<br><br>I think that we will be able to release the new components set in the
<br>following week.
<br><br>Regards
<br>JB
<br><br>Markus Wolf wrote:
<div class='shrinkable-quote'><br>> -----BEGIN PGP SIGNED MESSAGE-----
<br>> Hash: SHA1
<br>>
<br>> Hi there,
<br>>
<br>> are there any plans to release servicemix-camel 2009.02 in the near
<br>> future? We have a component requiring camel 2.0 and use servicemix 3.3.1
<br>> and noticed that camel 2.0 is not supported currently.
<br>>
<br>> Thanks
<br>> Markus Wolf
<br>> - --
<br>> NMMN - New Media Markets & Networks GmbH
<br>> Langbehnstrasse 6, 22761 Hamburg
<br>> Geschäftsführung: Kfm. Michael Schütt
<br>> Finanzamt HH-Altona - UStID DE 812 699 852 - HRB 71102 Hamburg
<br>> HypoVereinsbank - BLZ 200 300 00 - Konto-Nr. 156 29 82
<br>>
<br>> <a href="http://www.nmmn.com" target="_top" rel="nofollow">http://www.nmmn.com</a><br>> Tel.: +49 40 284 118-0 - Fax: +49 40 284118-999
<br>> Softwareentwicklung LLynch: -720
<br>> -----BEGIN PGP SIGNATURE-----
<br>> Version: GnuPG v1.4.9 (GNU/Linux)
<br>> Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_top" rel="nofollow">http://enigmail.mozdev.org</a><br>>
<br>> iEYEARECAAYFAkr4MgMACgkQDBHISU1oEKH3DACfRfXX6UKocQAe/pWqu6TbZrAU
<br>> eE4AoMa6PYywKRE6PMck34nr3emTQQT7
<br>> =0nye
<br>> -----END PGP SIGNATURE-----
<br></div><p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26268038
Camel 2.0 / servicemix-camel 2009.02
2009-11-09T07:15:15Z
2009-11-09T07:15:15Z
KnisterPeter
-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>Hi there,
<br><br>are there any plans to release servicemix-camel 2009.02 in the near
<br>future? We have a component requiring camel 2.0 and use servicemix 3.3.1
<br>and noticed that camel 2.0 is not supported currently.
<br><br>Thanks
<br>Markus Wolf
<br>- --
<br>NMMN - New Media Markets & Networks GmbH
<br>Langbehnstrasse 6, 22761 Hamburg
<br>Geschäftsführung: Kfm. Michael Schütt
<br>Finanzamt HH-Altona - UStID DE 812 699 852 - HRB 71102 Hamburg
<br>HypoVereinsbank - BLZ 200 300 00 - Konto-Nr. 156 29 82
<br><br><a href="http://www.nmmn.com" target="_top" rel="nofollow">http://www.nmmn.com</a><br>Tel.: +49 40 284 118-0 - Fax: +49 40 284118-999
<br>Softwareentwicklung LLynch: -720
<br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.9 (GNU/Linux)
<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_top" rel="nofollow">http://enigmail.mozdev.org</a><br><br>iEYEARECAAYFAkr4MgMACgkQDBHISU1oEKH3DACfRfXX6UKocQAe/pWqu6TbZrAU
<br>eE4AoMa6PYywKRE6PMck34nr3emTQQT7
<br>=0nye
<br>-----END PGP SIGNATURE-----
<br><p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26267989
Re: Camel vs. SMX Maven repository
2009-11-09T07:11:18Z
2009-11-09T07:11:18Z
Jean-Baptiste Onofré
Hi Martin,
<br><br>thanks for the update, I will add the new repo in the servicemix-camel pom.
<br><br>Regards
<br>JB
<br><br>Martin Krasser wrote:
<div class='shrinkable-quote'><br>> Hi Jean-Baptiste,
<br>>
<br>> seems that there are no objections against uploading the artifacts to
<br>> <a href="https://svn.apache.org/repos/asf/camel/m2-repo" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo</a>. So I'll put them there.
<br>>
<br>> Jean-Baptiste Onofré schrieb:
<br>>> Hi Martin,
<br>>>
<br>>> for my part, I think that we need to consider Camel as a SMX
<br>>> dependency (like CXF, ActiveMQ, etc). So, Camel should upload
<br>>> artifacts and dependencies to
<br>>> <a href="https://svn.apache.org/repos/asf/camel/m2-repo" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo</a> and the ServiceMix
<br>>> Camel component should have this repository in its pom.
<br>>>
<br>>> Let see the feeling of the other guys.
<br>>>
<br>>> Regards
<br>>> JB
<br>>>
<br>>> Martin Krasser wrote:
<br>>>> Hi,
<br>>>>
<br>>>> I started a thread on the Camel dev mailing list discussing which
<br>>>> Maven repo to use for uploading new artifacts needed by Camel.
<br>>>>
<br>>>> <a href="http://old.nabble.com/GAE-API-in-Maven-repo-tt26243221s22882.html" target="_top" rel="nofollow">http://old.nabble.com/GAE-API-in-Maven-repo-tt26243221s22882.html</a><br>>>>
<br>>>> We finally discussed the two options:
<br>>>>
<br>>>> - <a href="https://svn.apache.org/repos/asf/servicemix/m2-repo/" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/servicemix/m2-repo/</a> (ServiceMix
<br>>>> Maven repo)
<br>>>> - <a href="https://svn.apache.org/repos/asf/camel/m2-repo/" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo/</a> (Camel Maven repo)
<br>>>> Camel already uses the ServiceMix repo to download jars. Which option
<br>>>> do you prefer?
<br>>>>
<br>>>> Thanks,
<br>>>> Martin
<br>>>>
<br>>>>
<br>>>
<br>>
<br></div><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26267961
Re: Camel vs. SMX Maven repository
2009-11-09T07:09:47Z
2009-11-09T07:09:47Z
Martin Krasser
Hi Jean-Baptiste,
<br><br>seems that there are no objections against uploading the artifacts to
<br><a href="https://svn.apache.org/repos/asf/camel/m2-repo" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo</a>. So I'll put them there.
<br><br>Jean-Baptiste Onofré schrieb:
<div class='shrinkable-quote'><br>> Hi Martin,
<br>>
<br>> for my part, I think that we need to consider Camel as a SMX
<br>> dependency (like CXF, ActiveMQ, etc). So, Camel should upload
<br>> artifacts and dependencies to
<br>> <a href="https://svn.apache.org/repos/asf/camel/m2-repo" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo</a> and the ServiceMix
<br>> Camel component should have this repository in its pom.
<br>>
<br>> Let see the feeling of the other guys.
<br>>
<br>> Regards
<br>> JB
<br>>
<br>> Martin Krasser wrote:
<br>>> Hi,
<br>>>
<br>>> I started a thread on the Camel dev mailing list discussing which
<br>>> Maven repo to use for uploading new artifacts needed by Camel.
<br>>>
<br>>> <a href="http://old.nabble.com/GAE-API-in-Maven-repo-tt26243221s22882.html" target="_top" rel="nofollow">http://old.nabble.com/GAE-API-in-Maven-repo-tt26243221s22882.html</a><br>>>
<br>>> We finally discussed the two options:
<br>>>
<br>>> - <a href="https://svn.apache.org/repos/asf/servicemix/m2-repo/" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/servicemix/m2-repo/</a> (ServiceMix
<br>>> Maven repo)
<br>>> - <a href="https://svn.apache.org/repos/asf/camel/m2-repo/" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo/</a> (Camel Maven repo)
<br>>> Camel already uses the ServiceMix repo to download jars. Which option
<br>>> do you prefer?
<br>>>
<br>>> Thanks,
<br>>> Martin
<br>>>
<br>>>
<br>>
</div><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26267313
Re: Generating Camel SU with Maven
2009-11-09T06:26:03Z
2009-11-09T06:26:03Z
willem.jiang
Hi Kenneth,
<br><br>Can you try to download the spring-remoting.jar from this url?
<br><a href="http://repo1.maven.org/maven2/org/springframework/spring-remoting/2.0.8/spring-remoting-2.0.8.jar" target="_top" rel="nofollow">http://repo1.maven.org/maven2/org/springframework/spring-remoting/2.0.8/spring-remoting-2.0.8.jar</a><br><br>I just tried it on my box, it works.
<br>I also tried to run mvn install on the created camel su artifact, it
<br>works as I expected.
<br><br>Please check you network, to make sure you can access
<br><a href="http://repo1.maven.org/maven2" target="_top" rel="nofollow">http://repo1.maven.org/maven2</a>.
<br><br>Willem
<br><br>Kenneth H wrote:
<div class='shrinkable-quote'><br>> Hi Willem,
<br>>
<br>> It is now possible for me to:
<br>>
<br>> 1. Use the command: smx-arch su camel to create the SU
<br>> (see www.henriksenweb.com/servicemix/9.png)
<br>>
<br>> 2. Use the command: smx-arch sa to create the SA
<br>> (see www.henriksenweb.com/servicemix/10.png)
<br>>
<br>> But when I try to put it all together with the command: mvn install I get
<br>> the error below
<br>> (or see www.henriksenweb.com/servicemix/11.png):
<br>>
<br>> [INFO] Unable to find resource
<br>> 'org.springframework:spring-remoting:jar:2.0.8' in repository codehaus
<br>> (<a href="http://repository.codehaus.org" target="_top" rel="nofollow">http://repository.codehaus.org</a>)
<br>> Downloading:
<br>> <a href="http://download.java.net/maven/1/org.springframework/jars/spring-remoting-2.0.8.jar" target="_top" rel="nofollow">http://download.java.net/maven/1/org.springframework/jars/spring-remoting-2.0.8.jar</a><br>> [INFO] Unable to find resource
<br>> 'org.springframework:spring-remoting:jar:2.0.8' in repository java.net
<br>> (<a href="http://download.java.net/maven/1" target="_top" rel="nofollow">http://download.java.net/maven/1</a>)
<br>> Downloading:
<br>> <a href="http://repo1.maven.org/maven2/org/springframework/spring-remoting/2.0.8/spring-remoting-2.0.8.jar" target="_top" rel="nofollow">http://repo1.maven.org/maven2/org/springframework/spring-remoting/2.0.8/spring-remoting-2.0.8.jar</a><br>>
<br>> [INFO] [jbi:generate-depends-file {execution:
<br>> default-generate-depends-file}]
<br>> [INFO] Created:
<br>> C:\Servicemix\Test\Test3\my-camel-su\target\classes\META-INF\maven\dependencies.properties
<br>> [INFO] [compiler:compile {execution: default-compile}]
<br>> [INFO] Compiling 1 source file to
<br>> C:\Servicemix\Test\Test3\my-camel-su\target\classes
<br>> [INFO]
<br>> ------------------------------------------------------------------------
<br>> [ERROR] BUILD FAILURE
<br>> [INFO]
<br>> ------------------------------------------------------------------------
<br>> [INFO] Compilation failure
<br>>
<br>> error: error reading C:\Users\Kenneth
<br>> Henriksen\.m2\repository\org\springframework\spring-support\2.0.6\spring-support-2.0.6.jar;
<br>> error in opening zip file
<br>> error: error reading C:\Users\Kenneth
<br>> Henriksen\.m2\repository\xerces\xerces\2.0.2\xerces-2.0.2.jar; error in
<br>> opening zip file
<br>>
<br>> [INFO]
<br>> ------------------------------------------------------------------------
<br>> [INFO] For more information, run Maven with the -e switch
<br>> [INFO]
<br>> ------------------------------------------------------------------------
<br>> [INFO] Total time: 44 seconds
<br>> [INFO] Finished at: Sat Nov 07 01:06:26 CET 2009
<br>> [INFO] Final Memory: 25M/44M
<br>> [INFO]
<br>> ------------------------------------------------------------------------
<br>>
<br>> I have no idea what this is about. Hoping (again) for your help.
<br>>
<br>> Kind regards, Kenneth H
<br>>
</div><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26265009
[jira] Commented: (SMXCOMP-638) NotSerializableException with JMSFlow when camel returns an exception.
2009-11-09T03:44:52Z
2009-11-09T03:44:52Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SMXCOMP-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55226#action_55226" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55226#action_55226</a> ]
<br><br>Willem Jiang commented on SMXCOMP-638:
<br>--------------------------------------
<br><br>@Gertv
<br>+1 for you suggestion, it gives us a better back ward compatibility.
<br><br><br><br><div class='shrinkable-quote'><br>> NotSerializableException with JMSFlow when camel returns an exception.
<br>> -----------------------------------------------------------------------
<br>>
<br>> Key: SMXCOMP-638
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SMXCOMP-638" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-638</a><br>> Project: ServiceMix Components
<br>> Issue Type: Bug
<br>> Components: servicemix-camel
<br>> Affects Versions: servicemix-camel-2009.01
<br>> Reporter: Giovani Seben
<br>> Assignee: Gert Vanthienen
<br>> Attachments: fix.patch, JbiCamelExceptionsTest.java, MOD_testcase.patch, SMXCOMP-638.patch, smxcomp638.patch
<br>>
<br>>
<br>> In servicemix when a camel route handles an exception that is then returned to the NMR it will attempt to return the exception object with the exchange. Using JMSFlow if the exception object is not serializable, it will fail to be sent back with a NotSerializableException. This is similar to SMXCOMP-18, but instead the problem here happens with the CamelProviderEndpoint.
<br>> Below is the full exception stack trace:
<br>> {code}
<br>> java.lang.RuntimeException: org.apache.servicemix.camel.JbiExchange
<br>> at org.apache.activemq.command.ActiveMQObjectMessage.storeContent(ActiveMQObjectMessage.java:104)
<br>> at org.apache.activemq.command.ActiveMQObjectMessage.setObject(ActiveMQObjectMessage.java:155)
<br>> at org.apache.activemq.ActiveMQSession.createObjectMessage(ActiveMQSession.java:319)
<br>> at org.apache.activemq.pool.PooledSession.createObjectMessage(PooledSession.java:149)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.doRouting(AbstractJMSFlow.java:480)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.doSend(AbstractJMSFlow.java:435)
<br>> at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.send(AbstractFlow.java:126)
<br>> at org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(DefaultBroker.java:283)
<br>> at org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket(SecuredBroker.java:88)
<br>> at org.apache.servicemix.jbi.container.JBIContainer.sendExchange(JBIContainer.java:882)
<br>> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:396)
<br>> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:432)
<br>> at org.apache.servicemix.common.EndpointDeliveryChannel.send(EndpointDeliveryChannel.java:79)
<br>> at org.apache.servicemix.common.endpoints.SimpleEndpoint.send(SimpleEndpoint.java:70)
<br>> at org.apache.servicemix.common.endpoints.SimpleEndpoint.fail(SimpleEndpoint.java:94)
<br>> at org.apache.servicemix.camel.CamelProviderEndpoint.handleActiveProviderExchange(CamelProviderEndpoint.java:128)
<br>> at org.apache.servicemix.camel.CamelProviderEndpoint.process(CamelProviderEndpoint.java:73)
<br>> at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:540)
<br>> at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:492)
<br>> at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
<br>> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:623)
<br>> at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:183)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.access$401(AbstractJMSFlow.java:63)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow$4.run(AbstractJMSFlow.java:517)
<br>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
<br>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
<br>> at java.lang.Thread.run(Thread.java:595)
<br>> Caused by: java.io.NotSerializableException: org.apache.servicemix.camel.JbiExchange
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
<br>> at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
<br>> at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
<br>> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
<br>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
<br>> at java.util.HashMap.writeObject(HashMap.java:1039)
<br>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
<br>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
<br>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
<br>> at java.lang.reflect.Method.invoke(Method.java:585)
<br>> at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
<br>> at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
<br>> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
<br>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
<br>> at org.apache.servicemix.jbi.messaging.ExchangePacket.writeExternal(ExchangePacket.java:404)
<br>> at org.apache.servicemix.jbi.messaging.MessageExchangeImpl.writeExternal(MessageExchangeImpl.java:605)
<br>> at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
<br>> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
<br>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
<br>> at org.apache.activemq.command.ActiveMQObjectMessage.storeContent(ActiveMQObjectMessage.java:98)
<br>> {code}
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26264693
[jira] Updated: (SMXCOMP-638) NotSerializableException with JMSFlow when camel returns an exception.
2009-11-09T03:16:52Z
2009-11-09T03:16:52Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SMXCOMP-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Gert Vanthienen updated SMXCOMP-638:
<br>------------------------------------
<br><br> Attachment: JbiCamelExceptionsTest.java
<br><br>Using the patches provided will convert all exceptions into a JBI-specific exception type -- up to now, we just conveyed these back in the original type (as shown in the first test in the attached JbiCamelExceptionsTest), allowing us to handle it in a Camel route (as shown in the second test).
<br><br>Considering that all exceptions implement the Serializable interface so they're supposed to be serializable, I would suggest we keep this behavior as the default as I think a lot of people are relying on this when they are using Camel for defining exception handling inside servicemix.
<br><br>However, to handle this scenario with non-serializable exceptions and properties, I would like to suggest we add two optional flags to the endpoint:
<br>- *{{convertExceptions}}* to convert all exceptions in a JB-specific exception type, so people can use this to handle non-serializable exceptions
<br>- *{{serialization=strict}}* to perform a strict serialiation check (by attempting the write to a byte array output stream as suggested earlier by Giovani
<br><br>Wdyt?
<br><div class='shrinkable-quote'><br>> NotSerializableException with JMSFlow when camel returns an exception.
<br>> -----------------------------------------------------------------------
<br>>
<br>> Key: SMXCOMP-638
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SMXCOMP-638" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-638</a><br>> Project: ServiceMix Components
<br>> Issue Type: Bug
<br>> Components: servicemix-camel
<br>> Affects Versions: servicemix-camel-2009.01
<br>> Reporter: Giovani Seben
<br>> Assignee: Gert Vanthienen
<br>> Attachments: fix.patch, JbiCamelExceptionsTest.java, MOD_testcase.patch, SMXCOMP-638.patch, smxcomp638.patch
<br>>
<br>>
<br>> In servicemix when a camel route handles an exception that is then returned to the NMR it will attempt to return the exception object with the exchange. Using JMSFlow if the exception object is not serializable, it will fail to be sent back with a NotSerializableException. This is similar to SMXCOMP-18, but instead the problem here happens with the CamelProviderEndpoint.
<br>> Below is the full exception stack trace:
<br>> {code}
<br>> java.lang.RuntimeException: org.apache.servicemix.camel.JbiExchange
<br>> at org.apache.activemq.command.ActiveMQObjectMessage.storeContent(ActiveMQObjectMessage.java:104)
<br>> at org.apache.activemq.command.ActiveMQObjectMessage.setObject(ActiveMQObjectMessage.java:155)
<br>> at org.apache.activemq.ActiveMQSession.createObjectMessage(ActiveMQSession.java:319)
<br>> at org.apache.activemq.pool.PooledSession.createObjectMessage(PooledSession.java:149)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.doRouting(AbstractJMSFlow.java:480)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.doSend(AbstractJMSFlow.java:435)
<br>> at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.send(AbstractFlow.java:126)
<br>> at org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(DefaultBroker.java:283)
<br>> at org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket(SecuredBroker.java:88)
<br>> at org.apache.servicemix.jbi.container.JBIContainer.sendExchange(JBIContainer.java:882)
<br>> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:396)
<br>> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:432)
<br>> at org.apache.servicemix.common.EndpointDeliveryChannel.send(EndpointDeliveryChannel.java:79)
<br>> at org.apache.servicemix.common.endpoints.SimpleEndpoint.send(SimpleEndpoint.java:70)
<br>> at org.apache.servicemix.common.endpoints.SimpleEndpoint.fail(SimpleEndpoint.java:94)
<br>> at org.apache.servicemix.camel.CamelProviderEndpoint.handleActiveProviderExchange(CamelProviderEndpoint.java:128)
<br>> at org.apache.servicemix.camel.CamelProviderEndpoint.process(CamelProviderEndpoint.java:73)
<br>> at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:540)
<br>> at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:492)
<br>> at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
<br>> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:623)
<br>> at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:183)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.access$401(AbstractJMSFlow.java:63)
<br>> at org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow$4.run(AbstractJMSFlow.java:517)
<br>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
<br>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
<br>> at java.lang.Thread.run(Thread.java:595)
<br>> Caused by: java.io.NotSerializableException: org.apache.servicemix.camel.JbiExchange
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
<br>> at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
<br>> at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
<br>> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
<br>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
<br>> at java.util.HashMap.writeObject(HashMap.java:1039)
<br>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
<br>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
<br>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
<br>> at java.lang.reflect.Method.invoke(Method.java:585)
<br>> at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
<br>> at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
<br>> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
<br>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
<br>> at org.apache.servicemix.jbi.messaging.ExchangePacket.writeExternal(ExchangePacket.java:404)
<br>> at org.apache.servicemix.jbi.messaging.MessageExchangeImpl.writeExternal(MessageExchangeImpl.java:605)
<br>> at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
<br>> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
<br>> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
<br>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
<br>> at org.apache.activemq.command.ActiveMQObjectMessage.storeContent(ActiveMQObjectMessage.java:98)
<br>> {code}
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26262729
[jira] Created: (SMXCOMP-670) jms:soap-provider doesn't use custom marshaler
2009-11-09T00:28:52Z
2009-11-09T00:28:52Z
JIRA jira@apache.org
jms:soap-provider doesn't use custom marshaler
<br>----------------------------------------------
<br><br> Key: SMXCOMP-670
<br> URL: <a href="https://issues.apache.org/activemq/browse/SMXCOMP-670" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMXCOMP-670</a><br> Project: ServiceMix Components
<br> Issue Type: Bug
<br> Components: servicemix-jms
<br> Affects Versions: servicemix-jms-2009.01
<br> Environment: OS: Linux chriNB 2.6.24-24-generic #1 SMP Fri Jul 24 22:46:06 UTC 2009 i686 GNU/Linux
<br><br>JAVA:
<br>java version "1.6.0_14"
<br>Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
<br>Java HotSpot(TM) Server VM (build 14.0-b16, mixed mode)
<br><br>Server:
<br>apache-tomcat-6.0.14
<br> Reporter: Christian Connert
<br><br><br>Hi,
<br><br>The JmsSoapProviderEndpoint overrides the the custom JmsSoapProviderMarshaler in it's validate method:
<br><br> @Override
<br> public void validate() throws DeploymentException {
<br> if (wsdl == null) {
<br> throw new DeploymentException("wsdl property must be set");
<br> }
<br> JmsSoapProviderMarshaler marshaler = new JmsSoapProviderMarshaler();
<br> try {
<br> description = DomUtil.parse(wsdl.getInputStream());
<br> Element elem = description.getDocumentElement();
<br> if (WSDLUtils.WSDL1_NAMESPACE.equals(elem.getNamespaceURI())) {
<br> validateWsdl1(marshaler);
<br> } else if (WSDLUtils.WSDL2_NAMESPACE.equals(elem.getNamespaceURI())) {
<br> validateWsdl2(marshaler);
<br> } else {
<br> throw new DeploymentException("Unrecognized wsdl namespace: " + elem.getNamespaceURI());
<br> }
<br> marshaler.setUseJbiWrapper(useJbiWrapper);
<br> marshaler.setPolicies(policies);
<br> setMarshaler(marshaler);
<br> } catch (DeploymentException e) {
<br> throw e;
<br> } catch (Exception e) {
<br> throw new DeploymentException("Unable to read WSDL from: " + wsdl, e);
<br> }
<br> super.validate();
<br> }
<br><br>Thus one can't add a custom marshaler for this type of endpoint. A possible fix would be:
<br><br> public void validate() throws DeploymentException {
<br> if (wsdl == null) {
<br> throw new DeploymentException("wsdl property must be set");
<br> }
<br> JmsSoapProviderMarshaler marshaler = getMarshaler();
<br> if(marshaler==null)
<br> marshaler = new JmsSoapProviderMarshaler();
<br> try {
<br> description = DomUtil.parse(wsdl.getInputStream());
<br> Element elem = description.getDocumentElement();
<br> if (WSDLUtils.WSDL1_NAMESPACE.equals(elem.getNamespaceURI())) {
<br> validateWsdl1(marshaler);
<br> } else if (WSDLUtils.WSDL2_NAMESPACE.equals(elem.getNamespaceURI())) {
<br> validateWsdl2(marshaler);
<br> } else {
<br> throw new DeploymentException("Unrecognized wsdl namespace: " + elem.getNamespaceURI());
<br> }
<br> marshaler.setUseJbiWrapper(useJbiWrapper);
<br> marshaler.setPolicies(policies);
<br> setMarshaler(marshaler);
<br> } catch (DeploymentException e) {
<br> throw e;
<br> } catch (Exception e) {
<br> throw new DeploymentException("Unable to read WSDL from: " + wsdl, e);
<br> }
<br> super.validate();
<br> }
<br><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26262022
[jira] Resolved: (SMX4NMR-171) when stop a bundle, the underlying counterpart JBI sa/component/sharedlib instance in the bundle should be removed from jmx server
2009-11-08T23:02:53Z
2009-11-08T23:02:53Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SMX4NMR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMX4NMR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Freeman Fang resolved SMX4NMR-171.
<br>----------------------------------
<br><br> Resolution: Fixed
<br><br>commit fix
<br><a href="http://svn.apache.org/viewvc?rev=833981&view=rev" target="_top" rel="nofollow">http://svn.apache.org/viewvc?rev=833981&view=rev</a><br><div class='shrinkable-quote'><br>> when stop a bundle, the underlying counterpart JBI sa/component/sharedlib instance in the bundle should be removed from jmx server
<br>> ----------------------------------------------------------------------------------------------------------------------------------
<br>>
<br>> Key: SMX4NMR-171
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SMX4NMR-171" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMX4NMR-171</a><br>> Project: ServiceMix NMR
<br>> Issue Type: Bug
<br>> Reporter: Freeman Fang
<br>> Assignee: Freeman Fang
<br>> Fix For: 1.1.0
<br>>
<br>>
<br>> currently for example, if you do osgi:refresh 115, assuming bundle with id 115 is servicemix-http component, then you will get exception when start the bundle and try to do jmx registration like
<br>> Caused by: javax.management.InstanceAlreadyExistsException: org.apache.servicemix:Type=Component,Name=servicemix-http,SubType=LifeCycle
<br>> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
<br>> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
<br>> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
<br>> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
<br>> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
<br>> at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
<br>> in the log.
<br>> we need remove the old instance reference from jmx server when stop the bundle
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26262003
svn commit: r833981 - /servicemix/smx4/nmr/trunk/jbi/deployer/src/main/java/org/apache/servicemix/jbi/deployer/impl/Deployer.java
2009-11-08T22:59:08Z
2009-11-08T22:59:08Z
ffang
Author: ffang
<br>Date: Mon Nov 9 06:59:07 2009
<br>New Revision: 833981
<br><br>URL: <a href="http://svn.apache.org/viewvc?rev=833981&view=rev" target="_top" rel="nofollow">http://svn.apache.org/viewvc?rev=833981&view=rev</a><br>Log:
<br>[SMX4NMR-171]when stop a bundle, the underlying counterpart JBI sa/component/sharedlib instance in the bundle should be removed from jmx server
<br><br>Modified:
<br> servicemix/smx4/nmr/trunk/jbi/deployer/src/main/java/org/apache/servicemix/jbi/deployer/impl/Deployer.java
<br><br>Modified: servicemix/smx4/nmr/trunk/jbi/deployer/src/main/java/org/apache/servicemix/jbi/deployer/impl/Deployer.java
<br>URL: <a href="http://svn.apache.org/viewvc/servicemix/smx4/nmr/trunk/jbi/deployer/src/main/java/org/apache/servicemix/jbi/deployer/impl/Deployer.java?rev=833981&r1=833980&r2=833981&view=diff" target="_top" rel="nofollow">http://svn.apache.org/viewvc/servicemix/smx4/nmr/trunk/jbi/deployer/src/main/java/org/apache/servicemix/jbi/deployer/impl/Deployer.java?rev=833981&r1=833980&r2=833981&view=diff</a><br>==============================================================================
<br>--- servicemix/smx4/nmr/trunk/jbi/deployer/src/main/java/org/apache/servicemix/jbi/deployer/impl/Deployer.java (original)
<br>+++ servicemix/smx4/nmr/trunk/jbi/deployer/src/main/java/org/apache/servicemix/jbi/deployer/impl/Deployer.java Mon Nov 9 06:59:07 2009
<br>@@ -497,6 +497,11 @@
<br> ((SharedLibraryImpl) lib).removeComponent(component);
<br> }
<br> components.remove(component.getName());
<br>+ try {
<br>+ getManagementStrategy().unmanageObject(component);
<br>+ } catch (Exception e) {
<br>+ LOGGER.error("Error unmanage component: " + component.getName(), e);
<br>+ }
<br> }
<br> }
<br>
<br>@@ -505,6 +510,11 @@
<br> serviceAssemblies.remove(assembly.getName());
<br> pendingAssemblies.remove(assembly);
<br> unregisterServices(assembly.getBundle());
<br>+ try {
<br>+ getManagementStrategy().unmanageObject(assembly);
<br>+ } catch (Exception e) {
<br>+ LOGGER.error("Error unmanage service assembly: " + assembly.getName(), e);
<br>+ }
<br> for (ServiceUnitImpl su : assembly.getServiceUnitsList()) {
<br> su.getComponentImpl().removeServiceUnit(su);
<br> }
<br>@@ -515,6 +525,11 @@
<br> if (library != null) {
<br> // TODO: shutdown all components
<br> sharedLibraries.remove(library.getName());
<br>+ try {
<br>+ getManagementStrategy().unmanageObject(library);
<br>+ } catch (Exception e) {
<br>+ LOGGER.error("Error unmanage sharedlibrary: " + library.getName(), e);
<br>+ }
<br> }
<br> }
<br>
<br><br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26260776
When external service is shut down, message don't rollback to jms queue.
2009-11-08T19:26:55Z
2009-11-08T19:26:55Z
colin.chi
work flow as follow:
<br><br>[external client]--->cxf-bc-consumer--->jms-provider--->jms queue
<br><br>jms queue--->jms-consumer--->cxf-bc-provider--->[external service]
<br><br>when external service is shut down, message don't rollback to jms queue and throw exception.
<br><br>how to config jms consumer and cxf bc provider to do this case?
<br><br>=======================log begin==========================
<br><br>2009-11-09 11:19:28,046 DEBUG - JettyHTTPDestination - Service http request on thread: Thread[22434271@qtp0-0,5,RMI Runt
<br>ime]
<br>2009-11-09 11:19:28,046 DEBUG - AbstractHTTPDestination - Request Headers: {connection=[Keep-Alive], Host=[localhost:8080],
<br> Content-Length=[364], User-Agent=[Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; GOSURF)], accept-encoding=[gzip
<br>, deflate], Accept=[*/*], Cache-Control=[no-cache]}
<br>2009-11-09 11:19:28,046 DEBUG - PhaseInterceptorChain - Chain org.apache.cxf.phase.PhaseInterceptorChain@735ad7 was creat
<br>ed. Current flow:
<br> receive [AttachmentInInterceptor]
<br> post-stream [StaxInInterceptor]
<br> read [ReadHeadersInterceptor]
<br> pre-protocol [, MustUnderstandInterceptor, JbiJAASInterceptor]
<br> unmarshal [JbiOperationInterceptor]
<br> pre-invoke [JbiInWsdl1Interceptor, JbiInInterceptor]
<br> invoke [JbiInvokerInterceptor]
<br> post-invoke [JbiPostInvokerInterceptor, OutgoingChainInterceptor]
<br><br>2009-11-09 11:19:28,125 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.interceptor.
<br>AttachmentInInterceptor@14d8c8
<br>2009-11-09 11:19:28,125 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.interceptor.
<br>StaxInInterceptor@a4480d
<br>2009-11-09 11:19:28,125 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.binding.soap
<br>.interceptor.ReadHeadersInterceptor@1766d9c
<br>2009-11-09 11:19:28,125 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.servicemix.cxfbc
<br>.CxfBcConsumer$1@1b7715d
<br>2009-11-09 11:19:28,125 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.binding.soap
<br>.interceptor.MustUnderstandInterceptor@73a403
<br>2009-11-09 11:19:28,125 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.servicemix.cxfbc
<br>.interceptors.JbiJAASInterceptor@ca7c93
<br>2009-11-09 11:19:28,140 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.servicemix.cxfbc
<br>.interceptors.JbiOperationInterceptor@1626bf
<br>2009-11-09 11:19:28,140 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.servicemix.cxfbc
<br>.interceptors.JbiInWsdl1Interceptor@49e885
<br>2009-11-09 11:19:28,140 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.servicemix.cxfbc
<br>.interceptors.JbiInInterceptor@407909
<br>2009-11-09 11:19:28,140 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.servicemix.cxfbc
<br>.CxfBcConsumer$JbiInvokerInterceptor@1b8a6af
<br>2009-11-09 11:19:28,140 DEBUG - CxfBcComponent - Created correlation id: ID:10.80.12.85-124d6ebc094-2:10
<br>2009-11-09 11:19:28,140 DEBUG - DeliveryChannelImpl - Send ID:10.80.12.85-124d6ebc094-2:10 in DeliveryChannel{servicemi
<br>x-cxf-bc}
<br>2009-11-09 11:19:28,140 DEBUG - SecuredBroker - send exchange with secure broker
<br>2009-11-09 11:19:28,140 DEBUG - SecuredBroker - service name :{<a href="http://www.hcsys.com/novaesb/" target="_top" rel="nofollow">http://www.hcsys.com/novaesb/</a>}jms
<br>2009-11-09 11:19:28,140 DEBUG - SecuredBroker - operation name :{<a href="http://www.hcsys.com/novaesb/" target="_top" rel="nofollow">http://www.hcsys.com/novaesb/</a>}createCustomer
<br>2009-11-09 11:19:28,140 DEBUG - SedaFlow - Called Flow send
<br>2009-11-09 11:19:28,140 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.servicemix.cxfbc
<br>.CxfBcConsumer$JbiPostInvokerInterceptor@1c76cab
<br>2009-11-09 11:19:28,140 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.interceptor.
<br>OutgoingChainInterceptor@1af691b
<br>2009-11-09 11:19:28,156 DEBUG - JettyHTTPDestination - Finished servicing http request on thread: Thread[22434271@qtp0-0
<br>,5,RMI Runtime]
<br>2009-11-09 11:19:28,156 DEBUG - SedaQueue - org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@45ac89 dequeu
<br>ed exchange: InOnly[
<br> id: ID:10.80.12.85-124d6ebc094-2:10
<br> status: Active
<br> role: provider
<br> service: {<a href="http://www.hcsys.com/novaesb/" target="_top" rel="nofollow">http://www.hcsys.com/novaesb/</a>}jms
<br> endpoint: provider
<br> operation: {<a href="http://www.hcsys.com/novaesb/" target="_top" rel="nofollow">http://www.hcsys.com/novaesb/</a>}createCustomer
<br> in: <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:jbi="<a href="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper" target="_top" rel="nofollow">http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper</a>" xmlns:msg="htt
<br>p://www.hcsys.com/novaesb/" xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema-instance</a>" nam
<br>e="createCustomer" type="msg:createCustomer" version="1.0"><jbi:part><pns:createCustomer xmlns:pns="<a href="http://geneva.nova.com/custome" target="_top" rel="nofollow">http://geneva.nova.com/custome</a><br>r">
<br> <pns:value>aaaa</pns:value>
<br> </pns:createCustomer></jbi:part></jbi:message>
<br>]
<br>2009-11-09 11:19:28,156 DEBUG - JmsComponent - Received exchange: status: Active, role: provider
<br>2009-11-09 11:19:28,156 DEBUG - JmsComponent - Retrieved correlation id: ID:10.80.12.85-124d6ebc094-2:10
<br>2009-11-09 11:19:28,156 DEBUG - DeliveryChannelImpl - Send ID:10.80.12.85-124d6ebc094-2:10 in DeliveryChannel{servicemi
<br>x-jms}
<br>2009-11-09 11:19:28,156 DEBUG - SecuredBroker - send exchange with secure broker
<br>2009-11-09 11:19:28,156 DEBUG - SedaFlow - Called Flow send
<br>2009-11-09 11:19:28,156 DEBUG - MultiplexingConsumerProcessor - Received jms message ActiveMQTextMessage {commandId = 17, respons
<br>eRequired = true, messageId = ID:8014ac188efd43a-4422-1257736227984-2:10:1:1:11, originalDestination = null, originalTransactionId
<br> = null, producerId = ID:8014ac188efd43a-4422-1257736227984-2:10:1:1, destination = queue://queue/A, transactionId = null, expirat
<br>ion = 0, timestamp = 1257736768156, arrival = 0, brokerInTime = 1257736768156, brokerOutTime = 1257736768156, correlationId = null
<br>, replyTo = null, persistent = true, type = null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId = null, compre
<br>ssed = false, userID = null, content = null, marshalledProperties = org.apache.activemq.util.ByteSequence@1713c03, dataStructure =
<br> null, redeliveryCounter = 0, size = 0, properties = {MimeContentType=text/xml;charset=UTF-8, SoapAction=/{<a href="http://www.hcsys.com/no" target="_top" rel="nofollow">http://www.hcsys.com/no</a><br>vaesb/}createCustomer, SOAPJMS_soapAction=/{<a href="http://www.hcsys.com/novaesb/" target="_top" rel="nofollow">http://www.hcsys.com/novaesb/</a>}createCustomer}, readOnlyProperties = true, readOnlyBody
<br> = true, droppable = false, text = <?xml version='1.0' encoding='UTF-8'?><jbi:me...jbi:message>}
<br>2009-11-09 11:19:28,171 DEBUG - MultiplexingConsumerProcessor - Handling jms message ActiveMQTextMessage {commandId = 17, respons
<br>eRequired = true, messageId = ID:8014ac188efd43a-4422-1257736227984-2:10:1:1:11, originalDestination = null, originalTransactionId
<br> = null, producerId = ID:8014ac188efd43a-4422-1257736227984-2:10:1:1, destination = queue://queue/A, transactionId = null, expirat
<br>ion = 0, timestamp = 1257736768156, arrival = 0, brokerInTime = 1257736768156, brokerOutTime = 1257736768156, correlationId = null
<br>, replyTo = null, persistent = true, type = null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId = null, compre
<br>ssed = false, userID = null, content = null, marshalledProperties = org.apache.activemq.util.ByteSequence@1713c03, dataStructure =
<br> null, redeliveryCounter = 0, size = 0, properties = {MimeContentType=text/xml;charset=UTF-8, SoapAction=/{<a href="http://www.hcsys.com/no" target="_top" rel="nofollow">http://www.hcsys.com/no</a><br>vaesb/}createCustomer, SOAPJMS_soapAction=/{<a href="http://www.hcsys.com/novaesb/" target="_top" rel="nofollow">http://www.hcsys.com/novaesb/</a>}createCustomer}, readOnlyProperties = true, readOnlyBody
<br> = true, droppable = false, text = <?xml version='1.0' encoding='UTF-8'?><jbi:me...jbi:message>}
<br>2009-11-09 11:19:28,171 DEBUG - SedaQueue - org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@89e163 dequeu
<br>ed exchange: InOnly[
<br> id: ID:10.80.12.85-124d6ebc094-2:10
<br> status: Done
<br> role: consumer
<br> service: {<a href="http://www.hcsys.com/novaesb/" target="_top" rel="nofollow">http://www.hcsys.com/novaesb/</a>}jms
<br> endpoint: provider
<br> operation: {<a href="http://www.hcsys.com/novaesb/" target="_top" rel="nofollow">http://www.hcsys.com/novaesb/</a>}createCustomer
<br> in: <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:jbi="<a href="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper" target="_top" rel="nofollow">http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper</a>" xmlns:msg="htt
<br>p://www.hcsys.com/novaesb/" xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema-instance</a>" nam
<br>e="createCustomer" type="msg:createCustomer" version="1.0"><jbi:part><pns:createCustomer xmlns:pns="<a href="http://geneva.nova.com/custome" target="_top" rel="nofollow">http://geneva.nova.com/custome</a><br>r">
<br> <pns:value>aaaa</pns:value>
<br> </pns:createCustomer></jbi:part></jbi:message>
<br>]
<br>2009-11-09 11:19:28,171 DEBUG - JmsComponent - Created correlation id: ID:10.80.12.85-124d6ebc094-4:10
<br>2009-11-09 11:19:28,171 DEBUG - CxfBcComponent - Received exchange: status: Done, role: consumer
<br>2009-11-09 11:19:28,171 DEBUG - DeliveryChannelImpl - Send ID:10.80.12.85-124d6ebc094-4:10 in DeliveryChannel{servicemi
<br>x-jms}
<br>2009-11-09 11:19:28,171 DEBUG - CxfBcComponent - Retrieved correlation id: ID:10.80.12.85-124d6ebc094-2:10
<br>2009-11-09 11:19:28,171 DEBUG - SecuredBroker - send exchange with secure broker
<br>2009-11-09 11:19:28,171 DEBUG - SecuredBroker - service name :{<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}CustomerInImplServ
<br>ice
<br>2009-11-09 11:19:28,171 DEBUG - SecuredBroker - operation name :{<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}createCustomer
<br>2009-11-09 11:19:28,171 DEBUG - SedaFlow - Called Flow send
<br>2009-11-09 11:19:28,187 DEBUG - SedaQueue - org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@4437d3 dequeu
<br>ed exchange: InOnly[
<br> id: ID:10.80.12.85-124d6ebc094-4:10
<br> status: Active
<br> role: provider
<br> service: {<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}CustomerInImplService
<br> endpoint: CustomerInGenevaPortTypePort
<br> operation: {<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}createCustomer
<br> in: <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:jbi="<a href="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper" target="_top" rel="nofollow">http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper</a>" xmlns:msg="htt
<br>p://www.hcsys.com/novaesb/" xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema-instance</a>" nam
<br>e="createCustomer" type="msg:createCustomer" version="1.0"><jbi:part><pns:createCustomer xmlns:pns="<a href="http://geneva.nova.com/custome" target="_top" rel="nofollow">http://geneva.nova.com/custome</a><br>r">
<br> <pns:value>aaaa</pns:value>
<br> </pns:createCustomer></jbi:part></jbi:message>
<br>]
<br>2009-11-09 11:19:28,187 DEBUG - CxfBcComponent - Received exchange: status: Active, role: provider
<br>2009-11-09 11:19:28,187 DEBUG - CxfBcComponent - Retrieved correlation id: ID:10.80.12.85-124d6ebc094-4:10
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Adding interceptor org.apache.servicemix.cxfbc.interceptors.JbiOu
<br>tInterceptor@dd6a50 to phase pre-stream
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Adding interceptor org.apache.servicemix.cxfbc.interceptors.JbiOu
<br>tWsdl1Interceptor@6ed9d1 to phase marshal
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Adding interceptor org.apache.cxf.binding.soap.interceptor.SoapPr
<br>eProtocolOutInterceptor@19e4f8b to phase post-logical
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Adding interceptor org.apache.cxf.binding.soap.interceptor.SoapOu
<br>tInterceptor@782f81 to phase write
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Adding interceptor org.apache.cxf.binding.soap.interceptor.SoapAc
<br>tionOutInterceptor@76df38 to phase post-logical
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Adding interceptor org.apache.cxf.interceptor.StaxOutInterceptor@
<br>38df00 to phase pre-stream
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Chain org.apache.cxf.phase.PhaseInterceptorChain@1b896dc was crea
<br>ted. Current flow:
<br> post-logical [SoapPreProtocolOutInterceptor, SoapActionOutInterceptor]
<br> pre-stream [JbiOutInterceptor, StaxOutInterceptor]
<br> write [SoapOutInterceptor]
<br> marshal [JbiOutWsdl1Interceptor]
<br><br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.binding.soap
<br>.interceptor.SoapPreProtocolOutInterceptor@19e4f8b
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.binding.soap
<br>.interceptor.SoapActionOutInterceptor@76df38
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.servicemix.cxfbc
<br>.interceptors.JbiOutInterceptor@dd6a50
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.interceptor.
<br>StaxOutInterceptor@38df00
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Adding interceptor org.apache.cxf.interceptor.StaxOutInterceptor$
<br>StaxOutEndingInterceptor@1073a2e to phase pre-stream-ending
<br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Chain org.apache.cxf.phase.PhaseInterceptorChain@1b896dc was modi
<br>fied. Current flow:
<br> post-logical [SoapPreProtocolOutInterceptor, SoapActionOutInterceptor]
<br> pre-stream [JbiOutInterceptor, StaxOutInterceptor]
<br> write [SoapOutInterceptor]
<br> marshal [JbiOutWsdl1Interceptor]
<br> pre-stream-ending [StaxOutEndingInterceptor]
<br><br>2009-11-09 11:19:28,187 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.binding.soap
<br>.interceptor.SoapOutInterceptor@782f81
<br>2009-11-09 11:19:28,203 DEBUG - PhaseInterceptorChain - Adding interceptor org.apache.cxf.binding.soap.interceptor.SoapOu
<br>tInterceptor$SoapOutEndingInterceptor@17cb4ff to phase write-ending
<br>2009-11-09 11:19:28,203 DEBUG - PhaseInterceptorChain - Chain org.apache.cxf.phase.PhaseInterceptorChain@1b896dc was modi
<br>fied. Current flow:
<br> post-logical [SoapPreProtocolOutInterceptor, SoapActionOutInterceptor]
<br> pre-stream [JbiOutInterceptor, StaxOutInterceptor]
<br> write [SoapOutInterceptor]
<br> marshal [JbiOutWsdl1Interceptor]
<br> write-ending [SoapOutEndingInterceptor]
<br> pre-stream-ending [StaxOutEndingInterceptor]
<br><br>2009-11-09 11:19:28,203 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.servicemix.cxfbc
<br>.interceptors.JbiOutWsdl1Interceptor@6ed9d1
<br>2009-11-09 11:19:28,203 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.binding.soap
<br>.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor@17cb4ff
<br>2009-11-09 11:19:28,203 DEBUG - PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.interceptor.
<br>StaxOutInterceptor$StaxOutEndingInterceptor@1073a2e
<br>2009-11-09 11:19:28,203 DEBUG - HTTPConduit - Sending POST Message with Headers to <a href="http://10.80.12.100:8080/Gen" target="_top" rel="nofollow">http://10.80.12.100:8080/Gen</a><br>evaESB/services/CustomerAccount Conduit :{<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}CustomerInGenevaPortTypePort.http-conduit
<br>Content-Type: text/xml; charset=UTF-8
<br><br>2009-11-09 11:19:28,203 DEBUG - HTTPConduit - SOAPAction: ""
<br>2009-11-09 11:19:28,203 DEBUG - HTTPConduit - Accept: *
<br>2009-11-09 11:19:28,203 DEBUG - HTTPConduit - No Trust Decider for Conduit '{<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}Cu
<br>stomerInGenevaPortTypePort.http-conduit'. An afirmative Trust Decision is assumed.
<br>2009-11-09 11:19:28,234 DEBUG - HTTPConduit - Response Code: 404 Conduit: {<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}Cust
<br>omerInGenevaPortTypePort.http-conduit
<br>2009-11-09 11:19:28,234 DEBUG - HTTPConduit - Content length: 952
<br>2009-11-09 11:19:28,234 DEBUG - HTTPConduit - Header fields:
<br> null: [HTTP/1.1 404 Not Found]
<br> Date: [Mon, 09 Nov 2009 03:19:04 GMT]
<br> Content-Length: [952]
<br> Content-Type: [text/html;charset=utf-8]
<br> Server: [Apache-Coyote/1.1]
<br><br>2009-11-09 11:19:28,265 ERROR - CxfBcComponent - Error processing exchange InOnly[
<br> id: ID:10.80.12.85-124d6ebc094-4:10
<br> status: Active
<br> role: provider
<br> service: {<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}CustomerInImplService
<br> endpoint: CustomerInGenevaPortTypePort
<br> operation: {<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}createCustomer
<br> in: <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:jbi="<a href="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper" target="_top" rel="nofollow">http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper</a>" xmlns:msg="htt
<br>p://www.hcsys.com/novaesb/" xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema-instance</a>" nam
<br>e="createCustomer" type="msg:createCustomer" version="1.0"><jbi:part><pns:createCustomer xmlns:pns="<a href="http://geneva.nova.com/custome" target="_top" rel="nofollow">http://geneva.nova.com/custome</a><br>r">
<br> <pns:value>aaaa</pns:value>
<br> </pns:createCustomer></jbi:part></jbi:message>
<br>]
<br>javax.jbi.messaging.MessagingException: Fault not supported
<br> at org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setMessage(MessageExchangeImpl.java:366)
<br> at org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setFault(MessageExchangeImpl.java:290)
<br> at org.apache.servicemix.cxfbc.CxfBcProvider.faultProcess(CxfBcProvider.java:277)
<br> at org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:261)
<br> at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:627)
<br> at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:581)
<br> at org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:535)
<br> at org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:60)
<br> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:623)
<br> at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:172)
<br> at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:168)
<br> at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
<br> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
<br> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
<br> at java.lang.Thread.run(Thread.java:619)
<br>2009-11-09 11:19:28,296 DEBUG - DeliveryChannelImpl - Send ID:10.80.12.85-124d6ebc094-4:10 in DeliveryChannel{servicemi
<br>x-cxf-bc}
<br>2009-11-09 11:19:28,296 DEBUG - SecuredBroker - send exchange with secure broker
<br>2009-11-09 11:19:28,296 DEBUG - SedaFlow - Called Flow send
<br>2009-11-09 11:19:28,296 DEBUG - SedaQueue - org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@247262 dequeu
<br>ed exchange: InOnly[
<br> id: ID:10.80.12.85-124d6ebc094-4:10
<br> status: Error
<br> role: consumer
<br> service: {<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}CustomerInImplService
<br> endpoint: CustomerInGenevaPortTypePort
<br> operation: {<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}createCustomer
<br> in: <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:jbi="<a href="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper" target="_top" rel="nofollow">http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper</a>" xmlns:msg="htt
<br>p://www.hcsys.com/novaesb/" xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema-instance</a>" nam
<br>e="createCustomer" type="msg:createCustomer" version="1.0"><jbi:part><pns:createCustomer xmlns:pns="<a href="http://geneva.nova.com/custome" target="_top" rel="nofollow">http://geneva.nova.com/custome</a><br>r">
<br> <pns:value>aaaa</pns:value>
<br> </pns:createCustomer></jbi:part></jbi:message>
<br> error: javax.jbi.messaging.MessagingException: Fault not supported
<br>]
<br>2009-11-09 11:19:28,296 DEBUG - JmsComponent - Received exchange: status: Error, role: consumer
<br>2009-11-09 11:19:28,296 DEBUG - JmsComponent - Retrieved correlation id: ID:10.80.12.85-124d6ebc094-4:10
<br>2009-11-09 11:19:28,328 ERROR - JmsComponent - Error processing exchange InOnly[
<br> id: ID:10.80.12.85-124d6ebc094-4:10
<br> status: Error
<br> role: consumer
<br> service: {<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}CustomerInImplService
<br> endpoint: CustomerInGenevaPortTypePort
<br> operation: {<a href="http://geneva.nova.com/customer" target="_top" rel="nofollow">http://geneva.nova.com/customer</a>}createCustomer
<br> in: <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:jbi="<a href="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper" target="_top" rel="nofollow">http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper</a>" xmlns:msg="htt
<br>p://www.hcsys.com/novaesb/" xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema-instance</a>" nam
<br>e="createCustomer" type="msg:createCustomer" version="1.0"><jbi:part><pns:createCustomer xmlns:pns="<a href="http://geneva.nova.com/custome" target="_top" rel="nofollow">http://geneva.nova.com/custome</a><br>r">
<br> <pns:value>aaaa</pns:value>
<br> </pns:createCustomer></jbi:part></jbi:message>
<br> error: javax.jbi.messaging.MessagingException: Fault not supported
<br>]
<br>java.lang.UnsupportedOperationException: A destination must be specified.
<br> at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:195)
<br> at org.apache.activemq.pool.PooledProducer.send(PooledProducer.java:74)
<br> at org.apache.activemq.pool.PooledProducer.send(PooledProducer.java:59)
<br> at org.apache.servicemix.jms.multiplexing.MultiplexingConsumerProcessor.process(MultiplexingConsumerProcessor.java:126)
<br> at org.apache.servicemix.soap.SoapEndpoint.process(SoapEndpoint.java:368)
<br> at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:627)
<br> at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:598)
<br> at org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:535)
<br> at org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:60)
<br> at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:623)
<br> at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:172)
<br> at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:168)
<br> at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
<br> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
<br> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
<br> at java.lang.Thread.run(Thread.java:619)
<br><br><br>=======================log end==========================<p>From forum: <a href="http://old.nabble.com/ServiceMix---User-f12050.html" embed="fixTarget[12050]" target="_top" >ServiceMix - User</a></p>
tag:old.nabble.com,2006:post-26257266
Re: Camel vs. SMX Maven repository
2009-11-08T11:53:09Z
2009-11-08T11:53:09Z
Jean-Baptiste Onofré
Hi Martin,
<br><br>for my part, I think that we need to consider Camel as a SMX dependency
<br>(like CXF, ActiveMQ, etc). So, Camel should upload artifacts and
<br>dependencies to <a href="https://svn.apache.org/repos/asf/camel/m2-repo" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo</a> and the
<br>ServiceMix Camel component should have this repository in its pom.
<br><br>Let see the feeling of the other guys.
<br><br>Regards
<br>JB
<br><br>Martin Krasser wrote:
<div class='shrinkable-quote'><br>> Hi,
<br>>
<br>> I started a thread on the Camel dev mailing list discussing which Maven
<br>> repo to use for uploading new artifacts needed by Camel.
<br>>
<br>> <a href="http://old.nabble.com/GAE-API-in-Maven-repo-tt26243221s22882.html" target="_top" rel="nofollow">http://old.nabble.com/GAE-API-in-Maven-repo-tt26243221s22882.html</a><br>>
<br>> We finally discussed the two options:
<br>>
<br>> - <a href="https://svn.apache.org/repos/asf/servicemix/m2-repo/" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/servicemix/m2-repo/</a> (ServiceMix Maven
<br>> repo)
<br>> - <a href="https://svn.apache.org/repos/asf/camel/m2-repo/" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo/</a> (Camel Maven repo)
<br>> Camel already uses the ServiceMix repo to download jars. Which option do
<br>> you prefer?
<br>>
<br>> Thanks,
<br>> Martin
<br>>
<br>>
</div><br>--
<br>Jean-Baptiste Onofré (Nanthrax)
<br>BuildProcess/AutoDeploy Project Leader
<br><a href="http://buildprocess.sourceforge.net" target="_top" rel="nofollow">http://buildprocess.sourceforge.net</a><br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26257266&i=0" target="_top" rel="nofollow">jb@...</a>
<br>PGP : 17D4F086
<br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26251935
Camel vs. SMX Maven repository
2009-11-08T01:13:23Z
2009-11-08T01:13:23Z
Martin Krasser
Hi,
<br><br>I started a thread on the Camel dev mailing list discussing which Maven
<br>repo to use for uploading new artifacts needed by Camel.
<br><br><a href="http://old.nabble.com/GAE-API-in-Maven-repo-tt26243221s22882.html" target="_top" rel="nofollow">http://old.nabble.com/GAE-API-in-Maven-repo-tt26243221s22882.html</a><br><br>We finally discussed the two options:
<br><br>- <a href="https://svn.apache.org/repos/asf/servicemix/m2-repo/" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/servicemix/m2-repo/</a> (ServiceMix Maven
<br>repo)
<br>- <a href="https://svn.apache.org/repos/asf/camel/m2-repo/" target="_top" rel="nofollow">https://svn.apache.org/repos/asf/camel/m2-repo/</a> (Camel Maven repo)
<br>Camel already uses the ServiceMix repo to download jars. Which option do
<br>you prefer?
<br><br>Thanks,
<br>Martin
<br><br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26251308
[jira] Work started: (SMX4NMR-171) when stop a bundle, the underlying counterpart JBI sa/component/sharedlib instance in the bundle should be removed from jmx server
2009-11-07T22:28:54Z
2009-11-07T22:28:54Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SMX4NMR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMX4NMR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Work on SMX4NMR-171 started by Freeman Fang.
<br><div class='shrinkable-quote'><br>> when stop a bundle, the underlying counterpart JBI sa/component/sharedlib instance in the bundle should be removed from jmx server
<br>> ----------------------------------------------------------------------------------------------------------------------------------
<br>>
<br>> Key: SMX4NMR-171
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SMX4NMR-171" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMX4NMR-171</a><br>> Project: ServiceMix NMR
<br>> Issue Type: Bug
<br>> Reporter: Freeman Fang
<br>> Assignee: Freeman Fang
<br>> Fix For: 1.1.0
<br>>
<br>>
<br>> currently for example, if you do osgi:refresh 115, assuming bundle with id 115 is servicemix-http component, then you will get exception when start the bundle and try to do jmx registration like
<br>> Caused by: javax.management.InstanceAlreadyExistsException: org.apache.servicemix:Type=Component,Name=servicemix-http,SubType=LifeCycle
<br>> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
<br>> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
<br>> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
<br>> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
<br>> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
<br>> at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
<br>> in the log.
<br>> we need remove the old instance reference from jmx server when stop the bundle
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26251309
[jira] Created: (SMX4NMR-171) when stop a bundle, the underlying counterpart JBI sa/component/sharedlib instance in the bundle should be removed from jmx server
2009-11-07T22:28:54Z
2009-11-07T22:28:54Z
JIRA jira@apache.org
when stop a bundle, the underlying counterpart JBI sa/component/sharedlib instance in the bundle should be removed from jmx server
<br>----------------------------------------------------------------------------------------------------------------------------------
<br><br> Key: SMX4NMR-171
<br> URL: <a href="https://issues.apache.org/activemq/browse/SMX4NMR-171" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMX4NMR-171</a><br> Project: ServiceMix NMR
<br> Issue Type: Bug
<br> Reporter: Freeman Fang
<br> Assignee: Freeman Fang
<br> Fix For: 1.1.0
<br><br><br>currently for example, if you do osgi:refresh 115, assuming bundle with id 115 is servicemix-http component, then you will get exception when start the bundle and try to do jmx registration like
<br>Caused by: javax.management.InstanceAlreadyExistsException: org.apache.servicemix:Type=Component,Name=servicemix-http,SubType=LifeCycle
<br> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
<br> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
<br> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
<br> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
<br> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
<br> at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
<br>in the log.
<br>we need remove the old instance reference from jmx server when stop the bundle
<br><br><br><br><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26243303
[jira] Commented: (SMX4-421) JBI Maven plugin can not build SA if several Camel SUs are included
2009-11-07T01:42:53Z
2009-11-07T01:42:53Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SMX4-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55209#action_55209" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMX4-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55209#action_55209</a> ]
<br><br>Freeman Fang commented on SMX4-421:
<br>-----------------------------------
<br><br>Hi Sergey,
<br><br>another workaround is
<br>add
<br><br><properties>
<br> <componentName>servicemix-camel</componentName>
<br> </properties>
<br><br>into your su pom.xml
<br>if you still want to use 4.1 version.
<br><br>Freeman
<br><div class='shrinkable-quote'><br>> JBI Maven plugin can not build SA if several Camel SUs are included
<br>> -------------------------------------------------------------------
<br>>
<br>> Key: SMX4-421
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SMX4-421" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SMX4-421</a><br>> Project: ServiceMix 4
<br>> Issue Type: Bug
<br>> Affects Versions: 4.1.0
<br>> Reporter: Sergey Beryozkin
<br>> Assignee: Freeman Fang
<br>> Fix For: 4.1.0
<br>>
<br>>
<br>> 1. camelcxf-smxcxf-camel1-su pom :
<br>> <project>
<br>> <modelVersion>4.0.0</modelVersion>
<br>> <parent>
<br>> <groupId>xxx</groupId>
<br>> <artifactId>parent</artifactId>
<br>> <version>1.0-SNAPSHOT</version>
<br>> <relativePath>../../pom.xml</relativePath>
<br>> </parent>
<br>> <groupId>xxx</groupId>
<br>> <!-- ******************* -->
<br>> <artifactId>camelcxf-smxcxf-camel1-su</artifactId>
<br>> <!-- ******************* -->
<br>> <packaging>jbi-service-unit</packaging>
<br>> <name>Camel1</name>
<br>> <dependencies>
<br>> <dependency>
<br>> <groupId>org.apache.servicemix</groupId>
<br>> <artifactId>servicemix-camel</artifactId>
<br>> <version>${servicemix-camel-version}</version>
<br>> </dependency>
<br>> </dependencies>
<br>> <build>
<br>> <plugins>
<br>> <plugin>
<br>> <groupId>org.apache.servicemix.tooling</groupId>
<br>> <artifactId>jbi-maven-plugin</artifactId>
<br>> <version>${servicemix-jbi-plugin-version}</version>
<br>> <extensions>true</extensions>
<br>> </plugin>
<br>> </plugins>
<br>> </build>
<br>> </project>
<br>> 2. camelcxf-smxcxf-camel2-su pom :
<br>> <modelVersion>4.0.0</modelVersion>
<br>> <parent>
<br>> <groupId>xxx</groupId>
<br>> <artifactId>parent</artifactId>
<br>> <version>1.0-SNAPSHOT</version>
<br>> <relativePath>../../pom.xml</relativePath>
<br>> </parent>
<br>> <groupId>xxx</groupId>
<br>> <!-- ******************* -->
<br>> <artifactId>camelcxf-smxcxf-camel2-su</artifactId>
<br>> <!-- ******************* -->
<br>>
<br>> <packaging>jbi-service-unit</packaging>
<br>> <name>Camel2</name>
<br>> <dependencies>
<br>> <dependency>
<br>> <groupId>org.apache.servicemix</groupId>
<br>> <artifactId>servicemix-camel</artifactId>
<br>> <version>${servicemix-camel-version}</version>
<br>> </dependency>
<br>> </dependencies>
<br>> <build>
<br>> <plugins>
<br>> <plugin>
<br>> <groupId>org.apache.servicemix.tooling</groupId>
<br>> <artifactId>jbi-maven-plugin</artifactId>
<br>> <version>${servicemix-jbi-plugin-version}</version>
<br>> <extensions>true</extensions>
<br>> </plugin>
<br>> </plugins>
<br>> </build>
<br>> </project>
<br>> 3. camelcxf-smxcxf-sa pom :
<br>> <project>
<br>> <modelVersion>4.0.0</modelVersion>
<br>> <parent>
<br>> <groupId>xxx</groupId>
<br>> <artifactId>parent</artifactId>
<br>> <version>1.0-SNAPSHOT</version>
<br>> <relativePath>../../pom.xml</relativePath>
<br>> </parent>
<br>> <groupId>xxx</groupId>
<br>> <artifactId>camelcxf-smxcxf-sa</artifactId>
<br>> <packaging>jbi-service-assembly</packaging>
<br>> <name> CamelCxfSmxCxfSa :: SA</name>
<br>> <version>1.0-SNAPSHOT</version>
<br>> <dependencies>
<br>> <dependency>
<br>> <groupId>xxx</groupId>
<br>> <artifactId>camelcxf-smxcxf-camel1-su</artifactId>
<br>> <version>${project.version}</version>
<br>> </dependency>
<br>> <dependency>
<br>> <groupId>xxx</groupId>
<br>> <artifactId>camelcxf-smxcxf-http-su</artifactId>
<br>> <version>${project.version}</version>
<br>> </dependency>
<br>> <dependency>
<br>> <groupId>xxx</groupId>
<br>> <artifactId>camelcxf-smxcxf-camel2-su</artifactId>
<br>> <version>${project.version}</version>
<br>> </dependency>
<br>> </dependencies>
<br>> <build>
<br>> <plugins>
<br>> <plugin>
<br>> <groupId>org.apache.servicemix.tooling</groupId>
<br>> <artifactId>jbi-maven-plugin</artifactId>
<br>> <version>${servicemix-jbi-plugin-version}</version>
<br>> <extensions>true</extensions>
<br>> </plugin>
<br>> </plugins>
<br>> </build>
<br>> </project>
<br>> 4. camelcxf-smxcxf-sa build problem
<br>> [INFO] [jbi:generate-jbi-service-assembly-descriptor]
<br>> [INFO] Generating jbi.xml
<br>> [INFO] Determining component name for service unit camelcxf-smxcxf-camel1-su
<br>> [INFO] Project MavenProject: org.apache.servicemix:servicemix-camel:2009.02.0-ps
<br>> c-01-00M2 @ packaged jbi-component
<br>> [INFO] Determining component name for service unit camelcxf-smxcxf-http-su
<br>> [INFO] Project MavenProject: org.apache.servicemix:servicemix-http:2009.02.0-psc
<br>> -01-00M2 @ packaged jbi-component
<br>> [INFO] Determining component name for service unit camelcxf-smxcxf-camel2-su
<br>> [INFO] ------------------------------------------------------------------------
<br>> [ERROR] BUILD ERROR
<br>> [INFO] ------------------------------------------------------------------------
<br>> [INFO] The service unit camelcxf-smxcxf-camel2-su does not have a dependency whi
<br>> ch is packaged as a jbi-component or a project property 'componentName'
<br>> [INFO] ------------------------------------------------------------------------
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>
tag:old.nabble.com,2006:post-26243295
[jira] Resolved: (SM-1906) JBI Maven plugin is unable to manage several SU based on the same component in the same SA
2009-11-07T01:40:52Z
2009-11-07T01:40:52Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/activemq/browse/SM-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SM-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Freeman Fang resolved SM-1906.
<br>------------------------------
<br><br> Resolution: Fixed
<br> Fix Version/s: jbi-maven-plugin-4.2
<br><br>commit fix
<br><a href="http://svn.apache.org/viewvc?rev=833659&view=rev" target="_top" rel="nofollow">http://svn.apache.org/viewvc?rev=833659&view=rev</a><br><div class='shrinkable-quote'><br>> JBI Maven plugin is unable to manage several SU based on the same component in the same SA
<br>> ------------------------------------------------------------------------------------------
<br>>
<br>> Key: SM-1906
<br>> URL: <a href="https://issues.apache.org/activemq/browse/SM-1906" target="_top" rel="nofollow">https://issues.apache.org/activemq/browse/SM-1906</a><br>> Project: ServiceMix
<br>> Issue Type: Bug
<br>> Components: tooling
<br>> Reporter: Jean-Baptiste Onofré
<br>> Assignee: Freeman Fang
<br>> Fix For: jbi-maven-plugin-4.2
<br>>
<br>>
<br>> I have a SA composed by the following SU:
<br>> - SU1 based on CXF-SE component
<br>> - SU2 based on CXF-SE component
<br>> - SU3 based on HTTP component
<br>> Using JBI Maven plugin 4.0, I have no problem to build this SA:
<br>> mvn install
<br>> [...]
<br>> [INFO] Determining component name for service unit note-service-bos-su
<br>> [INFO] Project MavenProject: org.apache.servicemix:servicemix-cxf-se:2009.01.1-fsb-SNAPSHOT @ packaged jbi-component
<br>> [INFO] Determining component name for service unit note-service-ff-su
<br>> [INFO] Project MavenProject: org.apache.servicemix:servicemix-cxf-se:2009.01.1-fsb-SNAPSHOT @ packaged jbi-component
<br>> [INFO] Determining component name for service unit note-service-http-listener-su
<br>> [INFO] Project MavenProject: org.apache.servicemix:servicemix-http:2009.01.1-fsb-SNAPSHOT @ packaged jbi-component
<br>> [INFO] [jbi:generate-depends-file {execution: default-generate-depends-file}]
<br>> [INFO] Created: /home/jb/workspace/pf-fsb-services/note-service/note-service-sa/target/classes/META-INF/maven/dependencies.properties
<br>> [INFO] [resources:resources {execution: default-resources}]
<br>> [WARNING] Using platform encoding (ISO-8859-1 actually) to copy filtered resources, i.e. build is platform dependent!
<br>> [INFO] skip non existing resourceDirectory /home/jb/workspace/pf-fsb-services/note-service/note-service-sa/src/main/resources
<br>> [INFO] [compiler:compile {execution: default-compile}]
<br>> [INFO] No sources to compile
<br>> [INFO] [resources:testResources {execution: default-testResources}]
<br>> [WARNING] Using platform encoding (ISO-8859-1 actually) to copy filtered resources, i.e. build is platform dependent!
<br>> [INFO] skip non existing resourceDirectory /home/jb/workspace/pf-fsb-services/note-service/note-service-sa/src/test/resources
<br>> [INFO] [compiler:testCompile {execution: default-testCompile}]
<br>> [INFO] No sources to compile
<br>> [INFO] [surefire:test {execution: default-test}]
<br>> [INFO] No tests to run.
<br>> [INFO] [jbi:jbi-service-assembly {execution: default-jbi-service-assembly}]
<br>> [INFO] Generating service assembly /home/jb/workspace/pf-fsb-services/note-service/note-service-sa/target/note-service-sa-2009.3.00.rc3-SNAPSHOT.zip
<br>> [INFO] Building jar: /home/jb/workspace/pf-fsb-services/note-service/note-service-sa/target/note-service-sa-2009.3.00.rc3-SNAPSHOT.zip
<br>> [INFO] [jar:jar {execution: default-jar}]
<br>> [INFO] Building jar: /home/jb/workspace/pf-fsb-services/note-service/note-service-sa/target/note-service-sa-2009.3.00.rc3-SNAPSHOT.jar
<br>> [INFO] [install:install {execution: default-install}]
<br>> [INFO] Installing /home/jb/workspace/pf-fsb-services/note-service/note-service-sa/target/note-service-sa-2009.3.00.rc3-SNAPSHOT.jar to /home/jb/.m2/repository/com/fimasys/fsb/profinance/services/note-service/note-service-sa/2009.3.00.rc3-SNAPSHOT/note-service-sa-2009.3.00.rc3-SNAPSHOT.zip
<br>> [INFO] Installing /home/jb/workspace/pf-fsb-services/note-service/note-service-sa/target/note-service-sa-2009.3.00.rc3-SNAPSHOT.zip to /home/jb/.m2/repository/com/fimasys/fsb/profinance/services/note-service/note-service-sa/2009.3.00.rc3-SNAPSHOT/note-service-sa-2009.3.00.rc3-SNAPSHOT.zip
<br>> [INFO] ------------------------------------------------------------------------
<br>> [INFO] BUILD SUCCESSFUL
<br>> [INFO] ------------------------------------------------------------------------
<br>> Now, using JBI Maven plugin 4.1, I have the following error:
<br>> [INFO] Generating jbi.xml
<br>> [INFO] Determining component name for service unit note-service-bos-su
<br>> [INFO] Project MavenProject: commons-lang:commons-lang:2.1 @ packaged jar
<br>> [INFO] Project MavenProject: org.springframework:spring-context:2.5.6 @ packaged jar
<br>> [INFO] Project MavenProject: commons-beanutils:commons-beanutils-core:1.7.0 @ packaged jar
<br>> [INFO] Project MavenProject: org.apache.servicemix:servicemix-cxf-se:2009.01.1-fsb-SNAPSHOT @ packaged jbi-component
<br>> [INFO] Determining component name for service unit note-service-ff-su
<br>> [INFO] ------------------------------------------------------------------------
<br>> [ERROR] BUILD ERROR
<br>> [INFO] ------------------------------------------------------------------------
<br>> [INFO] The service unit note-service-ff-su does not have a dependency which is packaged as a jbi-component or a project property 'componentName'
<br>> [INFO] ------------------------------------------------------------------------
<br>> [INFO] For more information, run Maven with the -e switch
<br>> [INFO] ------------------------------------------------------------------------
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/ServiceMix---Dev-f12051.html" embed="fixTarget[12051]" target="_top" >ServiceMix - Dev</a></p>