[jira] Created: (SM-812) [patch] JAAS Login for Batch Processes
[patch] JAAS Login for Batch Processes --- Key: SM-812 URL: https://issues.apache.org/activemq/browse/SM-812 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Reporter: Kristian Koehler Attachments: patch.zip Hi the attached patch includes a PassThroughJAASLoginComponent which forwards a Message through the NMR and performs a JAAS login. The JAAS Subject is added to the message properties (javax.jbi.security.subject). This component can be used if you have a batch process which should call an JAAS secured component (for example a EJB service called with JSR-181). The attached StaticValueCallbackHandler for example enables you to configure static login information. Sample Config: --- 8 (start) --- ... sm:activationSpec componentName=login service=foo:login sm:component bean class=org.apache.servicemix.components.security.PassThroughJAASLoginComponent property name=loginContext ref=loginContext / /bean /sm:component /sm:activationSpec ... bean id=loginContext class=javax.security.auth.login.LoginContext constructor-arg valueservicemix-domain/value /constructor-arg constructor-arg ref local=callbackHandler / /constructor-arg /bean bean id=callbackHandler class=org.apache.servicemix.components.security.StaticValueCallbackHandler property name=name value=first / property name=password value=secret / /bean ... --- 8 (end) --- After the PassThroughJAASLoginComponent is invoked and the login could be performed you can call JAAS secured endpoints. The patch includes test cases for the component. Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-812) [patch] JAAS Login for Batch Processes
[ https://issues.apache.org/activemq/browse/SM-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Koehler updated SM-812: Attachment: patch.zip [patch] JAAS Login for Batch Processes --- Key: SM-812 URL: https://issues.apache.org/activemq/browse/SM-812 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Reporter: Kristian Koehler Attachments: patch.zip, patch.zip Hi the attached patch includes a PassThroughJAASLoginComponent which forwards a Message through the NMR and performs a JAAS login. The JAAS Subject is added to the message properties (javax.jbi.security.subject). This component can be used if you have a batch process which should call an JAAS secured component (for example a EJB service called with JSR-181). The attached StaticValueCallbackHandler for example enables you to configure static login information. Sample Config: --- 8 (start) --- ... sm:activationSpec componentName=login service=foo:login sm:component bean class=org.apache.servicemix.components.security.PassThroughJAASLoginComponent property name=loginContext ref=loginContext / /bean /sm:component /sm:activationSpec ... bean id=loginContext class=javax.security.auth.login.LoginContext constructor-arg valueservicemix-domain/value /constructor-arg constructor-arg ref local=callbackHandler / /constructor-arg /bean bean id=callbackHandler class=org.apache.servicemix.components.security.StaticValueCallbackHandler property name=name value=first / property name=password value=secret / /bean ... --- 8 (end) --- After the PassThroughJAASLoginComponent is invoked and the login could be performed you can call JAAS secured endpoints. The patch includes test cases for the component. Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-811) servicemix-jms does not set SoapAction property for SOAP jms messages
[ https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-811: --- Patch Info: [Patch Available] servicemix-jms does not set SoapAction property for SOAP jms messages - Key: SM-811 URL: https://issues.apache.org/activemq/browse/SM-811 Project: ServiceMix Issue Type: Bug Components: servicemix-jms Affects Versions: 3.0, 3.0.1, 3.1 Environment: Tested with Tibco EMS as jms server and Tibco Business works as system providing the service. The error should also occur with ActiveMQ. Reporter: Christian Schneider Priority: Critical Attachments: servicemix-jms-sm-811.patch, servicemix-jsr181-sm-811.patch When tibco is the client all works well but when tibco implements the service it rejects the soap/jms message as it wants the SoapAction jms property to be set. I have added a dummy SoapAction in StandardProviderProcessor: ... MessageProducer producer = session.createProducer(destination); TextMessage msg = session.createTextMessage(); NormalizedMessage nm = exchange.getMessage(in); fromNMS(nm, msg); String soapAction = default; msg.setStringProperty(SoapAction, soapAction); ... I was able to do a complete request/reply with tibco in this way. Of course the default SoapAction will only help if my service has only one method. From what I see in Tibco the SoapAction should at least contain the method name of the service being called. The servicemix-jms component should by default set this property to make it more compatible with other soap/jms compatible systems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SM-620) Issues with ServiceMix startup shell script on Solaris
[
https://issues.apache.org/activemq/browse/SM-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed SM-620.
--
Resolution: Duplicate
Issues with ServiceMix startup shell script on Solaris
--
Key: SM-620
URL: https://issues.apache.org/activemq/browse/SM-620
Project: ServiceMix
Issue Type: Bug
Components: servicemix-assembly
Affects Versions: 3.0
Reporter: Bruce Snyder
Problems with Solaris:
1. The following command does not work in Solaris:
{code}
export JAVA_MIN_MEM=64M
{code}
Solution:
{code}
if [ x$JAVA_MIN_MEM = x ]; then
JAVA_MIN_MEM=64M
export JAVA_MIN_MEM
fi
if [ x$JAVA_MAX_MEM = x ]; then
JAVA_MAX_MEM=256M
export JAVA_MAX_MEM
fi
{code}
2. Also, in locateHome()
if [ ! -e ]
does not work for Solaris (not supported option for test). Instead, the -e
should be -d
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-812) [patch] JAAS Login for Batch Processes
[ https://issues.apache.org/activemq/browse/SM-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37874 ] Guillaume Nodet commented on SM-812: Cool :) Just a question: did you handle the case where the EJB itself is secured in the J2EE server ? If so, how ? I think this component only solves the case where the jsr181 endpoint is secured by servicemix, right ? [patch] JAAS Login for Batch Processes --- Key: SM-812 URL: https://issues.apache.org/activemq/browse/SM-812 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Reporter: Kristian Koehler Attachments: patch.zip, patch.zip Hi the attached patch includes a PassThroughJAASLoginComponent which forwards a Message through the NMR and performs a JAAS login. The JAAS Subject is added to the message properties (javax.jbi.security.subject). This component can be used if you have a batch process which should call an JAAS secured component (for example a EJB service called with JSR-181). The attached StaticValueCallbackHandler for example enables you to configure static login information. Sample Config: --- 8 (start) --- ... sm:activationSpec componentName=login service=foo:login sm:component bean class=org.apache.servicemix.components.security.PassThroughJAASLoginComponent property name=loginContext ref=loginContext / /bean /sm:component /sm:activationSpec ... bean id=loginContext class=javax.security.auth.login.LoginContext constructor-arg valueservicemix-domain/value /constructor-arg constructor-arg ref local=callbackHandler / /constructor-arg /bean bean id=callbackHandler class=org.apache.servicemix.components.security.StaticValueCallbackHandler property name=name value=first / property name=password value=secret / /bean ... --- 8 (end) --- After the PassThroughJAASLoginComponent is invoked and the login could be performed you can call JAAS secured endpoints. The patch includes test cases for the component. Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-813) [patch] Unique Column Names for JdbcComponent
[ https://issues.apache.org/activemq/browse/SM-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Koehler updated SM-813: Attachment: patch.txt [patch] Unique Column Names for JdbcComponent - Key: SM-813 URL: https://issues.apache.org/activemq/browse/SM-813 Project: ServiceMix Issue Type: Bug Components: servicemix-components Reporter: Kristian Koehler Attachments: patch.txt HI using the JdbcComponent with a SQL Statement returing a ResultSet with two or more equal columnnames results in an invalid XML document. Example: SQL Statement SELECT * FROM TABLE1, TABLE2 WHERE TABLE1.ID = TABLE2.ID Resulting XML: --- 8 --- sqlResults resultSet row id=1 id=1/ ... --- 8 --- The column Names in this example are not unique. The attached patch solves this issue. The resulting document would look like this: --- 8 --- sqlResults resultSet row id=1 id_1=1/ ... --- 8 --- Test Case available. Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-812) [patch] JAAS Login for Batch Processes
[ https://issues.apache.org/activemq/browse/SM-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37882 ] Guillaume Nodet commented on SM-812: Do you use ST flow, acegi ? What happen if you dont set the subject property on the exchange, but only perfom the login call in the component ? I don't really understand who / how / when the subject is given to the EJB container [patch] JAAS Login for Batch Processes --- Key: SM-812 URL: https://issues.apache.org/activemq/browse/SM-812 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Reporter: Kristian Koehler Attachments: patch.zip, patch.zip Hi the attached patch includes a PassThroughJAASLoginComponent which forwards a Message through the NMR and performs a JAAS login. The JAAS Subject is added to the message properties (javax.jbi.security.subject). This component can be used if you have a batch process which should call an JAAS secured component (for example a EJB service called with JSR-181). The attached StaticValueCallbackHandler for example enables you to configure static login information. Sample Config: --- 8 (start) --- ... sm:activationSpec componentName=login service=foo:login sm:component bean class=org.apache.servicemix.components.security.PassThroughJAASLoginComponent property name=loginContext ref=loginContext / /bean /sm:component /sm:activationSpec ... bean id=loginContext class=javax.security.auth.login.LoginContext constructor-arg valueservicemix-domain/value /constructor-arg constructor-arg ref local=callbackHandler / /constructor-arg /bean bean id=callbackHandler class=org.apache.servicemix.components.security.StaticValueCallbackHandler property name=name value=first / property name=password value=secret / /bean ... --- 8 (end) --- After the PassThroughJAASLoginComponent is invoked and the login could be performed you can call JAAS secured endpoints. The patch includes test cases for the component. Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-808) Servicemix jboss deployer
[ https://issues.apache.org/activemq/browse/SM-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Dofonsou updated SM-808: - Attachment: SourceTransformer.diff Servicemix jboss deployer - Key: SM-808 URL: https://issues.apache.org/activemq/browse/SM-808 Project: ServiceMix Issue Type: Bug Environment: JBoss 4.0.5 GA Reporter: Eric Dofonsou Fix For: 3.1 Attachments: SourceTransformer.diff The servicemix-jboss-deployer-3.1-SNAPSHOT.sar file generated by the jboss depolyer does not include the xalan-2.7.0.jar file in the lib. This is required by servicemix and is not included in jboss. Adding the jar to the .sar file fixed the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SM-808) Remove Xalan dependency in SourceTransformer (was: Servicemix jboss deployer)
[ https://issues.apache.org/activemq/browse/SM-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-808. Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Thu Jan 11 07:00:30 2007 New Revision: 495245 URL: http://svn.apache.org/viewvc?view=revrev=495245 Log: SM-808: Remove Xalan dependency in SourceTransformer Thanks to Eric Dofonsu ! Modified: incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/jaxp/SourceTransformer.java incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/jaxp/StAXSourceTransformer.java incubator/servicemix/trunk/core/servicemix-core/src/test/java/org/apache/servicemix/jbi/jaxp/StaxSourceTest.java I have slightly modified your patch to keep the xalan optimization if available on the classpath. Thanks ! Remove Xalan dependency in SourceTransformer (was: Servicemix jboss deployer) - Key: SM-808 URL: https://issues.apache.org/activemq/browse/SM-808 Project: ServiceMix Issue Type: Bug Environment: JBoss 4.0.5 GA Reporter: Eric Dofonsou Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: SourceTransformer.diff The servicemix-jboss-deployer-3.1-SNAPSHOT.sar file generated by the jboss depolyer does not include the xalan-2.7.0.jar file in the lib. This is required by servicemix and is not included in jboss. Adding the jar to the .sar file fixed the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-815) Externalize values from main configuration file into a single property file
Externalize values from main configuration file into a single property file Key: SM-815 URL: https://issues.apache.org/activemq/browse/SM-815 Project: ServiceMix Issue Type: Improvement Components: servicemix-assembly Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SM-815) Externalize values from main configuration file into a single property file
[ https://issues.apache.org/activemq/browse/SM-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-815. Resolution: Fixed Author: gnodet Date: Thu Jan 11 08:05:55 2007 New Revision: 495271 URL: http://svn.apache.org/viewvc?view=revrev=495271 Log: SM-815: Externalize values from main configuration file into a single property file Added: incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/servicemix.properties (with props) Modified: incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/jmx.xml incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/jndi.xml incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/servicemix.xml Externalize values from main configuration file into a single property file Key: SM-815 URL: https://issues.apache.org/activemq/browse/SM-815 Project: ServiceMix Issue Type: Improvement Components: servicemix-assembly Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SM-813) [patch] Unique Column Names for JdbcComponent
[ https://issues.apache.org/activemq/browse/SM-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-813. Resolution: Fixed Fix Version/s: 3.1 Assignee: Guillaume Nodet Author: gnodet Date: Thu Jan 11 09:35:41 2007 New Revision: 495303 URL: http://svn.apache.org/viewvc?view=revrev=495303 Log: SM-813: Unique Column Names for JdbcComponent Patch provided by Kristian Koehler Added: incubator/servicemix/trunk/common/servicemix-components/src/test/java/org/apache/servicemix/components/jdbc/ incubator/servicemix/trunk/common/servicemix-components/src/test/java/org/apache/servicemix/components/jdbc/JdbcComponentUniqueNamesTest.java (with props) Modified: incubator/servicemix/trunk/common/servicemix-components/src/main/java/org/apache/servicemix/components/jdbc/JdbcComponent.java [patch] Unique Column Names for JdbcComponent - Key: SM-813 URL: https://issues.apache.org/activemq/browse/SM-813 Project: ServiceMix Issue Type: Bug Components: servicemix-components Reporter: Kristian Koehler Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: patch.txt HI using the JdbcComponent with a SQL Statement returing a ResultSet with two or more equal columnnames results in an invalid XML document. Example: SQL Statement SELECT * FROM TABLE1, TABLE2 WHERE TABLE1.ID = TABLE2.ID Resulting XML: --- 8 --- sqlResults resultSet row id=1 id=1/ ... --- 8 --- The column Names in this example are not unique. The attached patch solves this issue. The resulting document would look like this: --- 8 --- sqlResults resultSet row id=1 id_1=1/ ... --- 8 --- Test Case available. Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: log4j
So I implemted it. It works fine until now. I still have to do some improvements on it but I guess I can provide it to you tomorrow. Cheers, Thomas Thomas TERMIN wrote: I found it. ;-) I'm implementing at the moment the new service. Guillaume Nodet wrote: Forwarding to the dev list ... I think you may want to take a look at how the JdbcAuditor, DotViewService or StatisticsService are implemented. They all inherit the o.a.s.jbi.management.BaseSystemService abstract class. They come in different flavous wrt configuration however. I would recommend to look at the StatisticsService, which can be configured that way: sm:container ... sm:services sm:statistics .. / /sm:services /sm:container This way, the service is automatically registered in JMX and has its own lifecycle (which is tied to the container), so that you can stop / start the service from jmx. On 1/11/07, Thomas TERMIN [EMAIL PROTECTED] wrote: What I want to do is to implement a MBean which configure the log4j system periodicaly with a scheduler. But before I will look if there is a log4j.xml or log4j.properties in the conf directory if there is nothing in it then I assume that there is no log4j system and don't reconfigure log4j (I will give you a better explanation later ;-) ). The Problem what I have is to register a MBean in conf/servicemix.xml. How do I have to do this? I tried this with the spring MBeanExporter but it doesn't work for me. Cheers, Thomas Btw, if you don't mind, i'd rather have such discussion on servicemix-dev / servicemix-users ;-) No problem at all! If you open the thread... Cheers, Thomas Guillaume Nodet wrote: Did you implement something useful ? Would you consider giving it back to ServiceMix ? On 10/20/06, Thomas TERMIN [EMAIL PROTECTED] wrote: Sorry I did not mean a servicemix component. I use allways the word component ;-) since I started working with servicemix. What you said is exactly what I meant. So I will have a look on it! Thanks, Thomas Guillaume Nodet wrote: I would rather use a ServiceMix service instead of a component, as this is more related to management / configuration than a component if I understand you correctly. ... and use a timer to reload the log4j config. But iirc, log4j already has this feature, we just need to enable it. On 10/20/06, Thomas TERMIN [EMAIL PROTECTED] wrote: Hello Guillaume, We would need a log4j Component where you can change the debug level at runtime. I would implement a MBean which initialise the log4j system at startup and also have a scheduler which looks if the log4j.xml has changed and then reinitialise the log4j system. If I would provide you a patch would you accept this in servicemix? Cheers, Thomas Termin
[jira] Resolved: (SM-783) build fails under java 6
[ https://issues.apache.org/activemq/browse/SM-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-783. Resolution: Fixed Fix Version/s: 3.1 Assignee: Guillaume Nodet Author: gnodet Date: Thu Jan 11 12:23:43 2007 New Revision: 495362 URL: http://svn.apache.org/viewvc?view=revrev=495362 Log: SM-783: build fails under Java6 Modified: incubator/servicemix/trunk/common/servicemix-components/pom.xml incubator/servicemix/trunk/common/servicemix-components/src/main/java/org/apache/servicemix/components/groovy/GroovyComponent.java incubator/servicemix/trunk/common/servicemix-components/src/main/java/org/apache/servicemix/components/script/ScriptComponent.java build fails under java 6 Key: SM-783 URL: https://issues.apache.org/activemq/browse/SM-783 Project: ServiceMix Issue Type: Bug Components: servicemix-components Affects Versions: 3.0 Environment: x86 linux - FC5, sun jdk 1.6.0, apache-servicemix-3.0-incubating-src.tar.gz Reporter: tim biernat Assigned To: Guillaume Nodet Priority: Minor Fix For: 3.1 mvn -Dmaven.test.skip=true -Dprofile=step2 install ... [INFO] [compiler:compile] Compiling 114 source files to /home/tbiernat/work/servicemix/apache-servicemix-3.0-incubating/src/servicemix-components/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/tbiernat/work/servicemix/apache-servicemix-3.0-incubating/src/servicemix-components/src/main/java/org/apache/servicemix/components/script/ScriptComponent.java:[210,36] cannot find symbol symbol : method createNamespace() location: interface javax.script.ScriptEngine /home/tbiernat/work/servicemix/apache-servicemix-3.0-incubating/src/servicemix-components/src/main/java/org/apache/servicemix/components/script/ScriptComponent.java:[261,26] cannot find symbol symbol : method eval(javax.script.Namespace) location: class javax.script.CompiledScript /home/tbiernat/work/servicemix/apache-servicemix-3.0-incubating/src/servicemix-components/src/main/java/org/apache/servicemix/components/script/ScriptComponent.java:[269,14] cannot find symbol symbol : method eval(java.lang.String,javax.script.Namespace) location: interface javax.script.ScriptEngine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
question about servicemix-jsr181 component...
Hi, I have a question regarding servicemix-jsr181 component. I want to know if it has a thread pool or if I need to define several instances of it in order to be able to attend simultaneous messages. If it has a threadpool, is that the default behavior for any servicemix component? -- View this message in context: http://www.nabble.com/question-about-servicemix-jsr181-component...-tf2961908s12049.html#a8286938 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: question about servicemix-jsr181 component...
The threading is the same as for servlets. A single instance will server multiple concurrent requests. If you need pooling, use spring pooling support when declaring your pojo. On 1/11/07, eburgos [EMAIL PROTECTED] wrote: Hi, I have a question regarding servicemix-jsr181 component. I want to know if it has a thread pool or if I need to define several instances of it in order to be able to attend simultaneous messages. If it has a threadpool, is that the default behavior for any servicemix component? -- View this message in context: http://www.nabble.com/question-about-servicemix-jsr181-component...-tf2961908s12049.html#a8286938 Sent from the ServiceMix - Dev mailing list archive at Nabble.com. -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: Release ServiceMix 3.1
+1. I will test smx+geronimo gnodet wrote: I think it's time to start the release process for 3.1. I have been working on the distribution a bit, but it needs more work to check that the samples all work well, etc ... So please test the release to ensure everything is working well, that all legal stuff is ok (need to check all jars included in the distribution), etc ... This is a hard work, so help is really welcome :-) -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/ -- View this message in context: http://www.nabble.com/Release-ServiceMix-3.1-tf2962129s12049.html#a8288910 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Updated: (SM-816) useless include log framwork into jboss deployer
[ https://issues.apache.org/activemq/browse/SM-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégoire A. updated SM-816: --- Attachment: pom.diff useless include log framwork into jboss deployer Key: SM-816 URL: https://issues.apache.org/activemq/browse/SM-816 Project: ServiceMix Issue Type: Bug Affects Versions: incubation Environment: linux, jdk5, jboss 4-0-5 GA Reporter: Grégoire A. Fix For: 3.1 Attachments: pom.diff Original Estimate: 15 minutes Remaining Estimate: 15 minutes Exception raise when commons-logging and log4j jar are included into sar jboss deployer 00:51:07,136 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:58s:2ms 00:51:22,446 ERROR [STDERR] log4j:ERROR A org.jboss.logging.util.OnlyOnceErrorHandler object is not assignable to a org.apache.log4j.spi.ErrorHandler variable. 00:51:22,447 ERROR [STDERR] log4j:ERROR The class org.apache.log4j.spi.ErrorHandler was loaded by 00:51:22,447 ERROR [STDERR] log4j:ERROR [EMAIL PROTECTED] url=file:/home/keo/EclipseWorkspace/workspace_3.2.SMX.TEST/jboss-4.0.5.GA/server/default/tmp/deploy/tmp61318servicemix-jboss-deployer-3.1-SNAPSHOT.sar ,addedOrder=40}] whereas object of type 00:51:22,447 ERROR [STDERR] log4j:ERROR org.jboss.logging.util.OnlyOnceErrorHandler was loaded by [EMAIL PROTECTED] 00:51:22,489 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows. 00:51:22,489 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:175) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:394) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.LogManager.clinit(LogManager.java:122) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.Logger.getLogger(Logger.java:104) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.init(Log4JLogger.java:108) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) 00:51:22,491 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) 00:51:22,492 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1040) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:838) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:601) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645) 00:51:22,492 ERROR [STDERR] at org.apache.servicemix.jbi.container.JBIContainer.clinit(JBIContainer.java:95) 00:51:22,492 ERROR [STDERR] at org.servicemix.jboss.deployment.JBIService.init(JBIService.java:45) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-761) JRuby support
[ https://issues.apache.org/activemq/browse/SM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37900 ] Kit Plummer commented on SM-761: Not sure if it is really related to this particular thread of discussion, but I can see where creating a JBI component (with the lifecycle features) in Ruby would be very handy. Not that writing simple services in Java is painful, but the deployment process, including the Maven build can be quite tedious. Swapping a file out of a Service Assembly and redeploying to ServiceMix would be very efficient from a development/testing perspective. JRuby support - Key: SM-761 URL: https://issues.apache.org/activemq/browse/SM-761 Project: ServiceMix Issue Type: Improvement Components: servicemix-script Reporter: Guillaume Nodet JRuby support should work with spring 2.0.2 + jruby 0.9.1 See http://forum.springframework.org/showthread.php?t=28798 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
