Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject
+1 (binding as Karaf PMC member) Freeman On Wed, Jan 18, 2023 at 5:03 AM Jean-Baptiste Onofré wrote: > Hi guys, > > The Apache Camel community proposed to move Camel Karaf to the Apache > Karaf project (as a new subproject). > > As a reminder, Camel Karaf provides: > - support Camel Contexts/Routes as OSGi services (camel-core-osgi) > - Camel components specific to OSGi and Karaf (camel-blueprint, camel-scr, > ...) > - wrapping of Camel components as Karaf features (providing a features > repository XML) > > I think there are a bunch of users using camel-karaf, so, from a > community perspective, it would be great to maintain it. > Furthermore, I already have some ideas to improve karaf-camel, like > avoiding to wrap each Camel component as an OSGi bundle, but instead > creating a kind of Uber jar to simplify deployment and have more > reliable behavior. > > Concretely, accepting camel-karaf as Karaf subproject would mean: > - maintain the existing code, and improving it, preparing kind of > roadmap for camel-karaf > - deal with Camel versions and components (and all difficulties that > it could cause in an OSGi context :) ) > - maintain camel-karaf specific documentation > - vote for the releases (the PMC members would be the Karaf ones, so > binding vote from Karaf PMC members) > > I submit accepting camel-karaf (so karaf-camel :)) as new Karaf > subproject to your vote: > > Please vote to approve this release: > [ ] +1 Approve camel-karaf as new Karaf subproject > [ ] -1 Don't approve camel-karaf as new Karaf subproject (please > provide specific comments) > > This vote will be open for at least 72 hours. > > Thanks, > Regards > JB >
Re: [VOTE] Release Apache Camel 3.20.0 (LTS)
+1(non-binding) Thanks all! Freeman On Sat, Dec 17, 2022 at 6:35 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.20.0, a new LTS release with > 205 improvements and fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352266=12311211 > > == Apache Camel 3.20.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1506/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1506/org/apache/camel/apache-camel/3.20.0/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.20.0 > > == Apache Camel Spring Boot 3.20.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1508/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.20.0 > > == Apache Camel Karaf 3.20.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1509/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.20.0 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.20.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor >
Re: [VOTE] Release Apache Camel 3.14.4 (LTS)
+1 (non-binding) Thanks! Freeman On Sun, Jun 26, 2022 at 12:51 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.14.4, a new patch release > with 23 fixes and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351679=12311211 > > == Apache Camel 3.14.4 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1441/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1441/org/apache/camel/apache-camel/3.14.4/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.14.4 > > == Apache Camel Spring Boot 3.14.4 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1442/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.14.4 > > == Apache Camel Karaf 3.14.4 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1443/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.14.4 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.14.4 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor >
Re: [VOTE] Release Apache Camel Quarkus 2.8.0-M1
+1 (non-binding) Thanks! Freeman On Wed, Mar 9, 2022 at 5:03 AM Alexandre Gallice wrote: > Hi everyone, > > This is a vote to release Apache Camel Quarkus 2.8.0-M1. > > Highlights: > > * Camel 3.15.0 > * Quarkus 2.7.3.Final > * A JVM extension more (azure-servicebus) > * More native support (mybatis) > * Some deprecated extensions (spark, ahc, ahc-ws) > * Continuous Integration build on Windows > * Fixed issues: > https://github.com/apache/camel-quarkus/milestone/24?closed=1 > > * All commits: > https://github.com/apache/camel-quarkus/compare/2.7.0...2.8.0-M1 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1416 > > Tag: > https://github.com/apache/camel-quarkus/releases/tag/2.8.0-M1 > > Source release package: > > https://repository.apache.org/content/repositories/orgapachecamel-1416/org/apache/camel/quarkus/camel-quarkus/2.8.0-M1/camel-quarkus-2.8.0-M1-src.zip > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binary as Apache Camel Quarkus 2.8.0-M1 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Alex >
Re: [VOTE] Release Apache Camel 3.11.6 (LTS)
+1 (non-binding) Thanks! Freeman On Thu, Mar 10, 2022 at 5:13 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.11.6, a new patch release > with 23 fixes and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351167=12311211 > > == Apache Camel 3.11.6 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1417/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1417/org/apache/camel/apache-camel/3.11.6/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.11.6 > > == Apache Camel Spring Boot 3.11.6 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1418/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.11.6 > > == Apache Camel Karaf 3.11.6 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1419/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.11.6 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.11.6 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor >
Re: [VOTE] Release Apache Camel 3.14.2 (LTS)
+1 (non-binding) Thanks! Freeman On Mon, Mar 7, 2022 at 4:47 AM Zoran Regvart wrote: > +1 (binding) > > Thanks Gregor! > > On Fri, Mar 4, 2022 at 1:23 PM Gregor Zurowski > wrote: > > > > Hi Everyone: > > > > This is a vote to release Apache Camel 3.14.2, a new patch release > > with 27 fixes and improvements. > > > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351266=12311211 > > > > == Apache Camel 3.14.2 == > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1413/ > > > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1413/org/apache/camel/apache-camel/3.14.2/ > > > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.14.2 > > > > == Apache Camel Spring Boot 3.14.2 == > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1414/ > > > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.14.2 > > > > == Apache Camel Karaf 3.14.2 == > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1415/ > > > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.14.2 > > > > Please test this release candidate and cast your vote: > > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > > Karaf 3.14.2 > > [ ] -1 Veto the release (provide specific comments) > > > > The vote is open for at least 72 hours. > > > > Thanks, > > Gregor > > > > -- > Zoran Regvart >
Re: [VOTE] Release Apache Camel 3.15.0
+1 (non-binding) Thanks! Freeman On Tue, Feb 1, 2022 at 1:40 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.15.0, a new release with 217 > new features and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350874=12311211 > > == Apache Camel 3.15.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1407/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1407/org/apache/camel/apache-camel/3.15.0/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.15.0 > > == Apache Camel Spring Boot 3.15.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1408/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.15.0 > > == Apache Camel Karaf 3.15.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1409/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.15.0 > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.15.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor >
Re: [VOTE] Release Apache Camel Quarkus 2.7.0
+1 (non-binding) Thanks James! Freeman On Fri, Jan 28, 2022 at 4:37 AM James Netherton wrote: > Hi everyone, > > This is a vote to release Apache Camel Quarkus 2.7.0. > > Highlights: > > * Camel 3.14.1 > * Quarkus 2.7.0.Final > * Fixed issues: > https://github.com/apache/camel-quarkus/milestone/23?closed=1 > * All commits: > https://github.com/apache/camel-quarkus/compare/2.6.0...2.7.0 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1405 > > Tag: > https://github.com/apache/camel-quarkus/releases/tag/2.7.0 > > Source release package: > > https://repository.apache.org/content/repositories/orgapachecamel-1405/org/apache/camel/quarkus/camel-quarkus/2.7.0/camel-quarkus-2.7.0-src.zip > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binary as Apache Camel Quarkus 2.7.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > > James >
Re: [VOTE] Release Apache Camel Quarkus 2.3.0
+1 (non-binding) Thanks Zineb! Freeman On Fri, Oct 1, 2021 at 3:55 PM Zineb Bendhiba wrote: > Hello, > > This is a vote to release Apache Camel Quarkus 2.3.0. > > Highlights: > > * Quarkus 2.3.0.Final > * Fixed issues: > https://github.com/apache/camel-quarkus/milestone/19?closed=1 > * All commits: > https://github.com/apache/camel-quarkus/compare/2.2.0...2.3.0 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1365/ > > Tag: > https://github.com/apache/camel-quarkus/releases/tag/2.3.0 > > Source release package: > > > https://repository.apache.org/content/repositories/orgapachecamel-1365/org/apache/camel/quarkus/camel-quarkus/2.3.0/camel-quarkus-2.3.0-src.zip > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binary as Apache Camel Quarkus 2.3.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > > -- > Zineb >
Re: [VOTE] Release Apache Camel 3.7.6 (LTS)
+1 (non-binding) Thanks! Freeman On Thu, Sep 30, 2021 at 4:18 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.7.6 (with Apache Camel Spring > Boot and Apache Camel Karaf), a new minor release with 15 improvements > and fixes. > > This email contains the actual repository links. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350411=12311220 > > == Apache Camel 3.7.6 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1362/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1362/org/apache/camel/apache-camel/3.7.6/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.7.6 > > == Apache Camel Spring Boot 3.7.6 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1363/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.7.6 > > == Apache Camel Karaf 3.7.6 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1364/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.7.6 > > Please test this release candidate and cast your vote. > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.7.6 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor >
Re: [VOTE] Release Apache Camel 3.12.0
+1(non-binding) Thanks! Freeman On Wed, Sep 29, 2021 at 3:58 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.12.0, a new release with 206 > new features and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350283=12311211 > > == Apache Camel 3.12.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1359/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1359/org/apache/camel/apache-camel/3.12.0/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.12.0 > > == Apache Camel Spring Boot 3.12.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1360/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.12.0 > > == Apache Camel Karaf 3.12.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1361/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.12.0 > > Please test this release candidate and cast your vote. > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.12.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor >
Re: [VOTE] Release Apache Camel Quarkus 2.0.0
+1 (non-binding) Thanks Peter! Freeman On Fri, Jun 25, 2021 at 8:36 AM Peter Palaga wrote: > Hi, > > This is a vote to release Apache Camel Quarkus 2.0.0. > > This stable release comes after two milestone releases. > > Highlights: > > * Camel 3.11.0 (add its staging directory if you want to test) > * Quarkus 2.0.0.Final > * Fixed issues: >https://github.com/apache/camel-quarkus/milestone/15?closed=1 > * All commits: >* Since M2 > https://github.com/apache/camel-quarkus/compare/2.0.0-M2...2.0.0 >* Since 1.8.1 > https://github.com/apache/camel-quarkus/compare/1.8.1...2.0.0 > * Migration guide: > https://camel.apache.org/camel-quarkus/latest/migration-guide/2.0.0.html > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1340 > > Tag: https://github.com/apache/camel-quarkus/releases/tag/2.0.0 > > Source release package: > > https://repository.apache.org/content/repositories/orgapachecamel-1340/org/apache/camel/quarkus/camel-quarkus/2.0.0/camel-quarkus-2.0.0-src.zip > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binaries as Apache Camel Quarkus 2.0.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Many thanks to all contributors! > > -- Peter > >
Re: [VOTE] Release Apache Camel 3.11.0 (LTS)
+1 (non-binding) Thanks! Freeman On Wed, Jun 23, 2021 at 2:46 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.11.0, a new LTS release with > 101 improvements and fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350096=12311211 > > == Apache Camel 3.11.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1336/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1336/org/apache/camel/apache-camel/3.11.0/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.11.0 > > == Apache Camel Spring Boot 3.11.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1337/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.11.0 > > == Apache Camel Karaf 3.11.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1338/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.11.0 > > Please test this release candidate and cast your vote. > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.11.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor >
Re: [VOTE] Release Apache Camel Quarkus 2.0.0-M2
+1(non-bindng) Thanks Peter! Freeman On Thu, Jun 10, 2021 at 10:20 AM Peter Palaga wrote: > Hi, > > This is a vote to release Apache Camel Quarkus 2.0.0-M1. > > It is another milestone release based on Camel 3.10.0 and Quarkus > 2.0.0.CR3 to allow testing and gather feedback. > > Highlights: > > * Fixed issues: >https://github.com/apache/camel-quarkus/milestone/16?closed=1 > * All commits: >https://github.com/apache/camel-quarkus/compare/2.0.0-M1...2.0.0-M2 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1325 > > Tag: https://github.com/apache/camel-quarkus/releases/tag/2.0.0-M2 > > Source release package: > > https://repository.apache.org/content/repositories/orgapachecamel-1325/org/apache/camel/quarkus/camel-quarkus/2.0.0-M2/camel-quarkus-2.0.0-M2-src.zip > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binaries as Apache Camel Quarkus 2.0.0-M2 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 48 hours. > > Many thanks to all contributors! > > -- Peter > >
Re: [camel] branch camel-3.8.x updated: [CAMEL-16063]don't start camel context if event is from the self management ApplicationContext
Got it, thanks for the clarification!
Freeman
On Tue, Mar 2, 2021 at 9:25 AM Andrea Cosentino wrote:
> This is not needed, 3.8.x won't be released anymore, it's not an LTS. No
> need to revert, but just to avoid confusion.
>
> Il giorno mar 2 mar 2021 alle ore 15:19 ha scritto:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > ffang pushed a commit to branch camel-3.8.x
> > in repository https://gitbox.apache.org/repos/asf/camel.git
> >
> >
> > The following commit(s) were added to refs/heads/camel-3.8.x by this
> push:
> > new 7ef2913 [CAMEL-16063]don't start camel context if event is from
> > the self management ApplicationContext
> > 7ef2913 is described below
> >
> > commit 7ef2913089f6f5307ad2d75092f0e54421892928
> > Author: Freeman Fang
> > AuthorDate: Tue Mar 2 09:18:52 2021 -0500
> >
> > [CAMEL-16063]don't start camel context if event is from the self
> > management ApplicationContext
> > ---
> > .../java/org/apache/camel/spring/CamelContextFactoryBean.java | 8
> >
> > 1 file changed, 8 insertions(+)
> >
> > diff --git
> >
> a/components/camel-spring/src/main/java/org/apache/camel/spring/CamelContextFactoryBean.java
> >
> b/components/camel-spring/src/main/java/org/apache/camel/spring/CamelContextFactoryBean.java
> > index e91072e..43f4529 100644
> > ---
> >
> a/components/camel-spring/src/main/java/org/apache/camel/spring/CamelContextFactoryBean.java
> > +++
> >
> b/components/camel-spring/src/main/java/org/apache/camel/spring/CamelContextFactoryBean.java
> > @@ -462,6 +462,14 @@ public class CamelContextFactoryBean extends
> > AbstractCamelContextFactoryBean > // being started/refreshed, there could be a race condition with
> > // other ApplicationListeners that react to
> > // ContextRefreshedEvent but this is the best that we can do
> > +if (event.getSource() instanceof ApplicationContext) {
> > +ApplicationContext appCtx = (ApplicationContext)
> > event.getSource();
> > +if (appCtx.getId().equals("application:management")) {
> > +//don't start camel context if
> > +//event is from the self management ApplicationContext
> > +return;
> > +}
> > +}
> > start();
> > }
> >
> >
> >
>
Re: [camel] branch master updated: [CAMEL-15738]camel-fastjson|camel-fhir|camel-gson|camel-jackson|camel-jacksonxml|camel-jaxb|camel-xstream doc mismatch the value in src code
Thanks Andrea! Reverted the commit, and please see my questions below https://issues.apache.org/jira/browse/CAMEL-15738?focusedCommentId=17219130=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17219130 Freeman On Thu, Oct 22, 2020 at 11:18 AM Andrea Cosentino wrote: > This needs to be changed at javadoc level, the documentation is > autogenerated > > Il gio 22 ott 2020, 17:10 ha scritto: > > > This is an automated email from the ASF dual-hosted git repository. > > > > ffang pushed a commit to branch master > > in repository https://gitbox.apache.org/repos/asf/camel.git > > > > > > The following commit(s) were added to refs/heads/master by this push: > > new cbfc4c6 > > > [CAMEL-15738]camel-fastjson|camel-fhir|camel-gson|camel-jackson|camel-jacksonxml|camel-jaxb|camel-xstream > > doc mismatch the value in src code > > cbfc4c6 is described below > > > > commit cbfc4c6809b0ae183ad7027c785bde29c300341e > > Author: Freeman Fang > > AuthorDate: Thu Oct 22 11:10:30 2020 -0400 > > > > > > > [CAMEL-15738]camel-fastjson|camel-fhir|camel-gson|camel-jackson|camel-jacksonxml|camel-jaxb|camel-xstream > > doc mismatch the value in src code > > --- > > components/camel-fastjson/src/main/docs/json-fastjson-dataformat.adoc > | > > 2 +- > > .../camel-fhir-component/src/main/docs/fhirXml-dataformat.adoc > | > > 2 +- > > components/camel-gson/src/main/docs/json-gson-dataformat.adoc > | > > 2 +- > > components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc > | > > 2 +- > > components/camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc > | > > 2 +- > > components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc > | > > 2 +- > > components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc > | > > 2 +- > > 7 files changed, 7 insertions(+), 7 deletions(-) > > > > diff --git > > a/components/camel-fastjson/src/main/docs/json-fastjson-dataformat.adoc > > b/components/camel-fastjson/src/main/docs/json-fastjson-dataformat.adoc > > index d6587d2..31f6759 100644 > > --- > a/components/camel-fastjson/src/main/docs/json-fastjson-dataformat.adoc > > +++ > b/components/camel-fastjson/src/main/docs/json-fastjson-dataformat.adoc > > @@ -31,7 +31,7 @@ The JSON Fastjson dataformat supports 2 options, which > > are listed below. > > |=== > > | Name | Default | Java Type | Description > > | unmarshalTypeName | | String | Class name of the java type to use > when > > unmarshalling > > -| contentTypeHeader | false | Boolean | Whether the data format should > > set the Content-Type header with the type from the data format if the > data > > format is capable of doing so. For example application/xml for data > formats > > marshalling to XML, or application/json for data formats marshalling to > > JSON etc. > > +| contentTypeHeader | true | Boolean | Whether the data format should > set > > the Content-Type header with the type from the data format if the data > > format is capable of doing so. For example application/xml for data > formats > > marshalling to XML, or application/json for data formats marshalling to > > JSON etc. > > |=== > > // dataformat options: END > > > > diff --git > > > a/components/camel-fhir/camel-fhir-component/src/main/docs/fhirXml-dataformat.adoc > > > b/components/camel-fhir/camel-fhir-component/src/main/docs/fhirXml-dataformat.adoc > > index 5000efa..eeb79ea 100644 > > --- > > > a/components/camel-fhir/camel-fhir-component/src/main/docs/fhirXml-dataformat.adoc > > +++ > > > b/components/camel-fhir/camel-fhir-component/src/main/docs/fhirXml-dataformat.adoc > > @@ -35,6 +35,6 @@ The FHIR XML dataformat supports 13 options, which are > > listed below. > > | summaryMode | false | Boolean | If set to true (default is false) only > > elements marked by the FHIR specification as being summary elements will > be > > included. > > | suppressNarratives | false | Boolean | If set to true (default is > > false), narratives will not be included in the encoded values. > > | dontStripVersionsFromReferencesAtPaths | | List | If supplied > > value(s), any resource references at the specified paths will have their > > resource versions encoded instead of being automatically stripped during > > the encoding process. This setting has no effect on the parsing process. > > This method provides a finer-grained level of control than > > setStripVersionsFromReferences(String) and any paths specified by
Re: [VOTE] Release Apache Camel and Camel Spring Boot 3.1.0
+1 (non-binding) Thanks! Freeman On Sun, Feb 23, 2020 at 10:00 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.1.0 (with Apache Camel Spring > Boot), a new minor release with 291 improvements and fixes. Please > note that Spring Boot support (including all starter dependencies) has > been moved into a separate repository [1]. Therefore, this vote is for > the two staging repositories listed below. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346526=12311211 > > == Apache Camel 3.1.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1176/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1176/org/apache/camel/apache-camel/3.1.0/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.1.0 > > == Apache Camel Spring Boot 3.1.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1177/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.1.0 > > Please test this release candidate and cast your vote. > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 3.1.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > > [1] https://github.com/apache/camel-spring-boot >
Re: [HEADS UP] - camel3 - camel-http4 renaming to camel-http
+1 Thanks! － Freeman(Yue) Fang Red Hat, Inc. > On Jul 25, 2019, at 5:48 AM, Claus Ibsen wrote: > > Hi > > So what has been bothering Camel 2.x users is that when they use http > they would likely use the camel-http4 component and then they should > use http4 as the component name. The old camel-http component is > deprecated as the http client it uses is EOL for many many years. > > So with Camel 3 on the way we have deleted the old camel-http > component and the camel-http4 component now has both http and http4 as > component names. > > I think we should rename the camel-http4 back to camel-http and then > favour using http as the component name, and then deprecate http4 (or > even remove it). > > Any thoughts? > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)
+1 (non-binding) Thanks! － Freeman(Yue) Fang Red Hat, Inc. > On Jul 7, 2019, at 5:16 AM, Gregor Zurowski wrote: > > Hi Everyone: > > This is a vote to release Apache Camel 3.0.0-M4 (Milestone 4), the > fourth milestone towards a new 3.0.0 major release with another 105 > improvements and fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345567=12311211 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1143/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1143/org/apache/camel/apache-camel/3.0.0-M4/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M4 > > Please test this release candidate and cast your vote. > [ ] +1 Release the binary as Apache Camel 3.0.0-M4 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor
Re: [VOTE] Release Apache Camel 2.24.1
+1 Thanks! － Freeman(Yue) Fang Red Hat, Inc. > On Jun 20, 2019, at 3:04 PM, Gregor Zurowski wrote: > > Hi Everyone: > > This is a vote to release Apache Camel 2.24.1, the first patch release > for the camel-2.24.x branch with 22 improvements and bug fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345495=12311211 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1142/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1142/org/apache/camel/apache-camel/2.24.1/ > > Tag: > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.24.1 > > Please test this release candidate and cast your vote. > [ ] +1 Release the binary as Apache Camel 2.24.1 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor
Re: build camel-core JDK 11
Hi Zoran, Just FYI, in CXF we use maven profile which can define JDK9,10,11 specific dependencies such as jaxb, jaxws, activation and whatnot, probably camel can do this as well? Cheers － Freeman(Yue) Fang Red Hat, Inc. > On Nov 7, 2018, at 5:24 PM, Zoran Regvart wrote: > > Hi Freeman, Önder and Cameleers, > yeah that's correct, I focused on getting the right dependencies to > build (i.e. compile) on Java 11, we have ~2500 tests failing at the > moment on the CI build[1]. > > That CI build on the other hand is building on Java 8 and running > tests on Java 11, though I guess at some point we could build with > Java 11 and use `-source 1.8` and `-target 1.8`. > > I think the bulk of the issues is with missing JAXB implementation > that can be added. > > I was wondering though if we should add JAXB dependencies in `test` > scope or as `optional`. This would impact the users quite a bit on > Java 11+. > > Also we (currently) have `jaxb-core` and `jaxb-impl` from > `com.sun.xml.bind`, I think we should switch to > `org.glassfish.jaxb:jaxb-runtime`, > > zoran > > [1] > https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.daily-zregvart/lastCompletedBuild/testReport/ > > On Wed, Nov 7, 2018 at 8:58 AM, Onder SEZGIN wrote: >> Hi, >> >> i think all tests are not successful yet. >> My first goal was to build with JDK 11 and then i guess we will run the >> tests and provide possible fixes for failing ones. >> >> I have got a couple issues while trying to build. >> >> Zoran, did you run local successfull build? >> >> Thanks, >> >> On Wed, Nov 7, 2018 at 2:53 AM Freeman Fang wrote: >> >>> Hi Zoran, >>> >>> I consistently run into error when I use jdk11 to build camel on >>> java-10-test branch, is it a known issue or I did something wrong? >>> My java is >>> >>> java -version >>> openjdk version "11" 2018-09-25 >>> OpenJDK Runtime Environment 18.9 (build 11+28) >>> OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode) >>> >>> Thanks! >>> >>> [ERROR] Failures: >>> [ERROR] >>> org.apache.camel.component.validator.CustomSchemaFactoryFeatureTest.testCustomSchemaFactory(org.apache.camel.component.validator.CustomSchemaFactoryFeatureTest) >>> [ERROR] Run 1: >>> CustomSchemaFactoryFeatureTest.testCustomSchemaFactory:49->Assert.fail:88 >>> Expect exception here >>> [ERROR] Run 2: >>> CustomSchemaFactoryFeatureTest.testCustomSchemaFactory:49->Assert.fail:88 >>> Expect exception here >>> [ERROR] Run 3: >>> CustomSchemaFactoryFeatureTest.testCustomSchemaFactory:49->Assert.fail:88 >>> Expect exception here >>> [INFO] >>> [ERROR] >>> org.apache.camel.language.simple.SimpleTest.testOGNLHeaderLinesList(org.apache.camel.language.simple.SimpleTest) >>> [ERROR] Run 1: >>> SimpleTest.testOGNLHeaderLinesList:934->Assert.assertEquals:144->Assert.assertEquals:115 >>> expected: but was:>> ]bounds for length 2> >>> [ERROR] Run 2: >>> SimpleTest.testOGNLHeaderLinesList:934->Assert.assertEquals:144->Assert.assertEquals:115 >>> expected: but was:>> ]bounds for length 2> >>> [ERROR] Run 3: >>> SimpleTest.testOGNLHeaderLinesList:934->Assert.assertEquals:144->Assert.assertEquals:115 >>> expected: but was:>> ]bounds for length 2> >>> [INFO] >>> [ERROR] >>> org.apache.camel.language.simple.SimpleTest.testOGNLHeaderList(org.apache.camel.language.simple.SimpleTest) >>> [ERROR] Run 1: >>> SimpleTest.testOGNLHeaderList:911->Assert.assertEquals:144->Assert.assertEquals:115 >>> expected: but was:>> ]bounds for length 2> >>> [ERROR] Run 2: >>> SimpleTest.testOGNLHeaderList:911->Assert.assertEquals:144->Assert.assertEquals:115 >>> expected: but was:>> ]bounds for length 2> >>> [ERROR] Run 3: >>> SimpleTest.testOGNLHeaderList:911->Assert.assertEquals:144->Assert.assertEquals:115 >>> expected: but was:>> ]bounds for length 2> >>> [INFO] >>> [ERROR] >>> org.apache.camel.language.simple.SimpleTest.testOGNLPropertyLinesList(org.apache.camel.language.simple.SimpleTest) >>> [ERROR] Run 1: >>> SimpleTest.testOGNLPropertyLinesList:441->Assert.assertEquals:144->Assert.assertEquals:115 >>> expected: but was:>> ]bounds for length 2> >>> [ERROR] Run 2: >>> SimpleTest.testOGNLPropertyLinesLi
Re: build camel-core JDK 11
Hi Zoran, I consistently run into error when I use jdk11 to build camel on java-10-test branch, is it a known issue or I did something wrong? My java is java -version openjdk version "11" 2018-09-25 OpenJDK Runtime Environment 18.9 (build 11+28) OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode) Thanks! [ERROR] Failures: [ERROR] org.apache.camel.component.validator.CustomSchemaFactoryFeatureTest.testCustomSchemaFactory(org.apache.camel.component.validator.CustomSchemaFactoryFeatureTest) [ERROR] Run 1: CustomSchemaFactoryFeatureTest.testCustomSchemaFactory:49->Assert.fail:88 Expect exception here [ERROR] Run 2: CustomSchemaFactoryFeatureTest.testCustomSchemaFactory:49->Assert.fail:88 Expect exception here [ERROR] Run 3: CustomSchemaFactoryFeatureTest.testCustomSchemaFactory:49->Assert.fail:88 Expect exception here [INFO] [ERROR] org.apache.camel.language.simple.SimpleTest.testOGNLHeaderLinesList(org.apache.camel.language.simple.SimpleTest) [ERROR] Run 1: SimpleTest.testOGNLHeaderLinesList:934->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [ERROR] Run 2: SimpleTest.testOGNLHeaderLinesList:934->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [ERROR] Run 3: SimpleTest.testOGNLHeaderLinesList:934->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [INFO] [ERROR] org.apache.camel.language.simple.SimpleTest.testOGNLHeaderList(org.apache.camel.language.simple.SimpleTest) [ERROR] Run 1: SimpleTest.testOGNLHeaderList:911->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [ERROR] Run 2: SimpleTest.testOGNLHeaderList:911->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [ERROR] Run 3: SimpleTest.testOGNLHeaderList:911->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [INFO] [ERROR] org.apache.camel.language.simple.SimpleTest.testOGNLPropertyLinesList(org.apache.camel.language.simple.SimpleTest) [ERROR] Run 1: SimpleTest.testOGNLPropertyLinesList:441->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [ERROR] Run 2: SimpleTest.testOGNLPropertyLinesList:441->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [ERROR] Run 3: SimpleTest.testOGNLPropertyLinesList:441->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [INFO] [ERROR] org.apache.camel.language.simple.SimpleTest.testOGNLPropertyList(org.apache.camel.language.simple.SimpleTest) [ERROR] Run 1: SimpleTest.testOGNLPropertyList:417->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [ERROR] Run 2: SimpleTest.testOGNLPropertyList:417->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [ERROR] Run 3: SimpleTest.testOGNLPropertyList:417->Assert.assertEquals:144->Assert.assertEquals:115 expected: but was: [INFO] [INFO] [ERROR] Tests run: 6200, Failures: 5, Errors: 0, Skipped: 19 － Freeman(Yue) Fang Red Hat, Inc. > On Nov 6, 2018, at 7:49 PM, Zoran Regvart wrote: > > Hi Cameleers, > > So using Groovy 2.5.3 seems to work, I did leave Groovy Eclipse > compiler and the Maven plugin updated to the newer versions. > > Also I found that the `maven-shade-plugin` can hang (on Java 11?), so > to work around that I've set `createDependencyReducedPom` to `false`. > > Because of this I disabled the CI build[1] of the `java-10-test` > branch as it took ~19h, now it needs to be triggered manually. > > I've rebased on `master` and triggered the build, so lets see what the > CI says, and how many tests failures we'll see... > > zoran > > [1] > https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.daily-zregvart/ > > On Tue, Nov 6, 2018 at 10:18 AM, Zoran Regvart wrote: >> Hi Pascal & Cameleers, >> >> On Tue, Nov 6, 2018 at 8:23 AM, Pascal Schumacher >> wrote: >>> No related to camel-core, but this commit >>> https://github.com/apache/camel/commit/dda0e4c5890d8e12b5895b8736e3819d0b095d08 >>> can be reverted/dropped because groovy 2.5.3 should work on Java 11. >> >> Awesome, let me try that... >> >> zoran >> -- >> Zoran Regvart > > > > -- > Zoran Regvart
Re: camel git commit: [CAMEL-9821]add mep uri param for camel-cxf endpoint
Thanks Claus to point this out, on it!
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
> On Apr 6, 2016, at 12:58 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
>
> -1
>
> There is already an exchangePattern option from the DefaultEndpoint.
>
> Can you not use that, instead of inventing a new duplicate option?
>
>
>
> On Wed, Apr 6, 2016 at 4:35 AM, <ff...@apache.org> wrote:
>> Repository: camel
>> Updated Branches:
>> refs/heads/master 0437f7db6 -> 92becd2a9
>>
>>
>> [CAMEL-9821]add mep uri param for camel-cxf endpoint
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/camel/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/92becd2a
>> Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/92becd2a
>> Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/92becd2a
>>
>> Branch: refs/heads/master
>> Commit: 92becd2a94dc0135dee0b92c8caff31eb51dae31
>> Parents: 0437f7d
>> Author: Freeman Fang <freeman.f...@gmail.com>
>> Authored: Wed Apr 6 10:34:45 2016 +0800
>> Committer: Freeman Fang <freeman.f...@gmail.com>
>> Committed: Wed Apr 6 10:34:45 2016 +0800
>>
>> --
>> .../apache/camel/component/cxf/CxfConsumer.java | 5 ++
>> .../apache/camel/component/cxf/CxfEndpoint.java | 19 +++
>> .../cxf/feature/RAWDataFormatFeature.java | 26 ++
>> .../OneWayOutgoingChainInterceptor.java | 52
>> 4 files changed, 102 insertions(+)
>> --
>>
>>
>> http://git-wip-us.apache.org/repos/asf/camel/blob/92becd2a/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java
>> --
>> diff --git
>> a/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java
>>
>> b/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java
>> index fab7267..5b32832 100644
>> ---
>> a/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java
>> +++
>> b/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java
>> @@ -172,7 +172,12 @@ public class CxfConsumer extends DefaultConsumer {
>> if (boi.getOperationInfo().isOneWay()) {
>> camelExchange.setPattern(ExchangePattern.InOnly);
>> }
>> +} else {
>> +if (cxfEndpoint.getMep() != null &&
>> cxfEndpoint.getMep().equals("InOnly")) {
>> +camelExchange.setPattern(ExchangePattern.InOnly);
>> +}
>> }
>> +
>>
>> // set data format mode in Camel exchange
>> camelExchange.setProperty(CxfConstants.DATA_FORMAT_PROPERTY,
>> dataFormat);
>>
>> http://git-wip-us.apache.org/repos/asf/camel/blob/92becd2a/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfEndpoint.java
>> --
>> diff --git
>> a/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfEndpoint.java
>>
>> b/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfEndpoint.java
>> index 8dd5442..12b9ce0 100644
>> ---
>> a/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfEndpoint.java
>> +++
>> b/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfEndpoint.java
>> @@ -192,6 +192,8 @@ public class CxfEndpoint extends DefaultEndpoint
>> implements HeaderFilterStrategy
>> private String password;
>> @UriParam(label = "advanced", prefix = "properties.", multiValue = true)
>> private Map<String, Object> properties;
>> +@UriParam(name = "mep")
>> +private String mep;
>>
>> public CxfEndpoint() {
>> }
>> @@ -309,6 +311,11 @@ public class CxfEndpoint extends DefaultEndpoint
>> implements HeaderFilterStrategy
>> sfb.setDataBinding(new SourceDataBinding());
>> } else if (getDataFormat().dealias() == DataFormat.RAW) {
>> RAWDataFormatFeature feature = new RAWDataFormatFeature();
>> +if (this.getMep() != null &&
>> this.getMep().equals("InOnly")) {
>> +
Does camel-rx only works with Oracle/SUN JDK?
Hi Team, I have a question about the camel-rx component, in the camel-rx feature, it use the io.reactivex/rxjava/1.0.7 bundle which explicitly import sun.misc package so it means this component can only run with Oracle/SUN JDK, can we state it in the camel features.xml, like we do for several other components? Thanks － Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat
Re: camel git commit: [CAMEL-8333]Upgrade async-http-client to 1.9.0
Yeah, this commit[1] fixed it. ;-)
[1]http://git-wip-us.apache.org/repos/asf/camel/commit/fee91e7b
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
On 2015-2-11, at 下午6:15, Aki Yoshida wrote:
i think someone has fixed it already ;-)
2015-02-11 11:05 GMT+01:00 Aki Yoshida elak...@gmail.com:
i can look into it.
2015-02-11 8:16 GMT+01:00 Claus Ibsen claus.ib...@gmail.com:
Hi
I think this causes camel-ahc-ws to not compile anymore.
[ERROR]
/Users/davsclaus/workspace/camel/components/camel-ahc-ws/src/main/java/org/apache/camel/component/ahc/ws/WsEndpoint.java:[215,8]
error: method does not override or implement a method from a supertype
On Wed, Feb 11, 2015 at 7:43 AM, ff...@apache.org wrote:
Repository: camel
Updated Branches:
refs/heads/master c7cb9d3f0 - 5b4ac7886
[CAMEL-8333]Upgrade async-http-client to 1.9.0
Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/5b4ac788
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/5b4ac788
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/5b4ac788
Branch: refs/heads/master
Commit: 5b4ac788603fdf4003ddf8c40182df752b13b0bb
Parents: c7cb9d3
Author: Freeman Fang freeman.f...@gmail.com
Authored: Wed Feb 11 14:42:39 2015 +0800
Committer: Freeman Fang freeman.f...@gmail.com
Committed: Wed Feb 11 14:42:39 2015 +0800
--
.../ahc/AhcComponentClientConfigTest.java | 2 +-
...ConfigWithClientConfigUriParametersTest.java | 6 ++--
.../ahc/AhcComponentCustomClientConfigTest.java | 2 +-
.../ahc/AhcComponentNettyClientConfigTest.java | 4 +--
.../ahc/AhcProduceClientConfigTest.java | 2 +-
...ConfigWithClientConfigUriParametersTest.java | 6 ++--
...roduceWithClientConfigUriParametersTest.java | 2 +-
.../atmosphere/websocket/TestClient.java| 21 +
.../websocket/AllowAllHostnameVerifier.java | 32
.../WebsocketClientCamelRouteTest.java | 13 +++-
.../WebsocketComponentRouteExampleTest.java | 13 +++-
.../websocket/WebsocketConsumerRouteTest.java | 8 ++---
.../WebsocketProducerRouteExampleTest.java | 18 ---
.../websocket/WebsocketRouteExampleTest.java| 12 +++-
...ebsocketSSLContextInUriRouteExampleTest.java | 13
.../websocket/WebsocketSSLRouteExampleTest.java | 14 -
.../WebsocketTwoRoutesExampleTest.java | 19
parent/pom.xml | 2 +-
18 files changed, 94 insertions(+), 95 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/camel/blob/5b4ac788/components/camel-ahc/src/test/java/org/apache/camel/component/ahc/AhcComponentClientConfigTest.java
--
diff --git
a/components/camel-ahc/src/test/java/org/apache/camel/component/ahc/AhcComponentClientConfigTest.java
b/components/camel-ahc/src/test/java/org/apache/camel/component/ahc/AhcComponentClientConfigTest.java
index c03d9fe..fe77d05 100644
---
a/components/camel-ahc/src/test/java/org/apache/camel/component/ahc/AhcComponentClientConfigTest.java
+++
b/components/camel-ahc/src/test/java/org/apache/camel/component/ahc/AhcComponentClientConfigTest.java
@@ -30,7 +30,7 @@ public class AhcComponentClientConfigTest extends
BaseAhcTest {
AsyncHttpClientConfig.Builder builder = new
AsyncHttpClientConfig.Builder();
// use the builder to set the options we want, in this case we
want to follow redirects and try
// at most 3 retries to send a request to the host
-AsyncHttpClientConfig config =
builder.setFollowRedirects(true).setMaxRequestRetry(3).build();
+AsyncHttpClientConfig config =
builder.setFollowRedirect(true).setMaxRequestRetry(3).build();
// lookup AhcComponent
AhcComponent component = context.getComponent(ahc,
AhcComponent.class);
http://git-wip-us.apache.org/repos/asf/camel/blob/5b4ac788/components/camel-ahc/src/test/java/org/apache/camel/component/ahc/AhcComponentClientConfigWithClientConfigUriParametersTest.java
--
diff --git
a/components/camel-ahc/src/test/java/org/apache/camel/component/ahc/AhcComponentClientConfigWithClientConfigUriParametersTest.java
b/components/camel-ahc/src/test/java/org/apache/camel/component/ahc/AhcComponentClientConfigWithClientConfigUriParametersTest.java
index 46d5020..83c3445 100644
---
a/components/camel-ahc/src/test/java/org/apache/camel/component/ahc/AhcComponentClientConfigWithClientConfigUriParametersTest.java
+++
b/components/camel-ahc/src/test/java/org/apache/camel/component/ahc/AhcComponentClientConfigWithClientConfigUriParametersTest.java
@@ -28,13 +28,13 @@ public
Re: svn commit: r1356481 - /camel/trunk/parent/pom.xml
Hi Team, abdera 1.1.3 is out so we needn't bind to axiom 1.2.10 anymore. We can upgrade to both last abdera 1.1.3 and axiom 1.2.14. Cxf side already do this upgrade, so I think Camel should do the same. I can do this change if there's no known issue and objections. － Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋 On 2012-12-15, at 上午12:36, Christian Müller wrote: Thanks Freeman! Best, Christian On Fri, Dec 14, 2012 at 9:16 AM, Freeman Fang freeman.f...@gmail.comwrote: Done for trunk, 2.10.x and 2.9.x branches － Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋 On 2012-12-14, at 上午2:10, Christian Müller wrote: I can do it tomorrow. But feel free to revert this change by yourself if it's urgent... Best, Christian Sent from a mobile device Am 13.12.2012 03:34 schrieb Freeman Fang freeman.f...@gmail.com: Hi Christian, I'm -1 for this change, it re-introduce the issue tracked by CAMEL-5109[1], abdera 1.1.2 must work with axiom 1.2.10. Could you please take a look and revert this change? [1]https://issues.apache.org/jira/browse/CAMEL-5109 Thanks － Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋 On 2012-7-3, at 上午4:57, cmuel...@apache.org wrote: Author: cmueller Date: Mon Jul 2 20:57:49 2012 New Revision: 1356481 URL: http://svn.apache.org/viewvc?rev=1356481view=rev Log: upgrade to axiom 1.2.13 Modified: camel/trunk/parent/pom.xml Modified: camel/trunk/parent/pom.xml URL: http://svn.apache.org/viewvc/camel/trunk/parent/pom.xml?rev=1356481r1=1356480r2=1356481view=diff == --- camel/trunk/parent/pom.xml (original) +++ camel/trunk/parent/pom.xml Mon Jul 2 20:57:49 2012 @@ -45,7 +45,7 @@ avro-version1.6.2/avro-version avro-bundle-version1.6.1_1/avro-bundle-version aws-java-sdk-version1.3.10/aws-java-sdk-version -axiom-version1.2.10/axiom-version +axiom-version1.2.13/axiom-version beanio-version2.0.0/beanio-version bouncycastle-version1.46/bouncycastle-version castor-bundle-version1.3.2_1/castor-bundle-version --
Re: svn commit: r1356481 - /camel/trunk/parent/pom.xml
Done for trunk, 2.10.x and 2.9.x branches － Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋 On 2012-12-14, at 上午2:10, Christian Müller wrote: I can do it tomorrow. But feel free to revert this change by yourself if it's urgent... Best, Christian Sent from a mobile device Am 13.12.2012 03:34 schrieb Freeman Fang freeman.f...@gmail.com: Hi Christian, I'm -1 for this change, it re-introduce the issue tracked by CAMEL-5109[1], abdera 1.1.2 must work with axiom 1.2.10. Could you please take a look and revert this change? [1]https://issues.apache.org/jira/browse/CAMEL-5109 Thanks － Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋 On 2012-7-3, at 上午4:57, cmuel...@apache.org wrote: Author: cmueller Date: Mon Jul 2 20:57:49 2012 New Revision: 1356481 URL: http://svn.apache.org/viewvc?rev=1356481view=rev Log: upgrade to axiom 1.2.13 Modified: camel/trunk/parent/pom.xml Modified: camel/trunk/parent/pom.xml URL: http://svn.apache.org/viewvc/camel/trunk/parent/pom.xml?rev=1356481r1=1356480r2=1356481view=diff == --- camel/trunk/parent/pom.xml (original) +++ camel/trunk/parent/pom.xml Mon Jul 2 20:57:49 2012 @@ -45,7 +45,7 @@ avro-version1.6.2/avro-version avro-bundle-version1.6.1_1/avro-bundle-version aws-java-sdk-version1.3.10/aws-java-sdk-version -axiom-version1.2.10/axiom-version +axiom-version1.2.13/axiom-version beanio-version2.0.0/beanio-version bouncycastle-version1.46/bouncycastle-version castor-bundle-version1.3.2_1/castor-bundle-version
Re: [VOTE] Camel MUST use valid URIs for identifying and configuring Endpoints
-1, as it's working for a long time and stable. We may discuss this change or rename the URI to a more appropriate name for Camel 3.x, but we should keep it as is for Camel 2.x line Freeman On 2012-6-20, at 上午8:37, Hadrian Zbarcea wrote: Using URIs to identify and configure Endpoints is a notable Apache Camel innovation. This feature was present in Camel from its first release. The definition of the URIs syntax in unambiguous and defined in RFC-2396 [1]. Some components introduced along the way do not use valid URIs and this needs to be corrected. This vote is intended to formalize the apparent lazy consensus in the [discuss] thread [2] on the dev@ list. This vote reflects agreement with the principle only. If this vote passes the details of the solution will be fleshed out later. [ ] +1 Camel MUST use valid URIs for Endpoint configuration [ ] -1 Camel does not need to use valid URIs (please provide reason). Vote is open for at least 72 hours. -- Hadrian Zbarcea Principal Software Architect Talend, Inc http://coders.talend.com/ http://camelbot.blogspot.com/ [1] http://www.ietf.org/rfc/rfc2396.txt [2] http://mail-archives.apache.org/mod_mbox/camel-dev/201206.mbox/%3C4FD60168.5090009%40gmail.com%3E - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: http://weibo.com/u/1473905042
Re: Building the manual.....
+1 Freeman On 2012-5-17, at 下午9:39, Daniel Kulp wrote: I've discovered that the manual building is what is causing the Camel parallel builds to completely fail. If I do: $ mvn -Pfastinstall -P '!build.manual' -T 8 to turn that off, then the parallel build actually works. (when the repository update stuff in the install plugin doesn't barf, separate issue) That kind of brings up the question: should we build the manual by default? Since it requires things like prince to be installed, it's really not that useful out of the box. I'm kind of wondering if it make sense to NOT have it build by default, but have it built during certain profiles (release, deploy, etc...). Thoughts? -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: http://weibo.com/u/1473905042
Re: [PROPOSAL] - camel-test - @deprecate JUnit 3.x API
+1 Freeman On 2011-12-28, at 下午11:08, Claus Ibsen wrote: Hi The camel-test component supports currently both JUnit 3.x and 4.x, each in separate package. Supporting both requires us to have a fair amount of duplicated code, one for 3.x and another for 4.x. I suggest to @deprecated the JUnit 3.x part of the camel-test component. Then we can remove support for 3.x in Camel 3.0. Any thoughts? -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/ - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [VOTE] Release Apache Camel 2.9.0
+1 Freeman On 2011-12-15, at 下午10:20, Hadrian Zbarcea wrote: A new release candidate apache-camel-2.9.0 final is out with approximately 464 issues resolved so far: improvements and bug fixes [1]. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapachecamel-343/ The tarballs are here https://repository.apache.org/content/repositories/orgapachecamel-343/org/apache/camel/apache-camel/2.9.0/ Tag: http://svn.apache.org/repos/asf/camel/tags/camel-2.9.0/ Please review, help out with testing and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache Camel 2.9.0 [ ] -1 Veto the release (provide specific comments) Vote is open for at least 72 hours. Here's my +1 Hadrian [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12316374 -- Hadrian Zbarcea Principal Software Architect Talend, Inc http://coders.talend.com/ http://camelbot.blogspot.com/ - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [VOTE] Release Camel 2.8.3 (the second try)
Get chance to run more examples in Servicemix, they're camel-example-cafe camel-example-cxf camel-example-cxf-osgi camel-example-cxf-proxy camel-example-osgi camel-example-osgi-rmi camel-example-pojo-messaging camel-example-spring-xquery camel-example-spring all good for me. Though found some minor issues such as hardcoded camel version in README.txt(tracked by CAMEL-4699), but not a big deal at all. [1]https://issues.apache.org/jira/browse/CAMEL-4699 Freeman On 2011-11-18, at 下午6:27, Freeman Fang wrote: Hi Claus, I did a quick test for camel-example-spring-xquery and camel-example- cxf-blueprint, they all good for me, no exception and no unknown/ unsupported Source ERROR/WARN log. I'll see if I can run more over weekend or early next week. Freeman On 2011-11-18, at 下午4:36, Claus Ibsen wrote: Hi Freeman Do you mind trying to install some of the Camel 2.8.3 examples in the SMX ? I have been told for example the camel-example-spring-xquery had an issue where Saxon would throws some exception about unknown/unsupported Source. Check the logs if there is an ERROR/WARN etc. That should have been fixed on the Camel side, so I would like to know if that seems to work on SMX. A reason is the upcoming SMX 4.4.0 which will ship with Camel 2.8.3, should be as good as it can be. This is after all only the 2nd release of SMX this year. So we want it to be a great release. And if possible if you got a bit more time, try to install some of other Camel examples. And check the logs for ERROR/WARN. There should be features for some of them. On Fri, Nov 18, 2011 at 7:38 AM, Freeman Fang freeman.f...@gmail.com wrote: Build Servicemix kit against Camel 2.8.3, all looks good for me. +1 Freeman On 2011-11-18, at 上午9:51, Willem Jiang wrote: This is a vote to release Camel 2.8.3. 2.8.3 contains fixes about 60+ JIRA issues that would be good to get into the hands of Camel users. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapachecamel-204 The tarballs are here https://repository.apache.org/content/repositories/orgapachecamel-204/org/apache/camel/apache- camel/2.8.3/ Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12318649 Tag: http://svn.apache.org/repos/asf/camel/tags/camel-2.8.3/ Please review, test and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache Camel 2.8.3 [ ] -1 Don't release (provide specific comments) Willem - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/ - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [VOTE] Release Camel 2.8.3 (the second try)
Hi Claus, I did a quick test for camel-example-spring-xquery and camel-example- cxf-blueprint, they all good for me, no exception and no unknown/ unsupported Source ERROR/WARN log. I'll see if I can run more over weekend or early next week. Freeman On 2011-11-18, at 下午4:36, Claus Ibsen wrote: Hi Freeman Do you mind trying to install some of the Camel 2.8.3 examples in the SMX ? I have been told for example the camel-example-spring-xquery had an issue where Saxon would throws some exception about unknown/unsupported Source. Check the logs if there is an ERROR/WARN etc. That should have been fixed on the Camel side, so I would like to know if that seems to work on SMX. A reason is the upcoming SMX 4.4.0 which will ship with Camel 2.8.3, should be as good as it can be. This is after all only the 2nd release of SMX this year. So we want it to be a great release. And if possible if you got a bit more time, try to install some of other Camel examples. And check the logs for ERROR/WARN. There should be features for some of them. On Fri, Nov 18, 2011 at 7:38 AM, Freeman Fang freeman.f...@gmail.com wrote: Build Servicemix kit against Camel 2.8.3, all looks good for me. +1 Freeman On 2011-11-18, at 上午9:51, Willem Jiang wrote: This is a vote to release Camel 2.8.3. 2.8.3 contains fixes about 60+ JIRA issues that would be good to get into the hands of Camel users. Please find the staging repo here: https://repository.apache.org/content/repositories/ orgapachecamel-204 The tarballs are here https://repository.apache.org/content/repositories/orgapachecamel-204/org/apache/camel/apache- camel/2.8.3/ Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12318649 Tag: http://svn.apache.org/repos/asf/camel/tags/camel-2.8.3/ Please review, test and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache Camel 2.8.3 [ ] -1 Don't release (provide specific comments) Willem - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/ - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [VOTE] Release Camel 2.8.3 (the second try)
Build Servicemix kit against Camel 2.8.3, all looks good for me. +1 Freeman On 2011-11-18, at 上午9:51, Willem Jiang wrote: This is a vote to release Camel 2.8.3. 2.8.3 contains fixes about 60+ JIRA issues that would be good to get into the hands of Camel users. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapachecamel-204 The tarballs are here https://repository.apache.org/content/repositories/orgapachecamel-204/org/apache/camel/apache- camel/2.8.3/ Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12318649 Tag: http://svn.apache.org/repos/asf/camel/tags/camel-2.8.3/ Please review, test and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache Camel 2.8.3 [ ] -1 Don't release (provide specific comments) Willem - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [VOTE] Release Camel 2.8.3
Hi Willem,
Thanks very much.
but I'm really sorry to say I have to -1, in the camel-
features.xml[1], there're some version like ${scriptengines-version}
and ${rhino-bundle-version} not get filtered. Those actually were
introduced by me, I commit on trunk and merge back to 2.8.x branch,
but I didn't realize that trunk use scriptengines.version but 2.8.x
use scriptengines-version, one use . separator but another use -.
Anyway, this is no doubt my bad, I should have double check before I
merge.
This problem can cause Servicemix fail when build distribution kit as
it will use add-features-to-repo karaf-feature plugin and the invalid
bundle here break the build
I just commit a quick fix for it.
Btw, I've hacked camel-features.xml and build Servicemix 4.4 kit
against Camel 2.8.3 and all camel related examples are pass.
Sorry again.
[1]https://repository.apache.org/content/repositories/orgapachecamel-184/org/apache/camel/karaf/apache-camel/2.8.3/apache-camel-2.8.3-features.xml
Best Regards
Freeman
On 2011-11-16, at 上午9:57, Willem Jiang wrote:
This is a vote to release Camel 2.8.3. 2.8.3 contains fixes about
60 JIRA issues that would be good to get into the hands of Camel
users.
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-184
The tarballs are here
https://repository.apache.org/content/repositories/orgapachecamel-184/org/apache/camel/apache-
camel/2.8.3/
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12318649
Tag:
http://svn.apache.org/repos/asf/camel/tags/camel-2.8.3/
NOTE:
There is a known issue that camel-itest-osgi tests are failed due to
the change of CAMEL-4671, and it could be fixed by updating the
jre.properties in the camel-itest-osgi module.
The Karaf user need to install the jaxb,activation,stax API bundle,
if these api packages are not exported from the JRE before
installing apache-camel feature.
Please review, test and vote to approve this release binary. Your
vote counts!
[ ] +1 Release the binary as Apache Camel 2.8.2
[ ] -1 Don't release (provide specific comments)
Willem
-
Freeman Fang
FuseSource
Email:ff...@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Re: [DISCUSS] Extract camel-validator from camel-core
Yeah, pax-url absolutely is appropriate here. Freeman On 2011-11-13, at 上午10:07, Raul Kripalani wrote: Hi, Since we are talking OSGi, this looks like an appropriate use case for the PAX URL classpath protocol. It provides means to lookup resources in any other deployed bundle, either by specifying its symbolic name or by performing a container-wide search. It worked like a charm for me with a use case that involved Facelets and loading taglibs from other bundles under Karaf. -- Raul. On 13 Nov 2011, at 00:02, Christian Müller christian.muel...@gmail.com wrote: We found another library/dependency which JB can bundle... :-) I will provide a patch for it later... I discussed this with JB that this should of cure also work in OSGI in different scenarios: 1) the XSD is packaged together with the route in an OSGI bundle 2) the XSD is packages in another OSGI bundle (because it is used in multiple different OSGI bundles) 3) the XSD is located somewhere in the file system 4) the XSD is available somewhere over http All this should be possible. For 2), the user may have to use fragment bundles or require bundle. I will work on it later... Best, Christian - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
[jira] [Work started] (CAMEL-4676) use fine-grained granularity feature for camel-script-optional
[ https://issues.apache.org/jira/browse/CAMEL-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4676 started by Freeman Fang. use fine-grained granularity feature for camel-script-optional -- Key: CAMEL-4676 URL: https://issues.apache.org/jira/browse/CAMEL-4676 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang split camel-script-optional into camel-script-javascript camel-script-groovy camel-script-jruby so that we can control granularity much better, and version upgrades will be more manageable. In most cases, if the user does scripting, he'll probably standardise on only one particular language for all his routes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-4676) use fine-grained granularity feature for camel-script-optional
use fine-grained granularity feature for camel-script-optional -- Key: CAMEL-4676 URL: https://issues.apache.org/jira/browse/CAMEL-4676 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang split camel-script-optional into camel-script-javascript camel-script-groovy camel-script-jruby so that we can control granularity much better, and version upgrades will be more manageable. In most cases, if the user does scripting, he'll probably standardise on only one particular language for all his routes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4676) use fine-grained granularity feature for camel-script-optional
[ https://issues.apache.org/jira/browse/CAMEL-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-4676. - Resolution: Fixed Fix Version/s: 2.9.0 2.8.3 also specify mvn repo url for google scriptengines stuff which isn't in maven central repo so that needn't change Karaf/Servicemix etc/org.ops4j.pax.url.mvn.cfg before install camel-script-***. commit fix http://svn.apache.org/viewvc?rev=1201612view=rev for trunk http://svn.apache.org/viewvc?rev=1201613view=rev for 2.8.x branch use fine-grained granularity feature for camel-script-optional -- Key: CAMEL-4676 URL: https://issues.apache.org/jira/browse/CAMEL-4676 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.8.3, 2.9.0 split camel-script-optional into camel-script-javascript camel-script-groovy camel-script-jruby so that we can control granularity much better, and version upgrades will be more manageable. In most cases, if the user does scripting, he'll probably standardise on only one particular language for all his routes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-4639) upgrade to servicemix specs 1.9.0
upgrade to servicemix specs 1.9.0 - Key: CAMEL-4639 URL: https://issues.apache.org/jira/browse/CAMEL-4639 Project: Camel Issue Type: Task Reporter: Freeman Fang also per the discussion here[1], use jaxws-2.2 spec bundle from Servicemix which keep same OSGiLocatoer mechanism with other specs, and avoid the opt-in and optional import issues. [1]http://servicemix.396122.n5.nabble.com/DISCUSS-JAXWS-API-2-2-spec-td4932632.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4639) upgrade to servicemix specs 1.9.0
[ https://issues.apache.org/jira/browse/CAMEL-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-4639. - Resolution: Fixed Fix Version/s: 2.9.0 2.8.3 commit fix http://svn.apache.org/viewvc?rev=1199098view=rev for trunk http://svn.apache.org/viewvc?rev=1199099view=rev for 2.8.x branch upgrade to servicemix specs 1.9.0 - Key: CAMEL-4639 URL: https://issues.apache.org/jira/browse/CAMEL-4639 Project: Camel Issue Type: Task Reporter: Freeman Fang Fix For: 2.8.3, 2.9.0 also per the discussion here[1], use jaxws-2.2 spec bundle from Servicemix which keep same OSGiLocatoer mechanism with other specs, and avoid the opt-in and optional import issues. [1]http://servicemix.396122.n5.nabble.com/DISCUSS-JAXWS-API-2-2-spec-td4932632.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Add a new mailing list issues@
+1 Freeman On 2011-10-31, at 上午3:45, Christian Mueller wrote: Add a new mailing list iss...@camel.apache.org to which we send all [jira] messages (which are currently sent to dev@camel.apache.org). I could imagine we have to much messages in the dev@ mailing list which are not really interesting for the developers subscribed to this list. Maybe this is the reason why some discussions are not very active. Maybe we overlooked they... [ ] +1 Accept [ ] -1 Not at this time (provide specific comments) Vote is open for 168 hours (one week). Best, Christian - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [DISCUSS] fifth Camel sub-forum camel-issues
+1 Freeman On 2011-10-27, at 上午6:03, Christian Müller wrote: At present, we have four sub-forums: - camel-users - camel-commits - camel-development - camel-extra What's about adding a fifth sub-forum camel-issues (as we already have for CXF) and send all [jira] messages into this forum? I could imagine we have to much messages in the camel-development forum which are not really interesting for the developers subscribed to this list. Maybe this is the reason why some discussions are not very active. Maybe we overlooked they... Best, Christian - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
[jira] [Updated] (CAMEL-4232) duplicated camel-core-osgi module in camel-spring and camel-blueprint
[ https://issues.apache.org/jira/browse/CAMEL-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-4232: Fix Version/s: (was: 2.9.0) Future duplicated camel-core-osgi module in camel-spring and camel-blueprint - Key: CAMEL-4232 URL: https://issues.apache.org/jira/browse/CAMEL-4232 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Freeman Fang Fix For: Future I found that both camel-spring and camel-blueprint embeded camel-core-osgi module, that's not the best practice in OSGi container. We should install camel-core-osgi as a separate bundle which could be shared by camel-spring and camel-blueprint -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4553) camel-cxf endpoint should be able to determine soap version from incoming message
[ https://issues.apache.org/jira/browse/CAMEL-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-4553. - Resolution: Fixed Fix Version/s: 2.9.0 2.8.3 commit fix http://svn.apache.org/viewvc?rev=1185978view=rev for trunk http://svn.apache.org/viewvc?rev=1186705view=rev for 2.8.x branch camel-cxf endpoint should be able to determine soap version from incoming message - Key: CAMEL-4553 URL: https://issues.apache.org/jira/browse/CAMEL-4553 Project: Camel Issue Type: Bug Components: camel-cxf Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.8.3, 2.9.0 more details from http://camel.465427.n5.nabble.com/Camel-CXF-component-SOAP-1-1-amp-1-2-support-td4909456.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Camel 2.8.2
+1 Freeman On 2011-10-19, at 上午11:17, Daniel Kulp wrote: This is a vote to release Camel 2.8.2. 2.8.2 contains fixes for over 100 JIRA issues that would be good to get into the hands of Camel users. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapachecamel-077/ The tarballs are here https://repository.apache.org/content/repositories/orgapachecamel-077/org/apache/camel/apache- camel/2.8.2/ Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12317866 Tag: http://svn.apache.org/repos/asf/camel/tags/camel-2.8.2/ Please review, test and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache Camel 2.8.2 [ ] -1 Don't release (provide specific comments) -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [VOTE] Release Camel 2.7.4
+1 Freeman On 2011-10-18, at 上午5:12, Daniel Kulp wrote: This is a vote to release Camel 2.7.4. 2.7.4 contains fixes for over 11 JIRA issues that would be good to get into the hands of Camel users. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapachecamel-066/ The tarballs are here https://repository.apache.org/content/repositories/orgapachecamel-066/org/apache/camel/apache- camel/2.7.4/ Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12317151 (Willem: can you mark CAMEL-4497 resolved if it is or move it out of 2.7.4 if it's not? Thanks!) Tag: http://svn.apache.org/repos/asf/camel/tags/camel-2.7.4/ Please review, test and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache Camel 2.7.4 [ ] -1 Don't release (provide specific comments) I'll leave the vote open for at least 72 hours. -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: The new command aliases in Karaf 2.2.4
+1 to use singular Freeman On 2011-10-17, at 下午5:03, Jean-Baptiste Onofré wrote: Hi Claus, You are right: it depends if the command accepts several bundles or not. For instance: - bundles:start 23 34 56 - system:shutdown (no argument) On trunk, you will see bundle:* or bundles:* commands. It's the same: it depends if the commands accept several bundles, or only one. No problem to discuss if it's better to use the singular name (bundle:*, service:*, system:*). I'm fine with that, let see what the others think ;) For Camel, I plan more to use sub-shell in the future: karaf@root camel karaf@root/camel routes:list karaf@root/camel contexts:list I will work on sub-shells on Karaf trunk. Regards JB On 10/17/2011 10:53 AM, Claus Ibsen wrote: Hi I was reading Jean's blog about the Karaf 2.2.4 release http://blog.nanthrax.net/2011/10/whats-new-in-karaf-2-2-4/ And read about the command aliases, which IMHO seems like a good thing. However just wondering why you use the plural naming? - bundles - services And then you have a non plural for system - system I guess the answer is that there is always 1 system, and you can have 0..N bundles/services. I am just used to have singular naming such as - system - bundle - service And for 3rd party plugins, we have a Camel plugin that is singular as well - camel Anyway tab completion will help me pick the right command :) -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
[jira] [Created] (CAMEL-4553) camel-cxf endpoint should be able to determine soap version from incoming message
camel-cxf endpoint should be able to determine soap version from incoming message - Key: CAMEL-4553 URL: https://issues.apache.org/jira/browse/CAMEL-4553 Project: Camel Issue Type: Bug Reporter: Freeman Fang Assignee: Freeman Fang more details from http://camel.465427.n5.nabble.com/Camel-CXF-component-SOAP-1-1-amp-1-2-support-td4909456.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (CAMEL-4553) camel-cxf endpoint should be able to determine soap version from incoming message
[ https://issues.apache.org/jira/browse/CAMEL-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4553 started by Freeman Fang. camel-cxf endpoint should be able to determine soap version from incoming message - Key: CAMEL-4553 URL: https://issues.apache.org/jira/browse/CAMEL-4553 Project: Camel Issue Type: Bug Components: camel-cxf Reporter: Freeman Fang Assignee: Freeman Fang more details from http://camel.465427.n5.nabble.com/Camel-CXF-component-SOAP-1-1-amp-1-2-support-td4909456.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4553) camel-cxf endpoint should be able to determine soap version from incoming message
[ https://issues.apache.org/jira/browse/CAMEL-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-4553: Component/s: camel-cxf camel-cxf endpoint should be able to determine soap version from incoming message - Key: CAMEL-4553 URL: https://issues.apache.org/jira/browse/CAMEL-4553 Project: Camel Issue Type: Bug Components: camel-cxf Reporter: Freeman Fang Assignee: Freeman Fang more details from http://camel.465427.n5.nabble.com/Camel-CXF-component-SOAP-1-1-amp-1-2-support-td4909456.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: 2.8.1 build error
Hi, upgrade to latest JDK should fix, more discussion about this issue from [1] [1]http://camel.465427.n5.nabble.com/Compile-Exception-2-8-1-td4884516.html Freeman On 2011-10-18, at 上午9:30, karafman wrote: When building Camel 2.8.1, Camel-Core I get the following error: [INFO] Compilation failure /home/blue/workspace/camel-2.8.1/camel-core/src/main/java/org/apache/ camel/model/LoadBalanceDefinition.java:[134,16] inconvertible types found : org.apache.camel.model.ProcessorDefinitionlt;capture#425 of ?gt; required: org.apache.camel.model.LoadBalanceDefinition This is my build configuration: [blue@localhost camel-2.8.1]$ which mvn ~/Development/apache-maven-2.2.1/bin/mvn [blue@localhost camel-2.8.1]$ mvn --version Warning: JAVA_HOME environment variable is not set. Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400) Java version: 1.6.0_17 Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux version: 2.6.32-71.29.1.el6.x86_64 arch: amd64 Family: unix Any ideas what the problem might be? -- View this message in context: http://camel.465427.n5.nabble.com/2-8-1-build-error-tp4912101p4912101.html Sent from the Camel Development mailing list archive at Nabble.com. - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
[jira] [Commented] (CAMEL-4479) Camel-Karaf feature.xml has version numbers specified too tightly
[ https://issues.apache.org/jira/browse/CAMEL-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13113125#comment-13113125 ] Freeman Fang commented on CAMEL-4479: - Hi, I believe CAMEL-3995[1] already address the karaf version issue. And about the commons-pool, I don't see Karaf 2.2.2 kit specify any commons-pool bundle, it's not in karaf 2.2.2 kit by default, do I miss something? And from camel 2.8.0 we introduce the OBR resolver for camel-karaf features.xml, so if your OSGi container already have mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-pool/1.5.4_2 then it won't need install org.apache.servicemix.bundles.commons-pool/1.5.4_1. After you start karaf, you can do features:install obr //this install obr feature then features:addurl mvn:org.apache.camel.karaf/apache-camel/2.8.1/xml/features features:install camel-jms Notes: this won't resolve org.apache.servicemix.bundles.commons-pool/1.5.4_1 to org.apache.servicemix.bundles.commons-pool/1.5.4_2, so if your local machine has no org.apache.servicemix.bundles.commons-pool/1.5.4_1 , you need ensure you have a internet connection to download it. It's just that if your OSGi container already have org.apache.servicemix.bundles.commons-pool/1.5.4_2, it won't install org.apache.servicemix.bundles.commons-pool/1.5.4_1 again which keep your bundle list concise and also avoid potential trouble as you described in PAXURL-141 [1]https://issues.apache.org/jira/browse/CAMEL-3995 Freeman Camel-Karaf feature.xml has version numbers specified too tightly - Key: CAMEL-4479 URL: https://issues.apache.org/jira/browse/CAMEL-4479 Project: Camel Issue Type: Bug Components: karaf Affects Versions: 2.7.0 Environment: Karaf 2.2.2 Reporter: Chris Dolan I'm trying to load activemq-web 5.5.0 into Karaf 2.2.2 via the activemq feature.xml. ActiveMQ 5.5.0 depends on Camel 2.7.0's camel-jms feature. The Camel feature.xml has two things that make it incompatible with Karaf 2.2.2: repositorymvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features/repository which doesn't match my 2.2.2 version and bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-pool/1.5.4_1/bundle which does not match the 1.5.4_2 version that is specified by Karaf 2.2.2. Both of these cause runtime exceptions that prevent loading the feature. In each case, it should be possible (in theory) to make the Camel feature.xml more flexible my specifying ranges, like [2.2,3) or [1.5,2) which would cause pax-url-mvn to look for a match via the Maven metadata.xml. I haven't actually tested that such a change would work. In my own environment I simply hacked the XML to put the updated versions, but that's not a sustainable approach. Part of the problem is http://team.ops4j.org/browse/PAXURL-141 mvn: urls resolve versions differently from Maven. That defect complains that unadorned versions in mvn: URLs do not act like usual Maven soft version numbers. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4423) use geronimo-jaxws_2.2_spec 1.1 bundle
[ https://issues.apache.org/jira/browse/CAMEL-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107593#comment-13107593 ] Freeman Fang commented on CAMEL-4423: - commit fix http://svn.apache.org/viewvc?rev=1172413view=rev for 2.8.x branch use geronimo-jaxws_2.2_spec 1.1 bundle -- Key: CAMEL-4423 URL: https://issues.apache.org/jira/browse/CAMEL-4423 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.8.2, 2.9.0 since geronimo-jaxws_2.2_spec-1.1.jar already fixed the incorrect Import-Package javax.xml.namespace(previously it import javax.xml.namespace with version=1.0, which prevent us to use the one from system bundle, so we have to create a wrapper jaxws 2.2 spec bundle in Servicemix) OSGi header, so we can use it in features.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4423) use geronimo-jaxws_2.2_spec 1.1 bundle
[ https://issues.apache.org/jira/browse/CAMEL-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-4423. - Resolution: Fixed Fix Version/s: 2.9.0 2.8.2 use geronimo-jaxws_2.2_spec 1.1 bundle -- Key: CAMEL-4423 URL: https://issues.apache.org/jira/browse/CAMEL-4423 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.8.2, 2.9.0 since geronimo-jaxws_2.2_spec-1.1.jar already fixed the incorrect Import-Package javax.xml.namespace(previously it import javax.xml.namespace with version=1.0, which prevent us to use the one from system bundle, so we have to create a wrapper jaxws 2.2 spec bundle in Servicemix) OSGi header, so we can use it in features.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4423) use geronimo-jaxws_2.2_spec 1.1 bundle
[ https://issues.apache.org/jira/browse/CAMEL-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-4423: Component/s: osgi use geronimo-jaxws_2.2_spec 1.1 bundle -- Key: CAMEL-4423 URL: https://issues.apache.org/jira/browse/CAMEL-4423 Project: Camel Issue Type: Improvement Components: osgi Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.8.2, 2.9.0 since geronimo-jaxws_2.2_spec-1.1.jar already fixed the incorrect Import-Package javax.xml.namespace(previously it import javax.xml.namespace with version=1.0, which prevent us to use the one from system bundle, so we have to create a wrapper jaxws 2.2 spec bundle in Servicemix) OSGi header, so we can use it in features.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4443) Upgrade to Scala 2.9.1
[ https://issues.apache.org/jira/browse/CAMEL-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-4443. - Resolution: Fixed Fix Version/s: 2.8.2 commit fix http://svn.apache.org/viewvc?rev=1172417view=rev for trunk http://svn.apache.org/viewvc?rev=1172427view=rev for 2.8.x branch Upgrade to Scala 2.9.1 -- Key: CAMEL-4443 URL: https://issues.apache.org/jira/browse/CAMEL-4443 Project: Camel Issue Type: Task Components: camel-scala Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Minor Fix For: 2.8.2, 2.9.0 We need a Scala 2.9.1 osgi bundle from ticket: SMX4-917 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4459) CAMEL-4407 has caused a regression in the features.xml
[
https://issues.apache.org/jira/browse/CAMEL-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107015#comment-13107015
]
Freeman Fang commented on CAMEL-4459:
-
Hi Dan,
I think camel-script feature by default should contain those scriptengines
which make this feature working out of the box.
How about we address it using the way like
bundlemvn:http://scriptengines.googlecode.com/svn/m2-repo/!com.google.code.scriptengines/scriptengines-groovy/${scriptengines.version}/bundle
bundlemvn:http://scriptengines.googlecode.com/svn/m2-repo/!com.google.code.scriptengines/scriptengines-javascript/${scriptengines.version}/bundle
bundlemvn:http://scriptengines.googlecode.com/svn/m2-repo/!com.google.code.scriptengines/scriptengines-jruby/${scriptengines.version}/bundle
in the feature descriptor we can indicate mvn repo url which isn't the Central
one, and by this way we needn't configure karaf org.ops4j.pax.url.mvn.cfg.
camel-restlet feature already use this way so I think camel-script can do it as
well.
Freeman
CAMEL-4407 has caused a regression in the features.xml
--
Key: CAMEL-4459
URL: https://issues.apache.org/jira/browse/CAMEL-4459
Project: Camel
Issue Type: Bug
Components: osgi
Affects Versions: 2.8.1
Reporter: Daniel Kulp
Assignee: Daniel Kulp
Fix For: 2.8.2, 2.9.0
The scriptengine things that were added as part of CAMEL-4407 have made doing
a features:install camel-script in a plain Karaf instance not work as those
dependencies are not available in Central. Thus, setups that worked in the
past that did not need those no longer work.
Propose moving those three deps to a camel-script-optional feature that
would not be pulled in by default. If a user needs them, they would need to
configure Karaf to pull from another repo.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4443) Upgrade to Scala 2.9.1
[ https://issues.apache.org/jira/browse/CAMEL-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-4443: --- Assignee: Freeman Fang Upgrade to Scala 2.9.1 -- Key: CAMEL-4443 URL: https://issues.apache.org/jira/browse/CAMEL-4443 Project: Camel Issue Type: Task Components: camel-scala Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Minor Fix For: 2.9.0 We need a Scala 2.9.1 osgi bundle from ticket: SMX4-917 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (CAMEL-4443) Upgrade to Scala 2.9.1
[ https://issues.apache.org/jira/browse/CAMEL-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4443 started by Freeman Fang. Upgrade to Scala 2.9.1 -- Key: CAMEL-4443 URL: https://issues.apache.org/jira/browse/CAMEL-4443 Project: Camel Issue Type: Task Components: camel-scala Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Minor Fix For: 2.9.0 We need a Scala 2.9.1 osgi bundle from ticket: SMX4-917 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Apache Camel 2.8.1
Hi, Build servicemix-camel JBI component and smx4 kit against Camel 2.8.1, and all camel related example there works well. Here is my +1 Freeman On 2011-9-7, at 上午3:27, Zbarcea Hadrian wrote: A new patch release apache-camel-2.8.1 is out with approximately 45 issues resolved: improvements and bug fixes [1]. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapachecamel-037/ The tarballs are here https://repository.apache.org/content/repositories/orgapachecamel-037/org/apache/camel/apache-camel/2.8.1/ Tag: http://svn.apache.org/repos/asf/camel/tags/camel-2.8.1/ Please review, test and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache Camel 2.8.1 [ ] -1 Veto the release (provide specific comments) Vote is open for at least 72 hours. Here's my +1 Hadrian [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12317152 - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
[jira] [Created] (CAMEL-4423) use geronimo-jaxws_2.2_spec 1.1 bundle
use geronimo-jaxws_2.2_spec 1.1 bundle -- Key: CAMEL-4423 URL: https://issues.apache.org/jira/browse/CAMEL-4423 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang since geronimo-jaxws_2.2_spec-1.1.jar already fixed the incorrect Import-Package javax.xml.namespace(previously it import javax.xml.namespace with version=1.0, which prevent us to use the one from system bundle, so we have to create a wrapper jaxws 2.2 spec bundle in Servicemix) OSGi header, so we can use it in features.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (CAMEL-4423) use geronimo-jaxws_2.2_spec 1.1 bundle
[ https://issues.apache.org/jira/browse/CAMEL-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4423 started by Freeman Fang. use geronimo-jaxws_2.2_spec 1.1 bundle -- Key: CAMEL-4423 URL: https://issues.apache.org/jira/browse/CAMEL-4423 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang since geronimo-jaxws_2.2_spec-1.1.jar already fixed the incorrect Import-Package javax.xml.namespace(previously it import javax.xml.namespace with version=1.0, which prevent us to use the one from system bundle, so we have to create a wrapper jaxws 2.2 spec bundle in Servicemix) OSGi header, so we can use it in features.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4423) use geronimo-jaxws_2.2_spec 1.1 bundle
[ https://issues.apache.org/jira/browse/CAMEL-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13098858#comment-13098858 ] Freeman Fang commented on CAMEL-4423: - commit fix http://svn.apache.org/viewvc?rev=1166126view=rev for trunk hold merge for 2.8.x branch until 2.8.1 is out(to keep the jaxws bundle same as it used in cxf 2.4.2) use geronimo-jaxws_2.2_spec 1.1 bundle -- Key: CAMEL-4423 URL: https://issues.apache.org/jira/browse/CAMEL-4423 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang since geronimo-jaxws_2.2_spec-1.1.jar already fixed the incorrect Import-Package javax.xml.namespace(previously it import javax.xml.namespace with version=1.0, which prevent us to use the one from system bundle, so we have to create a wrapper jaxws 2.2 spec bundle in Servicemix) OSGi header, so we can use it in features.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4406) use cxf feature from apache-cxf-features.xml
[ https://issues.apache.org/jira/browse/CAMEL-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-4406. - Resolution: Fixed Fix Version/s: 2.9.0 commit fix http://svn.apache.org/viewvc?rev=1164383view=rev use cxf feature from apache-cxf-features.xml Key: CAMEL-4406 URL: https://issues.apache.org/jira/browse/CAMEL-4406 Project: Camel Issue Type: Improvement Components: karaf Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.9.0 currently camel features.xml maintain cxf feature by itself, we should reuse the one from apache-cxf-features.xml instead, this can save effort when upgrade to new cxf version but needn't upgrade lots of cxf feature bundles version accordingly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4406) use cxf feature from apache-cxf-features.xml
[ https://issues.apache.org/jira/browse/CAMEL-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095900#comment-13095900 ] Freeman Fang commented on CAMEL-4406: - back port to 2.8.x branch http://svn.apache.org/viewvc?rev=1164458view=rev use cxf feature from apache-cxf-features.xml Key: CAMEL-4406 URL: https://issues.apache.org/jira/browse/CAMEL-4406 Project: Camel Issue Type: Improvement Components: karaf Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.8.1, 2.9.0 currently camel features.xml maintain cxf feature by itself, we should reuse the one from apache-cxf-features.xml instead, this can save effort when upgrade to new cxf version but needn't upgrade lots of cxf feature bundles version accordingly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4406) use cxf feature from apache-cxf-features.xml
[ https://issues.apache.org/jira/browse/CAMEL-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-4406: Fix Version/s: 2.8.1 use cxf feature from apache-cxf-features.xml Key: CAMEL-4406 URL: https://issues.apache.org/jira/browse/CAMEL-4406 Project: Camel Issue Type: Improvement Components: karaf Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.8.1, 2.9.0 currently camel features.xml maintain cxf feature by itself, we should reuse the one from apache-cxf-features.xml instead, this can save effort when upgrade to new cxf version but needn't upgrade lots of cxf feature bundles version accordingly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: cxf : bean producer consumer
Hi, You misunderstand what the To means, the to(SERVICE_ENDPOINT_URI) means it will connect to an external server which is listening on port 9000, this port isn't started by camel router, it should be some external server already there. Freeman On 2011-9-2, at 下午7:19, skompelly wrote: Hi I am tring to invoke a webserive method from soapui 1) WSDL first approach , generated all the files using maven goal is wsdl2java 2) In the route i have below code ROUTER_ENDPOINT_URI = cxf:// + ROUTER_ADDRESS + ? + SERVICE_CLASS + + WSDL_LOCATION + + SERVICE_NAME + + SOAP_OVER_HTTP_ROUTER + dataFormat=POJO; SERVICE_ENDPOINT_URI = cxf:// + SERVICE_ADDRESS + ? + SERVICE_CLASS + + WSDL_LOCATION + + SERVICE_NAME + + SOAP_OVER_HTTP + dataFormat=POJO; from(ROUTER_ENDPOINT_URI) // this is listening at 9004 .processRef(testProcessor) .to(SERVICE_ENDPOINT_URI) // this one port is 9000 .stop() .end(); once i run mvn camel:run - 9004 port is listening, but 9000 port its not listening as a result i can see the wsdl xml in browser for 9004 but not for 9000. When i sent a message through soapui to invoke a method, i am getting below error. faultcodesoap:Server/faultcode faultstringCould not send Message./faultstring In the logs i am getting the error, attached is log http://camel.465427.n5.nabble.com/file/n4761986/file.txt file.txt Please can anyone let me know i am i doing anything wrong. Same one i am trying with cxf:bean:endpoint , i got the same error. Thanks, Santosh I am using cxf:bean:[endpoint] -- View this message in context: http://camel.465427.n5.nabble.com/cxf-bean-producer-consumer-tp4761986p4761986.html Sent from the Camel Development mailing list archive at Nabble.com. - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
[jira] [Created] (CAMEL-4407) camel-script feature should ship script implementation bundles like groovy/javascript/ruby
camel-script feature should ship script implementation bundles like groovy/javascript/ruby -- Key: CAMEL-4407 URL: https://issues.apache.org/jira/browse/CAMEL-4407 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang the camel-script feature looks like feature name=camel-script version=2.6.0 feature version=2.6.0camel-core/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.camel/camel-script/2.6.0/bundle /feature it has no specific script implementation bundles the servicemix-scripting feature looks like feature name=servicemix-scripting version=2011.01 feature version=2011.01servicemix-shared/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.asm/2.2.3_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.antlr/2.7.7_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.groovy/1.5.6_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.rhino/1.7R1_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jruby/1.1.2_3/bundle bundlemvn:com.google.code.scriptengines/scriptengines-groovy/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-javascript/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-jruby/1.1/bundle bundlemvn:org.apache.servicemix/servicemix-scripting/2011.01/bundle /feature It ship groovy/ruby/javascript implementation bundle. We should do same for camel-script feature, otherwise customer can't use camel-script feature without servicemix-scripting get installed. There's a related discussion on Servciemix mailing list, I think we need fix it in camel -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (CAMEL-4407) camel-script feature should ship script implementation bundles like groovy/javascript/ruby
[ https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4407 started by Freeman Fang. camel-script feature should ship script implementation bundles like groovy/javascript/ruby -- Key: CAMEL-4407 URL: https://issues.apache.org/jira/browse/CAMEL-4407 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang the camel-script feature looks like feature name=camel-script version=2.6.0 feature version=2.6.0camel-core/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.camel/camel-script/2.6.0/bundle /feature it has no specific script implementation bundles the servicemix-scripting feature looks like feature name=servicemix-scripting version=2011.01 feature version=2011.01servicemix-shared/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.asm/2.2.3_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.antlr/2.7.7_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.groovy/1.5.6_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.rhino/1.7R1_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jruby/1.1.2_3/bundle bundlemvn:com.google.code.scriptengines/scriptengines-groovy/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-javascript/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-jruby/1.1/bundle bundlemvn:org.apache.servicemix/servicemix-scripting/2011.01/bundle /feature It ship groovy/ruby/javascript implementation bundle. We should do same for camel-script feature, otherwise customer can't use camel-script feature without servicemix-scripting get installed. There's a related discussion on Servciemix mailing list[1], I think we need fix it in camel [1]http://servicemix.396122.n5.nabble.com/Exception-when-using-JavaScript-expression-in-Camel-routes-td4758137.html#a4761878 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4407) camel-script feature should ship script implementation bundles like groovy/javascript/ruby
[ https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-4407: Description: the camel-script feature looks like feature name=camel-script version=2.6.0 feature version=2.6.0camel-core/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.camel/camel-script/2.6.0/bundle /feature it has no specific script implementation bundles the servicemix-scripting feature looks like feature name=servicemix-scripting version=2011.01 feature version=2011.01servicemix-shared/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.asm/2.2.3_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.antlr/2.7.7_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.groovy/1.5.6_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.rhino/1.7R1_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jruby/1.1.2_3/bundle bundlemvn:com.google.code.scriptengines/scriptengines-groovy/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-javascript/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-jruby/1.1/bundle bundlemvn:org.apache.servicemix/servicemix-scripting/2011.01/bundle /feature It ship groovy/ruby/javascript implementation bundle. We should do same for camel-script feature, otherwise customer can't use camel-script feature without servicemix-scripting get installed. There's a related discussion on Servciemix mailing list[1], I think we need fix it in camel [1]http://servicemix.396122.n5.nabble.com/Exception-when-using-JavaScript-expression-in-Camel-routes-td4758137.html#a4761878 was: the camel-script feature looks like feature name=camel-script version=2.6.0 feature version=2.6.0camel-core/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.camel/camel-script/2.6.0/bundle /feature it has no specific script implementation bundles the servicemix-scripting feature looks like feature name=servicemix-scripting version=2011.01 feature version=2011.01servicemix-shared/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.asm/2.2.3_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.antlr/2.7.7_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.groovy/1.5.6_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.rhino/1.7R1_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jruby/1.1.2_3/bundle bundlemvn:com.google.code.scriptengines/scriptengines-groovy/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-javascript/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-jruby/1.1/bundle bundlemvn:org.apache.servicemix/servicemix-scripting/2011.01/bundle /feature It ship groovy/ruby/javascript implementation bundle. We should do same for camel-script feature, otherwise customer can't use camel-script feature without servicemix-scripting get installed. There's a related discussion on Servciemix mailing list, I think we need fix it in camel camel-script feature should ship script implementation bundles like groovy/javascript/ruby -- Key: CAMEL-4407 URL: https://issues.apache.org/jira/browse/CAMEL-4407 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang the camel-script feature looks like feature name=camel-script version=2.6.0 feature version=2.6.0camel-core/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.camel/camel-script/2.6.0/bundle /feature it has no specific script implementation bundles the servicemix-scripting feature looks like feature name=servicemix-scripting version=2011.01 feature version=2011.01servicemix-shared/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.asm/2.2.3_4/bundle
[jira] [Commented] (CAMEL-4407) camel-script feature should ship script implementation bundles like groovy/javascript/ruby
[ https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095999#comment-13095999 ] Freeman Fang commented on CAMEL-4407: - Hi Claus, Thanks for reminder. Yeah, we need use groovy 1.8.1 here. Regards Freeman camel-script feature should ship script implementation bundles like groovy/javascript/ruby -- Key: CAMEL-4407 URL: https://issues.apache.org/jira/browse/CAMEL-4407 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang the camel-script feature looks like feature name=camel-script version=2.6.0 feature version=2.6.0camel-core/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.camel/camel-script/2.6.0/bundle /feature it has no specific script implementation bundles the servicemix-scripting feature looks like feature name=servicemix-scripting version=2011.01 feature version=2011.01servicemix-shared/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.asm/2.2.3_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.antlr/2.7.7_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.groovy/1.5.6_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.rhino/1.7R1_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jruby/1.1.2_3/bundle bundlemvn:com.google.code.scriptengines/scriptengines-groovy/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-javascript/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-jruby/1.1/bundle bundlemvn:org.apache.servicemix/servicemix-scripting/2011.01/bundle /feature It ship groovy/ruby/javascript implementation bundle. We should do same for camel-script feature, otherwise customer can't use camel-script feature without servicemix-scripting get installed. There's a related discussion on Servciemix mailing list[1], I think we need fix it in camel [1]http://servicemix.396122.n5.nabble.com/Exception-when-using-JavaScript-expression-in-Camel-routes-td4758137.html#a4761878 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4407) camel-script feature should ship script implementation bundles like groovy/javascript/ruby
[ https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-4407. - Resolution: Fixed Fix Version/s: 2.9.0 2.8.1 commit fix http://svn.apache.org/viewvc?rev=1164540view=rev for trunk https://svn.apache.org/repos/asf/camel/trunk for 2.8.x branch camel-script feature should ship script implementation bundles like groovy/javascript/ruby -- Key: CAMEL-4407 URL: https://issues.apache.org/jira/browse/CAMEL-4407 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.8.1, 2.9.0 the camel-script feature looks like feature name=camel-script version=2.6.0 feature version=2.6.0camel-core/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.camel/camel-script/2.6.0/bundle /feature it has no specific script implementation bundles the servicemix-scripting feature looks like feature name=servicemix-scripting version=2011.01 feature version=2011.01servicemix-shared/feature bundlemvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/1.7.0/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.asm/2.2.3_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.antlr/2.7.7_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.groovy/1.5.6_4/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.rhino/1.7R1_3/bundle bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jruby/1.1.2_3/bundle bundlemvn:com.google.code.scriptengines/scriptengines-groovy/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-javascript/1.1/bundle bundlemvn:com.google.code.scriptengines/scriptengines-jruby/1.1/bundle bundlemvn:org.apache.servicemix/servicemix-scripting/2011.01/bundle /feature It ship groovy/ruby/javascript implementation bundle. We should do same for camel-script feature, otherwise customer can't use camel-script feature without servicemix-scripting get installed. There's a related discussion on Servciemix mailing list[1], I think we need fix it in camel [1]http://servicemix.396122.n5.nabble.com/Exception-when-using-JavaScript-expression-in-Camel-routes-td4758137.html#a4761878 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-4406) use cxf feature from apache-cxf-features.xml
use cxf feature from apache-cxf-features.xml Key: CAMEL-4406 URL: https://issues.apache.org/jira/browse/CAMEL-4406 Project: Camel Issue Type: Improvement Components: karaf Reporter: Freeman Fang Assignee: Freeman Fang currently camel features.xml maintain cxf feature by itself, we should reuse the one from apache-cxf-features.xml instead, this can save effort when upgrade to new cxf version but needn't upgrade lots of cxf feature bundles version accordingly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (CAMEL-4406) use cxf feature from apache-cxf-features.xml
[ https://issues.apache.org/jira/browse/CAMEL-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4406 started by Freeman Fang. use cxf feature from apache-cxf-features.xml Key: CAMEL-4406 URL: https://issues.apache.org/jira/browse/CAMEL-4406 Project: Camel Issue Type: Improvement Components: karaf Reporter: Freeman Fang Assignee: Freeman Fang currently camel features.xml maintain cxf feature by itself, we should reuse the one from apache-cxf-features.xml instead, this can save effort when upgrade to new cxf version but needn't upgrade lots of cxf feature bundles version accordingly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4378) camel-zookeper - Add osgi unit tests
[ https://issues.apache.org/jira/browse/CAMEL-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-4378. - Resolution: Fixed commit fix http://svn.apache.org/viewvc?rev=1163523view=rev camel-zookeper - Add osgi unit tests Key: CAMEL-4378 URL: https://issues.apache.org/jira/browse/CAMEL-4378 Project: Camel Issue Type: Sub-task Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Minor Fix For: 2.9.0 We need osgi unit tests in - camel-itest-karaf (easy as it just verify the component can be installed) - camel-itest-osgi (testing the component in use in osgi) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4377) camel-zookeper - Add features.xml
[ https://issues.apache.org/jira/browse/CAMEL-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-4377: --- Assignee: Freeman Fang camel-zookeper - Add features.xml - Key: CAMEL-4377 URL: https://issues.apache.org/jira/browse/CAMEL-4377 Project: Camel Issue Type: Sub-task Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Minor Fix For: 2.9.0 The new camel-zookeper component need to be added to the features.xml file. A possible osgi bundle is needed for zookeper if its not already osgi compliant. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4378) camel-zookeper - Add osgi unit tests
[ https://issues.apache.org/jira/browse/CAMEL-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-4378: --- Assignee: Freeman Fang camel-zookeper - Add osgi unit tests Key: CAMEL-4378 URL: https://issues.apache.org/jira/browse/CAMEL-4378 Project: Camel Issue Type: Sub-task Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Minor Fix For: 2.9.0 We need osgi unit tests in - camel-itest-karaf (easy as it just verify the component can be installed) - camel-itest-osgi (testing the component in use in osgi) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [DISCUSS] - Apache Camel 2.8.1 release
+1 Freeman On 2011-8-25, at 下午3:58, Claus Ibsen wrote: Hi Its been 1 month since Camel 2.8.0 was released. And we have a 2.8 branch where we have merged bug fixes. I suggest that we consider doing a 2.8.1 release in the near term, for example in about 1 - 2 weeks. Apache ActiveMQ 5.6.0 is upgrading to Apache Camel 2.8.x. And as we have a bug fixed in 2.8.1, I would love that AMQ could upgrade and use 2.8.1 instead of 2.8.0. Likewise SMX 4.4 is to be released with Camel 2.8.0. And I guess it would be great if SMX included 2.8.1. There is not so often a new SMX release so it would be good if we included an as most bug free version of 2.8 which would be 2.8.1 release. Any feedback? -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/ - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
[jira] [Work started] (CAMEL-4377) camel-zookeper - Add features.xml
[ https://issues.apache.org/jira/browse/CAMEL-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4377 started by Freeman Fang. camel-zookeper - Add features.xml - Key: CAMEL-4377 URL: https://issues.apache.org/jira/browse/CAMEL-4377 Project: Camel Issue Type: Sub-task Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Minor Fix For: 2.9.0 The new camel-zookeper component need to be added to the features.xml file. A possible osgi bundle is needed for zookeper if its not already osgi compliant. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4377) camel-zookeper - Add features.xml
[ https://issues.apache.org/jira/browse/CAMEL-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090860#comment-13090860 ] Freeman Fang commented on CAMEL-4377: - The zookeeper 3.3.3 is already OSGi friendly Freeman camel-zookeper - Add features.xml - Key: CAMEL-4377 URL: https://issues.apache.org/jira/browse/CAMEL-4377 Project: Camel Issue Type: Sub-task Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Minor Fix For: 2.9.0 The new camel-zookeper component need to be added to the features.xml file. A possible osgi bundle is needed for zookeper if its not already osgi compliant. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [DISCUSS] - Apache Camel 2.8.1 release
On 2011-8-25, at 下午4:12, Claus Ibsen wrote: On Thu, Aug 25, 2011 at 10:05 AM, Jean-Baptiste Onofré j...@nanthrax.ne t wrote: Hi Claus, +1, I guess that we could merge some fixes in this release (for instance, the xstream 1.4.1 update, etc).WDYT ? I would actually discourage against bigger dependency updates such as xstream 1.3 - 1.4. There was already some issues in xstream 1.4 so they had to do a 1.4.1. However if there is an update like groovy 1.8.0 - 1.8.1 we may consider that. Likewise I guess possible CXF 2.4.1 - 2.4.2 +1 to upgrade to 2.4.2, so that the upcoming servicemix 4.4 release can also pick up cxf 2.4.2 Freeman But yeah we should go over the JIRA tickets which has been fixed for 2.9 and backport bug fixes which can be easily backported. I will update ServiceMix to include Camel 2.8.1. Regards JB On 08/25/2011 09:58 AM, Claus Ibsen wrote: Hi Its been 1 month since Camel 2.8.0 was released. And we have a 2.8 branch where we have merged bug fixes. I suggest that we consider doing a 2.8.1 release in the near term, for example in about 1 - 2 weeks. Apache ActiveMQ 5.6.0 is upgrading to Apache Camel 2.8.x. And as we have a bug fixed in 2.8.1, I would love that AMQ could upgrade and use 2.8.1 instead of 2.8.0. Likewise SMX 4.4 is to be released with Camel 2.8.0. And I guess it would be great if SMX included 2.8.1. There is not so often a new SMX release so it would be good if we included an as most bug free version of 2.8 which would be 2.8.1 release. Any feedback? -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/ - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
[jira] [Resolved] (CAMEL-4377) camel-zookeper - Add features.xml
[ https://issues.apache.org/jira/browse/CAMEL-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-4377. - Resolution: Fixed commit fix http://svn.apache.org/viewvc?rev=1161465view=rev camel-zookeper - Add features.xml - Key: CAMEL-4377 URL: https://issues.apache.org/jira/browse/CAMEL-4377 Project: Camel Issue Type: Sub-task Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Minor Fix For: 2.9.0 The new camel-zookeper component need to be added to the features.xml file. A possible osgi bundle is needed for zookeper if its not already osgi compliant. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (CAMEL-4378) camel-zookeper - Add osgi unit tests
[ https://issues.apache.org/jira/browse/CAMEL-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4378 started by Freeman Fang. camel-zookeper - Add osgi unit tests Key: CAMEL-4378 URL: https://issues.apache.org/jira/browse/CAMEL-4378 Project: Camel Issue Type: Sub-task Reporter: Claus Ibsen Assignee: Freeman Fang Priority: Minor Fix For: 2.9.0 We need osgi unit tests in - camel-itest-karaf (easy as it just verify the component can be installed) - camel-itest-osgi (testing the component in use in osgi) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4379) upgrade to jetty 7.4.5.v20110725
[ https://issues.apache.org/jira/browse/CAMEL-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090960#comment-13090960 ] Freeman Fang commented on CAMEL-4379: - Hi Jon, Would you please also backport this fix to camel 2.8.x branch? As Servicemix will use camel 2.8.x for next release. Thanks Freeman upgrade to jetty 7.4.5.v20110725 Key: CAMEL-4379 URL: https://issues.apache.org/jira/browse/CAMEL-4379 Project: Camel Issue Type: Task Reporter: Jonathan Anstey Assignee: Jonathan Anstey Fix For: 2.9.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [DISCUSS] - Dropping Maven 2.x support
+1 Freeman On 2011-8-14, at 下午5:35, Claus Ibsen wrote: Hi I wonder if we should consider dropping any official support for Maven 2.x on the Apache Camel project? I guess most people is now migrated to Maven 3.0. And the last number of releases has been done using Maven 3.0.x. Also in light of JDK 7 is now GA, and thus there could be issues with old Maven 2.x to use that to build Apache Camel. And the maintainers of Maven is most likely to focus on Maven 3.x to fix any JDK 7 issues and whatnot. We may want to coordinate this with some of the Apache projects that we work closely with such as - Apache ServiceMix - Apache Karaf - Apache CXF - Apache ActiveMQ As some people use Maven to build all the projects from the source. For example for Camel 2.9 we could put out in the release notes that Maven 2.x supports is being @deprecated and expected to be dropped in a future release. Then at least we have put out the word that Maven 2.x is to be dropped. Any thoughts? -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/ - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [DISCUSS] - Adjust Apache Camel product descriptions
On 2011-8-13, at 下午7:14, Claus Ibsen wrote: Hi I noticed the README.txt file in the distribution kit starts as follows: Apache Camel is a powerful Spring based Integration Framework. And our website starts as follows: Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful Bean Integration. I think we should align the product descriptions on the web site and the README.txt file. There may be other places the product description is present, and could use a bit upgrade. For example I think the README.txt file is a bit outdated as it gives the impression that Camel requires Spring and is Spring based. As we all know Camel is more than that and we try to be neutral and let people use and run Camel in any kind of environment. Whether its Spring, OSGi, Karaf, ServiceMix, WebSphere, Cloud, Scala, Standalone etc. So anyone got suggestions/feedback to have the product description updated a bit to reflect where we are today with Apache Camel? For example we may want to mention Apache Karaf on the front page as a product that Camel runs with out of the box. etc. +1 for adjusting Camel Product descriptions. And I think we should mention Camel runs with Apache Servicemix out of the box instead of Apache karaf, as Apache Servicemix ships camel features.xml by default and fine-tune the jre export package and boot.delegation(such as jaxb and jaxws) which ensure camel components run. Freeman -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/ - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [jira] [Commented] (CAMEL-4308) commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports
Hi Claus, commons-dbcp may not be used directly by camel components. But as datasource like org.apache.commons.dbcp.BasicDataSource is popularly used by specifying DAO when use database related camel features such as camel-jpa, so I'm not sure simply remove commons-dbcp bundle from camel features.xml is a good idea. Best Regards Freeman On 2011-8-6, at 下午5:12, Claus Ibsen wrote: On Sat, Aug 6, 2011 at 3:31 AM, Freeman Fang freeman.f...@gmail.com wrote: Hi Christian, Yeah, If camel team agree to upgrade to commons-dbcp 1.4 then we can use SMX wrapped commons-dbcp 1.4 bundle directly. If there's no other objection I'll append a patch which upgrade to commons-dbcp 1.4 also. The commons-dbcp is not used by any of the camel components in non osgi mode. So its something somebody added in the features file. Its not required by Camel or by the 3rd party components. I wonder if we can just remove it? In the features file its listed in - camel-bam - camel-ibatis - camel-jpa - camel-mybatis - camel-quartz Best Regards Freeman On 2011-8-6, at 上午12:50, Christian Müller wrote: I wonder is there a reason not to upgrade Camel to use commons- dbcp 1.4 when SMX already use this version? Best, Christian On Fri, Aug 5, 2011 at 9:27 AM, Freeman Fang (JIRA) j...@apache.org wrote: [ https://issues.apache.org/jira/browse/CAMEL-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079810 #comment-13079810] Freeman Fang commented on CAMEL-4308: - I noticed that camel now use commons-dbcp 1.3 but in servicemix we have wrapped commons-dbcp 1.2.2 and 1.4, so I create SMX4-892[1] and will add commons-dbcp 1.3 bundle in servicemix firstly. [1]https://issues.apache.org/jira/browse/SMX4-892 Freeman commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports --- Key: CAMEL-4308 URL: https://issues.apache.org/jira/browse/ CAMEL-4308 Project: Camel Issue Type: Improvement Reporter: Freeman Fang currently the commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports, it will cause exception like org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver' as JDBC driver class not found actually is a common issue in OSGi container, this problem generally from a bundle(let's say it bundle A, commons-dbcp in this case) using some code like classForName(jdbc_driver_classname) to init a jdbc driver class, this is a big problem in OSGi world, as if BundleA not import package for jdbc_driver_classname, we'll see the problem. However BundleA actually can't know about package name for jdbc_driver_classname beforehand, as the jdbc_driver_classname generally is passed in through configuration during runtime, it can't be determined during build time, so we can't add correct package import when we generate bundle A. The general solution is 1. add dynamic import for bundle A(commons-dbcp) or 2. create JDBC driver as a fragment bundle, and attach it to bundle A(bundle A is host bundle now), so that all resource from fragment bundle is available for the host bundle. Solution 1 left less effort for end user and n servicemix wrapped commons-dbcp bundle we already have dynamic-import header and I think camel features should use the servicemix wrapped commons-dbcp bundle as well. I will append a patch soon. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/ - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
[jira] [Updated] (CAMEL-4308) commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports
[ https://issues.apache.org/jira/browse/CAMEL-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-4308: Attachment: CAMEL-4308.patch append patch which use smx wrapped commons-dbcp 1.4 bundle and also upgrade commons-dbcp version used in camel to 1.4 commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports --- Key: CAMEL-4308 URL: https://issues.apache.org/jira/browse/CAMEL-4308 Project: Camel Issue Type: Improvement Reporter: Freeman Fang Attachments: CAMEL-4308.patch currently the commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports, it will cause exception like org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver' as JDBC driver class not found actually is a common issue in OSGi container, this problem generally from a bundle(let's say it bundle A, commons-dbcp in this case) using some code like classForName(jdbc_driver_classname) to init a jdbc driver class, this is a big problem in OSGi world, as if BundleA not import package for jdbc_driver_classname, we'll see the problem. However BundleA actually can't know about package name for jdbc_driver_classname beforehand, as the jdbc_driver_classname generally is passed in through configuration during runtime, it can't be determined during build time, so we can't add correct package import when we generate bundle A. The general solution is 1. add dynamic import for bundle A(commons-dbcp) or 2. create JDBC driver as a fragment bundle, and attach it to bundle A(bundle A is host bundle now), so that all resource from fragment bundle is available for the host bundle. Solution 1 left less effort for end user and n servicemix wrapped commons-dbcp bundle we already have dynamic-import header and I think camel features should use the servicemix wrapped commons-dbcp bundle as well. I will append a patch soon. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-4308) commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports
commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports --- Key: CAMEL-4308 URL: https://issues.apache.org/jira/browse/CAMEL-4308 Project: Camel Issue Type: Improvement Reporter: Freeman Fang currently the commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports, it will cause exception like org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver' as JDBC driver class not found actually is a common issue in OSGi container, this problem generally from a bundle(let's say it bundle A, commons-dbcp in this case) using some code like classForName(jdbc_driver_classname) to init a jdbc driver class, this is a big problem in OSGi world, as if BundleA not import package for jdbc_driver_classname, we'll see the problem. However BundleA actually can't know about package name for jdbc_driver_classname beforehand, as the jdbc_driver_classname generally is passed in through configuration during runtime, it can't be determined during build time, so we can't add correct package import when we generate bundle A. The general solution is 1. add dynamic import for bundle A(commons-dbcp) or 2. create JDBC driver as a fragment bundle, and attach it to bundle A(bundle A is host bundle now), so that all resource from fragment bundle is available for the host bundle. Solution 1 left less effort for end user and n servicemix wrapped commons-dbcp bundle we already have dynamic-import header and I think camel features should use the servicemix wrapped commons-dbcp bundle as well. I will append a patch soon. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4308) commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports
[ https://issues.apache.org/jira/browse/CAMEL-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079810#comment-13079810 ] Freeman Fang commented on CAMEL-4308: - I noticed that camel now use commons-dbcp 1.3 but in servicemix we have wrapped commons-dbcp 1.2.2 and 1.4, so I create SMX4-892[1] and will add commons-dbcp 1.3 bundle in servicemix firstly. [1]https://issues.apache.org/jira/browse/SMX4-892 Freeman commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports --- Key: CAMEL-4308 URL: https://issues.apache.org/jira/browse/CAMEL-4308 Project: Camel Issue Type: Improvement Reporter: Freeman Fang currently the commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports, it will cause exception like org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver' as JDBC driver class not found actually is a common issue in OSGi container, this problem generally from a bundle(let's say it bundle A, commons-dbcp in this case) using some code like classForName(jdbc_driver_classname) to init a jdbc driver class, this is a big problem in OSGi world, as if BundleA not import package for jdbc_driver_classname, we'll see the problem. However BundleA actually can't know about package name for jdbc_driver_classname beforehand, as the jdbc_driver_classname generally is passed in through configuration during runtime, it can't be determined during build time, so we can't add correct package import when we generate bundle A. The general solution is 1. add dynamic import for bundle A(commons-dbcp) or 2. create JDBC driver as a fragment bundle, and attach it to bundle A(bundle A is host bundle now), so that all resource from fragment bundle is available for the host bundle. Solution 1 left less effort for end user and n servicemix wrapped commons-dbcp bundle we already have dynamic-import header and I think camel features should use the servicemix wrapped commons-dbcp bundle as well. I will append a patch soon. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4308) commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports
[ https://issues.apache.org/jira/browse/CAMEL-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13080321#comment-13080321 ] Freeman Fang commented on CAMEL-4308: - Hi Christian, Yeah, If camel team agree to upgrade to commons-dbcp 1.4 then we can use SMX wrapped commons-dbcp 1.4 bundle directly. If there's no other objection I'll append a patch which upgrade to commons-dbcp 1.4 also. Freeman commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports --- Key: CAMEL-4308 URL: https://issues.apache.org/jira/browse/CAMEL-4308 Project: Camel Issue Type: Improvement Reporter: Freeman Fang currently the commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports, it will cause exception like org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver' as JDBC driver class not found actually is a common issue in OSGi container, this problem generally from a bundle(let's say it bundle A, commons-dbcp in this case) using some code like classForName(jdbc_driver_classname) to init a jdbc driver class, this is a big problem in OSGi world, as if BundleA not import package for jdbc_driver_classname, we'll see the problem. However BundleA actually can't know about package name for jdbc_driver_classname beforehand, as the jdbc_driver_classname generally is passed in through configuration during runtime, it can't be determined during build time, so we can't add correct package import when we generate bundle A. The general solution is 1. add dynamic import for bundle A(commons-dbcp) or 2. create JDBC driver as a fragment bundle, and attach it to bundle A(bundle A is host bundle now), so that all resource from fragment bundle is available for the host bundle. Solution 1 left less effort for end user and n servicemix wrapped commons-dbcp bundle we already have dynamic-import header and I think camel features should use the servicemix wrapped commons-dbcp bundle as well. I will append a patch soon. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (CAMEL-4308) commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports
Hi Christian, Yeah, If camel team agree to upgrade to commons-dbcp 1.4 then we can use SMX wrapped commons-dbcp 1.4 bundle directly. If there's no other objection I'll append a patch which upgrade to commons-dbcp 1.4 also. Best Regards Freeman On 2011-8-6, at 上午12:50, Christian Müller wrote: I wonder is there a reason not to upgrade Camel to use commons-dbcp 1.4 when SMX already use this version? Best, Christian On Fri, Aug 5, 2011 at 9:27 AM, Freeman Fang (JIRA) j...@apache.org wrote: [ https://issues.apache.org/jira/browse/CAMEL-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079810 #comment-13079810] Freeman Fang commented on CAMEL-4308: - I noticed that camel now use commons-dbcp 1.3 but in servicemix we have wrapped commons-dbcp 1.2.2 and 1.4, so I create SMX4-892[1] and will add commons-dbcp 1.3 bundle in servicemix firstly. [1]https://issues.apache.org/jira/browse/SMX4-892 Freeman commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports --- Key: CAMEL-4308 URL: https://issues.apache.org/jira/browse/CAMEL-4308 Project: Camel Issue Type: Improvement Reporter: Freeman Fang currently the commons-dbcp bundle used in camel feature.xml doesn't allow dynamic imports, it will cause exception like org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver' as JDBC driver class not found actually is a common issue in OSGi container, this problem generally from a bundle(let's say it bundle A, commons- dbcp in this case) using some code like classForName(jdbc_driver_classname) to init a jdbc driver class, this is a big problem in OSGi world, as if BundleA not import package for jdbc_driver_classname, we'll see the problem. However BundleA actually can't know about package name for jdbc_driver_classname beforehand, as the jdbc_driver_classname generally is passed in through configuration during runtime, it can't be determined during build time, so we can't add correct package import when we generate bundle A. The general solution is 1. add dynamic import for bundle A(commons-dbcp) or 2. create JDBC driver as a fragment bundle, and attach it to bundle A(bundle A is host bundle now), so that all resource from fragment bundle is available for the host bundle. Solution 1 left less effort for end user and n servicemix wrapped commons-dbcp bundle we already have dynamic-import header and I think camel features should use the servicemix wrapped commons-dbcp bundle as well. I will append a patch soon. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [DISCUSS] - Removing the camel-example-axis
+1 And cxf is a better candidate to show soap related feature IMHO. Freeman On 2011-7-22, at 上午12:04, Claus Ibsen wrote: Hi In the current Camel kit we have about 34 examples (give or take). One of these is the camel-example-axis. Its a very old example I created 3 years ago, when Camel was still in 1.x and rather new. The example uses Apache Axis 1.4 and uses Spring Servlet to show how to use the spring way back then to use Axis from a Spring Servlet. And then use a ProducerTemplate from that servlet to call Camel. I would propose that we remove this example as its outdated and not best practice anymore. We have new users to Camel that try it out, and get a bit confused. For example in Eclipse they get many warnings, due Axis auto generated code is not Java5 ready, and the Spring framework have deprecated the Spring Servlet as well. Also Axis 1.4 is well EOL. Any objections to removing this example? -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/ - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [VOTE] Release Apache Camel 2.8.0
+1(non-binding) Freeman On 2011-7-19, at 上午10:13, Zbarcea Hadrian wrote: A new minor release apache-camel-2.8.0 is out with approximately 420 issues resolved: improvements and bug fixes [1]. This is a release with a record number of fixes and reflects the increased popularity of Apache Camel and our growing community. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapachecamel-003/ The tarballs are here https://repository.apache.org/content/repositories/orgapachecamel-003/org/apache/camel/apache-camel/2.8.0/ Tag: http://svn.apache.org/repos/asf/camel/tags/camel-2.8.0/ Please review, test and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache Camel 2.8.0 [ ] -1 Veto the release (provide specific comments) Vote is open for at least 72 hours. Here's my +1 Hadrian [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12316226 - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
Re: [VOTE] Release Camel 2.7.3
+1 Freeman On 2011-7-14, at 上午2:31, Daniel Kulp wrote: This is a vote to release Camel 2.7.3. 2.7.3 contains fixes for over 70 JIRA issues that would be good to get into the hands of Camel users. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapachecamel-022/ The tarballs are here https://repository.apache.org/content/repositories/orgapachecamel-022/org/apache/camel/apache-camel/2.7.3/ Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12316520 Tag: http://svn.apache.org/repos/asf/camel/tags/camel-2.7.3/ Please review, test and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache Camel 2.7.3 [ ] -1 Don't release (provide specific comments) I'll leave the vote open until at least Monday. -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com - Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com
[jira] [Created] (CAMEL-4231) shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi container
shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi container
---
Key: CAMEL-4231
URL: https://issues.apache.org/jira/browse/CAMEL-4231
Project: Camel
Issue Type: Bug
Components: camel-core
Reporter: Freeman Fang
the Activator in camel-core take care of loading the converters from bundles,
we should avoid calling BaseTypeConverterRegistry.loadTypeConverters() in OSGi
container, otherwise due to no classloader was specified, see this code in
OsgiTypeConverter
@Override
public SetClassLoader getClassLoaders() {
// we don't need any classloaders as we use osgi service
tracker instead
return Collections.emptySet();
}
we'll get exception like
Caused by: org.apache.camel.TypeConverterLoaderException: Failed to load type
converters because of: Cannot find any type converter classes from the
following packages: [org.apache.servicemix.camel.converter]
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:90)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:406)
at
org.apache.camel.impl.converter.DefaultTypeConverter.doStart(DefaultTypeConverter.java:42)
at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:67)
at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:54)
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:56)
at
org.apache.camel.core.osgi.OsgiTypeConverter.createRegistry(OsgiTypeConverter.java:163)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4231) shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi container
[
https://issues.apache.org/jira/browse/CAMEL-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated CAMEL-4231:
Fix Version/s: 2.8.0
shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi
container
---
Key: CAMEL-4231
URL: https://issues.apache.org/jira/browse/CAMEL-4231
Project: Camel
Issue Type: Bug
Components: camel-core
Reporter: Freeman Fang
Fix For: 2.8.0
the Activator in camel-core take care of loading the converters from bundles,
we should avoid calling BaseTypeConverterRegistry.loadTypeConverters() in
OSGi container, otherwise due to no classloader was specified, see this code
in OsgiTypeConverter
@Override
public SetClassLoader getClassLoaders() {
// we don't need any classloaders as we use osgi service
tracker instead
return Collections.emptySet();
}
we'll get exception like
Caused by: org.apache.camel.TypeConverterLoaderException: Failed to load type
converters because of: Cannot find any type converter classes from the
following packages: [org.apache.servicemix.camel.converter]
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:90)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:406)
at
org.apache.camel.impl.converter.DefaultTypeConverter.doStart(DefaultTypeConverter.java:42)
at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:67)
at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:54)
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:56)
at
org.apache.camel.core.osgi.OsgiTypeConverter.createRegistry(OsgiTypeConverter.java:163)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4231) shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi container
[
https://issues.apache.org/jira/browse/CAMEL-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated CAMEL-4231:
Attachment: CAMEL-4231.patch
shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi
container
---
Key: CAMEL-4231
URL: https://issues.apache.org/jira/browse/CAMEL-4231
Project: Camel
Issue Type: Bug
Components: camel-core
Reporter: Freeman Fang
Fix For: 2.8.0
Attachments: CAMEL-4231.patch
the Activator in camel-core take care of loading the converters from bundles,
we should avoid calling BaseTypeConverterRegistry.loadTypeConverters() in
OSGi container, otherwise due to no classloader was specified, see this code
in OsgiTypeConverter
@Override
public SetClassLoader getClassLoaders() {
// we don't need any classloaders as we use osgi service
tracker instead
return Collections.emptySet();
}
we'll get exception like
Caused by: org.apache.camel.TypeConverterLoaderException: Failed to load type
converters because of: Cannot find any type converter classes from the
following packages: [org.apache.servicemix.camel.converter]
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:90)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:406)
at
org.apache.camel.impl.converter.DefaultTypeConverter.doStart(DefaultTypeConverter.java:42)
at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:67)
at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:54)
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:56)
at
org.apache.camel.core.osgi.OsgiTypeConverter.createRegistry(OsgiTypeConverter.java:163)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-4232) duplicated camel-core-osgi module in camel-spring and camel-blueprint
duplicated camel-core-osgi module in camel-spring and camel-blueprint - Key: CAMEL-4232 URL: https://issues.apache.org/jira/browse/CAMEL-4232 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Freeman Fang Fix For: 2.9.0 I found that both camel-spring and camel-blueprint embeded camel-core-osgi module, that's not the best practice in OSGi container. We should install camel-core-osgi as a separate bundle which could be shared by camel-spring and camel-blueprint -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
