[jbosstools-issues] [JBoss JIRA] Updated: (JBDS-1676) NullPointerException in SmooksGraphicalEditorPart

[Martin Weiler (JIRA)]

     [ https://issues.jboss.org/browse/JBDS-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Weiler updated JBDS-1676:
--------------------------------

    Attachment: SmooksProcessorException.zip


Attached a video ("SmooksProcessorException.zip") picturing the exception in action.

> NullPointerException in SmooksGraphicalEditorPart
> -------------------------------------------------
>
>                 Key: JBDS-1676
>                 URL: https://issues.jboss.org/browse/JBDS-1676
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: SOA Platform
>    Affects Versions: 4.0.0.GA
>         Environment: Windows 7
> -vm "C:\Program Files (x86)\Java\jdk1.6.0_23\bin"
>            Reporter: Martin Weiler
>            Assignee: Tom Fennelly
>             Fix For: 4.1.0.CR2
>
>         Attachments: debugInfo.txt, example.jar, example.xsd, SmooksProcessorException.zip
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I have a problem using the 'Smooks Processing' tool to configure a smooks file (used for converting XML to Java) when the Java-class is located in a jar file.
> The problem seems to relate to the 'Java Mapping' view of the 'Smooks Processing' tool and generates an OutOfMemoryException. The exception occurs when inside the 'Java Mapping' view and clicking or dragging input elements to corresponding output elements or selecting the connection between the elements. The exception sometimes occur at the first adjustments and sometimes it takes several adjustments before it occurs. When using a file where the elements already have been connected, the exception sometimes occur imidiatly when selecting the 'Java Mapping' icon.
> I have not seen this problem when using a Java-class which is not located in a jar file. 
> Attached is an example jar file ('example.jar') and XML schema ('example.xsd') which I have used to reproduce the problem. 

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