Re: SpringExamples and Java2AS

Martin Wood <[email protected]>
Newsgroups gmane.comp.java.openamf.user
Message-ID <[email protected]>
> Also checked in the Java2As utility, creates stub AS classes and methods from
> Java equivalents. Say you have a Java Person class, and you want to create an
> AS 2 class of it, Java2AS will eliminate the getters and setter creation for
> those exposed via JavaBean accessors. Sadly it doesn't actually translate the
> inside of the methods, all methods or variables.
> 

Hello again...

i've been avidly updating my openamf from CVS, but no changes come 
through yet.

Maybe not the best place to ask but whats the situation with sourceforge 
CVS? I thought that anything checked in should appear in the repository 
straight away.

Its not too important because i grabbed the latest astranslator and can 
successfuly use types that are declared by their interfaces (although of 
course the custom class mapping still refers to concrete types, but 
thats not a huge concern to me at the moment)

also i was thinking about things like keeping the java and as vo's in 
sync, as well as having to write the custom class mapping and advanced 
gateway definitions.

I think a lot of this burden could be eased with the use of xDoclet.

If people think this is a suitable idea then it would be good to spec 
out the xDoclet tags to use for generating the laborious parts of 
openamf-config.

Then with some cunning combination of openamf xDoclet tags, Java2AS and 
ant then most of the boring work can be automated.

anyway, just some ideas..

:)

thanks

martin




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.