The most urgent piece I need for my work is currently generation of XSD from
a class model.

The generation of a web service using axis can be quite simple and does not
need XSD generation. I will be writing several web services over the next
few months. If the AndroMDA community can wait several months then I would
be happy to feed that work back into AndroMDA.

Tony

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Matthias
Bohlen
Sent: Tuesday, July 29, 2003 10:56 AM
To: 'Philippe F. Monnet'; [EMAIL PROTECTED]
Subject: RE: [Andromda-user] Short term plans and long term plans


Hi, Philippe,

XSD and WSDL? I am afraid, no. Indeed, it would be nice to have
automatic generation of web services. Are there any volunteers for this?

Cheers...
Matthias

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Philippe F. Monnet
> Sent: Tuesday, July 29, 2003 8:07 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Andromda-user] Short term plans and long term plans
>
>
> Is the XSD generation on the timeline too?
> Also, WSDL support would be great.
>
> ----- Original Message -----
> From: "Matthias Bohlen" <[EMAIL PROTECTED]>
> To: "'Doroszlai Attila'" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Sunday, July 13, 2003 7:19 AM
> Subject: [Andromda-user] Short term plans and long term plans
>
>
> Hi Attila,
> hi to our developers and users,
>
> thank you for your offer to help - this is always appreciated.
>
> I think, there are some basic steps that future AndroMDA
> developers should take:
>
> * read the project summary at
> http://sourceforge.net/projects/andromda/
> * read about patches, feature requests and bugs of the product
> * subscribe to andromda-devel, andromda-cvs and andromda-user
>   (see http://sourceforge.net/mail/?group_id=73047)
> * check out the CVS version of AndroMDA and recompile it
>   (see http://sourceforge.net/cvs/?group_id=73047)
> * discuss a change to AndroMDA on the andromda-devel list
> * submit a good patch to solve an interesting problem with AndroMDA
>   (see http://sourceforge.net/tracker/?group_id=73047&atid=536547)
>
> Please submit the solution as a patch in AndroMDA's patch
> area (link see above). We'll examine it and if the code is
> good, you'll get committer rights for our CVS repository and
> become an official member of the team.
>
> OK, to answer your question now:
>
> > What are your current short-term plans?  Would a new sub-project be
> > acceptable for you?  If so, what kind of cartridges would
> you like to
> > see being developed in the future?
>
> We are just on the brink of a new release, AndroMDA 2.0.2
> final (as opposed to the alpha release that we have got
> today). To make it really *final*, there are a number of things to do:
>
> 2.1) Currently, AndroMDA is delivered in several ZIP files,
> one for each purpose (core, cartridges, samples, etc.). Users
> have reported that this is too complex to handle and install.
> So, the goal for 2.0.2 is to deliver only two ZIPs: one for
> the binaries, one for source code. This makes the ZIPs much
> larger but also much easier to install and run.
>
> 2.2) The web pages mention a wizard that creates an empty
> code generation project as a good starting point for new
> users to work with AndroMDA. This wizard was broken (by me!)
> when the software was reorganized and the cartridge mechanism
> was introduced. I did not have time to fix this, Tony (author
> of the wizard) had neither. The wizard must be working again
> before we release. The wizard consists of only one XML file,
> so that one should be easy to change (but must be throughly tested!).
>
> 2.3) Each cartridge that we have should be demonstrated with
> a template project that new users can copy and extend. Tony
> Mowers wrote a template project for the EJB cartridge, I will
> have to write a template project for the hibernate cartridge.
> I do not know if it makes sense to create one for the
> currently somewhat crude Struts cartridge.
>
> 2.4) A new XDoclet release has come out. AndroMDA V2.x should
> contain and use it.
>
> OK, these were the goals for V2.0.2.
>
> After the release of 2.x, we plan to create a branch in CVS
> for 2.x maintenance releases and continue with the
> development of V3.0 on the main trunk. My main goals for the
> V3.0 release are:
>
> 3.1) Make AndroMDA usable in an agile context. Examples: It
> should be possible to rename a class, attribute or method or
> move a class into a different package, etc. without breaking
> the compile cycle. With 2.x this is impossible because
> AndroMDA does not know that a model element was renamed or
> moved and happily generates a new one, keeping the old one as
> an orphan. This breaks the code and the user has to
> re-arrange it manually which is very tedious. I dream of an
> integration of AndroMDA as an Eclipse plugin, making AndroMDA
> aware of model changes. AndroMDA should then invoke the
> Eclipse JDT to do the name changes on the code level. I don't
> know if this is possible, but at least that's the goal.
>
> 3.2) Richard Kunze has supplied a sophisticated and powerful
> new EJB cartridge as a patch. This should become part of the
> 3.x release, too.
>
> 3.3) Andy Soroker works on a JDO cartridge (hi Andy, how is
> it?). This should also become part of the new release.
>
> 3.4) Netbeans MDR (the metadata engine we use in the core)
> has the possibility to notify AndroMDA when it creates an
> instance of a metamodel class. Upon that event, AndroMDA
> could instantiate a cartridge-supplied decorator class that
> implements model consistency checks and fine grain support
> for Velocity scripts. Trivial example: When a JMI class for a
> UML attribute is instantiated, AndroMDA could attach a
> decorator that has a "getGetterName()" method that retuns the
> name of the appropriate getter for the attribute. There are
> more complex things possible with this approach. Users of
> AndroMDA could write their own decorators for their own UML profiles.
>
> Well, that's it for the moment. There's more to come, I think.
>
> So, if you want to join us, please have a look at the two
> task lists above. Maybe, you can try to do 2.2 and submit a
> patch for it? After that, we can look what you can do next.
> Is that OK for you?
>
> Have fun...
> Matthias
>
> > -----Original Message-----
> > From: Doroszlai Attila [mailto:[EMAIL PROTECTED]
> > Sent: Sunday, July 13, 2003 12:29 PM
> > To: Matthias Bohlen
> > Subject: joining the AndroMDA development team
> >
> >
> > Dear Matthias,
> >
> > My name is Attila Doroszlai, I study software engineering at the
> > Technical University of Budapest, Hungary.  My current interest is
> > code generation.
> >
> > Recently, I examined a number of tools for the generation of J2EE
> > code, and found that the one I'd like to work with is
> AndroMDA, so I'd
> > like to join the development team.
> >
> > Since this is also a university project for me, my work on AndroMDA
> > would have to be evaluated by my teacher. Therefore, I'd need an
> > assignment that is large enough to last about half a year
> (working on
> > it in part-time), and at the same time small enough for me
> to be able
> > to handle it.
> >
> > My original goal was to write a tool for generating Entity
> Beans, but
> > I see that AndroMDA already has this capability. Thus, I'm
> considering
> > the generation of the (web) user interface instead.  In the Code
> > Generation Network interview, however, you said that your
> focus was on
> > the server-side quite for some time.  I don't stick to
> front-end code
> > generation, I'd accept any reasonable task.
> >
> > I understand that joining an already established project cannot be
> > done in a single step, so I'm ready to do bug-fixing and
> more before I
> > start working on a new cartridge.
> >
> > What are your current short-term plans?  Would a new sub-project be
> > acceptable for you?  If so, what kind of cartridges would
> you like to
> > see being developed in the future?
> >
> > sincerely,
> > Attila
> >
>
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01
/01
_______________________________________________
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user

Reply via email to