[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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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
Re: Shared bundle repository
+1 Freeman On 2010-7-13, at 下午6:05, Guillaume Nodet wrote: I guess we're not the only projects at Apache doing that, but at least we do it the same way. I wonder if we could cooperate more closely and have a common ground for releasing such bundles and making them available to others. I think having a single point to find OSGi bundles would be a great benefit for all OSGi-fied projects at Apache and also for the downstream users. Thoughts ? Btw, I'm just starting this thread because I've seen Rick is in the process of releasing some bundles in Geronimo ... -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com -- Freeman Fang Open Source SOA: http://fusesource.com Apache Servicemix:http://servicemix.apache.org Apache Cxf: http://cxf.apache.org Apache Karaf: http://karaf.apache.org Apache Felix: http://felix.apache.org
Re: WSIT Support
For servicemix cxf bc, we support ws-security, ws-ReliableMessage, ws-policy, ws-Addressing, MTOM now Regards Freeman ArmenH wrote: Yes, thank you for replying. Please confirm whether any of the WS-* specs below are not supported. We would need a true Enterprise solution for our financial systems. Thanks again for your kind attention. WS-Trust WS-Security WS-SecureConversation WS-Federation WS-ReliableMessaging WS-AtomicTransaction WS-Coordination WS-MetadataExchange WS-Policy WS-Addressing MTOM Freeman Fang-2 wrote: From my understanding, I think the question is What's the CXF version used in servicemix? :-) Regards Freeman Bozhong Lin wrote: Just to clarify, I think CXF is used in ServiceMix version 3.2, not version 2.0.2. Regards, Bo On Nov 13, 2007 1:10 PM, Freeman Fang wrote: Yes Freeman ArmenH wrote: Thanks, Is the CXF used in ServiceMix version 2.0.2? Freeman Fang wrote: Hi, We already have servicemix-cxf-bc to leverage ws-* feature from cxf. And I also know cxf team do lots of interoperability test between cxf and WCF(including ws-* feature), if you are interested in this issue, I guess you could post this thread on cxf mailling list, where more people can answer your question. Best Regards Freeman ArmenH wrote: It appears that CXF does support most of the WS-* Has anyone used Microsoft WCF based clients/services to show full interoperability? ArmenH wrote: Does ServiceMix fully support WSIT? If not, are there plans to support it? CXF is still not fully compliant with WSIT.
[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-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.
Re: [ANNOUNCE] Apache ServiceMix 3.2 released !
The missing parent module is already in the central repo now. Cheers Freeman Freeman Fang wrote: I will fix it and upload the missing parent module soon. Freeman On 11/8/07, *Guillaume Nodet* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Freeman, it seems this bit is missing from the repo and from your staging are too. Do you have a copy locally that we could upload ? -- Forwarded message -- From: *Daryl Richter* < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> Date: Nov 8, 2007 2:15 PM Subject: Re: [ANNOUNCE] Apache ServiceMix 3.2 released ! To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Ok. So I changed the servicmix-version references in my project from "3.2-incubating-SNAPSHOT" to "3.2" and tried to rebuild, but got the following: Downloading: http://repo1.maven.org/maven2/org/apache/servicemix/ <http://repo1.maven.org/maven2/org/apache/servicemix/> serviceengines/3.2/serviceengines-3.2.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/servicemix/ parent/3.2/parent-3.2.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.servicemix ArtifactId: parent Version: 3.2 Reason: Unable to download the artifact from any repository org.apache.servicemix:parent:pom:3.2 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 58 seconds [INFO] Finished at: Thu Nov 08 08:12:31 EST 2007 [INFO] Final Memory: 4M/8M [INFO] I dumped by .m2/repository/ but same result. What am I doing wrong? Thanks! On Nov 7, 2007, at 8:43 PM, Freeman Fang wrote: > The Apache ServiceMix team is proud to announce the availability of > the 3.2 release! > > Apache ServiceMix is a TLP (Top Level Project under Apache), which > is an open source distributed Enterprise > Service Bus (ESB) > and SOA toolkit built from the ground up on the semantics and APIs > of the Java > Business Integration (JBI) specification JSR 208 and released under > the Apache > 2.0 license. > > Apache ServiceMix is lightweight and easily embeddable, has > integrated Spring > support and can be run at the edge of the network (inside a client > or server), > as a standalone ESB provider or as a service within another ESB. > You can use ServiceMix in Java SE or a Java EE application server. > > This release includes a number of important fixes and a few > enhancements. > For more information see: > * Website: http://servicemix.apache.org/ > * Release Notes: http://servicemix.apache.org/servicemix-32.html > * Mailing lists: http://servicemix.apache.org/mailing-lists.html > > If you have feedback, questions or would like to get involved in the > ServiceMix project please join the mailing lists and let us know your > thoughts. > > > The Apache ServiceMix Team > http://servicemix.apache.org/team.html > -- Daryl http://itsallsemantics.com <http://itsallsemantics.com/> "Hell, there are no rules here-- we're trying to accomplish something." -- Thomas A. Edison -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: [ANNOUNCE] Apache ServiceMix 3.2 released !
I will fix it and upload the missing parent module soon. Freeman On 11/8/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > Freeman, it seems this bit is missing from the repo and from your staging > are too. > Do you have a copy locally that we could upload ? > > -- Forwarded message -- > From: Daryl Richter <[EMAIL PROTECTED]> > Date: Nov 8, 2007 2:15 PM > Subject: Re: [ANNOUNCE] Apache ServiceMix 3.2 released ! > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > > > Ok. So I changed the servicmix-version references in my project from > "3.2-incubating-SNAPSHOT" to "3.2" and tried to rebuild, but got the > following: > > Downloading: http://repo1.maven.org/maven2/org/apache/servicemix/ > serviceengines/3.2/serviceengines-3.2.pom > 1K downloaded > Downloading: http://repo1.maven.org/maven2/org/apache/servicemix/ > parent/3.2/parent-3.2.pom > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > > GroupId: org.apache.servicemix > ArtifactId: parent > Version: 3.2 > > Reason: Unable to download the artifact from any repository > > org.apache.servicemix:parent:pom:3.2 > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > > > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 1 minute 58 seconds > [INFO] Finished at: Thu Nov 08 08:12:31 EST 2007 > [INFO] Final Memory: 4M/8M > [INFO] > -------- > > I dumped by .m2/repository/ but same result. > > What am I doing wrong? > > Thanks! > > > On Nov 7, 2007, at 8:43 PM, Freeman Fang wrote: > > > The Apache ServiceMix team is proud to announce the availability of > > the 3.2 release! > > > > Apache ServiceMix is a TLP (Top Level Project under Apache), which > > is an open source distributed Enterprise > > Service Bus (ESB) > > and SOA toolkit built from the ground up on the semantics and APIs > > of the Java > > Business Integration (JBI) specification JSR 208 and released under > > the Apache > > 2.0 license. > > > > Apache ServiceMix is lightweight and easily embeddable, has > > integrated Spring > > support and can be run at the edge of the network (inside a client > > or server), > > as a standalone ESB provider or as a service within another ESB. > > You can use ServiceMix in Java SE or a Java EE application server. > > > > This release includes a number of important fixes and a few > > enhancements. > > For more information see: > > * Website: http://servicemix.apache.org/ > > * Release Notes: http://servicemix.apache.org/servicemix-32.html > > * Mailing lists: http://servicemix.apache.org/mailing-lists.html > > > > If you have feedback, questions or would like to get involved in the > > ServiceMix project please join the mailing lists and let us know your > > thoughts. > > > > > > The Apache ServiceMix Team > > http://servicemix.apache.org/team.html > > > > > -- > Daryl > http://itsallsemantics.com > > "Hell, there are no rules here-- we're trying to accomplish something." > -- Thomas A. Edison > > > > > > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ >
[ANNOUNCE] Apache ServiceMix 3.2 released !
The Apache ServiceMix team is proud to announce the availability of the 3.2 release! Apache ServiceMix is a TLP (Top Level Project under Apache), which is an open source distributed Enterprise Service Bus (ESB) and SOA toolkit built from the ground up on the semantics and APIs of the Java Business Integration (JBI) specification JSR 208 and released under the Apache 2.0 license. Apache ServiceMix is lightweight and easily embeddable, has integrated Spring support and can be run at the edge of the network (inside a client or server), as a standalone ESB provider or as a service within another ESB. You can use ServiceMix in Java SE or a Java EE application server. This release includes a number of important fixes and a few enhancements. For more information see: * Website: http://servicemix.apache.org/ * Release Notes: http://servicemix.apache.org/servicemix-32.html * Mailing lists: http://servicemix.apache.org/mailing-lists.html If you have feedback, questions or would like to get involved in the ServiceMix project please join the mailing lists and let us know your thoughts. The Apache ServiceMix Team http://servicemix.apache.org/team.html
[VOTE RESULT] Release ServiceMix 3.2
The vote is now over with five +1 votes, and no other votes. Cheers Freeman
Re: [VOTE] Release ServiceMix 3.2
Hi, This missing jar is needed for org.drools.drools-compiler, which is used for our servicemix-drools service engine. I am not sure why it's removed from pub maven repos recently, it's must be there a couple of days ago. But you can find it from http://dl.easyjf.com/maven2/commons-jci/commons-jci-eclipse/3.2.0.666/ Best Regards Freeman Freeman Fang wrote: It's weird. I can pass build on my machine. What's your settings.xml of mvn looks like? Thanks Freeman Alan D. Cabrera wrote: Step 2 in the build fails: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.commons:commons-jci-eclipse:jar:3.2.0.666 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.commons -DartifactId=commons-jci-eclipse \ -Dversion=3.2.0.666 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.commons -DartifactId=commons-jci-eclipse \ -Dversion=3.2.0.666 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.servicemix:servicemix-drools:jbi-component:3.2 2) org.drools:drools-compiler:jar:3.0.3 3) org.apache.commons:commons-jci-eclipse:jar:3.2.0.666 -- 1 required artifact is missing. for artifact: org.apache.servicemix:servicemix-drools:jbi-component:3.2 from the specified remote repositories: central (http://repo1.maven.org/maven2), servicemix-m2-repo (http://svn.apache.org/repos/asf/incubator/servicemix/m2-repo), apache.snapshots (http://svn.apache.org/maven-snapshot-repository), codehaus (http://repository.codehaus.org), apache-incubating (http://people.apache.org/repo/m2-incubating-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), jboss (http://repository.jboss.com/maven2) Regards, Alan On Nov 6, 2007, at 2:24 AM, Guillaume Nodet wrote: +1, sorry i was in vacation and offline most of the time... On 10/26/07, Freeman Fang <[EMAIL PROTECTED]> wrote: Hi All, I have uploaded a version of ServiceMix 3.2 for you to review. See http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.2 for all the links and release notes. [ ] +1 Release ServiceMix 3.2 [ ] ± 0 [ ] -1 Do not release ServiceMix 3.2 Cheers Freeman --Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: [VOTE] Release ServiceMix 3.2
It's weird. I can pass build on my machine. What's your settings.xml of mvn looks like? Thanks Freeman Alan D. Cabrera wrote: Step 2 in the build fails: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.commons:commons-jci-eclipse:jar:3.2.0.666 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.commons -DartifactId=commons-jci-eclipse \ -Dversion=3.2.0.666 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.commons -DartifactId=commons-jci-eclipse \ -Dversion=3.2.0.666 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.servicemix:servicemix-drools:jbi-component:3.2 2) org.drools:drools-compiler:jar:3.0.3 3) org.apache.commons:commons-jci-eclipse:jar:3.2.0.666 -- 1 required artifact is missing. for artifact: org.apache.servicemix:servicemix-drools:jbi-component:3.2 from the specified remote repositories: central (http://repo1.maven.org/maven2), servicemix-m2-repo (http://svn.apache.org/repos/asf/incubator/servicemix/m2-repo), apache.snapshots (http://svn.apache.org/maven-snapshot-repository), codehaus (http://repository.codehaus.org), apache-incubating (http://people.apache.org/repo/m2-incubating-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), jboss (http://repository.jboss.com/maven2) Regards, Alan On Nov 6, 2007, at 2:24 AM, Guillaume Nodet wrote: +1, sorry i was in vacation and offline most of the time... On 10/26/07, Freeman Fang <[EMAIL PROTECTED]> wrote: Hi All, I have uploaded a version of ServiceMix 3.2 for you to review. See http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.2 for all the links and release notes. [ ] +1 Release ServiceMix 3.2 [ ] ± 0 [ ] -1 Do not release ServiceMix 3.2 Cheers Freeman --Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: [VOTE] Release ServiceMix 3.2
my +1 Btw, this vote will be closed by end of today. cheers Freeman On 11/6/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > +1, sorry i was in vacation and offline most of the time... > > On 10/26/07, Freeman Fang <[EMAIL PROTECTED]> wrote: > > > > Hi All, > > > > I have uploaded a version of ServiceMix 3.2 for you to review. See > > http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.2 > > for all the links and release notes. > > > > [ ] +1 Release ServiceMix 3.2 > > [ ] ± 0 > > [ ] -1 Do not release ServiceMix 3.2 > > > > Cheers > > > > Freeman > > > > > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ >
[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 > xmlns:ns1="http://cxf.apache.org/bindings/jbi";> xmlns:ns2="http://servicemix.apache.org/samples/wsdl-first/types";> xmlns=""> > but the soap binding fault is > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>soap:ServerFault > occured xmlns:ns2="http://servicemix.apache.org/samples/wsdl-first/types";> xmlns="" xmlns="" > /> > 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] 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-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.
Re: Problems with service mix dependencies using maven
Hi, As Guillaume point out, our release to http://people.apache.org/repo/m2-ibiblio-rsync-repository already synchronized by http://repo1.maven.org/maven2/org/apache/servicemix now, so it's unnecessary to change your maven settings.xml and I believe you can build successfully. Cheers Freeman Freeman Fang wrote: > > Hi, > > Since srevicemic 3.1.2 is released after graduate, so now you should find > 3.1.2 artifacts from > http://people.apache.org/repo/m2-ibiblio-rsync-repository > Would you please add this url to your maven settings.xml, this should > resolve your build problem. > > Best Regards > Freeman > > > > > > Eduardo de Vera wrote: >> >> Hello, >> >> First of all congratulations for being graduated as a top level proyecto >> at >> the ASF. It's was about time considering all the efforts the whole group >> has >> done for this piece of fine work. >> >> I dont know if I should post a jira about this issue I found following >> the >> Apache Servicemix Tutorial. I have a problem with the maven dependencies >> that belong to the tutorial application. I dont know if this is due to a >> Maven bug or a problem with the pom files. >> >> The error I am getting when I try to build the service assembly is: >> >> [INFO] Scanning for projects... >> [INFO] Reactor build order: >> [INFO] Tutorial >> [INFO] Tutorial :: File SU >> [INFO] Tutorial :: SA >> [INFO] >> >> [INFO] Building Tutorial >> [INFO]task-segment: [install] >> [INFO] >> >> [INFO] [site:attach-descriptor] >> [INFO] [install:install] >> [INFO] Installing >> /Users/edevera/Documents/desarrollo/servicemix-tutorial-1/parent/pom.xml >> to >> /Users/edevera/.m2/repository/org/apache/servicemix/tutorial/parent/1.0-SNAPSHOT/parent- >> 1.0-SNAPSHOT.pom >> [INFO] >> >> [INFO] Building Tutorial :: File SU >> [INFO]task-segment: [install] >> [INFO] >> >> [INFO] [resources:resources] >> [INFO] Using default encoding to copy filtered resources. >> Downloading: >> http://people.apache.org/repo/m2-incubating-repository/wss4j/wss4j/1.5.0/wss4j-1.5.0.pom >> Downloading: >> http://repository.jboss.com/maven2//wss4j/wss4j/1.5.0/wss4j-1.5.0.pom >> Downloading: >> http://people.apache.org/repo/m2-incubating-repository/wss4j/wss4j/1.5.0/wss4j-1.5.0.pom >> Downloading: >> http://repo1.maven.org/maven2/wss4j/wss4j/1.5.0/wss4j-1.5.0.pom >> Downloading: >> http://people.apache.org/repo/m2-incubating-repository/org/opensaml/opensaml/1.1/opensaml-1.1.pom >> Downloading: >> http://repository.jboss.com/maven2//org/opensaml/opensaml/1.1/opensaml-1.1.pom >> Downloading: >> http://people.apache.org/repo/m2-incubating-repository/org/opensaml/opensaml/1.1/opensaml-1.1.pom >> Downloading: >> http://repo1.maven.org/maven2/org/opensaml/opensaml/1.1/opensaml-1.1.pom >> Downloading: >> http://people.apache.org/repo/m2-incubating-repository/xml-security/xmlsec/1.3.0/xmlsec-1.3.0.pom >> Downloading: >> http://repository.jboss.com/maven2//xml-security/xmlsec/1.3.0/xmlsec-1.3.0.pom >> Downloading: >> http://people.apache.org/repo/m2-incubating-repository/xml-security/xmlsec/1.3.0/xmlsec-1.3.0.pom >> Downloading: >> http://repo1.maven.org/maven2/xml-security/xmlsec/1.3.0/xmlsec-1.3.0.pom >> Downloading: >> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix-common/3.1.2/servicemix-common-3.1.2.jar >> Downloading: >> http://repository.jboss.com/maven2//org/apache/servicemix/servicemix-common/3.1.2/servicemix-common-3.1.2.jar >> Downloading: >> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix-common/3.1.2/servicemix-common-3.1.2.jar >> Downloading: >> http://www.ibiblio.org/maven2/org/apache/servicemix/servicemix-common/3.1.2/servicemix-common-3.1.2.jar >> Downloading: >> http://svn.apache.org/repos/asf/incubator/servicemix/m2-repo/org/apache/servicemix/servicemix-common/3.1.2/servicemix-common-3.1.2.jar >> Downloading: >> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix-shared/3.1.2/servicemix-shared-3.1.2.jar >> Downloading: >> http://repository.jboss.com/maven2//org/apache/servicemix/servicemix-shared/3.1.2/s
[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: > > > > > > > -- 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: > > > > > > > -- 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: > > > > > type="test.Echo" /> > > > > > 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: > > > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release ServiceMix 3.1.2
My +1 Freeman Freeman Fang wrote: > > Hi All, > > I have uploaded a version of ServiceMix 3.1.2 for you to review. See > http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.1.2 > for all the links and release notes. > > [ ] +1 Release ServiceMix 3.1.2 > [ ] ± 0 > [ ] -1 Do not release ServiceMix 3.1.2 > > Cheers > > Freeman > > -- View this message in context: http://www.nabble.com/-VOTE--Release-ServiceMix-3.1.2-tf4491617s12049.html#a12823200 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: [VOTE] Release ServiceMix 3.1.2
Hi Bruce, It's fine on my machine. I guess it caused by the repo mirror settings are different in our maven's settings.xml. What your settings.xml looks like? Best Regards Freeman Bruce Snyder wrote: On 9/20/07, Freeman Fang <[EMAIL PROTECTED]> wrote: Hi All, I have uploaded a version of ServiceMix 3.1.2 for you to review. See http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.1.2 for all the links and release notes. [ ] +1 Release ServiceMix 3.1.2 [ ] ± 0 [ ] -1 Do not release ServiceMix 3.1.2 While the binary starts up just fine, I cannot get a build from source to complete successfully when working with a clean Maven repo. Currently a clean build failing on the step1 profile with the following: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.geronimo.specs:geronimo-servlet_2.4_spec:jar:1.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.specs -DartifactId=geronimo-servlet_2.4_spec \ -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.specs -DartifactId=geronimo-servlet_2.4_spec \ -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.servicemix:servicemix-components:jar:3.1.2 2) org.apache.geronimo.specs:geronimo-servlet_2.4_spec:jar:1.1 2) janino:janino:jar:2.3.2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=janino -DartifactId=janino \ -Dversion=2.3.2 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=janino -DartifactId=janino \ -Dversion=2.3.2 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.servicemix:servicemix-components:jar:3.1.2 2) janino:janino:jar:2.3.2 3) jivesoftware:smackx:jar:2.2.1 Try downloading the file manually from: http://www.jivesoftware.org/smack/ Then, install it using the command: mvn install:install-file -DgroupId=jivesoftware -DartifactId=smackx \ -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=jivesoftware -DartifactId=smackx \ -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.servicemix:servicemix-components:jar:3.1.2 2) jivesoftware:smackx:jar:2.2.1 4) javax.activation:activation:jar:1.1 Try downloading the file manually from: https://maven-repository.dev.java.net/nonav/repository/javax.activation/jars/activation-1.1.jar Then, install it using the command: mvn install:install-file -DgroupId=javax.activation -DartifactId=activation \ -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.activation -DartifactId=activation \ -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.servicemix:servicemix-components:jar:3.1.2 2) org.codehaus.xfire:xfire-all:jar:1.2.5 3) org.codehaus.xfire:xfire-core:jar:1.2.5 4) javax.activation:activation:jar:1.1 -- 4 required artifacts are missing. for artifact: org.apache.servicemix:servicemix-components:jar:3.1.2 from the specified remote repositories: central (http://www.ibiblio.org/maven2), servicemix-m2-repo (http://svn.apache.org/repos/asf/incubator/servicemix/m2-repo), apache.snapshots (http://svn.apache.org/maven-snapshot-repository), apache-incubating (http://people.apache.org/repo/m2-incubating-repository), codehaus-snapshots (http://repository.codehaus.org) Bruce
Re: How to get the ComponentContext in CXF SU?
Sure. https://issues.apache.org/activemq/browse/SM-1060 Cheers Freeman Guillaume Nodet wrote: Freeman, I think being able to inject the endpoint DeliveryChannel and ComponentContext is a really important feature. Can you raise a JIRA for that please ? On 9/20/07, Freeman Fang <[EMAIL PROTECTED]> wrote: Hi Ryan, Attachment is the schema for servicemix-cxf-se. So far the cxf-se is not exactly same as jsr-181 service engine, so I think now we don't support it. Also I investigate the jsr-181 client proxy issue you mentioned in previous mail, we don't support it in cxf se neither, sorry for misleading previous response. The main purpose we add cxf-bc and cxf-se is leverage cxf ws-* features. You can see the tests and examples how the typical scenario looks like. If you need any feature we don't support now, please fill jira issue. Best Regards Freeman Ryan Moquin wrote: I'm still having a hard time figuring out how to replicated my interservice communication through the bus between two CXF services in Servicemix. My latest problem is that this doesn't appear to work: According to the servicemix docs, it says I should be able to reference the context which was created as a parent bean. Is there an xsd I can look at for cxfse? I need to figure out how I can do interservice communication with it over the bus still.
[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] 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-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.
Re: question about servicemix 3.1.2 release
Thanks Guillaume Cheers Freeman Guillaume Nodet wrote: I have updated the releasing notes to something that I hope will work ;-) See http://cwiki.apache.org/confluence/display/SM/Release+Guide If you have any questions, just yell ! On 9/12/07, Nodet Guillaume <[EMAIL PROTECTED]> wrote: On Sep 12, 2007, at 8:46 AM, Freeman Fang wrote: Hi all, When are we going to release servicemix 3.1.2? As a new commiter in servicemix team, I'd like to know how is the release process looks like. If possible, shall I be release manager of this time? :-) Yeah of course you can :-) There are some instructions available at http://incubator.apache.org/servicemix/release-guide.html but these are a bit outdated, so we'll have to update those (and maven can not really be used for creating the release)... Let me have a breakfast and write something more accurate... Any suggestion is appreciated. Best Regards Freeman -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[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: 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.
Re: [jira] Updated: (SM-939) CXF based Service Engine and Bnding Component
Hi All, Can someone review and apply this patch? patch0629.txt Thanks very much Freeman Freeman Fang (JIRA) wrote: [ 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
[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.
Re: Hello All
Thanks Nodet.
Freeman
Guillaume Nodet wrote:
The patch was good (except for a few tabs that slipped in) so I have
checked
it in.
Thanks !
On 6/25/07, Freeman Fang <[EMAIL PROTECTED]> wrote:
Ok, it's done.
Cheers
Freeman
Guillaume Nodet wrote:
> Could you please attach your patch to a JIRA issue ?
> You can reuse the existing one:
> http://issues.apache.org/activemq/browse/SM-939
> Thanks !
>
> On 6/25/07, Freeman Fang <[EMAIL PROTECTED]> wrote:
>>
>> Hi All,
>>
>> 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.
>>
>> Tons of thanks
>>
>> Freeman
>>
>> Freeman Fang wrote:
>> > Hi all,
>> >
>> > I am from apache cxf team.
>> >
>> > I am going to add cxf binding component into servicemix which can
>> > support ws-*.
>> >
>> > In next several weeks there would be questions and patches.
>> >
>> > Thanks in advance for answering my questions and reviewing and
>> > applying the patches.
>> >
>> > Thanks again
>> >
>> > Freeman
>> >
>>
>>
>> Index:
>>
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiOperationInterceptor.java
>>
>> ===
>> ---
>>
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiOperationInterceptor.java
>>
>> (revision 550382)
>> +++
>>
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiOperationInterceptor.java
>>
>> (working copy)
>> @@ -37,8 +37,7 @@
>> public class JbiOperationInterceptor extends
>> AbstractPhaseInterceptor {
>>
>> public JbiOperationInterceptor() {
>> -super();
>> -setPhase(Phase.UNMARSHAL);
>> + super(Phase.UNMARSHAL);
>> addAfter(URIMappingInterceptor.class.getName());
>> }
>>
>> Index:
>>
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiInWsdl1Interceptor.java
>>
>> ===
>> ---
>>
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiInWsdl1Interceptor.java
>>
>> (revision 550382)
>> +++
>>
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiInWsdl1Interceptor.java
>>
>> (working copy)
>> @@ -37,6 +37,7 @@
>> import org.apache.cxf.binding.soap.model.SoapBindingInfo;
>> import org.apache.cxf.binding.soap.model.SoapHeaderInfo;
>> import org.apache.cxf.endpoint.Endpoint;
>> +import org.apache.cxf.headers.Header;
>> import org.apache.cxf.interceptor.Fault;
>> import org.apache.cxf.message.Exchange;
>> import org.apache.cxf.message.Message;
>> @@ -56,7 +57,7 @@
>> public class JbiInWsdl1Interceptor extends AbstractSoapInterceptor {
>>
>> public JbiInWsdl1Interceptor() {
>> -setPhase(Phase.UNMARSHAL);
>> +super(Phase.UNMARSHAL);
>> addAfter(JbiOperationInterceptor.class.getName());
>> }
>>
>> @@ -104,7 +105,7 @@
>> }
>> Element body = getBodyElement(message);
>> List headers = wsdlMessage.getExtensors(
>> SoapHeaderInfo.class);
>> -Element headerElement = message.getHeaders(Element.class);
>> +List headerElement = message.getHeaders();
>> List parts = new ArrayList();
>> for (MessagePartInfo part : wsdlMessage.getMessageParts()) {
>> if ("document".equals(style)) {
>> @@ -129,10 +130,10 @@
>> if (headers != null) {
>> for (SoapHeaderInfo header : headers) {
>> MessagePartInfo part = header.getPart();
>> -Element param = findHeader(headerElement, part);
>> +Header param = findHeader(headerElement, part);
>> int idx = part.getIndex();
>> QName element = part.getElementQName();
>> -Element hdr = getHeaderElement(message, element);
>> +Header hdr = getHeaderElement(message, element);
>> if (hdr ==
[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.
Re: Hello All
Ok, it's done.
Cheers
Freeman
Guillaume Nodet wrote:
Could you please attach your patch to a JIRA issue ?
You can reuse the existing one:
http://issues.apache.org/activemq/browse/SM-939
Thanks !
On 6/25/07, Freeman Fang <[EMAIL PROTECTED]> wrote:
Hi All,
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.
Tons of thanks
Freeman
Freeman Fang wrote:
> Hi all,
>
> I am from apache cxf team.
>
> I am going to add cxf binding component into servicemix which can
> support ws-*.
>
> In next several weeks there would be questions and patches.
>
> Thanks in advance for answering my questions and reviewing and
> applying the patches.
>
> Thanks again
>
> Freeman
>
Index:
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiOperationInterceptor.java
===
---
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiOperationInterceptor.java
(revision 550382)
+++
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiOperationInterceptor.java
(working copy)
@@ -37,8 +37,7 @@
public class JbiOperationInterceptor extends
AbstractPhaseInterceptor {
public JbiOperationInterceptor() {
-super();
-setPhase(Phase.UNMARSHAL);
+ super(Phase.UNMARSHAL);
addAfter(URIMappingInterceptor.class.getName());
}
Index:
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiInWsdl1Interceptor.java
===
---
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiInWsdl1Interceptor.java
(revision 550382)
+++
deployables/bindingcomponents/servicemix-cxf-bc/src/main/java/org/apache/servicemix/cxfbc/interceptors/JbiInWsdl1Interceptor.java
(working copy)
@@ -37,6 +37,7 @@
import org.apache.cxf.binding.soap.model.SoapBindingInfo;
import org.apache.cxf.binding.soap.model.SoapHeaderInfo;
import org.apache.cxf.endpoint.Endpoint;
+import org.apache.cxf.headers.Header;
import org.apache.cxf.interceptor.Fault;
import org.apache.cxf.message.Exchange;
import org.apache.cxf.message.Message;
@@ -56,7 +57,7 @@
public class JbiInWsdl1Interceptor extends AbstractSoapInterceptor {
public JbiInWsdl1Interceptor() {
-setPhase(Phase.UNMARSHAL);
+super(Phase.UNMARSHAL);
addAfter(JbiOperationInterceptor.class.getName());
}
@@ -104,7 +105,7 @@
}
Element body = getBodyElement(message);
List headers = wsdlMessage.getExtensors(
SoapHeaderInfo.class);
-Element headerElement = message.getHeaders(Element.class);
+List headerElement = message.getHeaders();
List parts = new ArrayList();
for (MessagePartInfo part : wsdlMessage.getMessageParts()) {
if ("document".equals(style)) {
@@ -129,10 +130,10 @@
if (headers != null) {
for (SoapHeaderInfo header : headers) {
MessagePartInfo part = header.getPart();
-Element param = findHeader(headerElement, part);
+Header param = findHeader(headerElement, part);
int idx = part.getIndex();
QName element = part.getElementQName();
-Element hdr = getHeaderElement(message, element);
+Header hdr = getHeaderElement(message, element);
if (hdr == null) {
throw new Fault(new Exception("Missing required
header element: "
+ QNameUtil.toString(element)));
@@ -190,7 +191,7 @@
}
}
-protected Element getHeaderElement(SoapMessage message, QName
name) {
+protected Header getHeaderElement(SoapMessage message, QName
name) {
Exchange exchange = message.getExchange();
BindingOperationInfo bop = exchange.get(
BindingOperationInfo.class);
if (bop.isUnwrapped()) {
@@ -206,11 +207,11 @@
if (headers == null || headers.size() == 0) {
return null;
}
-Element headerElement = message.getHeaders(Element.class);
+List headerElement = message.getHeaders();
for (SoapHeaderInfo header : headers) {
if (header.getPart().getElementQName().equals(name)) {
MessagePartInfo mpi = header.getPart();
-Element param = findHeader(headerElement, mpi);
+Header param = findHeader(headerElement, mpi);
return param;
}
}
@@ -236,18 +237,16 @@
}
}
-private static El
