[
https://issues.apache.org/activemq/browse/CAMEL-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-2018:
--
Assignee: Claus Ibsen
> Timer Endpoint starts the thread before configuration
> ---
[
https://issues.apache.org/activemq/browse/CAMEL-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54328#action_54328
]
Claus Ibsen commented on CAMEL-2023:
Christian, see CAMEL-1850 which implements this.
>
[
https://issues.apache.org/activemq/browse/CAMEL-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54326#action_54326
]
Claus Ibsen commented on CAMEL-1675:
Cool
Ashwin the components are on a special page: C
[
https://issues.apache.org/activemq/browse/CAMEL-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54327#action_54327
]
Claus Ibsen commented on CAMEL-2007:
Cool
Ashwin the components are on a special page: C
[
https://issues.apache.org/activemq/browse/CAMEL-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated CAMEL-1989:
Affects Version/s: (was: 2.2.0)
2.1.0
> Implement support for JAX-WS
[
https://issues.apache.org/activemq/browse/CAMEL-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-1989.
-
Resolution: Fixed
Fix Version/s: (was: 2.2.0)
2.1.0
Applied pat
[
https://issues.apache.org/activemq/browse/CAMEL-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-1989:
---
Assignee: Willem Jiang (was: William Tam)
> Implement support for JAX-WS beans
> ---
[
https://issues.apache.org/activemq/browse/CAMEL-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54324#action_54324
]
Christian Mueller commented on CAMEL-2023:
--
If you agree with this contribution, I w
[
https://issues.apache.org/activemq/browse/CAMEL-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Mueller updated CAMEL-2023:
-
Attachment: camel-velocity.patch
camel-velocity-tests.patch
> Allow t
Allow the usage of velocity templates, which are placed/defined in the
exchanges In message header or attachment
Key: CAMEL-2023
URL: https://issues.a
[
https://issues.apache.org/activemq/browse/CAMEL-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54323#action_54323
]
Ashwin Karpe commented on CAMEL-1675:
-
Hi Claus & Jon,
I have added the Camel Printer p
[
https://issues.apache.org/activemq/browse/CAMEL-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54322#action_54322
]
Ashwin Karpe commented on CAMEL-2007:
-
Hi Claus,
I have added the Camel Cache page to t
[
https://issues.apache.org/activemq/browse/CAMEL-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated CAMEL-2022:
---
Attachment: CAMEL-2022.patch
Attach work in progress. Does not even compile ...
> Bluep
Blueprint support
-
Key: CAMEL-2022
URL: https://issues.apache.org/activemq/browse/CAMEL-2022
Project: Apache Camel
Issue Type: New Feature
Reporter: Guillaume Nodet
--
This message is automatically generated
Schema versioning for camel-spring schema
-
Key: CAMEL-2021
URL: https://issues.apache.org/activemq/browse/CAMEL-2021
Project: Apache Camel
Issue Type: Bug
Components: camel-spring
Affect
[
https://issues.apache.org/activemq/browse/CAMEL-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved CAMEL-1988.
Resolution: Fixed
Marking this issue as resolved as mostly everyhing is in place.
I wil
On Thu, Sep 17, 2009 at 11:17, Claus Ibsen wrote:
> On Thu, Sep 17, 2009 at 10:55 AM, Guillaume Nodet wrote:
>> I've looked at both spring-dm and blueprint, and there is no way to
>> have a single schema namespace supported by two different handlers.
>> I mean, you can always do that, but you hav
[
https://issues.apache.org/activemq/browse/CAMEL-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated CAMEL-1936:
Affects Version/s: 1.5.0
1.6.0
2.0-M1
[
https://issues.apache.org/activemq/browse/CAMEL-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54304#action_54304
]
Willem Jiang commented on CAMEL-1936:
-
back port the patch into camel-1.x branch
http://s
[
https://issues.apache.org/activemq/browse/CAMEL-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated CAMEL-1936:
Fix Version/s: 1.6.2
> TypeConverters aren't loaded in OSGi when bundle is not started
> --
[
https://issues.apache.org/activemq/browse/CAMEL-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-2020.
-
Resolution: Fixed
trunk
http://svn.apache.org/viewvc?rev=816105&view=rev
camel 1.x branch
>> Having the schema versioned with 2.1, 2.2, etc sounds good to me.
+1 for versioning the schema - from the tools p.o.v. it
makes life easier as things like XML editors can cope
better with on-the-fly validation and element/attribute
completion options.
> Hmmm so in all other situations with OSG
NPE when the bundle is camel-osgi bundle is inactive
Key: CAMEL-2020
URL: https://issues.apache.org/activemq/browse/CAMEL-2020
Project: Apache Camel
Issue Type: Bug
Affects Versions: 2
On Thu, Sep 17, 2009 at 10:55 AM, Guillaume Nodet wrote:
> I've looked at both spring-dm and blueprint, and there is no way to
> have a single schema namespace supported by two different handlers.
> I mean, you can always do that, but you have no way to control which
> one will be used.
> So I gue
I've looked at both spring-dm and blueprint, and there is no way to
have a single schema namespace supported by two different handlers.
I mean, you can always do that, but you have no way to control which
one will be used.
So I guess versionning the schema is the only solution.
Having the schema v
Same here.
On Thu, Sep 17, 2009 at 10:49, Willem Jiang wrote:
> Hi Claus,
>
> The mock-javamail-1.7 building is passed on my box.
> Here is my environment.
>
> Apache Maven 2.2.0 (r788681; 2009-06-26 21:04:01+0800)
> Java version: 1.5.0_20
> Java home: /System/Library/Frameworks/JavaVM.framework/
Hi Claus,
The mock-javamail-1.7 building is passed on my box.
Here is my environment.
Apache Maven 2.2.0 (r788681; 2009-06-26 21:04:01+0800)
Java version: 1.5.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
Default locale: en_US, platform encoding: MacRoman
OS nam
+1 for adding the version number on the camel-spring namespace.
But I don't know if the "http://camel.apache.org/schema/spring/2.1"; is
enough for use to pick the camel-spring 2.1.x instead of camel 2.1.0.
Willem
Gert Vanthienen wrote:
L.S.,
How about we register the default namespace
"http:
L.S.,
How about we register the default namespace
"http://camel.apache.org/schema/spring"; as well as a version-specific
namespace "http://camel.apache.org/schema/spring/2.1"; with the
namespace handler? If people are only using one version, they can
still use the default namespace and if they wa
On Thu, Sep 17, 2009 at 09:59, Claus Ibsen wrote:
> Hi
>
> This must be an universal problem with OSGi + Spring + Your Apps and
> having multiple versions in same container.
I think it is. I'll have a closer look as the spring-dm code, but I
suspect the only way would be to version the schema co
Right, I missed that. So the point is moot.
But as Claus noted, the problem will also happen between 2.1.x and 2.2.x ...
On Thu, Sep 17, 2009 at 09:52, Willem Jiang wrote:
> Hi Guillaume,
>
> Camel 1.6.x is still using the old namespace for the namespace handler
> "http://activemq.apache.org/cam
Yes, this is because OSGi versioning is strictly defined.
So we need to translate the maven version into an OSGi version.
Usually, the work is done by the maven bundle plugin, but in our case,
it's not completely covered yet, so I had to do a bit of maven-antrun
plugin to do this transformation.
I
On Thu, Sep 17, 2009 at 9:52 AM, Willem Jiang wrote:
> Hi Guillaume,
>
> Camel 1.6.x is still using the old namespace for the namespace handler
> "http://activemq.apache.org/camel/schema/spring";
>
> Can you check if your camel context is updated to new camel namespace
> "http://camel.apache.org/s
Hi
Just wondering about the versions below. I assume its correct that
OSGI is not identical to the maven version?
[INFO] Executing tasks
[echo] Maven version: 2.1-SNAPSHOT
[echo] OSGi version:2.1.0.SNAPSHOT
[mkdir] Created dir: /Users/davsclaus/workspace/camel/tooling/target
This one is failing with a mvn clean install -Dtest=false from camel trunk
[INFO] Building Apache Camel Test Bundles: mock-javamail-1.7
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting file
Hi
This must be an universal problem with OSGi + Spring + Your Apps and
having multiple versions in same container.
For example Mule ESB is also leveraging spring namespace handler and
thus will have same issue. So what are they doing?
Don't you have specified in the bundle that contains the cam
Hi Guillaume,
Camel 1.6.x is still using the old namespace for the namespace handler
"http://activemq.apache.org/camel/schema/spring";
Can you check if your camel context is updated to new camel namespace
"http://camel.apache.org/schema/spring";
Willem
Guillaume Nodet wrote:
Unfortunately, I
Unfortunately, I doubt it will work. The reason is that only the
schema namespace is used to choose the namespace handler, not it's
location, and both namespaces are defined by:
http://camel.apache.org/schema/spring
On Thu, Sep 17, 2009 at 09:31, Charles Moulliard wrote:
> Guillaume,
>
> I t
Guillaume,
I think that you can solve easily the problem by specifying in the xml file,
the version of the camel-spring file
By default, you don't mention it in the schema location and the last ont
will be used (so now 2.0)
xsi:schemaLocation="
http://www.springframework.org/schema/b
Ok, I'm mostly done with the OSGi metadata.
I've committed fixes to both trunk and 1.x branch.
But my original goal is only partially achieved.
I've run some basic tests in Karaf and deployed camel 1.6-SNAPSHOT and
2.1-SNAPSHOT.
Then, I deployed a simple spring-powered camel route and dropped it
i
40 matches
Mail list logo
