You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2007/11/16 18:16:26 UTC
[jira] Created: (CAMEL-228) annotate the definitions of all the
Camel headers/properties (e.g. CamelFileName) so that we can slup the code
and auto-generate a nice reference document?
annotate the definitions of all the Camel headers/properties (e.g. CamelFileName) so that we can slup the code and auto-generate a nice reference document?
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Key: CAMEL-228
URL: https://issues.apache.org/activemq/browse/CAMEL-228
Project: Apache Camel
Issue Type: Improvement
Reporter: James Strachan
Priority: Minor
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-228) annotate the definitions of all the
Camel headers/properties (e.g. CamelFileName) so that we can slup the code
and auto-generate a nice reference document?
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-228.
-------------------------------
Resolution: Won't Fix
> annotate the definitions of all the Camel headers/properties (e.g. CamelFileName) so that we can slup the code and auto-generate a nice reference document?
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-228
> URL: https://issues.apache.org/activemq/browse/CAMEL-228
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Priority: Minor
> Fix For: Future
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-228) annotate the definitions of all the
Camel headers/properties (e.g. CamelFileName) so that we can slup the code
and auto-generate a nice reference document?
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-228:
------------------------------
Fix Version/s: (was: 2.0.0)
Future
> annotate the definitions of all the Camel headers/properties (e.g. CamelFileName) so that we can slup the code and auto-generate a nice reference document?
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-228
> URL: https://issues.apache.org/activemq/browse/CAMEL-228
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Priority: Minor
> Fix For: Future
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-228) annotate the definitions of all the
Camel headers/properties (e.g. CamelFileName) so that we can slup the code
and auto-generate a nice reference document?
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48080#action_48080 ]
James Strachan commented on CAMEL-228:
--------------------------------------
am kinda wondering that all header/property names used by components are in some well known annotated place that we can then find?
e.g.
maybe we annotate the classes they live in (typically a Component or Endpoint?) then annotate each header that they are a standard camel header.
e.g. something like
{code}
@CamelDocument
public class FooComponent {
@HeaderDocument
public static final String FOO_NAME = "CamelFooName";
...
}
{code}
Then we can start to automatically generate reference documentation of all the special header names used by components
> annotate the definitions of all the Camel headers/properties (e.g. CamelFileName) so that we can slup the code and auto-generate a nice reference document?
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-228
> URL: https://issues.apache.org/activemq/browse/CAMEL-228
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Priority: Minor
> Fix For: 2.0.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.