[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

[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

[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,

[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

[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,

[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

[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.

[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

[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

[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.

[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

[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

[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:

[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

[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

[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

[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 -

[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

[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

[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

[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

[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

[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

[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

[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)

[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