You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by Apache Wiki <wi...@apache.org> on 2007/12/10 19:56:12 UTC
[Ws Wiki] Update of "FrontPage/Woden/ValidationAPI" by LawrenceMandel
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.
The following page has been changed by LawrenceMandel:
http://wiki.apache.org/ws/FrontPage/Woden/ValidationAPI
New page:
= Woden Validation API =
This page captures the goals of the Woden validation API and potential options for implementation that will achieve the goals.
== Goals of the Validation API ==
1. Enable validation with any implementation of the Woden API
2. Enable 3rd parties to add new validation assertions to Woden
3. Allow for specification of dependencies among assertions for the benefit of
* Performance (only run assertions that have a chance to pass)
* User experience (only show one error message per error)
== Goal 1: Enable validation with any implementation of the Woden API ==
This goal requires that the validation API and assertions only reference Woden's API. No references can be made to Woden's implementation classes.
== Goal 2: Enable 3rd parties to add new validation assertions to Woden ==
This goal requires a public assertion interface that adopters can implement and contribute to Woden.
The following are two potential assertion interfaces with pros and cons:
1. public Interface IAssertion {
public void validate(Description desc, ErrorReporter errorReporter);
}
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
Re: [Ws Wiki] Update of "FrontPage/Woden/ValidationAPI" by LawrenceMandel
Posted by Lawrence Mandel <lm...@ca.ibm.com>.
Hi Jeremy,
WRT IAssertion vs Assertion I'm used to sticking the "I" in front but
don't have a strong preference. Woden doesn't use "I"s for interfaces so
likely this should just be Assertion. Thanks for the reminder. :)
When it comes to the discovery mechanism I think Woden can provide a
method that allows adopters to programmatically add assertions when using
the parser. We can enhance this by creating a declarative extension
mechanism (reuse what Eclipse/OSGi has - I've been meaning to create a
Jira issue about creating a Woden bundle) on top of the method way of
adding assertions for those who don't want to use OSGi bundles. The impl
classes can of course live in the Woden source tree and we can
preconfigure Woden to define all of the Woden assertions so that consumers
do not have to manually define all of the assertions themselves.
Lawrence
"Jeremy Hughes" <hu...@apache.org>
Sent by: jpjhughes@gmail.com
12/10/2007 02:14 PM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org
cc
Subject
Re: [Ws Wiki] Update of "FrontPage/Woden/ValidationAPI" by LawrenceMandel
Hi Lawrence, This looks good. I was wondering about the discovery /
factory mechanism behind creating the IAssertion (should that be
IAssertion or just Assertion?) instances. Perhaps the OSGi bundle /
extension mechanism is the way to go. A while back we were considering
that for the WSDL extensions. Alternatively a
META-INF/woden-assertions file in the jar containing the impl objects.
Cheers,
Jeremy
On 10/12/2007, Apache Wiki <wi...@apache.org> wrote:
> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "Ws Wiki" for
change notification.
>
> The following page has been changed by LawrenceMandel:
> http://wiki.apache.org/ws/FrontPage/Woden/ValidationAPI
>
> New page:
> = Woden Validation API =
> This page captures the goals of the Woden validation API and potential
options for implementation that will achieve the goals.
>
> == Goals of the Validation API ==
> 1. Enable validation with any implementation of the Woden API
> 2. Enable 3rd parties to add new validation assertions to Woden
> 3. Allow for specification of dependencies among assertions for the
benefit of
> * Performance (only run assertions that have a chance to pass)
> * User experience (only show one error message per error)
>
> == Goal 1: Enable validation with any implementation of the Woden API ==
> This goal requires that the validation API and assertions only reference
Woden's API. No references can be made to Woden's implementation classes.
>
> == Goal 2: Enable 3rd parties to add new validation assertions to Woden
==
> This goal requires a public assertion interface that adopters can
implement and contribute to Woden.
>
> The following are two potential assertion interfaces with pros and cons:
>
> 1. public Interface IAssertion {
> public void validate(Description desc, ErrorReporter errorReporter);
> }
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
> For additional commands, e-mail: general-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: [Ws Wiki] Update of "FrontPage/Woden/ValidationAPI" by LawrenceMandel
Posted by Jeremy Hughes <hu...@apache.org>.
Hi Lawrence, This looks good. I was wondering about the discovery /
factory mechanism behind creating the IAssertion (should that be
IAssertion or just Assertion?) instances. Perhaps the OSGi bundle /
extension mechanism is the way to go. A while back we were considering
that for the WSDL extensions. Alternatively a
META-INF/woden-assertions file in the jar containing the impl objects.
Cheers,
Jeremy
On 10/12/2007, Apache Wiki <wi...@apache.org> wrote:
> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.
>
> The following page has been changed by LawrenceMandel:
> http://wiki.apache.org/ws/FrontPage/Woden/ValidationAPI
>
> New page:
> = Woden Validation API =
> This page captures the goals of the Woden validation API and potential options for implementation that will achieve the goals.
>
> == Goals of the Validation API ==
> 1. Enable validation with any implementation of the Woden API
> 2. Enable 3rd parties to add new validation assertions to Woden
> 3. Allow for specification of dependencies among assertions for the benefit of
> * Performance (only run assertions that have a chance to pass)
> * User experience (only show one error message per error)
>
> == Goal 1: Enable validation with any implementation of the Woden API ==
> This goal requires that the validation API and assertions only reference Woden's API. No references can be made to Woden's implementation classes.
>
> == Goal 2: Enable 3rd parties to add new validation assertions to Woden ==
> This goal requires a public assertion interface that adopters can implement and contribute to Woden.
>
> The following are two potential assertion interfaces with pros and cons:
>
> 1. public Interface IAssertion {
> public void validate(Description desc, ErrorReporter errorReporter);
> }
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
> For additional commands, e-mail: general-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org