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

[Oisin Hurley <ohurley@xxxxxxxx>]

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.

>  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.

> 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 :)


 --oh