Nabble - Eclipse WTP

Paul Fullbright <paul.fullbright@...> · 11/26/2008 10:52 AM

org.eclipse.wst.validation.ValidationResult
setSuspendValidation(IProject
project)

public void setSuspendValidation(IProject project)

project

Hello all,

As a result of adding a new resource type in our extension of our own 

JPA tools framework, it seems we need to advance quickly to the v2 

validator framework.  Very quickly.  I wonder if I could pose
a few 

questions:

- In the presentation (here: 
http://www.eclipse.org./webtools/common/validation/New-VF-2007-12-11.pdf
)

it was hinted that one could provide a v2 implementation by wrapping an

existing v1 implementation.  Obviously, if we need to do this quickly,

this sounds very good.  Looking at the existing v2 validators, I don't

see anyone who has done what I understand as wrapping.Can someone give

me a thumbnail sketch of how that might be done?  I tried finding
a 

post-implementation overview, but only found one from 2005 

(
http://www.eclipse.org/webtools/wst/components/validation/ValidationOverview.html
).

Do I want the delegating validator?  And if so, do I need to use the

validatorDelegates extension point?

- Relatedly, there was a hint in the bug 

(
https://bugs.eclipse.org/bugs/show_bug.cgi?id=212196
)
that there might 

be a getting started guide.  *Is* there a getting started guide?

- Most of the validator framework surrounds validation of a *file*.  Are

there any thoughts about *project-wide* validation?  The nature of
the 

beast that is JPA is that everything depends on everything else.  

Changing a java file can change validation for a persistence.xml file.

Changing the persistence.xml file can change validation for an orm.xml

file.  Changing the orm.xml file can change validation for the original

java file.  So each validation run for us, due to the nature of JPA,

implies a validation of the entire project.  But each validation run
is 

centered on a single file.  This means that if several files change
(or 

if a project wide validation is run), then the project gets validated 

once for each resource, which is a huge waste of cycles.  Any thoughts

on how we can register validation to be run on changes to all these 

files, but done only once per project, per validation run?  (OK, this

one isn't as quick, but it also isn't as pressing, either.)

Thanks in advance,

-- 

Paul Fullbright

Oracle Corp.

Eclipse Dali/Java Persistence Tools Development
paul.fullbright@...

_______________________________________________

wtp-dev mailing list
https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list
https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list
https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list

https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list

https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list

wtp-dev@...

https://dev.eclipse.org/mailman/listinfo/wtp-dev

I'm trying to extend WTP and provide content assist
for our own dialect of html.  I'm actually trying to do this by extending
PDT, but as this extension point comes from WTP, those guys directed me
here.  

I obviously know about CTRL space!  What I'm saying is that, after
implementing this extension point, when I press CTRL space, nothing happens.
 What I'm looking for is a tip that I'm missing some implementation
detail.

Thanks...

Sent from my Verizon Wireless BlackBerry

-----Original Message-----

From: Keith Chong <kchong@...>

Date: Thu, 27 Nov 2008 09:54:28 

To: <wtp-dev@...>

Subject: Re: [wtp-dev] Using ModelQueryExtension

_______________________________________________

wtp-dev mailing list

wtp-dev@...

https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list

wtp-dev@...

https://dev.eclipse.org/mailman/listinfo/wtp-dev

Hi all,

I'm having trouble implementing the

org.eclipse.wst.xml.core.modelQueryExtensions extension point.

I've declared it as follows in my plugin.xml:

<extension point="org.eclipse.wst.xml.core.modelQueryExtensions">

     <modelQueryExtension

           class="org.fhtml.eclipse.editors.MyModelQueryExtension"

           contentType="org.eclipse.wst.html.core.htmlsource">

     </modelQueryExtension>

 </extension>

and also built a class that extends ModelQueryExtension:

public class MyModelQueryExtension extends ModelQueryExtension {

      public MyModelQueryExtension() {

              System.out.print("NEVER
CALLED\n");

      }

      public String[] getAttributeValues(Element e, String
namespace,

String name) {

              //See XSDModelQueryExtension
for example...

      }

}

This is my first Eclipse plugin, so if anyone could explain to me the

mechanism that fires this code, that might help.  Even in the JSP
and

XSD packages that use this code, I haven't been able to find the place

where it is invoked (or where the listener is added).

Has anyone had success with this extension point?  Also, if anyone

knows of any real documentation on the topic, that would be great as

well.  As far as I can tell, there's almost nothing, as this is meant,

for now, to be an internal extension point.

Thanks,

Jim Kremens

_______________________________________________

wtp-dev mailing list

wtp-dev@...

https://dev.eclipse.org/mailman/listinfo/wtp-dev

org.eclipse.wst.validation.ValidationResult
setSuspendValidation(IProject
project)

public void setSuspendValidation(IProject project)

project

Hello all,

As a result of adding a new resource type in our extension of our own 

JPA tools framework, it seems we need to advance quickly to the v2 

validator framework.  Very quickly.  I wonder if I could pose
a few 

questions:

- In the presentation (here: 
http://www.eclipse.org./webtools/common/validation/New-VF-2007-12-11.pdf
)

it was hinted that one could provide a v2 implementation by wrapping an

existing v1 implementation.  Obviously, if we need to do this quickly,

this sounds very good.  Looking at the existing v2 validators, I don't

see anyone who has done what I understand as wrapping.Can someone give

me a thumbnail sketch of how that might be done?  I tried finding
a 

post-implementation overview, but only found one from 2005 

(
http://www.eclipse.org/webtools/wst/components/validation/ValidationOverview.html
).

Do I want the delegating validator?  And if so, do I need to use the

validatorDelegates extension point?

- Relatedly, there was a hint in the bug 

(
https://bugs.eclipse.org/bugs/show_bug.cgi?id=212196
)
that there might 

be a getting started guide.  *Is* there a getting started guide?

- Most of the validator framework surrounds validation of a *file*.
 Are

there any thoughts about *project-wide* validation?  The nature of
the 

beast that is JPA is that everything depends on everything else.  

Changing a java file can change validation for a persistence.xml file.

Changing the persistence.xml file can change validation for an orm.xml

file.  Changing the orm.xml file can change validation for the original

java file.  So each validation run for us, due to the nature of JPA,

implies a validation of the entire project.  But each validation run
is 

centered on a single file.  This means that if several files change
(or 

if a project wide validation is run), then the project gets validated 

once for each resource, which is a huge waste of cycles.  Any thoughts

on how we can register validation to be run on changes to all these 

files, but done only once per project, per validation run?  (OK, this

one isn't as quick, but it also isn't as pressing, either.)

Thanks in advance,

-- 

Paul Fullbright

Oracle Corp.

Eclipse Dali/Java Persistence Tools Development

_______________________________________________

wtp-dev mailing list

https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list

https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list

https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list

wtp-dev@...

https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________
wtp-dev mailing list
wtp-dev@...
https://dev.eclipse.org/mailman/listinfo/wtp-dev

org.eclipse.wst.validation.ValidationResult
setSuspendValidation(IProject
project)

public void setSuspendValidation(IProject project)

project

Hello all,

As a result of adding a new resource type in our extension of our own 

JPA tools framework, it seems we need to advance quickly to the v2 

validator framework.  Very quickly.  I wonder if I could pose
a few 

questions:

- In the presentation (here: 
http://www.eclipse.org./webtools/common/validation/New-VF-2007-12-11.pdf
)

it was hinted that one could provide a v2 implementation by wrapping an

existing v1 implementation.  Obviously, if we need to do this quickly,

this sounds very good.  Looking at the existing v2 validators, I don't

see anyone who has done what I understand as wrapping.Can someone give

me a thumbnail sketch of how that might be done?  I tried finding
a 

post-implementation overview, but only found one from 2005 

(
http://www.eclipse.org/webtools/wst/components/validation/ValidationOverview.html
).

Do I want the delegating validator?  And if so, do I need to use the

validatorDelegates extension point?

- Relatedly, there was a hint in the bug 

(
https://bugs.eclipse.org/bugs/show_bug.cgi?id=212196
)
that there might 

be a getting started guide.  *Is* there a getting started guide?

- Most of the validator framework surrounds validation of a *file*.  Are

there any thoughts about *project-wide* validation?  The nature of
the 

beast that is JPA is that everything depends on everything else.  

Changing a java file can change validation for a persistence.xml file.

Changing the persistence.xml file can change validation for an orm.xml

file.  Changing the orm.xml file can change validation for the original

java file.  So each validation run for us, due to the nature of JPA,

implies a validation of the entire project.  But each validation run
is 

centered on a single file.  This means that if several files change
(or 

if a project wide validation is run), then the project gets validated 

once for each resource, which is a huge waste of cycles.  Any thoughts

on how we can register validation to be run on changes to all these 

files, but done only once per project, per validation run?  (OK, this

one isn't as quick, but it also isn't as pressing, either.)

Thanks in advance,

-- 

Paul Fullbright

Oracle Corp.

Eclipse Dali/Java Persistence Tools Development

paul.fullbright@...

_______________________________________________

wtp-dev mailing list

https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list

https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list

https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________

wtp-dev mailing list

wtp-dev@...

https://dev.eclipse.org/mailman/listinfo/wtp-dev

Nabble - Eclipse WTP

Pointing the web content or wen-inf to a different folder outside the web project

Re: Some (hopefully) quick validator v2 questions

regrets for my absence from 12/2 meeting

Re: Cruise Control Down?

Cruise Control Down?

Re: Using ModelQueryExtension

Re: Using ModelQueryExtension

Re: Using ModelQueryExtension

Re: Using ModelQueryExtension

AUTO: Scott Rich is out of the office (returning 12/01/2008)

Using ModelQueryExtension

Re: Some (hopefully) quick validator v2 questions

No WTP dev call this week, no M4 I build to declare?

late regrets due to conflicting mtg.

Re: Some (hopefully) quick validator v2 questions

Shall we skip call this week?

AUTO: Jason Peterson/Raleigh/IBM is out of the office this week.

AUTO: Jason Peterson/Raleigh/IBM is out of the office this week.

AUTO: Jason Peterson/Raleigh/IBM is out of the office this week.

AUTO: Jason Peterson/Raleigh/IBM is out of the office this week.

AUTO: Jason Peterson/Raleigh/IBM is out of the office this week.

AUTO: Jason Peterson/Raleigh/IBM is out of the office this week.

AUTO: Jason Peterson/Raleigh/IBM is out of the office this week.

From:	Paul Fullbright <paul.fullbright@...>
To:	"General discussion of project-wide or architectural issues." <wtp-dev@...>
Date:	11/26/2008 10:52 AM
Subject:	Re: [wtp-dev] Some (hopefully) quick validator v2 questions

From:	Paul Fullbright paul.fullbright@...
To:	"General discussion of project-wide or architectural issues." wtp-dev@...
Date:	11/24/2008 04:08 PM
Subject:	Re: [wtp-dev] Some (hopefully) quick validator v2 questions