[jira] Updated: (SM-679) Create a servicemix-ehcache standard JBI component
[ https://issues.apache.org/activemq/browse/SM-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Puro updated SM-679: - Attachment: servicemix-ehcache.patch Please take a glance at this patch. There's still a bunch more coding that needs to be done in order to enable endpoint configuration of ehcache on the fly. Create a servicemix-ehcache standard JBI component -- Key: SM-679 URL: https://issues.apache.org/activemq/browse/SM-679 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Affects Versions: 3.0 Reporter: Jeff Puro Assigned To: Jeff Puro Priority: Minor Fix For: 3.2 Attachments: servicemix-ehcache.patch Add a servicemix-ehcache standard JBI component. Please see the following forum thread for more information on how this component should work. http://www.nabble.com/Ehcache-Standard-JBI-Component-tf2747953s12049.html#a7666554 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-679) Create a servicemix-ehcache standard JBI component
[ https://issues.apache.org/activemq/browse/SM-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Puro updated SM-679: - Attachment: (was: servicemix-ehcache.patch) Create a servicemix-ehcache standard JBI component -- Key: SM-679 URL: https://issues.apache.org/activemq/browse/SM-679 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Affects Versions: 3.0 Reporter: Jeff Puro Assigned To: Jeff Puro Priority: Minor Fix For: 3.2 Attachments: servicemix-ehcache.patch Add a servicemix-ehcache standard JBI component. Please see the following forum thread for more information on how this component should work. http://www.nabble.com/Ehcache-Standard-JBI-Component-tf2747953s12049.html#a7666554 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-679) Create a servicemix-ehcache standard JBI component
[ https://issues.apache.org/activemq/browse/SM-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38981 ] Jeff Puro commented on SM-679: -- Please review the attached patch. There is still a bit of work that needs to be done, but I'd like to get initial feedback. Create a servicemix-ehcache standard JBI component -- Key: SM-679 URL: https://issues.apache.org/activemq/browse/SM-679 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Affects Versions: 3.0 Reporter: Jeff Puro Assigned To: Jeff Puro Priority: Minor Fix For: 3.2 Attachments: servicemix-ehcache.patch Add a servicemix-ehcache standard JBI component. Please see the following forum thread for more information on how this component should work. http://www.nabble.com/Ehcache-Standard-JBI-Component-tf2747953s12049.html#a7666554 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-926) Add a standard JBI component for Velocity templates
Add a standard JBI component for Velocity templates --- Key: SM-926 URL: https://issues.apache.org/activemq/browse/SM-926 Project: ServiceMix Issue Type: New Feature Reporter: Jeff Puro Assigned To: Jeff Puro Priority: Minor Fix For: 3.2 I think it would be useful for ServiceMix to provide a velocity template service engine. This would serve as an alternative to using XSLT to tranform messages and could be particularly useful when creating the content of an email message etc. The way it would work, in conjunction with JDOM, is that a normalized message would be sent to the component that would inject the properties and the content of the message into the Velocity context. You can then use Velocity's syntax for generating XML documents or any content that has CDATA tags around it. The properties of the normalized message would be accessed via the $properties variable, whereas the content of the message would be accessed via either a $content or $root variable using JDOM methods. Since it is often nice to have Velocity templates pulled from sources other than a .vm file (for example a database), it would be useful for the velocity:endpoint/ to have a pluggable resource property where the resource could be pulled from either the filesystem, a database, etc... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-841) The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section.
[ https://issues.apache.org/activemq/browse/SM-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Puro updated SM-841: - Attachment: servicemix-soap-fault-3.1.patch This patch can be specifically used against 3.1 of servicemix, although there aren't all that many differences so we may not need this. I have also included a junit test in this patch version. The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section. Key: SM-841 URL: https://issues.apache.org/activemq/browse/SM-841 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.0.1, 3.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.1.1, 3.2 Attachments: servicemix-soap-fault-3.1.patch, servicemix-soap-fault.patch Original Estimate: 2 hours Remaining Estimate: 2 hours The servicemix-http provider endpoint fails when a web service it calls returns a fault with multiple child elements in the detail section. The solution to this is when there are multiple elements, we should wrap them all in a root element so they get properly passed back as a fault. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-679) Create a servicemix-ehcache standard JBI component
[ https://issues.apache.org/activemq/browse/SM-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Puro updated SM-679: - Description: Add a servicemix-ehcache standard JBI component. Please see the following forum thread for more information on how this component should work. http://www.nabble.com/Ehcache-Standard-JBI-Component-tf2747953s12049.html#a7666554 was:Add support for ehcache using a Map. Put example of how to set this up in Wiki. Summary: Create a servicemix-ehcache standard JBI component (was: Add map support for Ehcache) Create a servicemix-ehcache standard JBI component -- Key: SM-679 URL: https://issues.apache.org/activemq/browse/SM-679 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Affects Versions: 3.0 Reporter: Jeff Puro Assigned To: Jeff Puro Priority: Minor Fix For: 3.2 Add a servicemix-ehcache standard JBI component. Please see the following forum thread for more information on how this component should work. http://www.nabble.com/Ehcache-Standard-JBI-Component-tf2747953s12049.html#a7666554 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-841) The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section.
[ https://issues.apache.org/activemq/browse/SM-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Puro updated SM-841: - Attachment: servicemix-soap-fault.patch I have attached a patch file that affects the servicemix-soap module. The way the fix works is that it determines if multiple elements have been returned in the Details section of the soap fault, if so, then it goes ahead and wraps a parent element around the multiple elements. Here are some notes to keep in mind: 1) We may want to change the name of the parent element to be more unique so that it doesn't conflict with other elements that may be part of the actual fault details. 2) Perhaps adding a boolean onto the http endpoints to turn this on or off is a good idea. I'm not 100% on this mostly because servicemix should properly handle multiple elements by default since the SOAP spec seems to indicate that this is a valid fault. 3) Because of the way the wrapping and unwrapping of the fault's content work, while the fault is traveling within the servicemix nmr to different endpoints, they will see the fault content with the parent tag wrapped around the main detail elements. This may be undesirable and may indicate that either we need a more specific name for the parent element or that we need to make this behavior optional. I'm not 100% on how to best handle this. 4) The code may be refactored more to improve performance of the wrapping and unwrapping of the parent element. The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section. Key: SM-841 URL: https://issues.apache.org/activemq/browse/SM-841 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.0.1, 3.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1, 3.1.1 Attachments: servicemix-soap-fault.patch Original Estimate: 2 hours Remaining Estimate: 2 hours The servicemix-http provider endpoint fails when a web service it calls returns a fault with multiple child elements in the detail section. The solution to this is when there are multiple elements, we should wrap them all in a root element so they get properly passed back as a fault. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-841) The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section.
[ https://issues.apache.org/activemq/browse/SM-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38737 ] Jeff Puro commented on SM-841: -- Before applying this patch, let's make sure that this definately doesn't go against the SOAP 1.1 or SOAP 1.2 spec. Perhaps the web services that I've been calling are improperly setting the details section. The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section. Key: SM-841 URL: https://issues.apache.org/activemq/browse/SM-841 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.0.1, 3.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1, 3.1.1 Attachments: servicemix-soap-fault.patch Original Estimate: 2 hours Remaining Estimate: 2 hours The servicemix-http provider endpoint fails when a web service it calls returns a fault with multiple child elements in the detail section. The solution to this is when there are multiple elements, we should wrap them all in a root element so they get properly passed back as a fault. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-841) The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section.
[ https://issues.apache.org/activemq/browse/SM-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38647 ] Jeff Puro commented on SM-841: -- Yes, this is still an issue. I have a potential fix for it, so I need to attach the patch files to this defect. Will do so in the next day or so. The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section. Key: SM-841 URL: https://issues.apache.org/activemq/browse/SM-841 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.0.1, 3.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1, 3.1.1 Original Estimate: 2 hours Remaining Estimate: 2 hours The servicemix-http provider endpoint fails when a web service it calls returns a fault with multiple child elements in the detail section. The solution to this is when there are multiple elements, we should wrap them all in a root element so they get properly passed back as a fault. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-841) The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section.
The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section. Key: SM-841 URL: https://issues.apache.org/activemq/browse/SM-841 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.1, 3.0.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.1.1, 3.0.1 The servicemix-http provider endpoint fails when a web service it calls returns a fault with multiple child elements in the detail section. The solution to this is when there are multiple elements, we should wrap them all in a root element so they get properly passed back as a fault. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-762) Address in WSDL is incorrectly adding the protocol information in the begining of the URL
[ https://issues.apache.org/activemq/browse/SM-762?page=all ] Jeff Puro resolved SM-762. -- Resolution: Fixed Please see notes on attached patches. Address in WSDL is incorrectly adding the protocol information in the begining of the URL - Key: SM-762 URL: https://issues.apache.org/activemq/browse/SM-762 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1 Attachments: servicemix-http-host-port-is-secure.patch, servicemix-http-host-port-scheme.patch Original Estimate: 30 minutes Remaining Estimate: 30 minutes Here is an example of the error when generating the WSDL: service name=HttpService port binding=tns:nullBinding wsdlsoap:address location=HTTP/1.1://10.0.102.12:8080/servicemix-web/jbi/tracker// /port /service -- 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] Reopened: (SM-762) Address in WSDL is incorrectly adding the protocol information in the begining of the URL
[ https://issues.apache.org/activemq/browse/SM-762?page=all ] Jeff Puro reopened SM-762: -- Address in WSDL is incorrectly adding the protocol information in the begining of the URL - Key: SM-762 URL: https://issues.apache.org/activemq/browse/SM-762 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1 Attachments: servicemix-http-host-port-is-secure.patch, servicemix-http-host-port-scheme.patch Original Estimate: 30 minutes Remaining Estimate: 30 minutes Here is an example of the error when generating the WSDL: service name=HttpService port binding=tns:nullBinding wsdlsoap:address location=HTTP/1.1://10.0.102.12:8080/servicemix-web/jbi/tracker// /port /service -- 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-771) ServiceMix-Http component has its ConnectionManager shutdown when installed under the servicemix-web module (managed mode)
ServiceMix-Http component has its ConnectionManager shutdown when installed under the servicemix-web module (managed mode) -- Key: SM-771 URL: https://issues.apache.org/activemq/browse/SM-771 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1, 3.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.1, 3.0.1 When using an HTTP provider endpoint while the service unit is deployed using the apache servicemix web project (that is using managed mode), it generates the following Exception. java.lang.IllegalStateException: Connection factory has been shutdown. at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:454) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.java:407) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:152) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:153) at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:410) at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:43) at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:624) at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170) at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:177) at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:227) at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:595) -- 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-771) An IllegalStateException is generated when using an http provider endpoint when it is deployed using the Servicemix Web war (managed mode).
[ https://issues.apache.org/activemq/browse/SM-771?page=all ] Jeff Puro updated SM-771: - Summary: An IllegalStateException is generated when using an http provider endpoint when it is deployed using the Servicemix Web war (managed mode). (was: ServiceMix-Http component has its ConnectionManager shutdown when installed under the servicemix-web module (managed mode)) An IllegalStateException is generated when using an http provider endpoint when it is deployed using the Servicemix Web war (managed mode). --- Key: SM-771 URL: https://issues.apache.org/activemq/browse/SM-771 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1, 3.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1, 3.1 Original Estimate: 1 hour Remaining Estimate: 1 hour When using an HTTP provider endpoint while the service unit is deployed using the apache servicemix web project (that is using managed mode), it generates the following Exception. java.lang.IllegalStateException: Connection factory has been shutdown. at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:454) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.java:407) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:152) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:153) at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:410) at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:43) at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:624) at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170) at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:177) at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:227) at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:595) -- 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-771) An IllegalStateException is generated when using an http provider endpoint when it is deployed using the Servicemix Web war (managed mode).
[ https://issues.apache.org/activemq/browse/SM-771?page=all ] Jeff Puro updated SM-771: - Attachment: servicemix-http-connection-manager-3.0.1.patch The attached file is a patch for ServiceMix 3.0.1. This solves the issue by setting the connectionManager and client object references to null so that when doInit is executed again it reinitializes the connectionManager. There will be a subsequent patch file for 3.1. An IllegalStateException is generated when using an http provider endpoint when it is deployed using the Servicemix Web war (managed mode). --- Key: SM-771 URL: https://issues.apache.org/activemq/browse/SM-771 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1, 3.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1, 3.1 Attachments: servicemix-http-connection-manager-3.0.1.patch Original Estimate: 1 hour Remaining Estimate: 1 hour When using an HTTP provider endpoint while the service unit is deployed using the apache servicemix web project (that is using managed mode), it generates the following Exception. java.lang.IllegalStateException: Connection factory has been shutdown. at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:454) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.java:407) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:152) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:153) at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:410) at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:43) at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:624) at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170) at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:177) at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:227) at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:595) -- 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] Assigned: (SM-762) Address in WSDL is incorrectly adding the protocol information in the begining of the URL
[ https://issues.apache.org/activemq/browse/SM-762?page=all ] Jeff Puro reassigned SM-762: Assignee: Jeff Puro Address in WSDL is incorrectly adding the protocol information in the begining of the URL - Key: SM-762 URL: https://issues.apache.org/activemq/browse/SM-762 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1 Original Estimate: 30 minutes Remaining Estimate: 30 minutes Here is an example of the error when generating the WSDL: service name=HttpService port binding=tns:nullBinding wsdlsoap:address location=HTTP/1.1://10.0.102.12:8080/servicemix-web/jbi/tracker// /port /service -- 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] Work started: (SM-762) Address in WSDL is incorrectly adding the protocol information in the begining of the URL
[ https://issues.apache.org/activemq/browse/SM-762?page=all ] Work on SM-762 started by Jeff Puro. Address in WSDL is incorrectly adding the protocol information in the begining of the URL - Key: SM-762 URL: https://issues.apache.org/activemq/browse/SM-762 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1 Original Estimate: 30 minutes Remaining Estimate: 30 minutes Here is an example of the error when generating the WSDL: service name=HttpService port binding=tns:nullBinding wsdlsoap:address location=HTTP/1.1://10.0.102.12:8080/servicemix-web/jbi/tracker// /port /service -- 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-762) Address in WSDL is incorrectly adding the protocol information in the begining of the URL
[ https://issues.apache.org/activemq/browse/SM-762?page=all ] Jeff Puro updated SM-762: - Attachment: servicemix-http-host-port-scheme.patch This patch uses the request.getScheme() method to determine the protocol. I have attached an alternative that uses request.isSecure() since that is used elsewhere in the servicemix-http component. Either one should work. Address in WSDL is incorrectly adding the protocol information in the begining of the URL - Key: SM-762 URL: https://issues.apache.org/activemq/browse/SM-762 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1 Attachments: servicemix-http-host-port-is-secure.patch, servicemix-http-host-port-scheme.patch Original Estimate: 30 minutes Remaining Estimate: 30 minutes Here is an example of the error when generating the WSDL: service name=HttpService port binding=tns:nullBinding wsdlsoap:address location=HTTP/1.1://10.0.102.12:8080/servicemix-web/jbi/tracker// /port /service -- 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-762) Address in WSDL is incorrectly adding the protocol information in the begining of the URL
[ https://issues.apache.org/activemq/browse/SM-762?page=all ] Jeff Puro updated SM-762: - Attachment: servicemix-http-host-port-is-secure.patch The attached patch uses the isSecure() method to determine the protocol (http or https) as used in other places in servicemix-http. Address in WSDL is incorrectly adding the protocol information in the begining of the URL - Key: SM-762 URL: https://issues.apache.org/activemq/browse/SM-762 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1 Attachments: servicemix-http-host-port-is-secure.patch, servicemix-http-host-port-scheme.patch Original Estimate: 30 minutes Remaining Estimate: 30 minutes Here is an example of the error when generating the WSDL: service name=HttpService port binding=tns:nullBinding wsdlsoap:address location=HTTP/1.1://10.0.102.12:8080/servicemix-web/jbi/tracker// /port /service -- 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-762) Address in WSDL is incorrectly adding the protocol information in the begining of the URL
[ https://issues.apache.org/activemq/browse/SM-762?page=comments#action_37640 ] Jeff Puro commented on SM-762: -- I have attached two different patches. Either one will resolve the issue. It is up to the commiter to decide which to use: 1) The first one uses the request.getScheme() method to determine the protocol. 2) The second one uses the isSecure() method to determine the protocol (http or https) as used in other places in servicemix-http. Address in WSDL is incorrectly adding the protocol information in the begining of the URL - Key: SM-762 URL: https://issues.apache.org/activemq/browse/SM-762 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1 Attachments: servicemix-http-host-port-is-secure.patch, servicemix-http-host-port-scheme.patch Original Estimate: 30 minutes Remaining Estimate: 30 minutes Here is an example of the error when generating the WSDL: service name=HttpService port binding=tns:nullBinding wsdlsoap:address location=HTTP/1.1://10.0.102.12:8080/servicemix-web/jbi/tracker// /port /service -- 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-762) Address in WSDL is incorrectly adding the protocol information in the begining of the URL
Address in WSDL is incorrectly adding the protocol information in the begining of the URL - Key: SM-762 URL: https://issues.apache.org/activemq/browse/SM-762 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0.1 Reporter: Jeff Puro Fix For: 3.0.1 Here is an example of the error when generating the WSDL: service name=HttpService port binding=tns:nullBinding wsdlsoap:address location=HTTP/1.1://10.0.102.12:8080/servicemix-web/jbi/tracker// /port /service -- 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-679) Add map support for Ehcache
[ https://issues.apache.org/activemq/browse/SM-679?page=comments#action_37605 ] Jeff Puro commented on SM-679: -- Perhaps we should create this into a standard jbi component called servicemix-ehcache. This would probably be preferred because then you can have a service engine that manages all caches, is integrated with JMX etc... Add map support for Ehcache --- Key: SM-679 URL: https://issues.apache.org/activemq/browse/SM-679 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Affects Versions: 3.0 Reporter: Jeff Puro Assigned To: Jeff Puro Priority: Minor Fix For: 3.1 Add support for ehcache using a Map. Put example of how to set this up in Wiki. -- 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-604) Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs Key: SM-604 URL: https://issues.apache.org/activemq/browse/SM-604 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-jsr181 Affects Versions: 3.0 Reporter: Jeff Puro Fix For: 3.0.1 Currently when ServiceMix has an http endpoint that is running in managed mode and that endpoint has a target service of a jsr181 endpoint it generates WSDLs with a hardcoded value of localhost. However, it should determine the server, port, and context path of the web container that it is running under and use this information to generate the service element in the WSDL. -- 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-565) Enhance the JSR181 Proxy so that it can proxy non WSDL publishing components
Enhance the JSR181 Proxy so that it can proxy non WSDL publishing components Key: SM-565 URL: https://issues.apache.org/activemq/browse/SM-565 Project: ServiceMix Issue Type: Improvement Components: servicemix-jsr181 Affects Versions: 3.0-M2 Environment: All Reporter: Jeff Puro Fix For: 3.0-M3 It would be useful to be able to use the jsr181:proxy/ tag to create a pojo proxy around lightweight components. For example, being able to invoke a method on a pojo and have it proxied to a Drools component that is configured in ServiceMix. -- 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-435) VFS ftp writer makes a connection in the init() method, but this causes the component to stay connected throughout the lifetime of the ESB (instead of reconnecting each time)
VFS ftp writer makes a connection in the init() method, but this causes the component to stay connected throughout the lifetime of the ESB (instead of reconnecting each time) -- Key: SM-435 URL: https://issues.apache.org/activemq/browse/SM-435 Project: ServiceMix Type: Bug Components: servicemix-components Versions: 3.0 Reporter: Jeff Puro -- 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-384) In org.apache.servicemix.jbi.messaging.NormalizedMessageImpl, it appears that the getters and setters are innappropriately synchronized
In org.apache.servicemix.jbi.messaging.NormalizedMessageImpl, it appears that the getters and setters are innappropriately synchronized --- Key: SM-384 URL: https://issues.apache.org/activemq/browse/SM-384 Project: ServiceMix Type: Improvement Components: servicemix-core Versions: 3.0 Reporter: Jeff Puro It's possible that we do not need to synchronize the getters and setters of the NormalizedMessageImpl class. Removing these synchronizations should increase performance when manipulating messages. Whoever authored this class should be consulted as to the reasons behind doing this. Are we worried about multiple threads accessing the same normalized message? The only time I see this happening is if a component spawns multiple threads working on the same NormalizedMessage, but even in this case we could use a wrapper class that synchronizes the necessary methods. Perhaps there is something in the core library of servicemix that needs these synchronized? -- 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
