Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: camel spring xml restructure
Date: Sat, 30 Aug 2008 17:15:11 +0200
Message-ID: <4C1FB9C00D24A140906239533638C4D20536F751@EXVS04.exserver.dk>
Thread-Topic: camel spring xml restructure
Thread-Index: AckKszITszr4q8aeS0amC6+OH5awIw==
From: "Claus Ibsen" <ci@silverbullet.dk>
To: <camel-dev@activemq.apache.org>

Hi

I would suggest to restructure the camel spring xml format a bit.

The overall goal is:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
- ease of use

Current situations:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
- there are too many different types of xml tags possible that confuses =
end-users.=20
- most list types don't have a parent "holder" so they are mixed with =
all the others


IDE auto completion
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Using the IDE auto complete reveals many of these problems. For instance =
in the root camelContext tag, you get datatypes, endpoint, spring =
remoting, and other stuff and of course the routes etc is a bit of mixed =
content.

I would suggest to restructure the xml so you have some parent holder =
tags to ease end-users.


Motivation behind
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
I would love the spring xml to be more firm and structured before =
letting loose my programming team on the spring xml instead of java DSL. =
Having IDE completion with less mixed type of elements would help a lot.

=20

Camel 1.5
=3D=3D=3D=3D=3D=3D=3D=3D=3D
We are nearly there I think the daatatypes must be restructure so they =
don't appear in the tag list from the root tag. Now you get articDS, =
xmlBeans, string, hl7, xstram and others. I think they should be child =
tags of a parent holder tag named dataTypes. This will help a lot.

I thing this change can be done in camel 1.5 without breaking to much. =
After all we have a bug in Camel so datatypes configured as camel tags =
isn't useable from the marshal and unmarshal tags. So it doesn't work =
(CAMEL-871).


Camel 2.0
=3D=3D=3D=3D=3D=3D=3D=3D=3D
For Camel 2.0 we can consider having parent holders for
- endpoints
- routes
- the spring remote stuff
- jmx

And I also think the <package> tag should have a parent holder that =
better describes what it does. As now it's a bit of magic for new users =
reading the spring xml. Package doesn't hint that is the route builder =
and that is it a very important tag. Also we should consider making it =
possible to configure <package> as classnames or spring bean ids. So you =
better can get the link from camel context to what java class is the =
actual route builder.=20

We could consider having a restructure for this and have it something on =
the way as:

<routeBuilder>
   <package>com.acme</package>
</routeBuilder>

Or even better I think:

<routeBuilder>
   <builder package=3D"com.acme"/>
</rouyteBuilder>

<routeBuilder>
   <builder class=3D"com.acme.MyCheeseRoute"/>
   <builder class=3D"com.acme.MyBeerRoute"/>
</rouyteBuilder>


And the spring ref variation is also very great:

<bean id=3D"cheeseRoute" class=3D"com.acme.MyCheeseRoute"/>

<routeBuilder>
   <builder ref=3D"cheeseRoute/>
</rouyteBuilder>


Med venlig hilsen

Claus Ibsen
......................................
Silverbullet
Skovsg=E5rdsv=E6nget 21
8362 H=F8rning
Tlf. +45 2962 7576
Web: www.silverbullet.dk