[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-7308:
--------------------------------------

Hi Yahor,
I couldn't find any new JBDS build, so I tried to test this on jbosstools-3.2_stable_branch.aggregate-Update-2011-03-15_08-44-17-H563.zip but it still doesn't contain the fix (i.e. I got the message Could not open the Visual Page Editor...).
VPE is version 3.2.0.v20110311-0855-H50-GA .
I suppose I need 3.2.1, right? But unfortunately I couldn't find it anywhere. Do you think there is a build I can check against which would contain the fix?

> VPE Part should not show exceptions but readable explanation why it cannot be loaded
> ------------------------------------------------------------------------------------
>
>                 Key: JBIDE-7308
>                 URL: https://issues.jboss.org/browse/JBIDE-7308
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Visual Page Editor core
>    Affects Versions: 3.2.0.Final
>         Environment: All other platforms except supported ones: 
> macosx-carbon-x86
> macosx-cocoa-x86
> win32-win32-x86
> linux-gtk-x86
> linux-gtk-x86_64
>            Reporter: Denis Golovin
>            Assignee: Yahor Radtsevich
>              Labels: usability
>             Fix For: 3.2.1, 3.3.0.M1
>
>         Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png, XL-x86_64-1.png, XL-x86_64-2.png
>
>
> Exceptions related to loading xulrunner should be handled right way. Human friendly messages would be good here for usecases we know. VPE should check for current platform and if it is not supported do not scary users with exceptions. It should try to load XL just in case path to XL injected outside through System property, but show explanation instead of just exception. Something like:
> "Current platform ${os}-${ws}-${arch} is not supported. To find list of supported platforms and possible workarounds. please read this article on JBoss Tools Community Portal". If someone is trying to inject XULRunner implementation using system property it can say, That "Visual Editor tried to load XL from provided loaction ${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log View".
> We could also have check box to remove VE related parts from editor:
> "[x] Open only source part of Visual Editor".

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