[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [stp-dev] fixed: [Bug 160190] annotation view contents needs tobe entirely driven via the annotation classes meta-data
|
Almost ...
The view content is entirely driven by the annotation classes we
register with it (via an extension point) so we can add support for as
many annotations as we want. At this point I have an extension
specifically targeting JAX-WS annotation that's all.
With a small addition to that extension point we could define distinct
annotation views targeting specific context (docs, jax-ws, Tuscany...)
It is in my todo list...
d.
-----Original Message-----
From: stp-dev-bounces@xxxxxxxxxxx [mailto:stp-dev-bounces@xxxxxxxxxxx]
On Behalf Of Hurley, Oisin
Sent: 11 October 2006 08:44
To: STP Dev list
Subject: Re: [stp-dev] fixed: [Bug 160190] annotation view contents
needs tobe entirely driven via the annotation classes meta-data
David, do you think that the discovery mechanism for
annotations could be generalized to provide a base framework for
supporting
annotation-driven interfaces, e.g. if we were to add some support
for Tuscany Java services could we just do it by extending a generalized
approach?
--oh
----
+353 1 637 2639
http://blogs.iona.com/ohurley
_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/stp-dev
