camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CAMEL-769) Spring Camel Main should provide option to export all the RouteDefinitions as XML to a file
Date Wed, 06 Aug 2008 13:03:52 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44768#action_44768
] 

hadrian edited comment on CAMEL-769 at 8/6/08 6:02 AM:
---------------------------------------------------------------

Exactly :)

While almost all xml is defined via jaxb in oac.model, there is no root element, so those
don't fully define a schema.  That is generated from camel spring.  The root element over
there is camelContext correct.  That means a few things:
* camel xml can only be valid(ated) in a spring xml document, or something conforming to the
spring xml schema
* the xml you generate is not valid (in the absence of a schema)
* the xml you generate cannot be later used to say instantiate a clone of the process.  i.e.
if some archaeologist discovers a file generated using your method, what else should she do
create an exact replica of the camel process.  

I put quite a lot of thought lately into what improvements could be made to the dsl, which
imho is one of the most significant innovations in camel.  Most notably:
* How could we for instance translate from one dsl to another (java, xml, scala, etc)?
* What is the most suitable language for tooling? Is it xml, an EIP DSL (which we'd have to
define)?


      was (Author: hadrian):
    Exactly :)

While almost all xml is defined via jaxb in oac.model, there is no root element, so those
don't fully define a schema.  That is generated from camel spring.  The root element over
there is camelContext correct.  That means a few things:
* camel xml can only be valid(ated) in a spring xml document, or something conforming to the
spring xml schema
* the xml you generate is not valid (in the absence of a schema)
* the xml you generate cannot be later used to say instantiate a clone of the process.  i.e.
if some archaeologist discovers a file generated using your method, what else should she do
create an exact replica of the camel process.  How could we for instance translate from one
dsl to another (java, xml, scala, etc).  What is the most suitable 

I put quite a lot of thought lately into what improvements could be made to the dsl, which
imho is one of the most significant innovations in camel.  Most notably:
* How could we for instance translate from one dsl to another (java, xml, scala, etc)?
* What is the most suitable language for tooling? Is it xml, an EIP DSL (which we'd have to
define)?

  
> Spring Camel Main should provide option to export all the RouteDefinitions as XML to
a file
> -------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-769
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-769
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: James Strachan
>            Assignee: Hadrian Zbarcea
>             Fix For: 1.5.0
>
>         Attachments: dumpRoutesToXml.patch
>
>
> e.g. 
> {code}
> java org.apache.camel.spring.Main -out foo.xml
> {code}
> Then once the CamelContext is created it grabs the getRouteDefintions() and writes them
to an XML file
> {code}
> <routes xmlns="...">
>   <route/> ...
> </routes>
> {code}
> This will then make it easy for tooling to visualise the routes

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message