[jira] [Commented] (GERONIMO-4576) Make persistence exceptions more visible to client
[ https://issues.apache.org/jira/browse/GERONIMO-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13598798#comment-13598798 ] Freeman Fang commented on GERONIMO-4576: Hi Andrew, No, I must change the source code for my case. Cheers Freeman Make persistence exceptions more visible to client -- Key: GERONIMO-4576 URL: https://issues.apache.org/jira/browse/GERONIMO-4576 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: persistence Affects Versions: 2.2 Environment: Linux, Windows Reporter: Joe Bohn Priority: Minor Fix For: Wish List See http://issues.apache.org/jira/browse/GERONIMO-3907 for details of the original problem. That core problem was resolved. However, upon resolution it was mentioned that it would be beneficial to report more specific failure information back to the client. From GERONIMO-3907: Ralf Baumhof - 06/May/08 06:17 AM Today if have tested the new Geronimo release 2.1.1 (published on 28.04.2008). The problem is now fixed. If the server gets an error on trying a commit, this error is now thrown to the web bean. Exception text: javax.ejb.EJBTransactionRolledbackException: Transaction was rolled back, presumably because setRollbackOnly was called during a synchronization: Unable to commit: transaction marked for rollback Root Cause: javax.transaction.TransactionRolledbackException : Transaction was rolled back, presumably because setRollbackOnly was called during a synchronization: Unable to commit: transaction marked for rollback Unfortunately there is no proper root cause attached to the exception. So the cause can only be seen in the server console, but can not be reported to the user. It would be very nice if you could change this in a later release. Thanks for your help. Vincent MATHON - 06/Nov/08 02:03 AM I agree that exceptions on the server side should not be thrown to the client side since such exceptions types might not be known by the client. However, for unit testing purpose, it is useful to attach the root cause to the RollBackException. I have modified a few lines in org.apache.geronimo.transaction.manager.TransactionImpl.java to attach the root cause in case of RollBackException and it works for my unit testing purpose (I have not enough background on the java transaction architecture topic to submit a patch for production). It would be great to define a configuration parameter that permits to provide the root cause to the client and keep the current behaviour that does not by default. Geoff Callender - 22/Dec/08 03:36 AM It's useful for more than unit testing - it's essential to be able to inform the client what's wrong with the request. I've added some examples of this to https://issues.apache.org/jira/browse/OPENEJB-782 . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-4576) Make persistence exceptions more visible to client
[ https://issues.apache.org/jira/browse/GERONIMO-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13598548#comment-13598548 ] Freeman Fang commented on GERONIMO-4576: Hi, Yeah, I ran into same issue recently, the SetRollbackOnlyException hide real root cause if we call setRollbackOnly() method. And I'm OK with your option 1 3. Thanks Freeman Make persistence exceptions more visible to client -- Key: GERONIMO-4576 URL: https://issues.apache.org/jira/browse/GERONIMO-4576 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: persistence Affects Versions: 2.2 Environment: Linux, Windows Reporter: Joe Bohn Priority: Minor Fix For: Wish List See http://issues.apache.org/jira/browse/GERONIMO-3907 for details of the original problem. That core problem was resolved. However, upon resolution it was mentioned that it would be beneficial to report more specific failure information back to the client. From GERONIMO-3907: Ralf Baumhof - 06/May/08 06:17 AM Today if have tested the new Geronimo release 2.1.1 (published on 28.04.2008). The problem is now fixed. If the server gets an error on trying a commit, this error is now thrown to the web bean. Exception text: javax.ejb.EJBTransactionRolledbackException: Transaction was rolled back, presumably because setRollbackOnly was called during a synchronization: Unable to commit: transaction marked for rollback Root Cause: javax.transaction.TransactionRolledbackException : Transaction was rolled back, presumably because setRollbackOnly was called during a synchronization: Unable to commit: transaction marked for rollback Unfortunately there is no proper root cause attached to the exception. So the cause can only be seen in the server console, but can not be reported to the user. It would be very nice if you could change this in a later release. Thanks for your help. Vincent MATHON - 06/Nov/08 02:03 AM I agree that exceptions on the server side should not be thrown to the client side since such exceptions types might not be known by the client. However, for unit testing purpose, it is useful to attach the root cause to the RollBackException. I have modified a few lines in org.apache.geronimo.transaction.manager.TransactionImpl.java to attach the root cause in case of RollBackException and it works for my unit testing purpose (I have not enough background on the java transaction architecture topic to submit a patch for production). It would be great to define a configuration parameter that permits to provide the root cause to the client and keep the current behaviour that does not by default. Geoff Callender - 22/Dec/08 03:36 AM It's useful for more than unit testing - it's essential to be able to inform the client what's wrong with the request. I've added some examples of this to https://issues.apache.org/jira/browse/OPENEJB-782 . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-1065) ActiveMQ integration
[ https://issues.apache.org/activemq/browse/SM-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40627 ] Freeman Fang commented on SM-1065: -- all tests passed, apply it on behalf of Jeff Yu. ActiveMQ integration Key: SM-1065 URL: https://issues.apache.org/activemq/browse/SM-1065 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Jeff Yu Fix For: 4.0 Attachments: SM-1065.patch ActiveMQ jars are already OSGified, but we may want to create a bundle that would create a broker by default and registering a pooled connection factory in OSGi maybe. That way, everyone could use the ConnectionFactory registered in OSGi. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1133) verify how camel is used as core of jax-ws process
verify how camel is used as core of jax-ws process -- Key: SM-1133 URL: https://issues.apache.org/activemq/browse/SM-1133 Project: ServiceMix Issue Type: Sub-task Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 4.0 As Guillaume point out we should split the soap processing with the pojo invocation, as in jbi with the bc/se, to reuse most of the existing code, we could easily reusecode from either the cxf se/bc, or the camel cxf support for the end user, if you deploy a pojo with a soap annotation, it would be exposed both internally and externally (using some kind of BC) if we reuse the camel - servicemix bridge, it should be easy to do both part from(soap:http:xxx).to(smx:the-endpoint) for the BC part from(smx:the-endpoint).to(cxf:the-bean) for the SE part This task need verify how camel play as the core of this process, maybe an integration test is needed here -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1106) deploying a jaxws spring bean as OSGI bundles which is auto-discoverable by OSGi NMR/JBI
[ https://issues.apache.org/activemq/browse/SM-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved SM-1106. -- Resolution: Fixed deploying a jaxws spring bean as OSGI bundles which is auto-discoverable by OSGi NMR/JBI Key: SM-1106 URL: https://issues.apache.org/activemq/browse/SM-1106 Project: ServiceMix Issue Type: Sub-task Affects Versions: 4.0 Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 4.0 refer the discussion about this issue from the dev mailing list What would be awesome is if we can deploy various things (JAX-WS, EJB3 and so forth) using Spring+OSGi and we have a way to auto-discover things and expose them on the OSGi NMR type stuff (and so in JBI too). i.e. rather than folks having to put their JAX-WS / EJB3 / SCA stuff into a service engine; it'd be nice if we had a way of kinda binding to them direclty via OSGi. Maybe wishful thinking though - I'm just wondering if we can kinda make the OSGiNMR/JBI stuff invisible and for it to auto-hook into whatever folks are actually using. Even if we can just find a way of getting CXF services when deployed as OSGi bundles to be discoverable so we can export 'em on the OSGi NMR thingy it'd be a big win for CXF users. Agreed. What I was thinking was along those lines. That's the main reason why the ServiceMix api does not have any notion of component as in JBI. Instead we would create OSGi deployers (baically a bundle listener or service listener). For example to activate a ServiceMix endpoint, it's just a matter of registering it in the OSGi registry. For JAX-WS, we could add a spring extension for deploying a bean, kinda like the jaxws namespace for cxf (http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html). So exposing a bean in that way would perform all the necessary steps to register on as a JBI endpoint and make it available remotely (maybe we need a boolean to say if we want to export it remotely or not) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1128) ws-* support
ws-* support Key: SM-1128 URL: https://issues.apache.org/activemq/browse/SM-1128 Project: ServiceMix Issue Type: Sub-task Reporter: Freeman Fang Fix For: 4.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-626) Failed unit test (servicemix-core) : org.apache.servicemix.client.RemoteServiceMixClientTest
[ https://issues.apache.org/activemq/browse/SM-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-626: Fix Version/s: (was: 3.2) 3.2.1 Failed unit test (servicemix-core) : org.apache.servicemix.client.RemoteServiceMixClientTest Key: SM-626 URL: https://issues.apache.org/activemq/browse/SM-626 Project: ServiceMix Issue Type: Sub-task Affects Versions: 3.0 Reporter: Fritz Oconer Fix For: 3.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-992) Fix XSD schema locations for use with plain spring
[ https://issues.apache.org/activemq/browse/SM-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-992: Fix Version/s: (was: 3.2) 3.2.1 Fix XSD schema locations for use with plain spring -- Key: SM-992 URL: https://issues.apache.org/activemq/browse/SM-992 Project: ServiceMix Issue Type: Task Reporter: Guillaume Nodet Fix For: 3.2.1 The spring application loaders use validation and requires a schema location. We need to do the same as ActiveMQ did: * https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/resources/META-INF/spring.schemas * http://activemq.apache.org/xml-reference.html * http://activemq.apache.org/schemas/ (12:10:25 PM) gnodet: jstrachan: what did you fix for the xbean / amq / spring problem ? (12:10:43 PM) jstrachan: the spring 2 stuff on the AMQ lists? (12:11:03 PM) gnodet: the schemas locations iirc (12:11:26 PM) gnodet: someone just reported the same problem on smx user list (12:11:32 PM) jstrachan: mostly it was to put the XSDs in a nice place and use a nice URI to the location of the schemas (12:11:32 PM) jstrachan: http://activemq.apache.org/schema/ (12:11:41 PM) jstrachan: so the namespaces URIS are like: http://activemq.apache.org/schema/core/ (12:11:47 PM) jstrachan: which points to all versions of the XSD (12:12:07 PM) jstrachan: then I've a cron script to copy 'em there from mvn 1 repo (12:12:15 PM) gnodet: and the spring.schemas metadata, right ? (12:12:20 PM) jstrachan: then the other one - and this was the biggie I guess - was to create a spring.schemas (12:12:22 PM) jstrachan: yeah (12:12:32 PM) jstrachan: where it takes possible XSD locations (not namespace URI) (12:12:55 PM) jstrachan: this also means you have to in spring 2 to put the full XSD locations at the top of the XML file (12:13:11 PM) gnodet: yeah, because of strict validation (12:13:18 PM) jstrachan: http://activemq.apache.org/xml-reference.html (12:13:25 PM) jstrachan: yeah (12:13:32 PM) gnodet: ok, thx (12:13:43 PM) jstrachan: though there's no reason why an EntityResolver can't resolve an XSD purely on the namespace URI (12:14:03 PM) jstrachan: seems a bit bizarre that spring only supports namespace resolving on the XSD location (which is an optional thing) (12:14:26 PM) jstrachan: AFAIK an xml parser can still validate, so long as an EntityResolver can find the XSD location (12:14:38 PM) jstrachan: (I might be wrong on that - but I thought that was the case) (12:16:26 PM) jstrachan: here's the spring.schemas: https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/resources/META-INF/spring.schemas (12:16:26 PM) jstrachan: notice how it points the XSD location to the local embedded xsd (12:17:32 PM) gnodet: yeah (12:17:40 PM) jstrachan: I did 2 kinds, like spring do - one XSD with no version number (which always resolves to the one on the classpath) and one using the actual version - only the first 2 lines are useful (12:18:01 PM) jstrachan: (I experimented adding the namespace URI in there but its never used) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-625) Failed unit test (servicemix-core) : org.apache.servicemix.jbi.nmr.flow.MultipleFlowsTest
[ https://issues.apache.org/activemq/browse/SM-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-625: Fix Version/s: (was: 3.2) 3.2.1 Failed unit test (servicemix-core) : org.apache.servicemix.jbi.nmr.flow.MultipleFlowsTest - Key: SM-625 URL: https://issues.apache.org/activemq/browse/SM-625 Project: ServiceMix Issue Type: Sub-task Components: servicemix-core Affects Versions: 3.0 Reporter: Fritz Oconer Fix For: 3.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1076) NotificationBroker should return SOAP fault when error occurs from soap request, instead of HTML
[ https://issues.apache.org/activemq/browse/SM-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-1076: - Fix Version/s: (was: 3.2) 3.2.1 NotificationBroker should return SOAP fault when error occurs from soap request, instead of HTML - Key: SM-1076 URL: https://issues.apache.org/activemq/browse/SM-1076 Project: ServiceMix Issue Type: Bug Components: servicemix-wsn2005 Environment: Windows XP, Servicemix 3.2 Reporter: Ryan Moquin Fix For: 3.2.1 When I attempt to get current messages from a topic that I have created a subscription to, I get an html error back when there aren't any messages (there should have been, but that's besides the point). This should be a soap fault instead: html head meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1/ titleError 500 /title /head bodyh2HTTP ERROR: 500/h2preorg.apache.servicemix.wsn.jaxws.NoCurrentMessageOnTopicFault: There is no current message on this topic./pre pRequestURI=/NotificationBroker//ph3Caused by:/h3prejava.lang.Exception: org.apache.servicemix.wsn.jaxws.NoCurrentMessageOnTopicFault: There is no current message on this topic. at org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:195) at org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:313) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:375) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396) at org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectChannelConnector.java:511) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) Caused by: org.apache.servicemix.wsn.jaxws.NoCurrentMessageOnTopicFault: There is no current message on this topic. at org.apache.servicemix.wsn.AbstractNotificationBroker.getCurrentMessage(AbstractNotificationBroker.java:234) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java:143) at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538) at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490) at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46) at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610) at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170) at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:167) at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) /pre h3Caused by:/h3preorg.apache.servicemix.wsn.jaxws.NoCurrentMessageOnTopicFault: There is no current message on this topic. at org.apache.servicemix.wsn.AbstractNotificationBroker.getCurrentMessage(AbstractNotificationBroker.java:234) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
[jira] Updated: (SM-627) Failed unit test (servicemix-core) : org.apache.servicemix.jbi.nmr.flow.jca.JCAFlowTest
[ https://issues.apache.org/activemq/browse/SM-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-627: Fix Version/s: (was: 3.2) 3.2.1 Failed unit test (servicemix-core) : org.apache.servicemix.jbi.nmr.flow.jca.JCAFlowTest --- Key: SM-627 URL: https://issues.apache.org/activemq/browse/SM-627 Project: ServiceMix Issue Type: Sub-task Components: servicemix-core Affects Versions: 3.0 Reporter: Fritz Oconer Fix For: 3.2.1 Attachments: JCAFlowTest_patch.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-984) Two exchanges with the same dynamic endpoint processed at the same lead to an exception
[ https://issues.apache.org/activemq/browse/SM-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-984: Fix Version/s: (was: 3.2) 3.2.1 Two exchanges with the same dynamic endpoint processed at the same lead to an exception Key: SM-984 URL: https://issues.apache.org/activemq/browse/SM-984 Project: ServiceMix Issue Type: Bug Components: servicemix-common Affects Versions: 3.1 Reporter: Guillaume Nodet Fix For: 3.2.1 The exception is thrown at: Thread [pool-flow.seda.ID:10.59.0.34-1136c103485-0:0-thread-3] (Suspended (exception JBIException)) EndpointRegistry.registerInternalEndpoint(ComponentContextImpl, QName, String) line: 189 Registry.activateEndpoint(ComponentContextImpl, QName, String) line: 192 ComponentContextImpl.activateEndpoint(QName, String) line: 126 BeanEndpoint(ProviderEndpoint).start() line: 58 BeanEndpoint.start() line: 94 BeanEndpoint(SimpleEndpoint).activate() line: 55 BeanComponent.getResolvedEPR(ServiceEndpoint) line: 120 BeanComponent(AsyncBaseLifeCycle).processExchange(MessageExchange) line: 429 BeanComponent(BaseLifeCycle).onMessageExchange(MessageExchange) line: 46 DeliveryChannelImpl.processInBound(MessageExchangeImpl) line: 595 SedaFlow(AbstractFlow).doRouting(MessageExchangeImpl) line: 174 SedaFlow.doRouting(MessageExchangeImpl) line: 176 SedaQueue$1.run() line: 134 ThreadPoolExecutor$Worker.runTask(Runnable) line: 665 ThreadPoolExecutor$Worker.run() line: 690 Thread.run() line: 595 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-642) org.apache.servicemix.components.saaj.SaajSoapActionTest (Hangs)
[ https://issues.apache.org/activemq/browse/SM-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-642: Fix Version/s: (was: 3.2) 3.2.1 org.apache.servicemix.components.saaj.SaajSoapActionTest (Hangs) Key: SM-642 URL: https://issues.apache.org/activemq/browse/SM-642 Project: ServiceMix Issue Type: Sub-task Components: servicemix-components Affects Versions: 3.0 Reporter: Fritz Oconer Fix For: 3.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-629) org.apache.servicemix.jbi.messaging.TransactionsTest
[ https://issues.apache.org/activemq/browse/SM-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-629: Fix Version/s: (was: 3.2) 3.2.1 org.apache.servicemix.jbi.messaging.TransactionsTest Key: SM-629 URL: https://issues.apache.org/activemq/browse/SM-629 Project: ServiceMix Issue Type: Sub-task Components: servicemix-core Affects Versions: 3.0 Reporter: Fritz Oconer Fix For: 3.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-908) Upgrade to ActiveMQ 5.0
[ https://issues.apache.org/activemq/browse/SM-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-908: Fix Version/s: (was: 3.2) 3.2.1 Upgrade to ActiveMQ 5.0 --- Key: SM-908 URL: https://issues.apache.org/activemq/browse/SM-908 Project: ServiceMix Issue Type: Improvement Reporter: Guillaume Nodet Fix For: 3.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1035) Continuation problems when Max Idle Time ocurr
[
https://issues.apache.org/activemq/browse/SM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated SM-1035:
-
Fix Version/s: (was: 3.2)
3.2.1
Continuation problems when Max Idle Time ocurr
--
Key: SM-1035
URL: https://issues.apache.org/activemq/browse/SM-1035
Project: ServiceMix
Issue Type: Bug
Components: servicemix-http
Environment: Servicemix 3.1
Reporter: Jorge RodrÃguez Pedrianes
Assignee: Guillaume Nodet
Fix For: 3.2.1
Original Estimate: 2 minutes
Remaining Estimate: 2 minutes
HI!
I saw in Http binding component, that if my service work too time, the
http endpoint retry the current request. but this it's wrong. I think that in
ConsumerProcessor class it's better to do this:
{code:title=ConsumerProcessor java|borderStyle=solid}
...
public void process(HttpServletRequest request, HttpServletResponse
response) throws Exception {
// If the continuation is not a retry
if (!cont.isPending() cont.isNew()) {
...
}
{code}
Whith this we avoid put the request two times in the bus.
Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-628) org.apache.servicemix.jbi.nmr.flow.jms.JMSFlowTest
[ https://issues.apache.org/activemq/browse/SM-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-628: Fix Version/s: (was: 3.2) 3.2.1 org.apache.servicemix.jbi.nmr.flow.jms.JMSFlowTest -- Key: SM-628 URL: https://issues.apache.org/activemq/browse/SM-628 Project: ServiceMix Issue Type: Sub-task Components: servicemix-core Affects Versions: 3.0 Reporter: Fritz Oconer Fix For: 3.2.1 Attachments: SMTestCasesPatches.zip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-624) Failed unit test (servicemix-core) : org.apache.servicemix.jbi.nmr.flow.jms.MultipleJMSFlowTest
[ https://issues.apache.org/activemq/browse/SM-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-624: Fix Version/s: (was: 3.2) 3.2.1 Failed unit test (servicemix-core) : org.apache.servicemix.jbi.nmr.flow.jms.MultipleJMSFlowTest --- Key: SM-624 URL: https://issues.apache.org/activemq/browse/SM-624 Project: ServiceMix Issue Type: Sub-task Components: servicemix-core Affects Versions: 3.0 Environment: Windows and linux Reporter: Fritz Oconer Fix For: 3.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1096) File-based message auditor
[ https://issues.apache.org/activemq/browse/SM-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-1096: - Fix Version/s: (was: 3.2) 3.2.1 File-based message auditor -- Key: SM-1096 URL: https://issues.apache.org/activemq/browse/SM-1096 Project: ServiceMix Issue Type: New Feature Components: servicemix-audit Reporter: Gert Vanthienen Priority: Minor Fix For: 3.2.1 Adding a file-based auditor implementation. As discussed in SM-990, a TeeInputStream should be used for optimizing performance -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-580) Support for standard POST request from the provider.
[ https://issues.apache.org/activemq/browse/SM-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-580: Fix Version/s: (was: 3.2) 3.2.1 Support for standard POST request from the provider. Key: SM-580 URL: https://issues.apache.org/activemq/browse/SM-580 Project: ServiceMix Issue Type: New Feature Components: servicemix-http Reporter: Jimmy Kongoli Priority: Minor Fix For: 3.2.1 Attachments: diff.txt We may run in situations where we need to POST the xml message to the provider in a post standard form named=value. Proposed solution: Add an optional parameter postParamName at http:endpoint. If the parameter is defined and http:endpoint soap parameter is false than - modify the http Contet-Type header to support Post method. - create the http post body postParamName=xml (message). I have attached a potential solution as a .diff file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1113) SOAP faults don't work when elementFormDefault is unqualified
[ https://issues.apache.org/activemq/browse/SM-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved SM-1113. -- Resolution: Fixed SOAP faults don't work when elementFormDefault is unqualified -- Key: SM-1113 URL: https://issues.apache.org/activemq/browse/SM-1113 Project: ServiceMix Issue Type: Bug Components: servicemix-cxf-bc Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 3.2 the JBI binding fault is ns1:JBIFault xmlns:ns1=http://cxf.apache.org/bindings/jbi;ns2:UnknownPersonFault xmlns:ns2=http://servicemix.apache.org/samples/wsdl-first/types;personId xmlns=/personId/ns2:UnknownPersonFault/ns1:JBIFault but the soap binding fault is soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:Bodysoap:Faultfaultcodesoap:Server/faultcodefaultstringFault occured/faultstringdetailns2:UnknownPersonFault xmlns:ns2=http://servicemix.apache.org/samples/wsdl-first/types;personId xmlns= xmlns= //ns2:UnknownPersonFault/detail/soap:Fault/soap:Body/soap:Envelope the transform from JBI binding fault to soap binding fault is incorrect, which cause the duplicated namespace -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1109) attachment should be supported in cxf se and bc
attachment should be supported in cxf se and bc --- Key: SM-1109 URL: https://issues.apache.org/activemq/browse/SM-1109 Project: ServiceMix Issue Type: Improvement Components: servicemix-cxf-bc, servicemix-cxf-se Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 3.2 cxf bc should handle soap message with mtom attachment and save the attachment into NormalizeMessage then deliver to cxf se, cxf se should handle attachment correctly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1088) CXFbc provider should provider a targetURI element
[ https://issues.apache.org/activemq/browse/SM-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40342 ] Freeman Fang commented on SM-1088: -- we provide locationURI as provider's attribute something like cxfbc:provider wsdl=/wsdl/calculator.wsdl locationURI=http://localhost:9001/providertest; endpoint=CalculatorPort service=calculator:CalculatorService interfaceName=calculator:CalculatorPortType CXFbc provider should provider a targetURI element -- Key: SM-1088 URL: https://issues.apache.org/activemq/browse/SM-1088 Project: ServiceMix Issue Type: Improvement Components: servicemix-cxf-bc Affects Versions: 3.2 Environment: Windows XP, Servicemix 3.2 Reporter: Ryan Moquin Assignee: Freeman Fang Priority: Minor Fix For: 3.2 Even though I didn't get the cxfbc provider to work, I did notice in the XSD there doesn't appear to be an option to specify a target URI, wsdl, or useJBIWrapper. I mentioned this in the bug report to create an example, but I figured I'd open a separate issue for clarity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1088) CXFbc provider should provider a targetURI element
[ https://issues.apache.org/activemq/browse/SM-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved SM-1088. -- Resolution: Fixed Fix Version/s: 3.2 CXFbc provider should provider a targetURI element -- Key: SM-1088 URL: https://issues.apache.org/activemq/browse/SM-1088 Project: ServiceMix Issue Type: Improvement Components: servicemix-cxf-bc Affects Versions: 3.2 Environment: Windows XP, Servicemix 3.2 Reporter: Ryan Moquin Assignee: Freeman Fang Priority: Minor Fix For: 3.2 Even though I didn't get the cxfbc provider to work, I did notice in the XSD there doesn't appear to be an option to specify a target URI, wsdl, or useJBIWrapper. I mentioned this in the bug report to create an example, but I figured I'd open a separate issue for clarity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1086) Example of how to use CXFBC Provider.
[ https://issues.apache.org/activemq/browse/SM-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned SM-1086: Assignee: Freeman Fang Example of how to use CXFBC Provider. - Key: SM-1086 URL: https://issues.apache.org/activemq/browse/SM-1086 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.2 Environment: Windows XP, Servicemix 3.2 Reporter: Ryan Moquin Assignee: Freeman Fang No matter how hard I tried, I couldn't seem to figure out how to make the cxfbc provider work. I don't remember exactly what the problem was but I'm sure it was simply a configuration error on my end. It doesn't appear that there is any option to point it to a wsdl or a target URI like there is for the cxfse proxy, and the servicemix http consumer/provider. Please provide an example that shows how to use them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1088) CXFbc provider should provider a targetURI element
[ https://issues.apache.org/activemq/browse/SM-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned SM-1088: Assignee: Freeman Fang CXFbc provider should provider a targetURI element -- Key: SM-1088 URL: https://issues.apache.org/activemq/browse/SM-1088 Project: ServiceMix Issue Type: Improvement Components: beanflow Affects Versions: 3.2 Environment: Windows XP, Servicemix 3.2 Reporter: Ryan Moquin Assignee: Freeman Fang Priority: Minor Even though I didn't get the cxfbc provider to work, I did notice in the XSD there doesn't appear to be an option to specify a target URI, wsdl, or useJBIWrapper. I mentioned this in the bug report to create an example, but I figured I'd open a separate issue for clarity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1069) JAX-WS support
[ https://issues.apache.org/activemq/browse/SM-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned SM-1069: Assignee: Freeman Fang JAX-WS support -- Key: SM-1069 URL: https://issues.apache.org/activemq/browse/SM-1069 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Fix For: 4.0 It should be easy to expose a JAX-WS annotated bean on the bus, or even outside using http/soap ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1077) CXFSE should allow a proxy to another CXFSE service like jsr181 does.
[ https://issues.apache.org/activemq/browse/SM-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved SM-1077. -- Resolution: Fixed CXFSE should allow a proxy to another CXFSE service like jsr181 does. - Key: SM-1077 URL: https://issues.apache.org/activemq/browse/SM-1077 Project: ServiceMix Issue Type: Improvement Environment: Windows XP Reporter: Ryan Moquin Assignee: Freeman Fang Fix For: 3.2 With the JSR181 services with XFire, I was able to do this, per the documentation: jsr181:endpoint serviceInterface=test.Echo jsr181:pojo bean class=test.EchoProxy property name=echo jsr181:proxy service=test:EchoService context=#context type=test.Echo / /property /bean /jsr181:pojo /jsr181:endpoint In order to create a proxy to another JSR181 service on the bus. I'm currently not able to do this now that I'm using CXF. This means I have to use spring to populate an instance of my service class on the service that I want to access it. This leads to confusion since there is now the instance of the target service that my service holds a reference to, and then there is an instance of that target service that servicemix creates itself. It would be nice to be able to have a service reference the actual endpoint on the bus. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1078) CXFSE xbean.xml should allow the injection of the spring parent context, just like JSR181
[ https://issues.apache.org/activemq/browse/SM-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned SM-1078: Assignee: Freeman Fang CXFSE xbean.xml should allow the injection of the spring parent context, just like JSR181 - Key: SM-1078 URL: https://issues.apache.org/activemq/browse/SM-1078 Project: ServiceMix Issue Type: Improvement Environment: Windows XP Reporter: Ryan Moquin Assignee: Freeman Fang Fix For: 3.2 It would be nice to be able to inject the ComponentContext into a CXF service in servicemix like you can with jsr181 services. Without this, it makes it a lot more difficult to access the bus and use it's services. So in other words, a CXF version of this: jsr181:endpoint ... jsr181:pojo bean class=xxx property name=context ref=context / /bean /jsr181:pojo /jsr181:endpoint -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1077) CXFSE should allow a proxy to another CXFSE service like jsr181 does.
[ https://issues.apache.org/activemq/browse/SM-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned SM-1077: Assignee: Freeman Fang CXFSE should allow a proxy to another CXFSE service like jsr181 does. - Key: SM-1077 URL: https://issues.apache.org/activemq/browse/SM-1077 Project: ServiceMix Issue Type: Improvement Environment: Windows XP Reporter: Ryan Moquin Assignee: Freeman Fang Fix For: 3.2 With the JSR181 services with XFire, I was able to do this, per the documentation: jsr181:endpoint serviceInterface=test.Echo jsr181:pojo bean class=test.EchoProxy property name=echo jsr181:proxy service=test:EchoService context=#context type=test.Echo / /property /bean /jsr181:pojo /jsr181:endpoint In order to create a proxy to another JSR181 service on the bus. I'm currently not able to do this now that I'm using CXF. This means I have to use spring to populate an instance of my service class on the service that I want to access it. This leads to confusion since there is now the instance of the target service that my service holds a reference to, and then there is an instance of that target service that servicemix creates itself. It would be nice to be able to have a service reference the actual endpoint on the bus. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1078) CXFSE xbean.xml should allow the injection of the spring parent context, just like JSR181
[ https://issues.apache.org/activemq/browse/SM-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40171 ] Freeman Fang commented on SM-1078: -- duplicated with SM-1060, will close this one as a duplicated issue. Please refer SM-1060 CXFSE xbean.xml should allow the injection of the spring parent context, just like JSR181 - Key: SM-1078 URL: https://issues.apache.org/activemq/browse/SM-1078 Project: ServiceMix Issue Type: Improvement Environment: Windows XP Reporter: Ryan Moquin Assignee: Freeman Fang Fix For: 3.2 It would be nice to be able to inject the ComponentContext into a CXF service in servicemix like you can with jsr181 services. Without this, it makes it a lot more difficult to access the bus and use it's services. So in other words, a CXF version of this: jsr181:endpoint ... jsr181:pojo bean class=xxx property name=context ref=context / /bean /jsr181:pojo /jsr181:endpoint -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1078) CXFSE xbean.xml should allow the injection of the spring parent context, just like JSR181
[ https://issues.apache.org/activemq/browse/SM-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved SM-1078. -- Resolution: Duplicate CXFSE xbean.xml should allow the injection of the spring parent context, just like JSR181 - Key: SM-1078 URL: https://issues.apache.org/activemq/browse/SM-1078 Project: ServiceMix Issue Type: Improvement Environment: Windows XP Reporter: Ryan Moquin Assignee: Freeman Fang Fix For: 3.2 It would be nice to be able to inject the ComponentContext into a CXF service in servicemix like you can with jsr181 services. Without this, it makes it a lot more difficult to access the bus and use it's services. So in other words, a CXF version of this: jsr181:endpoint ... jsr181:pojo bean class=xxx property name=context ref=context / /bean /jsr181:pojo /jsr181:endpoint -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1059) Upgrade to CXF 2.0.2
[ https://issues.apache.org/activemq/browse/SM-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned SM-1059: Assignee: Freeman Fang Upgrade to CXF 2.0.2 Key: SM-1059 URL: https://issues.apache.org/activemq/browse/SM-1059 Project: ServiceMix Issue Type: Improvement Components: servicemix-jsr181 Affects Versions: 3.2 Environment: Windows XP Reporter: Ryan Moquin Assignee: Freeman Fang Priority: Minor Some fixes were made to CXF 2.0.2 which should be released very soon. Servicemix 3.2 currently uses CXF 2.0.1 and should be upgraded to use 2.0.2 if possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1047) rewrite wsdl-first sample with servicemix-cxf-se and servicemix-cxf-bc
[ https://issues.apache.org/activemq/browse/SM-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved SM-1047. -- Resolution: Fixed rewrite wsdl-first sample with servicemix-cxf-se and servicemix-cxf-bc -- Key: SM-1047 URL: https://issues.apache.org/activemq/browse/SM-1047 Project: ServiceMix Issue Type: Sub-task Reporter: Freeman Fang Assignee: Freeman Fang -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-883) MBean registration in Websphere returns different objectName
[ https://issues.apache.org/activemq/browse/SM-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-883: Fix Version/s: (was: 3.1.2) MBean registration in Websphere returns different objectName Key: SM-883 URL: https://issues.apache.org/activemq/browse/SM-883 Project: ServiceMix Issue Type: Improvement Components: servicemix-core Affects Versions: 3.0.1, 3.1 Environment: Windows XP SP1, Ubuntu Linux, Java 1.5 Reporter: Grant McDonald Assignee: Grant McDonald Fix For: 3.2 Attachments: PatchTo3.0.1.zip, PatchToCurrentVersion.zip, SM-883-MBeanRegistration.patch Original Estimate: 2 hours Remaining Estimate: 2 hours Description courtesy of David Potter: When running serviceMix V3.0 on WebSphere 6.1.0.0 I get the following error after stopping and starting serviceMix from the WebSphere console. ERROR - ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbi' defined in ServletContext resource [/WEB-INF/servicemix.xml]: Invocation of init method failed; nested exception is javax.jbi.JBIException: javax.management.InstanceAlreadyExistsException: org.apache.servicemix:Name=ManagementContext,cell=SD1464Node01Cell,Type=SystemService,ContainerName=ServiceMix,node=SD1464Node01,process=server1 I have traced the error to the fact that when you register an mbean IBM adds additional information to the bean. So when serviceMix regesters the bean org.apache.servicemix:Name=ManagementContext,Type=SystemService,ContainerName=ServiceMix IBM, in the method com.ibm.ws.management.PlatformMBeanServer.registerMBean(PlatformMBeanServer.java:469) , adds the attributes cell=SD1464Node01Cell, node=SD1464Node01,process=server1 These means that when we try to unregister the bean on application shutdown we cannot find it (as we look the been up by name). Solution Ideas: 1) In AsyncBaseLifeCycle.doInit() use queryNames() instead of isRegistered(). Care would need to be taken in unregistering the bean is case the bean is not ours. 2) After a bean is registered, update its name (or the complete bean) with the name of the bean returned by the register operation. (this is preferred) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1011) WSDLFlattenner / SchemaCollection do not handle nested schemas inclusions properly
[
https://issues.apache.org/activemq/browse/SM-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated SM-1011:
-
Fix Version/s: (was: 3.1.2)
WSDLFlattenner / SchemaCollection do not handle nested schemas inclusions
properly
--
Key: SM-1011
URL: https://issues.apache.org/activemq/browse/SM-1011
Project: ServiceMix
Issue Type: Bug
Components: servicemix-common
Affects Versions: 3.1.1
Environment: Windows XP
Reporter: Konrad Argasinski
Fix For: 3.2
Attachments: nested schemas.txt, nested-schemas-reproduced-sm.zip
WSDLFlattener fails to analyse JSR-181 SU WSDL which imports multi-level
(nested) schemas structure.
My JSR-181 SU WSDL imports A1.xsd schema. A1.xsd includes B1.xsd, B2.xsd and
B3.xsd. B1.xsd includes C1.xsd.
The schema is used by JAXB during the project build and it works ok, however
when the SU gets deployed on ServiceMix I receive following error:
loc-messageNOT_FOUND_ERR: An attempt is made to reference a node in a
context where it does not exist./loc-message
stack-trace![CDATA[org.w3c.dom.DOMException: NOT_FOUND_ERR: An attempt is
made to reference a node in a context where it does not exist.
at org.apache.xerces.dom.ParentNode.internalRemoveChild(Unknown Source)
at org.apache.xerces.dom.ParentNode.removeChild(Unknown Source)
at
org.apache.servicemix.common.tools.wsdl.SchemaCollection.handleImports(SchemaCollection.java:150)
The full stack trace is attached.
As workaround I compiled my custom SchemaCollection and it works ok now,
however I think a better fix is needed.
My custom changes in org.apache.servicemix.common.tools.wsdl.SchemaCollection
are:
around line 149 I have replaced:
String location = ce.getAttribute(schemaLocation);
schema.getRoot().removeChild(ce);
with:
String location = ce.getAttribute(schemaLocation);
Node parentNode = ce.getParentNode();
Element root = schema.getRoot();
if (root == parentNode) {
log.debug(Removing child include node: + ce);
schema.getRoot().removeChild(ce);
} else {
log.warn(Skipping child include node removal: + ce);
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1035) Continuation problems when Max Idle Time ocurr
[
https://issues.apache.org/activemq/browse/SM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated SM-1035:
-
Fix Version/s: (was: 3.1.2)
Continuation problems when Max Idle Time ocurr
--
Key: SM-1035
URL: https://issues.apache.org/activemq/browse/SM-1035
Project: ServiceMix
Issue Type: Bug
Components: servicemix-http
Environment: Servicemix 3.1
Reporter: Jorge RodrÃguez Pedrianes
Assignee: Guillaume Nodet
Fix For: 3.2
Original Estimate: 2 minutes
Remaining Estimate: 2 minutes
HI!
I saw in Http binding component, that if my service work too time, the
http endpoint retry the current request. but this it's wrong. I think that in
ConsumerProcessor class it's better to do this:
{code:title=ConsumerProcessor java|borderStyle=solid}
...
public void process(HttpServletRequest request, HttpServletResponse
response) throws Exception {
// If the continuation is not a retry
if (!cont.isPending() cont.isNew()) {
...
}
{code}
Whith this we avoid put the request two times in the bus.
Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-848) ServiceMix 3.x with Java 1.4.x
[ https://issues.apache.org/activemq/browse/SM-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-848: Fix Version/s: (was: 3.1.2) 3.2 ServiceMix 3.x with Java 1.4.x -- Key: SM-848 URL: https://issues.apache.org/activemq/browse/SM-848 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.1 Environment: Java Runtime Environment 1.4.x Reporter: Juergen Mayrbaeurl Fix For: 3.2 Since ServiceMix 3.1 can only be used with Java 5 or higher, rework it to make it Java 1.4.x compatible -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-998) In-Out Exchanges in a JMS queue cannot be successfully processed after a crash/shutdown
[ https://issues.apache.org/activemq/browse/SM-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-998: Affects Version/s: (was: 3.1.2) 3.2 Fix Version/s: (was: 3.1.2) 3.2 In-Out Exchanges in a JMS queue cannot be successfully processed after a crash/shutdown --- Key: SM-998 URL: https://issues.apache.org/activemq/browse/SM-998 Project: ServiceMix Issue Type: Bug Components: servicemix-jms Affects Versions: 3.2 Environment: any Reporter: Sam Gerstein Fix For: 3.2 Attachments: servicemix-jms_patch.txt Original Estimate: 0 minutes Remaining Estimate: 0 minutes Because a temporary queue is used for the reply-to destination and the Exchange is stored in an in-memory Map, In-Out message exchanges in a JMS queue cannot be returned to their sender after a crash or shutdown of ServiceMix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-984) Two exchanges with the same dynamic endpoint processed at the same lead to an exception
[ https://issues.apache.org/activemq/browse/SM-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-984: Fix Version/s: (was: 3.1.2) Two exchanges with the same dynamic endpoint processed at the same lead to an exception Key: SM-984 URL: https://issues.apache.org/activemq/browse/SM-984 Project: ServiceMix Issue Type: Bug Components: servicemix-common Affects Versions: 3.1 Reporter: Guillaume Nodet Fix For: 3.2 The exception is thrown at: Thread [pool-flow.seda.ID:10.59.0.34-1136c103485-0:0-thread-3] (Suspended (exception JBIException)) EndpointRegistry.registerInternalEndpoint(ComponentContextImpl, QName, String) line: 189 Registry.activateEndpoint(ComponentContextImpl, QName, String) line: 192 ComponentContextImpl.activateEndpoint(QName, String) line: 126 BeanEndpoint(ProviderEndpoint).start() line: 58 BeanEndpoint.start() line: 94 BeanEndpoint(SimpleEndpoint).activate() line: 55 BeanComponent.getResolvedEPR(ServiceEndpoint) line: 120 BeanComponent(AsyncBaseLifeCycle).processExchange(MessageExchange) line: 429 BeanComponent(BaseLifeCycle).onMessageExchange(MessageExchange) line: 46 DeliveryChannelImpl.processInBound(MessageExchangeImpl) line: 595 SedaFlow(AbstractFlow).doRouting(MessageExchangeImpl) line: 174 SedaFlow.doRouting(MessageExchangeImpl) line: 176 SedaQueue$1.run() line: 134 ThreadPoolExecutor$Worker.runTask(Runnable) line: 665 ThreadPoolExecutor$Worker.run() line: 690 Thread.run() line: 595 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-992) Fix XSD schema locations for use with plain spring
[ https://issues.apache.org/activemq/browse/SM-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-992: Fix Version/s: (was: 3.1.2) Fix XSD schema locations for use with plain spring -- Key: SM-992 URL: https://issues.apache.org/activemq/browse/SM-992 Project: ServiceMix Issue Type: Task Reporter: Guillaume Nodet Fix For: 3.2 The spring application loaders use validation and requires a schema location. We need to do the same as ActiveMQ did: * https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/resources/META-INF/spring.schemas * http://activemq.apache.org/xml-reference.html * http://activemq.apache.org/schemas/ (12:10:25 PM) gnodet: jstrachan: what did you fix for the xbean / amq / spring problem ? (12:10:43 PM) jstrachan: the spring 2 stuff on the AMQ lists? (12:11:03 PM) gnodet: the schemas locations iirc (12:11:26 PM) gnodet: someone just reported the same problem on smx user list (12:11:32 PM) jstrachan: mostly it was to put the XSDs in a nice place and use a nice URI to the location of the schemas (12:11:32 PM) jstrachan: http://activemq.apache.org/schema/ (12:11:41 PM) jstrachan: so the namespaces URIS are like: http://activemq.apache.org/schema/core/ (12:11:47 PM) jstrachan: which points to all versions of the XSD (12:12:07 PM) jstrachan: then I've a cron script to copy 'em there from mvn 1 repo (12:12:15 PM) gnodet: and the spring.schemas metadata, right ? (12:12:20 PM) jstrachan: then the other one - and this was the biggie I guess - was to create a spring.schemas (12:12:22 PM) jstrachan: yeah (12:12:32 PM) jstrachan: where it takes possible XSD locations (not namespace URI) (12:12:55 PM) jstrachan: this also means you have to in spring 2 to put the full XSD locations at the top of the XML file (12:13:11 PM) gnodet: yeah, because of strict validation (12:13:18 PM) jstrachan: http://activemq.apache.org/xml-reference.html (12:13:25 PM) jstrachan: yeah (12:13:32 PM) gnodet: ok, thx (12:13:43 PM) jstrachan: though there's no reason why an EntityResolver can't resolve an XSD purely on the namespace URI (12:14:03 PM) jstrachan: seems a bit bizarre that spring only supports namespace resolving on the XSD location (which is an optional thing) (12:14:26 PM) jstrachan: AFAIK an xml parser can still validate, so long as an EntityResolver can find the XSD location (12:14:38 PM) jstrachan: (I might be wrong on that - but I thought that was the case) (12:16:26 PM) jstrachan: here's the spring.schemas: https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/resources/META-INF/spring.schemas (12:16:26 PM) jstrachan: notice how it points the XSD location to the local embedded xsd (12:17:32 PM) gnodet: yeah (12:17:40 PM) jstrachan: I did 2 kinds, like spring do - one XSD with no version number (which always resolves to the one on the classpath) and one using the actual version - only the first 2 lines are useful (12:18:01 PM) jstrachan: (I experimented adding the namespace URI in there but its never used) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1055) jbi maven plugin can't pick up jar from maven repos if this jar has no relavant pom file when build component installer
jbi maven plugin can't pick up jar from maven repos if this jar has no relavant pom file when build component installer --- Key: SM-1055 URL: https://issues.apache.org/activemq/browse/SM-1055 Project: ServiceMix Issue Type: Bug Reporter: Freeman Fang For example, neethi-2.0.2.jar has no neethi-2.0.2.pom in http://repo1.maven.org/maven2/org/apache/neethi/neethi/2.0.2/ So even my component has dependency on neethi-2.0.2, the jbi maven plugin still can't pick up neethi-2.0.2.jar when build the component installer, neither wirte this jar to component descriptor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1019) support ws-addressing
[
https://issues.apache.org/activemq/browse/SM-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved SM-1019.
--
Resolution: Fixed
support ws-addressing
-
Key: SM-1019
URL: https://issues.apache.org/activemq/browse/SM-1019
Project: ServiceMix
Issue Type: Sub-task
Reporter: Freeman Fang
Assignee: Freeman Fang
already support ws-addressing between cxf bc and external request, as for
things inside jbi container, should refer to how servicemix-http implement
ws-addressing, append how servicemix-http do ws-addressing from wiki
WS-Addressing
When used on a SOAP consumer endpoint, servicemix-http handles the
WS-Adressing Action and To headers.
wsa:Action
The wsa:Action header can be used to specify the target interface name and
operation to use for the JBI exchange.
The header uses the following syntax:
[target namespace][delimiter][interface name][delimiter][operation name]
where:
* [delimiter] is : when the [target namespace] is a URN, otherwise /.
* [target namespace] is the namespace of the interface.
* [interface name] is the name of the interface.
* [operation name] is the name of the operation.
For example, the following header
wsa:Actionhttp://example.com/stockquote/StockQuoteInterface/GetLastTradePrice/wsa:Action
will be used to address the JBI exchange with the following properties:
* interface name: {http://example.com/stockquote\}StockQuoteInterface
* operation name: {http://example.com/stockquote\}GetLastTradePrice
wsa:To
The wsa:To header specifies the target JBI service name and endpoint name.
The header uses the following syntax:
[target namespace][delimiter][service name][delimiter][endpoint name]
where:
* [delimiter] is : when the [target namespace] is a URN, otherwise /.
* [target namespace] is the namespace of the interface.
* [service name] is the name of the service.
* [endpoint name] is the name of the endpoint.
For example, the following header
wsa:Tourn:example:stockquote:StockQuoteService:JBIEndpoint/wsa:To
will be used to address the JBI exchange with the following properties:
* service name: {urn:example:stockquote}StockQuoteService
* endpoint name: JBIEndpoint
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1018) support ws-security
[ https://issues.apache.org/activemq/browse/SM-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved SM-1018. -- Resolution: Fixed support ws-security --- Key: SM-1018 URL: https://issues.apache.org/activemq/browse/SM-1018 Project: ServiceMix Issue Type: Sub-task Reporter: Freeman Fang Assignee: Freeman Fang should refer to the ws-security implementation in servicemix-soap model -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1047) rewrite wsdl-first sample with servicemix-cxf-se and servicemix-cxf-bc
rewrite wsdl-first sample with servicemix-cxf-se and servicemix-cxf-bc -- Key: SM-1047 URL: https://issues.apache.org/activemq/browse/SM-1047 Project: ServiceMix Issue Type: Sub-task Reporter: Freeman Fang Assignee: Freeman Fang -- 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-1047) rewrite wsdl-first sample with servicemix-cxf-se and servicemix-cxf-bc
[ https://issues.apache.org/activemq/browse/SM-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SM-1047 started by Freeman Fang. rewrite wsdl-first sample with servicemix-cxf-se and servicemix-cxf-bc -- Key: SM-1047 URL: https://issues.apache.org/activemq/browse/SM-1047 Project: ServiceMix Issue Type: Sub-task Reporter: Freeman Fang Assignee: Freeman Fang -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1018) support ws-security
[ https://issues.apache.org/activemq/browse/SM-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned SM-1018: Assignee: Freeman Fang support ws-security --- Key: SM-1018 URL: https://issues.apache.org/activemq/browse/SM-1018 Project: ServiceMix Issue Type: Sub-task Reporter: Freeman Fang Assignee: Freeman Fang should refer to the ws-security implementation in servicemix-soap model -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1018) support ws-security
support ws-security --- Key: SM-1018 URL: https://issues.apache.org/activemq/browse/SM-1018 Project: ServiceMix Issue Type: Sub-task Reporter: Freeman Fang should refer to the ws-security implementation in servicemix-soap model -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1019) support ws-addressing
support ws-addressing
-
Key: SM-1019
URL: https://issues.apache.org/activemq/browse/SM-1019
Project: ServiceMix
Issue Type: Sub-task
Reporter: Freeman Fang
already support ws-addressing between cxf bc and external request, as for
things inside jbi container, should refer to how servicemix-http implement
ws-addressing, append how servicemix-http do ws-addressing from wiki
WS-Addressing
When used on a SOAP consumer endpoint, servicemix-http handles the WS-Adressing
Action and To headers.
wsa:Action
The wsa:Action header can be used to specify the target interface name and
operation to use for the JBI exchange.
The header uses the following syntax:
[target namespace][delimiter][interface name][delimiter][operation name]
where:
* [delimiter] is : when the [target namespace] is a URN, otherwise /.
* [target namespace] is the namespace of the interface.
* [interface name] is the name of the interface.
* [operation name] is the name of the operation.
For example, the following header
wsa:Actionhttp://example.com/stockquote/StockQuoteInterface/GetLastTradePrice/wsa:Action
will be used to address the JBI exchange with the following properties:
* interface name: {http://example.com/stockquote\}StockQuoteInterface
* operation name: {http://example.com/stockquote\}GetLastTradePrice
wsa:To
The wsa:To header specifies the target JBI service name and endpoint name.
The header uses the following syntax:
[target namespace][delimiter][service name][delimiter][endpoint name]
where:
* [delimiter] is : when the [target namespace] is a URN, otherwise /.
* [target namespace] is the namespace of the interface.
* [service name] is the name of the service.
* [endpoint name] is the name of the endpoint.
For example, the following header
wsa:Tourn:example:stockquote:StockQuoteService:JBIEndpoint/wsa:To
will be used to address the JBI exchange with the following properties:
* service name: {urn:example:stockquote}StockQuoteService
* endpoint name: JBIEndpoint
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: patch0806.txt CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt, patch0702.txt, patch0720.txt, patch0806.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: patch0720.txt re-upload patch0720 which follow servicemix checkstyle and pmd rules CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt, patch0702.txt, patch0720.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: (was: patch0720.txt) CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt, patch0702.txt, patch0720.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: patch0720.txt CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt, patch0702.txt, patch0720.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: (was: patch0720.txt) CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt, patch0702.txt, patch0720.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: (was: patch0720.txt) CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt, patch0702.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: patch0720.txt Could somebody review and apply patch0720.txt for me This patch: 1. config interceptors from SE and BC xbean.xml 2. load cxf bus from xbean.xml 3. end to end test which wire SE and BC together to handle external oneway/twoway/Fault request 4. verify ws-policy works with cxf BC 5. remove redundant endpoint publish in patch0702.txt CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt, patch0702.txt, patch0720.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: (was: patch0629.txt) CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: patch0702.txt Please review and apply this path which include config cxf inteceptors in xbean.xml and add endtoend test wired cxf se and bc to handle external request. The se and bc are launched from spring config(xbean.xml) with specified logging inteceptors CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt, patch0702.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: patch0629.txt This patch 1. test CXF bc work with CXF se to handle external request, return the correct Fault type defined by wsdl 2. support config interceptors in xbean.xml Since this patch depend on some changes from cxf, so need mvn -U install to build it CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt, patch0629.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: patch0629.txt CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt, patch0629.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: (was: patch0629.txt) CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: patch0627.txt patch for CXF bc to handle external cusumer request. CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated SM-939: Attachment: patch.txt I'd like to provide my first patch as the start. This patch is based on Nodet's cxf bc module, and fix compile and test failure which is caused by cxf api changed. Please review and apply this patch for me. CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
