[jira] Resolved: (SM-1084) make configurable if CONTENT-TYPE is used as property from the normalized message or not
[ https://issues.apache.org/activemq/browse/SM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-1084. --- Resolution: Fixed fixed for 3.2 Author: tterm Date: Thu Oct 4 09:02:44 2007 New Revision: 581955 URL: http://svn.apache.org/viewvc?rev=581955&view=rev Log: SM-1084 make configurable if CONTENT-TYPE is used as property from the normalized message or not Modified: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfiguration.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfigurationMBean.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ProviderProcessor.java fixed for 3.1.3 Author: tterm Date: Thu Oct 4 09:23:11 2007 New Revision: 581959 URL: http://svn.apache.org/viewvc?rev=581959&view=rev Log: SM-1084 make configurable if CONTENT-TYPE is used as property from the normalized message or not Modified: incubator/servicemix/branches/servicemix-3.1/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfiguration.java incubator/servicemix/branches/servicemix-3.1/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfigurationMBean.java incubator/servicemix/branches/servicemix-3.1/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpEndpoint.java incubator/servicemix/branches/servicemix-3.1/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ProviderProcessor.java > make configurable if CONTENT-TYPE is used as property from the normalized > message or not > > > Key: SM-1084 > URL: https://issues.apache.org/activemq/browse/SM-1084 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-http >Affects Versions: 3.1.2 >Reporter: Thomas Termin >Assignee: Thomas Termin > Fix For: 3.1.3, 3.2 > > > Make it configurable if the http content type will be used from the property > of the normalized message or not -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (SM-1084) make configurable if CONTENT-TYPE is used as property from the normalized message or not
[ https://issues.apache.org/activemq/browse/SM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin reopened SM-1084: --- Should be configurable on per endpoint basis. So tha's not the right solution > make configurable if CONTENT-TYPE is used as property from the normalized > message or not > > > Key: SM-1084 > URL: https://issues.apache.org/activemq/browse/SM-1084 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-http >Affects Versions: 3.1.2 >Reporter: Thomas Termin >Assignee: Thomas Termin > Fix For: 3.1.3, 3.2 > > > Make it configurable if the http content type will be used from the property > of the normalized message or not -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release ServiceMix 3.1.2
+1 Cheers, Thomas Freeman Fang wrote: > Hi All, > > I have uploaded a version of ServiceMix 3.1.2 for you to review. See > http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.1.2 > for all the links and release notes. > > [ ] +1 Release ServiceMix 3.1.2 > [ ] ± 0 > [ ] -1 Do not release ServiceMix 3.1.2 > > Cheers > > Freeman > -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: [jira] Commented: (SM-1044) Routing based on message property and set new property on the message in EIP content based router
Sorry for long response time. I will look into your patch as soon as possible. Cheers, Thomas Termin Vinod Chhabria (JIRA) wrote: > [ > https://issues.apache.org/activemq/browse/SM-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40120 > ] > > Vinod Chhabria commented on SM-1044: > > > We think this is a good enhancement to the existing predicate classes. Can > you please approve so we can go ahead and add this to our servicemix > installation. We do not want to apply any patch that will not be available in > future releases. > > If you think this is too specific and not good enough to be added as a patch > to the servicemix-eip distribution, then please provide us documentation as > to how to include our custom predicate class to our service unit. We tried > doing it but it is requiring all other eip classes to be included in the > service unit. > > Please advise so we can resolve either way. > > >>Routing based on message property and set new property on the message in EIP >>content based router >>- >> >>Key: SM-1044 >>URL: https://issues.apache.org/activemq/browse/SM-1044 >>Project: ServiceMix >> Issue Type: New Feature >> Components: servicemix-eip >> Affects Versions: 3.1 >>Environment: Windows, JBoss-4.0.4-GA using Servicemix deployer >> Reporter: Srivatsan Sridharan >> Priority: Minor >>Attachments: SwitchPredicate.java, XPathPredicate.java >> >> >>SwitchPredicate.java (available in Servicemix trunk) routes based on the >>(boolean) value of the property set on the message exchange. It would be good >>to have it >>1) route based on the value (not particularly boolean) of a property set on >>the message. >>2) set additional property on the message when the evaluation of property >>value is true. >>SwitchPredicate.java attached herewith has the changes to address the above. >> >>XPathPredicate.java attached herewith has the changes to set additional >>property in the ContentBasedRouter. >>Please let me know if this is the right approach. > > -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Commented: (SM-1038) http provider endpoint sends wrong Host header
[ https://issues.apache.org/activemq/browse/SM-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39996 ] Thomas Termin commented on SM-1038: --- Patch should be undone if a new jetty release is available > http provider endpoint sends wrong Host header > -- > > Key: SM-1038 > URL: https://issues.apache.org/activemq/browse/SM-1038 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-http >Affects Versions: 3.1.1 > Environment: JDK 5.0 >Reporter: Torsten Mielke > Fix For: 3.2 > > Attachments: http-marshaler.patch > > > The current ServiceMix http:provider endpoint uses jetty-client-6.1.5 > library, which contains a bug fixed in their trunk. More infomation on > http://fisheye.codehaus.org/browse/jetty-contrib/jetty/trunk/contrib/client/src/main/java/org/mortbay/jetty/client/HttpConnection.java?r1=374&r2=378. > This causes wrong Host header in HTTP request. > Actual Host header looks like this: > Host: [EMAIL PROTECTED]//host.com:8080(1,0,0) > Of course such header causes HTTP 400 response and endpoint cannot be used at > all. > To work around this bug > deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/DefaultHttpProviderMarshaler.java > needs to get the attached patch applied. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1038) http provider endpoint sends wrong Host header
[ https://issues.apache.org/activemq/browse/SM-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-1038. --- Resolution: Fixed Fix Version/s: 3.2 Fixed Many thanks to Torsten Mielke for the patch!!! Author: tterm Date: Wed Aug 22 08:09:59 2007 New Revision: 568645 URL: http://svn.apache.org/viewvc?rev=568645&view=rev Log: SM-1038 http provider endpoint sends wrong Host header Modified: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/DefaultHttpProviderMarshaler.java > http provider endpoint sends wrong Host header > -- > > Key: SM-1038 > URL: https://issues.apache.org/activemq/browse/SM-1038 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-http >Affects Versions: 3.1.1 > Environment: JDK 5.0 >Reporter: Torsten Mielke > Fix For: 3.2 > > Attachments: http-marshaler.patch > > > The current ServiceMix http:provider endpoint uses jetty-client-6.1.5 > library, which contains a bug fixed in their trunk. More infomation on > http://fisheye.codehaus.org/browse/jetty-contrib/jetty/trunk/contrib/client/src/main/java/org/mortbay/jetty/client/HttpConnection.java?r1=374&r2=378. > This causes wrong Host header in HTTP request. > Actual Host header looks like this: > Host: [EMAIL PROTECTED]//host.com:8080(1,0,0) > Of course such header causes HTTP 400 response and endpoint cannot be used at > all. > To work around this bug > deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/DefaultHttpProviderMarshaler.java > needs to get the attached patch applied. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-854) LogService uses hard-coded path to the log4j.xml file
[
https://issues.apache.org/activemq/browse/SM-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Termin resolved SM-854.
--
Resolution: Fixed
Fix Version/s: 3.1.2
backport to 3.1.2
Applied the patch from Bruce.
Author: tterm
Date: Thu Jul 26 04:09:05 2007
New Revision: 559781
URL: http://svn.apache.org/viewvc?view=rev&rev=559781
Log:
SM-854 LogService uses hard-coded path to the log4j.xml file
Modified:
incubator/servicemix/branches/servicemix-3.1/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/logging/LogService.java
incubator/servicemix/branches/servicemix-3.1/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/logging/LogTask.java
> LogService uses hard-coded path to the log4j.xml file
> --
>
> Key: SM-854
> URL: https://issues.apache.org/activemq/browse/SM-854
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
>Affects Versions: 3.1
>Reporter: Bruce Snyder
>Assignee: Thomas Termin
> Fix For: 3.1.2, 3.2
>
> Attachments: SM-854.patch.txt
>
>
> The path the log4j.xml file is hard-coded to {{conf/log4j.xml}}. If
> ServiceMix is started from inside the {{bin}} directory, ServiceMix won't be
> able to locate this file and logging will not work properly. Below is the
> output from a started in the {{bin}} directory:
> {panel}
> $ ./servicemix
> servicemix: JAVA_HOME not set; results may vary
> java version "1.5.0_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
> Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
> Starting Apache ServiceMix ESB: 3.1-incubating-SNAPSHOT
> Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
> INFO - ConnectorServerFactoryBean - JMX connector available at:
> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> INFO - JBIContainer - ServiceMix 3.1-incubating-SNAPSHOT
> JBI Container (ServiceMix) is starting
> INFO - JBIContainer - For help or more informations please
> see: http://incubator.apache.org/servicemix/
> INFO - ComponentMBeanImpl - Initializing component:
> #SubscriptionManager#
> INFO - DeploymentService - Restoring service assemblies
> INFO - JBIContainer - ServiceMix JBI Container
> (ServiceMix) started
> INFO - JDBCAdapterFactory - Database driver recognized:
> [apache_derby_embedded_jdbc_driver]
> ERROR - LogTask- java.io.FileNotFoundException:
> conf/log4j.xml (No such file or directory)
> {panel}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (SM-854) LogService uses hard-coded path to the log4j.xml file
[
https://issues.apache.org/activemq/browse/SM-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Termin reopened SM-854:
--
Assignee: Thomas Termin (was: Bruce Snyder)
Should be also fixed for 3.1.2
> LogService uses hard-coded path to the log4j.xml file
> --
>
> Key: SM-854
> URL: https://issues.apache.org/activemq/browse/SM-854
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
>Affects Versions: 3.1
>Reporter: Bruce Snyder
> Assignee: Thomas Termin
> Fix For: 3.2
>
> Attachments: SM-854.patch.txt
>
>
> The path the log4j.xml file is hard-coded to {{conf/log4j.xml}}. If
> ServiceMix is started from inside the {{bin}} directory, ServiceMix won't be
> able to locate this file and logging will not work properly. Below is the
> output from a started in the {{bin}} directory:
> {panel}
> $ ./servicemix
> servicemix: JAVA_HOME not set; results may vary
> java version "1.5.0_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
> Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
> Starting Apache ServiceMix ESB: 3.1-incubating-SNAPSHOT
> Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
> INFO - ConnectorServerFactoryBean - JMX connector available at:
> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> INFO - JBIContainer - ServiceMix 3.1-incubating-SNAPSHOT
> JBI Container (ServiceMix) is starting
> INFO - JBIContainer - For help or more informations please
> see: http://incubator.apache.org/servicemix/
> INFO - ComponentMBeanImpl - Initializing component:
> #SubscriptionManager#
> INFO - DeploymentService - Restoring service assemblies
> INFO - JBIContainer - ServiceMix JBI Container
> (ServiceMix) started
> INFO - JDBCAdapterFactory - Database driver recognized:
> [apache_derby_embedded_jdbc_driver]
> ERROR - LogTask- java.io.FileNotFoundException:
> conf/log4j.xml (No such file or directory)
> {panel}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Checkstyle and PMD
Bruce Snyder wrote: > 1) Is there a reason why the maven-checkstyle-plugin is enabled in > many subproject level POMs instead of just in the build module POM? It > seems like this should be enabled in one location instead of being > spread throughout 14 POMs across the code base. Even the PMD ruleset > is only enabled in build module POM. I guess it is because not all components are refactored. See for example https://issues.apache.org/activemq/browse/SM-933 On some day there should be all components refactored and the checkstyle will be enabled in only one POM. > 2) It is a *major* pain to have a build fail simply because the code > is not formatted according to the Checkstyle and PMD conventions being > used in ServiceMix. So I've taken a stab at creating a code formatter > profile for Eclipse and some quick docs located here: This prevents a user to checkin stuff which is not in the correct style. There were a hint from Guillaume some day. > > http://cwiki.apache.org/confluence/display/SM/Building#Building-CodeConventions > > > If you're using Eclipse, please try it out and improve it if necessary. > Cheers Thomas -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: Concurrent connection in servicemix
Hello, Could you provide a little bit more info. Does this appear with http prvoider BC ? Thomas Ruwan Linton wrote: > Hi, > > I am trying to do a performance test on servicemix. > > When I send 1 requests from 20 threads concurrently servicemix is > working fine, no errors. But when the thread count is increased to 40, SM > seems to be hanging and I didn't get any reply to my requests. > > Is there a mechanism to tune SM for handling simultaneous connections? > > If so can some one please point me how to do that. > > Thanks in advance, > Ruwan > 1 -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: [VOTE] Release ServiceMix 3.1.1 (2nd try)
+1 Guillaume Nodet wrote: > I have uploaded a version of ServiceMix 3.1.1 in the standard repo > for you to review. See > http://incubator.apache.org/servicemix/servicemix-311.html > for the future download page and release notes (these are also included in > the > distribution). The distribution have been uploaded to > > http://people.apache.org/~gnodet/servicemix-3.1.1-incubating/org/apache/servicemix/apache-servicemix/3.1.1-incubating/ > > > I send this mail both to the dev list and [EMAIL PROTECTED], as a first vote > has > been > conducted on the ServiceMix dev list and some issues have been fixed since > that, so hopefully this one will be fine. > > [ ] +1 Release ServiceMix 3.1.1 > [ ] +/- 0 > [ ] -1 Do not release ServiceMix 3.1.1 > > The rat log is available at > http://people.apache.org/~gnodet/rat-servicemix-3.1.1-incubating.txt<http://people.apache.org/%7Egnodet/rat-servicemix-3.1.1-incubating.txt> > > > Here's my +1 > -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: [ANNOUNCE] Welcome Gert Vanthienen as our newest committer
Guillaume Nodet wrote: > Gert has accepted the PPMC invitation to become a committer on ServiceMix. > Congratulations and welcome aboard Gert ! > Congratulations Gert! Cheers, Thomas -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Commented: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39053 ] Thomas Termin commented on SM-932: -- Fixed for servicemix-http! Thanks a lot to Gert Vanthienen! Author: tterm Date: Fri Apr 27 05:23:20 2007 New Revision: 533074 URL: http://svn.apache.org/viewvc?view=rev&rev=533074 Log: SM-932 Enable PMD/CheckStyle for binding components Added: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/AbstractProcessor.java Removed: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/Constants.java Modified: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/BasicAuthCredentials.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/ContextManager.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpBootstrap.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpBridgeServlet.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpComponent.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfiguration.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfigurationMBean.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpManagedServlet.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpProcessor.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpWsdl1Deployer.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/ManagedContextManager.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/ProxyParameters.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/SslParameters.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/DefaultHttpConsumerMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/DefaultHttpProviderMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpConsumerEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpConsumerMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpProviderEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpProviderMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpSoapConsumerEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpSoapConsumerMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/SerializedMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JCLLogger.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JaasJettyPrincipal.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JaasUserRealm.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JettyContextManager.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/ServiceMixSslSocketConnector.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-
[jira] Commented: (SM-606) Ability to customize http requests when acting as a client
[ https://issues.apache.org/activemq/browse/SM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39043 ] Thomas Termin commented on SM-606: -- What is still to do here? There were some things done on this issue, right! > Ability to customize http requests when acting as a client > -- > > Key: SM-606 > URL: https://issues.apache.org/activemq/browse/SM-606 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-http >Affects Versions: 3.0 >Reporter: Guillaume Nodet > > We should be able to deactivate retries, configure timeouts, aso... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (SM-795) HTTP headers attached as properties may cause requests to fail
[ https://issues.apache.org/activemq/browse/SM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SM-795 started by Thomas Termin. > HTTP headers attached as properties may cause requests to fail > -- > > Key: SM-795 > URL: https://issues.apache.org/activemq/browse/SM-795 > Project: ServiceMix > Issue Type: Improvement >Affects Versions: 3.1 > Environment: W2KS, JDK1.5 >Reporter: Maxim Y. Tebenev > Assigned To: Thomas Termin > Attachments: SM-795.patch > > > When SMX receives HTTP response from provider HTTP endpoint it attaches HTTP > headers as message properties. When forwarding the message to another > provider endpoint the properties goes as HTTP headers in request. For > example, the following request to the second provider endpoint will have > following headers: > POST /DeliveryService/DeliveryService HTTP/1.1 > Date: Wed, 27 Dec 2006 13:24:46 GMT > Server: Apache-Coyote/1.1 > Transfer-Encoding: chunked > Content-Type: text/xml > Content-Length: 359 > SOAPAction: "" > User-Agent: Jakarta Commons-HttpClient/3.0 > Host: localhost:8082 > Server, Date and Transfer-Encoding headers are illegal in client request and > cause Apache Tomcat server to fail with 500 error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-795) HTTP headers attached as properties may cause requests to fail
[ https://issues.apache.org/activemq/browse/SM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin reassigned SM-795: Assignee: Thomas Termin > HTTP headers attached as properties may cause requests to fail > -- > > Key: SM-795 > URL: https://issues.apache.org/activemq/browse/SM-795 > Project: ServiceMix > Issue Type: Improvement >Affects Versions: 3.1 > Environment: W2KS, JDK1.5 >Reporter: Maxim Y. Tebenev > Assigned To: Thomas Termin > Attachments: SM-795.patch > > > When SMX receives HTTP response from provider HTTP endpoint it attaches HTTP > headers as message properties. When forwarding the message to another > provider endpoint the properties goes as HTTP headers in request. For > example, the following request to the second provider endpoint will have > following headers: > POST /DeliveryService/DeliveryService HTTP/1.1 > Date: Wed, 27 Dec 2006 13:24:46 GMT > Server: Apache-Coyote/1.1 > Transfer-Encoding: chunked > Content-Type: text/xml > Content-Length: 359 > SOAPAction: "" > User-Agent: Jakarta Commons-HttpClient/3.0 > Host: localhost:8082 > Server, Date and Transfer-Encoding headers are illegal in client request and > cause Apache Tomcat server to fail with 500 error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-934) change checkstyle line length to 140
[ https://issues.apache.org/activemq/browse/SM-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-934. -- Resolution: Fixed Author: tterm Date: Thu Apr 12 09:56:07 2007 New Revision: 528028 URL: http://svn.apache.org/viewvc?view=rev&rev=528028 Log: SM-934 change checkstyle line length to 140 Modified: incubator/servicemix/trunk/build/src/main/resources/smx-checkstyle.xml > change checkstyle line length to 140 > > > Key: SM-934 > URL: https://issues.apache.org/activemq/browse/SM-934 > Project: ServiceMix > Issue Type: Improvement > Reporter: Thomas Termin > Assigned To: Thomas Termin >Priority: Trivial > > change line length in smx-checkstyle.xml to 140 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Checkstyle / PMD and recent commits
Gert,
I checked in the change of the line length to 140.
Thomas
Gert Vanthienen wrote:
> Guillaume,
>
> Just a few questions/remarks about the CheckStyle rules:
> - a lot of the code seems to be written with a line length of 132 in
> mind, why change it to 120?
> - the rules don't allow using this way of creating setters
>public void setMBeanServer(MBeanServer mbeanServer) {
>this.mbeanServer = mbeanServer;
>}
>
> Regards,
>
> Gert Vanthienen
>
>
> Guillaume Nodet wrote:
>> Hi everybody !
>>
>> I have recently checked in lots of changes. These are mostly
>> code conventions fixes. Let me explain.
>>
>> I've started to add checkstyle and pmd checks at build time.
>> For those who do not know these tools, checkstyle
>> (http://checkstyle.sourceforge.net/) enforces
>> code conventions (braces, spaces, etc ...), while PMD
>> (http://pmd.sourceforge.net/) checks for possible bugs.
>>
>> These tools are configured in the new parent module
>> which all other modules should inherit directly or indirectly
>> when they pass these checks (the buid fails if these checks
>> do not pass).
>>
>> Currently, only the serviceengines module inherit from parent
>> so any help to migrate the other modules is welcome :-)
>> The goal is to have all modules (core, common, deployables mainly)
>> inherit from parent.
>>
>> Btw, thanks to the CXF team which did that a few months ago,
>> and where I borrowed the configuration and all ...
>>
>
>
--
Thomas Termin
___
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel: (+49) 0711 - 45 10 17 676
Fax: (+49) 0711 - 45 10 17 573
WWW: http://www.blue-elephant-systems.com
Email : [EMAIL PROTECTED]
blue elephant systems GmbH
Firmensitz : Wollgrasweg 49, D-70599 Stuttgart
Registergericht : Amtsgericht Stuttgart, HRB 24106
Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Created: (SM-934) change checkstyle line length to 140
change checkstyle line length to 140 Key: SM-934 URL: https://issues.apache.org/activemq/browse/SM-934 Project: ServiceMix Issue Type: Improvement Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Trivial change line length in smx-checkstyle.xml to 140 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: antlib.xml in servicemix-core
Guillaume Nodet wrote: > What about these files which is already included in the distribution ? > > http://svn.apache.org/repos/asf/incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/ant/ > > > Isn't it the same thing ? Yeah this is the same thing. Thx. ;-) > > On 4/11/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> What do you think to package an antlib.xml file in servicemix-core so >> that the user can easily declare all jbi tasks like: >> > uri="http://servicemix.apache.org/ant/1.0"/> >> >> Otherwise the user has to declare a taskdef for each task. >> >> Cheers, >> Thomas >> >> -- >> Thomas Termin >> ___ >> blue elephant systems GmbH >> Wollgrasweg 49 >> D-70599 Stuttgart >> >> Tel: (+49) 0711 - 45 10 17 676 >> Fax: (+49) 0711 - 45 10 17 573 >> WWW: http://www.blue-elephant-systems.com >> Email : [EMAIL PROTECTED] >> >> blue elephant systems GmbH >> Firmensitz : Wollgrasweg 49, D-70599 Stuttgart >> Registergericht : Amtsgericht Stuttgart, HRB 24106 >> Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle >> >> > > -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
antlib.xml in servicemix-core
What do you think to package an antlib.xml file in servicemix-core so that the user can easily declare all jbi tasks like: http://servicemix.apache.org/ant/1.0"/> Otherwise the user has to declare a taskdef for each task. Cheers, Thomas -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Created: (SM-933) Enable PMD/CheckStyle for servicemix-core
Enable PMD/CheckStyle for servicemix-core - Key: SM-933 URL: https://issues.apache.org/activemq/browse/SM-933 Project: ServiceMix Issue Type: Task Components: servicemix-core Reporter: Thomas Termin Priority: Minor PMD/Checkstyle should be enabled for servicemix-core -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-929) eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter
[ https://issues.apache.org/activemq/browse/SM-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-929. -- Resolution: Fixed Author: tterm Date: Tue Apr 10 09:58:29 2007 New Revision: 527197 URL: http://svn.apache.org/viewvc?view=rev&rev=527197 Log: SM-929 eip message filter switch predicate where you can easily turn on/off the exchange flow in a message filter depending on a property Added: incubator/servicemix/trunk/deployables/serviceengines/servicemix-eip/src/main/java/org/apache/servicemix/eip/support/SwitchPredicate.java > eip message filter switch predicate where you can easily turn on/off the > exchange flow depending on a property in a message filter > -- > > Key: SM-929 > URL: https://issues.apache.org/activemq/browse/SM-929 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-eip > Reporter: Thomas Termin > Assigned To: Thomas Termin >Priority: Minor > Fix For: 3.2 > > > This switch predicate can be used to easily switch on/off an exchange flow. > This might be interessting for environments where you have different things > installed. With an property file or an exchange property can you switch the > behaviour. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-929) eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter
eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter -- Key: SM-929 URL: https://issues.apache.org/activemq/browse/SM-929 Project: ServiceMix Issue Type: New Feature Components: servicemix-eip Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Minor Fix For: 3.2 This switch predicate can be used to easily switch on/off an exchange flow. This might be interessting for environments where you have different things installed. With an property file or an exchange property can you switch the behaviour. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (SM-929) eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter
[ https://issues.apache.org/activemq/browse/SM-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SM-929 started by Thomas Termin. > eip message filter switch predicate where you can easily turn on/off the > exchange flow depending on a property in a message filter > -- > > Key: SM-929 > URL: https://issues.apache.org/activemq/browse/SM-929 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-eip > Reporter: Thomas Termin > Assigned To: Thomas Termin >Priority: Minor > Fix For: 3.2 > > > This switch predicate can be used to easily switch on/off an exchange flow. > This might be interessting for environments where you have different things > installed. With an property file or an exchange property can you switch the > behaviour. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-905) message filter registers predicates as mbean as well as a new predicate for on/off filtering
message filter registers predicates as mbean as well as a new predicate for on/off filtering Key: SM-905 URL: https://issues.apache.org/activemq/browse/SM-905 Project: ServiceMix Issue Type: New Feature Components: servicemix-eip Reporter: Thomas Termin Priority: Minor Attachments: eip-message-filter.patch Predicat MBeans are registered exactly as the endpoint just with the extension "Predicate" Interessting is the message filter which do all with reflection and just register predicates if an MBean interface is implemented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-876) jmx.xml should use the jmx.url property
[ https://issues.apache.org/activemq/browse/SM-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-876. -- Resolution: Fixed Date: Wed Mar 28 08:01:33 2007 New Revision: 523355 URL: http://svn.apache.org/viewvc?view=rev&rev=523355 Log: SM-876 jmx.xml should use the jmx.url property from servicemix.properties Modified: incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/jmx.xml incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/servicemix.properties > jmx.xml should use the jmx.url property > --- > > Key: SM-876 > URL: https://issues.apache.org/activemq/browse/SM-876 > Project: ServiceMix > Issue Type: Improvement > Reporter: Thomas Termin > Assigned To: Thomas Termin >Priority: Trivial > Attachments: patch.jmx.xml > > > Just a small patch. ;-) The jmx.xml should specify the jmx.url from > servicemix.properties. Furthermore the hostname should be configurable. (Very > nice for us) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (SM-876) jmx.xml should use the jmx.url property
[ https://issues.apache.org/activemq/browse/SM-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SM-876 started by Thomas Termin. > jmx.xml should use the jmx.url property > --- > > Key: SM-876 > URL: https://issues.apache.org/activemq/browse/SM-876 > Project: ServiceMix > Issue Type: Improvement > Reporter: Thomas Termin > Assigned To: Thomas Termin >Priority: Trivial > Attachments: patch.jmx.xml > > > Just a small patch. ;-) The jmx.xml should specify the jmx.url from > servicemix.properties. Furthermore the hostname should be configurable. (Very > nice for us) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Switching trunk to full java 5 ?
Guillaume Nodet wrote: > Most of our components uses java 5 now. > The container itself works on JDK 1.4 > with some minor modifications (see > http://issues.apache.org/activemq/browse/SM-848) > but i think it would be easier to officially switch > to JDK 5 for everything > Thoughts ? I fully agree with you. ;-)
Re: correlation id with tracing
>> I extended component support so that we have the four methods with the >> MessageExchange parameter to get and set the correlation id. >> >> public InOnly createInOnlyExchange(MessageExchange beforeExchange) >> public InOptionalOut createInOptionalOutExchange(MessageExchange >> beforeExchange) >> public InOut createInOutExchange(MessageExchange beforeExchange) >> public RobustInOnly createRobustInOnlyExchange(MessageExchange >> beforeExchange) >> >> this are the corresponding methods to the four methods without >> parameters to create a new excahnge. > > > Cool, thx :-) > > Do you want to create corresponding methods to the other methods like >> >> public InOut createInOutExchange(QName service, QName interfaceName, >> QName operation) > > > What about adding a helper method to progate / create the correlation id. create correlation id means (if correlation id == null) get the exchange id from the source exchange, right? > > public void propagateCorrelationId(MessageExchange source, MessageExchange > dest); > > This method could be used by the four methods you've written, and could be > called > if the component use other methods. > > Hopefully your account will be created soon. I have sent a reminder, but I > can't do much :-( > > Cheers, >> Thomas >> >> Thomas TERMIN wrote: >> >> Is there a JIRA for that ? >> > No not yet. I will create one. Do you want to implement this or >> should I >> > do it? >> > >> > >> >> On 3/7/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >>> Guillaume Nodet wrote: >> >>>> However, it might be possible to enhance the ComponentSupport >> >>>> or another class to support the correlation id automatically. >> >>>> This would make all lightweight components to support that. >> >>> We could extend ComponentSupport with methods to create the new >> >>> exchanges and this methods could put the correlation id automatically >> in >> >>> the new excahnge. So if you would use ComponentSupport to create the >> >>> exchange the correlationId will be propagated. The advantage is that >> you >> >>> don't have to use this functions and it would be backward compatible. >> >>> >> >>> What do you think? >> >>> >> >>> >> >>>> On 1/23/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: >> >>>>> I don't think so, as the container (or the ecxhange factory) has no >> >>> way >> >>>>> to know which jbi exchange is currently handled by the component. >> >>>>> And you can not use a thread local, has the component may delegate >> >>>>> the exhcange processing to another thread. >> >>>>> That's the reason why it has been implemented in servicemix-common. >> >>>>> Do you see something else ? >> >>>>> >> >>>>> On 1/23/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >>>>>> A question again. If I have a lw component which opens a new >> message >> >>>>>> exchange the correlation id has to be propageted in the component >> >>>>>> itself. Would it be better or is it possible to do this >> automaticaly >> >>> in >> >>>>>> the exchange factory? >> >>>>>> >> >>>>>> Cheers, >> >>>>>> Thomas >> >>>>>> >> >>>>>> Guillaume Nodet wrote: >> >>>>>>> The way it works now is that >> >>>>>>> all components using servicemix-common that create an exchange >> >>>>>>> as part of the processing of a received exchange, will >> >>> automatically >> >>>>>>> put the correlationId in the new exchange properties. >> >>>>>>> The correlationId is equal to correlationId of the input >> exchange, >> >>>>> or the >> >>>>>>> input exchange id if no correlation id is set. >> >>>>>>> >> >>>>>>> So if an endpoint A sends a JBI exchange to enpoint B, and >> >>> endpoint >> >>> B >> >>>>>>> sends a jbi exchange to endpoint C while processing the exchange, >> >>>>>>> both exchange
Re: correlation id with tracing
Guillaume, I extended component support so that we have the four methods with the MessageExchange parameter to get and set the correlation id. public InOnly createInOnlyExchange(MessageExchange beforeExchange) public InOptionalOut createInOptionalOutExchange(MessageExchange beforeExchange) public InOut createInOutExchange(MessageExchange beforeExchange) public RobustInOnly createRobustInOnlyExchange(MessageExchange beforeExchange) this are the corresponding methods to the four methods without parameters to create a new excahnge. Do you want to create corresponding methods to the other methods like public InOut createInOutExchange(QName service, QName interfaceName, QName operation) Cheers, Thomas Thomas TERMIN wrote: >> Is there a JIRA for that ? > No not yet. I will create one. Do you want to implement this or should I > do it? > > >> On 3/7/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >>> Guillaume Nodet wrote: >>>> However, it might be possible to enhance the ComponentSupport >>>> or another class to support the correlation id automatically. >>>> This would make all lightweight components to support that. >>> We could extend ComponentSupport with methods to create the new >>> exchanges and this methods could put the correlation id automatically in >>> the new excahnge. So if you would use ComponentSupport to create the >>> exchange the correlationId will be propagated. The advantage is that you >>> don't have to use this functions and it would be backward compatible. >>> >>> What do you think? >>> >>> >>>> On 1/23/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: >>>>> I don't think so, as the container (or the ecxhange factory) has no >>> way >>>>> to know which jbi exchange is currently handled by the component. >>>>> And you can not use a thread local, has the component may delegate >>>>> the exhcange processing to another thread. >>>>> That's the reason why it has been implemented in servicemix-common. >>>>> Do you see something else ? >>>>> >>>>> On 1/23/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >>>>>> A question again. If I have a lw component which opens a new message >>>>>> exchange the correlation id has to be propageted in the component >>>>>> itself. Would it be better or is it possible to do this automaticaly >>> in >>>>>> the exchange factory? >>>>>> >>>>>> Cheers, >>>>>> Thomas >>>>>> >>>>>> Guillaume Nodet wrote: >>>>>>> The way it works now is that >>>>>>> all components using servicemix-common that create an exchange >>>>>>> as part of the processing of a received exchange, will >>> automatically >>>>>>> put the correlationId in the new exchange properties. >>>>>>> The correlationId is equal to correlationId of the input exchange, >>>>> or the >>>>>>> input exchange id if no correlation id is set. >>>>>>> >>>>>>> So if an endpoint A sends a JBI exchange to enpoint B, and >>> endpoint >>> B >>>>>>> sends a jbi exchange to endpoint C while processing the exchange, >>>>>>> both exchange will have the same correlationId. >>>>>>> >>>>>>> If we write a MessageExchange event listener, we should be able to >>>>>>> retrieve all these informations. Note that the flow can be >>> retrieved >>>>>>> with the same logic used in the DotViewFlowListener instead. >>>>>>> >>>>>>> Just copy the DotViewFlowListener and change the drawing >>>>>>> logic. What tool are will you use to draw the flow ? The output >>>>>>> of the DotViewFlowListener is not very impressive, so any >>>>>>> improvement would be welcome. >>>>>>> >>>>>>> On 1/10/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >>>>>>>> How is this intended to work? I want to implement a tracing tool >>> or >>>>>>>> whatever to see the flows between the components. >>>>>>>> >>>>>>>> Cheers >>>>>>>> >>>>>>>> Guillaume Nodet wrote: >>>>>>>>> No one leverage the correlation ids, but i it co
Re: eip filter extension
Guillaume Nodet wrote:
> Yeah, it should work. Even if not embedded in servicemix,
> though I would prefer to avoid hard dependencies on internal
> classes. The other solution is to do it with reflection, as done
> in AsyncBaseLifeCycle#findExecutorFactory
>
> If you can try to hide this hideous cast in a common parent class,
> that would be fine ;-)
So I did the complete stuff with reflection. It would be nice if you
would have a look at the code.
>
> On 3/15/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote:
>>
>> Guillaume,
>>
>> can I do this?
>>
>> if (isComponentContextImpl(getContext().getMBeanNames()))
>> {
>> ComponentContextImpl contextImpl
>> =(ComponentContextImpl)getContext().getMBeanNames();
>> }
>>
>> or is it to dirty? I would have all information then. ;-)
>>
>> Guillaume Nodet wrote:
>> > Well, i think it will be difficult without accessing
>> > ServiceMix internals.
>> > Or maybe tweaking with the mbean names factory
>> > available on the component context ? I don't recall what it gives ...
>> >
>> > On 3/14/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Guillaume Nodet wrote:
>> >> > Yeah, sounds good.
>> >> > Make sure you use the facilities available on
>> >> > the ComponentContext to create the mbean names ...
>> >> Do you have special vision there? What I thought is to have it under
>> the
>> >> Type=Endpoint,SubType=Internal or External. But it seems not so easy.
>> >> > If the mbean name for this interface could be related
>> >> > to the endpoint name, that would make it easier to find.
>> >>
>> >> >
>> >> > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]> wrote:
>> >> >>
>> >> >> Guillaume Nodet wrote:
>> >> >> > I mean, did you already implement the JMX part ?
>> >> >> > Which interface are you exposing to JMX ?
>> >> >> > Anyway, you should raise a JIRA ...
>> >> >> I didn't implemtet it up to now. But what I want to do is expose an
>> >> >> SwitchPredicateMBean interface where you can change some
>> properties.
>> >> >> What do you think. This could also be done for the XpathPredicate
>> and
>> >> so
>> >> >> on. I have implemented the SwitchPredicate and doing tests at the
>> >> moment.
>> >> >>
>> >> >> >
>> >> >> > On 3/13/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote:
>> >> >> >>
>> >> >> >> Yes of course should also be changeable via JMX.
>> >> >> >>
>> >> >> >> Guillaume Nodet wrote:
>> >> >> >> > Well, it sounds good.
>> >> >> >> > What about the JMX stuff ?
>> >> >> >> >
>> >> >> >> > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]>
>> wrote:
>> >> >> >> >>
>> >> >> >> >> Guillaume Nodet wrote:
>> >> >> >> >> > On 3/12/07, Thomas TERMIN <[EMAIL PROTECTED] >
>> >> wrote:
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> Peter my colleague asked if you need a switch-filter as an
>> >> EIP
>> >> >> >> >> >> > component. It does nothing more then check a property
>> for
>> >> >> message
>> >> >> >> >> flow.
>> >> >> >> >> >> > If this property is true it sends the message to the
>> >> >> destination
>> >> >> >> and
>> >> >> >> >> if
>> >> >> >> >> >> > it is false the exchange will be discarde. This is
>> helpfull
>> >> if
>> >> >> >> you
>> >> >> >> >> have
>> >> >> >> >> >> > different installations where some services are
>> >> installed or
>> >> >> not
>> >> >> >> >> >> > installed in servicemix. What he want to do is that you
>> can
>> >> >> >> >> enable or
>> >> >> >> >> >> > disbale the f
Re: eip filter extension
Guillaume Nodet wrote: > Yeah, sounds good. > Make sure you use the facilities available on > the ComponentContext to create the mbean names ... Do you have special vision there? What I thought is to have it under the Type=Endpoint,SubType=Internal or External. But it seems not so easy. > If the mbean name for this interface could be related > to the endpoint name, that would make it easier to find. > > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]> wrote: >> >> Guillaume Nodet wrote: >> > I mean, did you already implement the JMX part ? >> > Which interface are you exposing to JMX ? >> > Anyway, you should raise a JIRA ... >> I didn't implemtet it up to now. But what I want to do is expose an >> SwitchPredicateMBean interface where you can change some properties. >> What do you think. This could also be done for the XpathPredicate and so >> on. I have implemented the SwitchPredicate and doing tests at the moment. >> >> > >> > On 3/13/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> >> >> Yes of course should also be changeable via JMX. >> >> >> >> Guillaume Nodet wrote: >> >> > Well, it sounds good. >> >> > What about the JMX stuff ? >> >> > >> >> > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Guillaume Nodet wrote: >> >> >> > On 3/12/07, Thomas TERMIN <[EMAIL PROTECTED] > wrote: >> >> >> >> >> >> >> >> >> >> >> >> Peter my colleague asked if you need a switch-filter as an EIP >> >> >> >> > component. It does nothing more then check a property for >> message >> >> >> flow. >> >> >> >> > If this property is true it sends the message to the >> destination >> >> and >> >> >> if >> >> >> >> > it is false the exchange will be discarde. This is helpfull if >> >> you >> >> >> have >> >> >> >> > different installations where some services are installed or >> not >> >> >> >> > installed in servicemix. What he want to do is that you can >> >> >> enable or >> >> >> >> > disbale the flow via JMX as well as an property in a property >> >> >> file at >> >> >> >> > runtime. (Hope the explanation was understandable) >> >> >> >> >> >> >> >> >> >> >> >> Sounds good, but I wonder wha's the difference with the >> >> >> >> >> >> >> >> >> >> http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter >> >> >> >> >> >> >> >> >> >> >> >> >> >> . >> >> >> >> We only need to implement a new predicate based on properties, >> >> which >> >> >> >> could >> >> >> >> be >> >> >> >> reused by the router for example. I'm not sure if this is what >> you >> >> >> meant >> >> >> >> or not >> >> >> >> (maybe you were talking about a system property ?) >> >> >> >> As for the JMX stuff, it's a very good idea. >> >> >> >> >> >> >> >> >> >> >> >> I'm still not sure if you were talking about a property on the >> JBI >> >> >> > exchange >> >> >> > or a system property. There's no predicate on message properties >> it >> >> >> > could be implemented easily (and should anyway). As I said, JMX >> >> >> controlled >> >> >> > routers or filters would be very useful for manually re-routing >> >> flows, >> >> >> etc >> >> >> This filter is intended just as a on/off filter. >> >> >> >> >> >> >> >> >> > >> >> propertyResource="file:conf/feature.properties" propertyName="on"/> >> >> >> >> >> >> >> >> >> So as you can see above there is a spring resourece defined and a >> >> >> property name. This property name will be read from the resource >> and >> >> >&g
Re: RE : servicemix.properties
Guillaume Nodet wrote:
> This property is used to configure the
> org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean
> so I gess this class could be improved to trim the url before
> using it.
> Thomas, you can fix it, once your account is activated.
Ok. That's what I mean. ;-)
>
> On 3/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hello,
>>
>> Spring framework reads this file to provide all
>> properties into servicemix.xml file
>> please see @servicemix.xml:
>> > class="
>> org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>> > value="classpath:servicemix.properties" />
>>
>>
>> You can use all properties from servicemix.properties
>> in your servicemix.xml file. For example
>> ${activemq.url} property.
>>
>> i hope it is could help you.
>>
>> Cordialement,
>>
>>
>> --- Thomas TERMIN <[EMAIL PROTECTED]> a
>> écrit :
>>
>> > Which class is reading the servicemix.properties
>> > file? If you have some
>> > spaces after a property the jmx.url is then also
>> > with spaces and that
>> > doesn't work.
>> >
>> >
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>>
>> Découvrez une nouvelle façon d'obtenir des réponses à toutes vos
>> questions
>> !
>> Profitez des connaissances, des opinions et des expériences des
>> internautes sur Yahoo! Questions/Réponses
>> http://fr.answers.yahoo.com
>>
>
>
>
--
Thomas Termin
___
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel: (+49) 0711 - 45 10 17 676
Fax: (+49) 0711 - 45 10 17 573
WWW: http://www.blue-elephant-systems.com
Email : [EMAIL PROTECTED]
blue elephant systems GmbH
Firmensitz : Wollgrasweg 49, D-70599 Stuttgart
Registergericht : Amtsgericht Stuttgart, HRB 24106
Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
servicemix.properties
Which class is reading the servicemix.properties file? If you have some spaces after a property the jmx.url is then also with spaces and that doesn't work.
Re: eip filter extension
Guillaume Nodet wrote: > I mean, did you already implement the JMX part ? > Which interface are you exposing to JMX ? > Anyway, you should raise a JIRA ... I didn't implemtet it up to now. But what I want to do is expose an SwitchPredicateMBean interface where you can change some properties. What do you think. This could also be done for the XpathPredicate and so on. I have implemented the SwitchPredicate and doing tests at the moment. > > On 3/13/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> Yes of course should also be changeable via JMX. >> >> Guillaume Nodet wrote: >> > Well, it sounds good. >> > What about the JMX stuff ? >> > >> > On 3/13/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> >> >> Guillaume Nodet wrote: >> >> > On 3/12/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> >> >> >> Peter my colleague asked if you need a switch-filter as an EIP >> >> >> > component. It does nothing more then check a property for message >> >> flow. >> >> >> > If this property is true it sends the message to the destination >> and >> >> if >> >> >> > it is false the exchange will be discarde. This is helpfull if >> you >> >> have >> >> >> > different installations where some services are installed or not >> >> >> > installed in servicemix. What he want to do is that you can >> >> enable or >> >> >> > disbale the flow via JMX as well as an property in a property >> >> file at >> >> >> > runtime. (Hope the explanation was understandable) >> >> >> >> >> >> >> >> >> Sounds good, but I wonder wha's the difference with the >> >> >> >> >> >> http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter >> >> >> >> >> >> >> >> >> . >> >> >> We only need to implement a new predicate based on properties, >> which >> >> >> could >> >> >> be >> >> >> reused by the router for example. I'm not sure if this is what you >> >> meant >> >> >> or not >> >> >> (maybe you were talking about a system property ?) >> >> >> As for the JMX stuff, it's a very good idea. >> >> >> >> >> >> >> >> >> I'm still not sure if you were talking about a property on the JBI >> >> > exchange >> >> > or a system property. There's no predicate on message properties it >> >> > could be implemented easily (and should anyway). As I said, JMX >> >> controlled >> >> > routers or filters would be very useful for manually re-routing >> flows, >> >> etc >> >> This filter is intended just as a on/off filter. >> >> >> >> >> >> > >> propertyResource="file:conf/feature.properties" propertyName="on"/> >> >> >> >> >> >> So as you can see above there is a spring resourece defined and a >> >> property name. This property name will be read from the resource and >> can >> >> have the value true(on) or false(off). The property could also be an >> >> exchange property. The configuration would be: >> >> >> >> >> >> >> >> >> >> >> >> >> >> We implemented this just as a SwitchPredicate which just returns true >> or >> >> false depending on the property. >> >> >> >> >> >> >> > >> > >> >> >> -- >> Thomas Termin >> ___ >> blue elephant systems GmbH >> Wollgrasweg 49 >> D-70599 Stuttgart >> >> Tel: (+49) 0711 - 45 10 17 676 >> Fax: (+49) 0711 - 45 10 17 573 >> WWW: http://www.blue-elephant-systems.com >> Email : [EMAIL PROTECTED] >> >> blue elephant systems GmbH >> Firmensitz : Wollgrasweg 49, D-70599 Stuttgart >> Registergericht : Amtsgericht Stuttgart, HRB 24106 >> Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle >> >> > > -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: eip filter extension
Yes of course should also be changeable via JMX. Guillaume Nodet wrote: > Well, it sounds good. > What about the JMX stuff ? > > On 3/13/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> Guillaume Nodet wrote: >> > On 3/12/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Peter my colleague asked if you need a switch-filter as an EIP >> >> > component. It does nothing more then check a property for message >> flow. >> >> > If this property is true it sends the message to the destination and >> if >> >> > it is false the exchange will be discarde. This is helpfull if you >> have >> >> > different installations where some services are installed or not >> >> > installed in servicemix. What he want to do is that you can >> enable or >> >> > disbale the flow via JMX as well as an property in a property >> file at >> >> > runtime. (Hope the explanation was understandable) >> >> >> >> >> >> Sounds good, but I wonder wha's the difference with the >> >> >> http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter >> >> >> >> >> . >> >> We only need to implement a new predicate based on properties, which >> >> could >> >> be >> >> reused by the router for example. I'm not sure if this is what you >> meant >> >> or not >> >> (maybe you were talking about a system property ?) >> >> As for the JMX stuff, it's a very good idea. >> >> >> >> >> >> I'm still not sure if you were talking about a property on the JBI >> > exchange >> > or a system property. There's no predicate on message properties it >> > could be implemented easily (and should anyway). As I said, JMX >> controlled >> > routers or filters would be very useful for manually re-routing flows, >> etc >> This filter is intended just as a on/off filter. >> >> >> > propertyResource="file:conf/feature.properties" propertyName="on"/> >> >> >> So as you can see above there is a spring resourece defined and a >> property name. This property name will be read from the resource and can >> have the value true(on) or false(off). The property could also be an >> exchange property. The configuration would be: >> >> >> >> >> >> >> We implemented this just as a SwitchPredicate which just returns true or >> false depending on the property. >> >> >> > > -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: eip filter extension
Guillaume Nodet wrote: > On 3/12/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> >> Peter my colleague asked if you need a switch-filter as an EIP >> > component. It does nothing more then check a property for message flow. >> > If this property is true it sends the message to the destination and if >> > it is false the exchange will be discarde. This is helpfull if you have >> > different installations where some services are installed or not >> > installed in servicemix. What he want to do is that you can enable or >> > disbale the flow via JMX as well as an property in a property file at >> > runtime. (Hope the explanation was understandable) >> >> >> Sounds good, but I wonder wha's the difference with the >> http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter >> >> . >> We only need to implement a new predicate based on properties, which >> could >> be >> reused by the router for example. I'm not sure if this is what you meant >> or not >> (maybe you were talking about a system property ?) >> As for the JMX stuff, it's a very good idea. >> >> >> I'm still not sure if you were talking about a property on the JBI > exchange > or a system property. There's no predicate on message properties it > could be implemented easily (and should anyway). As I said, JMX controlled > routers or filters would be very useful for manually re-routing flows, etc This filter is intended just as a on/off filter. So as you can see above there is a spring resourece defined and a property name. This property name will be read from the resource and can have the value true(on) or false(off). The property could also be an exchange property. The configuration would be: We implemented this just as a SwitchPredicate which just returns true or false depending on the property.
[jira] Created: (SM-876) jmx.xml should use the jmx.url property
jmx.xml should use the jmx.url property --- Key: SM-876 URL: https://issues.apache.org/activemq/browse/SM-876 Project: ServiceMix Issue Type: Improvement Reporter: Thomas Termin Priority: Trivial Attachments: patch.jmx.xml Just a small patch. ;-) The jmx.xml should specify the jmx.url from servicemix.properties. Furthermore the hostname should be configurable. (Very nice for us) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] [PROPOSAL] Coding standards
Is there also an code formatting setup for idea available? Would be nice. Juergen Mayrbaeurl wrote: > OK for me. Can anyone provide an Eclipse code formatting setup? > > Kind regards > Juergen > > > gnodet wrote: >> I propose the following coding standards (taken from the Geronimo web >> site) >> which are actually the most common in ServiceMix code base: >> >> http://cwiki.apache.org/SM/coding-standards.html >> >> Does anyone want to modify / add / change something ? >> >> -- >> Cheers, >> Guillaume Nodet >> >> Architect, LogicBlaze (http://www.logicblaze.com/) >> Blog: http://gnodet.blogspot.com/ >> >> > -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Created: (SM-746) JettyContextManager does not set the truststore parameters for unmanaged ssl endpoints
JettyContextManager does not set the truststore parameters for unmanaged ssl endpoints -- Key: SM-746 URL: https://issues.apache.org/activemq/browse/SM-746 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0, 3.0-M2, 3.0-M1, 3.0.1, 3.1, incubation Reporter: Thomas Termin Priority: Minor Attachments: jettyContextManager-Patch The sslParamters for the truststore environment are ignored in the JettyContextManager. If you use an unmanaged ssl consumer endpoint the values for the truststore are not set. The result is that the jre truststore is always used which is problematical for selfsigned certificates! You could set the java system properties in servicemix but that is not really a solution! -- 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-714) component.properties in conf directory
component.properties in conf directory -- Key: SM-714 URL: https://issues.apache.org/activemq/browse/SM-714 Project: ServiceMix Issue Type: Improvement Components: servicemix-http Reporter: Thomas Termin Attachments: component.properties, patch.txt There should be support for an initial component.properties file in the servicemix/conf directory. I added support for that (see the patch). The file in the conf directory will be loaded if no property file is in the workspace directory (I implemented that just for the servicemix-http component). If you change properties via JMX the changes will be saved in the workspace directory. The file in the conf directory has then still the original values. I added also a component.properties file. -- 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
