You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/09/28 06:19:40 UTC
[jira] Created: (CAMEL-3167) Be able to use constant from java
classes in Spring XML
Be able to use constant from java classes in Spring XML
-------------------------------------------------------
Key: CAMEL-3167
URL: https://issues.apache.org/activemq/browse/CAMEL-3167
Project: Apache Camel
Issue Type: New Feature
Components: camel-core, camel-spring
Affects Versions: 2.4.0
Reporter: Claus Ibsen
Priority: Minor
Fix For: 2.6.0
For example you want to do
{code:xml}
<setHeader headerName="Exchange.CONTENT_TYPE">
<constant>application/exi</constant>
</setHeader>
{code}
By using the constants on {{Exchange}} you can have Camel check this on startup, that the constant exists and use its value. This ensures that any spelling errors is detected on startup. So if you typed:
{code:xml}
<setHeader headerName="Exchange.CNTENT_TYP">
<constant>application/exi</constant>
</setHeader>
{code}
Then Camel can see there is no constant with the name {{CNTENT_TYP}} and throw an exception on startup.
This also makes it easier to do a 1:1 between Java DSL and Spring XML.
See also
http://fusesource.com/forums/thread.jspa?threadID=2285&tstart=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-3167) Be able to use constant from java
classes in Spring XML
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-3167:
----------------------------------
Assignee: Claus Ibsen
> Be able to use constant from java classes in Spring XML
> -------------------------------------------------------
>
> Key: CAMEL-3167
> URL: https://issues.apache.org/activemq/browse/CAMEL-3167
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core, camel-spring
> Affects Versions: 2.4.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.6.0
>
>
> For example you want to do
> {code:xml}
> <setHeader headerName="Exchange.CONTENT_TYPE">
> <constant>application/exi</constant>
> </setHeader>
> {code}
> By using the constants on {{Exchange}} you can have Camel check this on startup, that the constant exists and use its value. This ensures that any spelling errors is detected on startup. So if you typed:
> {code:xml}
> <setHeader headerName="Exchange.CNTENT_TYP">
> <constant>application/exi</constant>
> </setHeader>
> {code}
> Then Camel can see there is no constant with the name {{CNTENT_TYP}} and throw an exception on startup.
> This also makes it easier to do a 1:1 between Java DSL and Spring XML.
> See also
> http://fusesource.com/forums/thread.jspa?threadID=2285&tstart=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-3167) Be able to use constant from java
classes in Spring XML
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-3167.
--------------------------------
Resolution: Fixed
trunk: 1039384.
> Be able to use constant from java classes in Spring XML
> -------------------------------------------------------
>
> Key: CAMEL-3167
> URL: https://issues.apache.org/activemq/browse/CAMEL-3167
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core, camel-spring
> Affects Versions: 2.4.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.6.0
>
>
> For example you want to do
> {code:xml}
> <setHeader headerName="Exchange.CONTENT_TYPE">
> <constant>application/exi</constant>
> </setHeader>
> {code}
> By using the constants on {{Exchange}} you can have Camel check this on startup, that the constant exists and use its value. This ensures that any spelling errors is detected on startup. So if you typed:
> {code:xml}
> <setHeader headerName="Exchange.CNTENT_TYP">
> <constant>application/exi</constant>
> </setHeader>
> {code}
> Then Camel can see there is no constant with the name {{CNTENT_TYP}} and throw an exception on startup.
> This also makes it easier to do a 1:1 between Java DSL and Spring XML.
> See also
> http://fusesource.com/forums/thread.jspa?threadID=2285&tstart=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.