You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Sachin Patel <sp...@gmail.com> on 2005/11/18 06:06:41 UTC
validators
Could someone point me to where validation is being done on the
deployment plans prior to deployment? Is there a single entry point for
validation or is it being done within each of the builders?
Thanks
Re: validators
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I think each builder does it separately, just by passing a flag to the
XmlBeans objects when loading them from the deployment plan
file/stream. But I don't have the source code in front of me, so I
can't be more specific at the moment.
Aaron
On 11/18/05, Sachin Patel <sp...@gmail.com> wrote:
> Could someone point me to where validation is being done on the
> deployment plans prior to deployment? Is there a single entry point for
> validation or is it being done within each of the builders?
>
> Thanks
>
Re: validators
Posted by Sachin Patel <sp...@gmail.com>.
Yes thanks David, that does help. So technically, could I directly call
validateDD() and get the list of errors? I'm wanting to hook into the
validation framework in Eclipse so that the validation errors appear in
the "Problems View" prior to deployment.
Sachin.
David Jencks wrote:
>
> On Nov 17, 2005, at 9:06 PM, Sachin Patel wrote:
>
>> Could someone point me to where validation is being done on the
>> deployment plans prior to deployment? Is there a single entry point
>> for validation or is it being done within each of the builders?
>>
>> Thanks
>
> Process goes something like this:
>
> builder determines through some black magic that the stuff you are
> asking about is something it can deploy
>
> builder finds some files in likely places for the spec dd (if
> appropriate) and geronimo plan (if present)
>
> builder reads xml files into xmlbeans XmlObjects
>
> builder applies a lot of transformations to change pre-j2ee1.4 dds to
> 1.4 dds, and to update geronimo plans in various ways in an attempt to
> preserve backwards compatibility even when we upgrade schemas.
>
> builder asks xmlbeans to validate against the schema. The usual
> method to call is SchemaConversionUtils.validateDD.
>
> The process for web module plans is a little different since you can
> supply either a generic schema with container specific stuff or a
> container specific plan. A generic plan is converted into a plan for
> a specific web container (currently jetty or tomcat).
>
> Hope this explains something :-)
>
> david jencks
>
>
Re: validators
Posted by David Jencks <da...@yahoo.com>.
On Nov 17, 2005, at 9:06 PM, Sachin Patel wrote:
> Could someone point me to where validation is being done on the
> deployment plans prior to deployment? Is there a single entry point
> for validation or is it being done within each of the builders?
>
> Thanks
Process goes something like this:
builder determines through some black magic that the stuff you are
asking about is something it can deploy
builder finds some files in likely places for the spec dd (if
appropriate) and geronimo plan (if present)
builder reads xml files into xmlbeans XmlObjects
builder applies a lot of transformations to change pre-j2ee1.4 dds to
1.4 dds, and to update geronimo plans in various ways in an attempt to
preserve backwards compatibility even when we upgrade schemas.
builder asks xmlbeans to validate against the schema. The usual method
to call is SchemaConversionUtils.validateDD.
The process for web module plans is a little different since you can
supply either a generic schema with container specific stuff or a
container specific plan. A generic plan is converted into a plan for a
specific web container (currently jetty or tomcat).
Hope this explains something :-)
david jencks