Re: [wtp-jsf-dev] Bug in contentassistantprocessor extension

[David M Williams <david_williams@xxxxxxxxxx>]

> What is the action plan to resolve this? 

Cam, normally, the first step in our project, is that
the originator mark the bug as "blocker" 
See https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#bug_severity
<g>

Then, any help you can provide to help us reproduce
or debug or patch would be greatly appreciated. 
Does this happen at start-up? Or when CA requested?
for example (appears to be te latter from the stack trace). 
Details on exactly which build is used that shows
the problem is also usually important .... such as, the final declared
M5? 
A JUnit test that shows the problem is sometimes required,
and always helpful, if if not required. 

From the (helpful) stack trace you provided, looks
like something obvious, 
So, we'll investigate and update bug report with any
findings or further questions.

CAMERON.BATEMAN@xxxxxxxxxx
Sent by: wtp-jsf-dev-bounces@xxxxxxxxxxx

03/03/2006 05:23 PM

Please respond to
Java Server Faces Tools developer discussion <wtp-jsf-dev@xxxxxxxxxxx>

To	Java Server Faces Tools developer discussion <wtp-jsf-dev@xxxxxxxxxxx>
cc
Subject	[wtp-jsf-dev] Bug in contentassistantprocessor extension

Hi Amy,

In theory this extension does what we need, but there appears to be a bug
in the implementation that causes a StackOverFlow and brings down the whole
workbench. 

I have entered a bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=130402
including a stack trace.

What is the action plan to resolve this? 


--Cam

----- Message from Amy Wu <amywu@xxxxxxxxxx> on Fri, 3 Mar 2006 15:07:15 -0500 -----

To:	Java Server Faces Tools developer discussion <wtp-jsf-dev@xxxxxxxxxxx>
Subject:	Re: [wtp-jsf-dev] JSF Tools Project: Design discussion meeting

In this discussion, we discussed hooking into an existing extensible content assist mechanism that is currently provisional/experimental.  Here is more information about it:

To utilize the provisional extensible content assistant, you would need to add something like the following to your plugin.xml
       <extension point="org.eclipse.wst.sse.ui.editorConfiguration">
               <provisionalConfiguration
                       type="contentassistprocessor"
                       class="Class that implements IContentAssistProcessor"
                       target="Partition type associated with processor like org.eclipse.jst.jsp.SCRIPT.JSP_EL2" />
       </extension>


Code details if curious:
If you are curious to see what is happening under the covers, the code that handles the bulk of associating the IContentAssistProcessor to the partition type is in: org.eclipse.wst.sse.ui.internal.contentassist.StructuredContentAssistant.
All this provisionalConfiguration does is add an additional partition type to contentassistprocessor mapping to the StructuredContentAssistant (which is the content assistant used by all StructuredTextEditors - See StructuredTextViewerConfiguration#getContentAssistant)  Then when IContentAssistant#getContentAssistProcessor is called, a "compound content assist processor" is called.  This "compound content assist processor" basically contains all the content assist processors associated with the current partition type.  This "compound content assist processor" allows the ability to associate more then 1 content assist processor to a partition type.  This "compound content assist processor" will basically get the proposals from all of its content assist processors and combine them.


______________________________
Amy Wu
Structured Source Editor
919.254.0299, T/L 444.0299
amywu@xxxxxxxxxx

Raghu Srinivasan <raghunathan.srinivasan@xxxxxxxxxx>
Sent by: wtp-jsf-dev-bounces@xxxxxxxxxxx

02/27/2006 08:25 PM

Please respond to
Java Server Faces Tools developer discussion <wtp-jsf-dev@xxxxxxxxxxx>

To	Java Server Faces Tools developer discussion <wtp-jsf-dev@xxxxxxxxxxx>
cc
Subject	[wtp-jsf-dev] JSF Tools Project: Design discussion meeting

Hi David,

As planned in the call two weeks back, I would like to schedule the next meeting the coming Friday, 03/03, 11.00 AM PST.

Agenda:
Demo prototype to illustrate the hooks in WTP that the JSF Tools project is using to provide features such as Content Assist.

The prototype will not showcase the design-time metadata framework. We will do that in a subsequent call.

The meeting notes form the last conference call is available here:
http://www.eclipse.org/webtools/jsf/dev_resource/DesignDiscussions-2006-02-17.html

Thanks
Raghu

Conference Call info:

Date: 03/03, 11.00 AM PST

Conference No: 1-888-967-2253
Meeting ID: 444461
Meeting password: 573573

Web Conference info:
https://conference.oracle.com/imtapp/app/cmn_jm_hub.uix?mID=38579867&loginRequired=y
Conference Title           JSF Design meeting
Conference ID       38579867
Conference Key
To check that your system is ready for web conferencing, click New User and then Test.
_______________________________________________
wtp-jsf-dev mailing list
wtp-jsf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-jsf-dev
_______________________________________________
wtp-jsf-dev mailing list
wtp-jsf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-jsf-dev
_______________________________________________
wtp-jsf-dev mailing list
wtp-jsf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-jsf-dev