Re: [stp-pmc] Fwd: [stp-dev] writing an introspector...

[Daniel Berg <danberg@xxxxxxxxxx>]

stp-pmc-bounces@xxxxxxxxxxx wrote on 08/29/2006 05:49:42
AM:

> 
> On 22 Aug 2006, at 16:32, Daniel Berg wrote:
> 
> > There are several things to keep in mind.  First, you may
need to  
> > process the annotations within the source files outside of a
build  
> > in order to get any content assist support within the file.
> 
> On the content assist - we would need to adjust the classpath to get
 
> this
> information, which implies that there needs to be some way to mark
the
> project as a Tuscany project, or some way to recognize it as such.

<dcb>
This is not what I am talking about.  I assume
the classpath will have the
necessary SCA annotations available and registered
(e.g., using facets in
WTP possibly).  The point I am talking about
is providing intelligent content
assist "values" for tags.  This is
only possible if you are processing the
actual source code and not just the binaries.  The
Tuscany processor will be
using java.lang.Class to process the binaries.  Within
Eclipse we should be
processing the annotation using AST.

I agree that it may be easier to reuse the Tuscany
code here but it will not
be integrated well at all.
</dcb>

> 
> >  Second, we would need to know how Tuscany code processes
the  
> > annotations.  If it generates files then these need to be
 
> > integrated seamlessly into the IDE which is difficult when  the
 
> > executing code knows nothing about the Eclipse workspace.
> >  If the processing logic tries to update in-memory models
we are  
> > positive that this will not work since the model instances are
 
> > completely different.  They only share the schemas.
> 
> There's two approaches I think -
> 
>   1. let the tuscany code process the annotations and somehow
>      consume the output
>   2. make an introspector that will process the annotations and
>      populate the UI-specific model
> 
> choice of approach will probably be governed by what the tuscany
> code does right now and how it could be reused.



<dcb>
I don't know what you mean by the UI-specific model
in option 2.  I assume
it is the SCA model we have in core?.?  I can
guarantee that in option 1 the
Tuscany code can only update the actual serialized
form of the SCA XML files
and not the in-memory model (it is different than
what is used in Tuscany).
</dcb>


> 
> > I would also like to know which components within STP are blocked
 
> > by the models not being up to date.
> 
> Nothing yet, but I'm sure this will change :)


<dcb>
I'm sure it will.  I would like to see a plan that shows which components
plan to use it and how.
</dcb>


> 
> 
>   --oh
> _______________________________________________
> stp-pmc mailing list
> stp-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/stp-pmc