[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8475) Rich Faces editor won't code complete if file opened Read/Only

[Victor Rubezhny (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586943#comment-12586943 ] 

Victor Rubezhny commented on JBIDE-8475:
----------------------------------------

This is an UpStream issue on WTP JSP/HTML editors.

After you set up the read-only flag on a file opened in HTML/JSP editor the map containing the Content Assist Processor for each document partition type is cleared by the editor actions update procedure. After this, if you set the file to be writable again the editor doesn't configures the Content Assist Processors due to allow CA functionality, so editor's CA stays miscongifured.

So, the only make file readable, then close editor and then open editor again may help to make CA to work.

The issue is reproducible in Web Page Editor as well.

Also, the WTP's editor doesn't invokes editor state validation before CA is invoked. This results in that you can open a read-only file in Editor, then invoke CA and apply some proposal. This will insert the proposals text the editor will show that its content is modified (asterisk will be shown in title). Then the dialog will be shown to suggest you to make the file writable (and you may accept this suggestion) but Content Assist will not work normally anymore.

I suppose that this is the UpStream issue over WTP editors because all the actions causing this issue happen in WTP's classes. Any modifications of JBoss CA Processors will not fix the issue.

> Rich Faces editor won't code complete if file opened Read/Only
> --------------------------------------------------------------
>
>                 Key: JBIDE-8475
>                 URL: https://issues.jboss.org/browse/JBIDE-8475
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jsp/jsf/xml source editing
>    Affects Versions: 3.1.1, 3.2.0.CR1
>         Environment: Windows and Mac Eclipse 3.5 (3.1) and 3.6 (3.2) using SCM where files are left read only until Eclipse SCM plugin checks them out and changes permissions
>            Reporter: joe freeman
>            Assignee: Victor Rubezhny
>             Fix For: 3.2.1, 3.3.0.M1
>
>
> We use Perforce which leaves files read/only until they are checked out for modification.  The Perforce Eclipse plugin will check out a file and make it writable as soon as someone edits the file in Eclipse.  
> The JBoss Tools Web (Rich Faces) editor does not support code completion if the file is initially opened read/only.  You have to check out the file in Eclipse before opening it in the JBoss web editor.  Or, if you open the file while still read/only. You have to open the file and make any change so that Perforce checks it out. Then close the file and re-open it.  Now code completion works.
> The Jboss Tools Web (xhtml) should support code completion on read/only files the same way the java editor does

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira