Glad you brought this up.

I was about to embark on rewriting the deployment process and meta data
stuff.  I was considering using JAXB or equivavlnet to convert xml to
objects.  JAXB works by generating classes that contain the xml parsing and
validation in them.  Your classes with real behavior can then subclass
these, reading a doc will then generate instances of your subclasses.

In this idea, the first step in deployment is transforming the xml using
xslt to a form ideally suited to our objects.

What I was hoping for, although I haven't even prototyped it yet, is that
the classes created from reading the (transformed) xml are the ones that do
the work -- so for instance (slightly atypical) the container configuration
is an mbean config as we have now in service-xml.  Whatever objects are
used in cmp2 are created by being "read" from the xml.


Anyway... from what you say it looks like one requirement is that the xml
to object creation step should not involve xml parsing in the classes... so
jaxb is out, what we have now is also out, we need an external xml reader
solution.  Is this a consequence of what you are saying here?

Or... perhaps we could provide a more code generation and compile time
solution whereby one set of classes for use with xml is generated by jaxb +
our subclasses, whereas for other non-xml purposes another equivalent set
is generated from [unknown base classes specific to the situation] + our
same subclasses.

Thanks
david jencks

On 2002.02.24 21:06:24 -0500 Scott M Stark wrote:
> 
> The metadata stuff in deployment I think should be independent of
> XML deployment descriptors. What is now in metadata or somewhere
> else should be the XML to metadata object model mapping. As I
> indicated in the embedded requirements, some applications of
> embedding JBoss already have service frameworks equivalent to
> J2EE and they just want to map existing services onto J2EE compatible
> APIs. There is no reason to force a packaging and building xml
> descriptors if one can go directly to the deployment object model.
> XML is really not a great programming API.
> 
> ----- Original Message -----
> From: "Jason Dillon" <[EMAIL PROTECTED]>
> To: "Scott M Stark" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Sunday, February 24, 2002 5:35 PM
> Subject: Re: [JBoss-dev] CVS update: jboss/src/main/org/jboss/deployment
> DeploymentInfo.java
> 
> 
> > It probably should be... or rather a framework for taking xml
> desciptors
> > and turning them into metadata objects.  That requires a lot more
> > thought and planning.
> >
> > --jason
> >
> >
> 
> 
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to