[jira] Commented: (SM-999) InOut to InOnly pattern Endpoint for eip-su
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39638 ] Piotr Bzdyl commented on SM-999: There is already such a pattern - PipeLine - http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-Pipeline. Or maybe you are referring to something else? InOut to InOnly pattern Endpoint for eip-su --- Key: SM-999 URL: https://issues.apache.org/activemq/browse/SM-999 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Reporter: Netflexity Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-996) ServiceMix doesn't start correctly due to javax.management.MalformedObjectNameException: Invalid ObjectName value type [javax.xml.namespace.QName]: only ObjectName and String
[ https://issues.apache.org/activemq/browse/SM-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Bzdyl updated SM-996: --- Attachment: SM-996.patch.diff This is a simple patch for this. I guess there is another solution (like specifying target type using some @org.apache.xbean annotation or some more pretty xml in the jmx.xml), but I am not aware of it. ServiceMix doesn't start correctly due to javax.management.MalformedObjectNameException: Invalid ObjectName value type [javax.xml.namespace.QName]: only ObjectName and String supported Key: SM-996 URL: https://issues.apache.org/activemq/browse/SM-996 Project: ServiceMix Issue Type: Bug Affects Versions: 3.2 Environment: ServiceMix trunk rev. 553445 Reporter: Piotr Bzdyl Priority: Blocker Attachments: SM-996.patch.diff After I rebuild SMix from trunk with revision 553445 I got following error upon startup: Loading Apache ServiceMix from servicemix.xml on the CLASSPATH Caught: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean' defined in class path resource [jmx.xml]: Invocation of init method failed; nested exception is javax.management.MalformedObjectNameException: Invalid ObjectName value type [javax.xml.namespace.QName]: only ObjectName and String supported. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean' defined in class path resource [jmx.xml]: Invocation of init method failed; nested exception is javax.management.MalformedObjectNameException: Invalid ObjectName value type [ javax.xml.namespace.QName]: only ObjectName and String supported. Caused by: javax.management.MalformedObjectNameException: Invalid ObjectName value type [javax.xml.namespace.QName]: only ObjectName and String supported. at org.springframework.jmx.support.ObjectNameManager.getInstance(ObjectNameManager.java:58) at org.springframework.jmx.support.ConnectorServerFactoryBean.setObjectName(ConnectorServerFactoryBean.java:104) at org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:186) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1201) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1171) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:284) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352) at org.apache.xbean.spring.context.ClassPathXmlApplicationContext.init(ClassPathXmlApplicationContext.java:161) at org.apache.xbean.spring.context.ClassPathXmlApplicationContext.init(ClassPathXmlApplicationContext.java:51) at org.apache.servicemix.Main.main(Main.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchStandard(Launcher.java:410) at org.codehaus.classworlds.Launcher.launch(Launcher.java:344) at org.codehaus.classworlds.Launcher.main(Launcher.java:461) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-991) servicemix-saxon component lacks ServiceUnit analyzer which results in generating incomplete jbi.xml
servicemix-saxon component lacks ServiceUnit analyzer which results in generating incomplete jbi.xml Key: SM-991 URL: https://issues.apache.org/activemq/browse/SM-991 Project: ServiceMix Issue Type: Bug Components: servicemix-saxon Affects Versions: 3.2, incubation Reporter: Piotr Bzdyl Attachments: servicemix-saxon-service-unit-analyzer.diff.txt Due to lack of Service unit analyzer in the servicemix-saxon component, generated jbi.xml file doesn't contain services provided by saxon service unit (there is no problem with consumed services since saxon endpoints are only providers). I am attaching patch containing very simple service unit analyzer and change in pom.xml adding this analyzer to the built component. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-969) JBIMarshaler doesn't copy Subject from NormalizedMessage to SoapMessage
JBIMarshaler doesn't copy Subject from NormalizedMessage to SoapMessage --- Key: SM-969 URL: https://issues.apache.org/activemq/browse/SM-969 Project: ServiceMix Issue Type: Bug Components: servicemix-soap Reporter: Piotr Bzdyl Attachments: JBIMarshaler.java.diff JBIMarshaler doesn't copy Subject from NormalizedMessage to SoapMessage so the information about the subject is lost. It does so in opposite way (from SoapMessage to NormalizedMessage). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-963) NullPointerExceptions during JMS component initialization
NullPointerExceptions during JMS component initialization - Key: SM-963 URL: https://issues.apache.org/activemq/browse/SM-963 Project: ServiceMix Issue Type: Bug Components: servicemix-jms Affects Versions: 3.2, incubation Environment: Windows XP, JDK 1.5.0_11 Reporter: Piotr Bzdyl Attachments: MultiplexingConsumerProcessor.java.patch Currently org.apache.servicemix.jms.AbstractJmsProcessor.start() starts JMS connection (and thus starts fetching messages on all already registered and all new registered listeners) before org.apache.servicemix.jms.multiplexing.MultiplexingConsumerProcessor initializes its pendingMessages map in doStart() method. It can be resolved by: 1) moving initialization of MultiplexingConsumerProcessor.pendingMessages before consumer.setMessageListener(this); Also initializing MultiplexingConsumerProcessor.channel field should be done before any message arrives via listener's onMessage method. OR 2) starting JMS connection in org.apache.servicemix.jms.AbstractJmsProcessor.start() after whole initialization in subclasses is done (after doStart()) I am attaching patch for the first solution. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
