[jbosstools-issues] [JBoss JIRA] (JBIDE-10301) "Link with Editor" does not work for tld file which is in jar taglib and opened by "JBoss Tools XML Editor"

[Victor Rubezhny (Issue Comment Edited) (JIRA)]

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

Victor Rubezhny edited comment on JBIDE-10301 at 12/6/11 12:59 PM:
-------------------------------------------------------------------

I have used the project suggested in JBIDE-10173 to reproduce the issue.

All the steps from JBIDE-10173 were done exactly as described in Steps to Reproduce except the step 4: 
When I just do the Ctrl-LetfClick no TLD-file was found for <stopka:css /> tag - this is because actually there are 3 open-ons registered for this tag and the first (the WTP one) cannot find the appropriate TLD-file. So, I've used JBoss Tools open-on due to open the TLD-file as follows:

Step #4: Move mouse over <stopka:css /> tag name while Ctrl-key is pressed. The list of possible open-ons will be displayed for the tag <stopka:css />. Select "Open 'stopka-ui-base-1.0.1.jar :stopka.tld : css'" open-on (which was second for me) to open the stopka.tld file.

After the stopka.tld was opened in JBoss Tools Tag Library Editor, other file (test.jspx) still was selected in Package Explorer. 
When I pressed 'Link with Editor' button, the appropriate file was selected in Package Explorer.

The changing the active editor/selecting the other files in Package explorer didn't brake this functionality: when the JBoss Tools Tag Library Editor is active it could be linked to according stopka.tld file in Package Explorer by pressing 'Link With Editor' button.

So, the issue is not reproducible for me.
                
      was (Author: vrubezhny):
    I have used the project suggested in JBIDE-10173 to reproduce the issue.

All the steps from JBIDE-10173 were done exactly as described in Steps to Reproduce except the step 4: 
When I just do the Ctrl-LetfClick no TLD-file was found for <stopka:css /> tag - this is because actually there are 3 open-ons registered for this tag and the first (the WTP one) cannot find the appropriate TLD-file. So, I've used JBoss Tools open-on due to open the TLD-file as follows:

Step #4: Move mouse over <stopka:css /> tag name while Ctrl-key is pressed. The listof possible open-ons will be displayed for the tag <stopka:css />. Select "Open 'stopka-ui-base-1.0.1.jar :stopka.tld : css'" open-on (which was second for me) to open the stopka.tld file.

After the stopka.tld was opened in JBoss Tools Tag Library Editor, other file (test.jspx) still was selected in Package Explorer. 
When I pressed 'Link with Editor' button, the appropriate file was selected in Package Explorer.

The changing the active editor/selecting the other files in Package explorer didn't brake this functionality: when the JBoss Tools Tag Library Editor is active it could be linked to according stopka.tld file in Package Explorer by pressing 'Link With Editor' button.

So, the issue is not reproducible for me.
                  
> "Link with Editor" does not work for tld file which is in jar taglib and opened by "JBoss Tools XML Editor"
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-10301
>                 URL: https://issues.jboss.org/browse/JBIDE-10301
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jsp/jsf/xml source editing
>    Affects Versions: 3.3.0.M5
>            Reporter: Vitali Yemialyanchyk
>            Assignee: Viacheslav Kabanovich
>             Fix For: 3.3.0.Beta1
>
>
> take a look to https://issues.jboss.org/browse/JBIDE-10300 for steps to reproduce;
> when you open stopka.tld - check "Link with Editor" if it does not checked.
> as a result - Project or Package Explorer should direct to 
> stopka-ui-test --> Java Resources --> Libraries --> Web App Libraries --> stopka-ui-base-1.0.1.jar --> META-INF --> stopka.tld
> but it does not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira