[jboss-jira] [JBoss JIRA] Resolved: (GPD-128) ClassCastException in XmlAdapterFactory.getConfigurationElementByXmlElementName(String)

[Koen Aers (JIRA)]

     [ http://jira.jboss.com/jira/browse/GPD-128?page=all ]

Koen Aers resolved GPD-128.
---------------------------

    Resolution: Won't Fix

John, 

I forgot to delete the XmlAdapterRegistry.getConfigurationElementByXmlElementName(String) method while implementing GPD-111. In fact you should now use the XmlAdapterRegistry.getConfigurationElementByXmlNode(Node) to obtain the correct configuration element. You can have multiple configurationelements related to the same xml node name. There are still issues with it, but I am working on fixing those. Have a look at GPD-111 and feel free to ask for clarifications.

Regards,
Koen

> ClassCastException in XmlAdapterFactory.getConfigurationElementByXmlElementName(String)
> ---------------------------------------------------------------------------------------
>
>                 Key: GPD-128
>                 URL: http://jira.jboss.com/jira/browse/GPD-128
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: John Ruud
>         Assigned To: Koen Aers
>
> I just noticed this problem in the current HEAD (so not in the official 3.1.0.CR release, I think). In XmlAdapterFactory (1.2), a TreeSet (as opposed to a IConfigurationElement) is now returned under certain conditions, and this causes a ClassCastException to be thrown (and this is breaking some of my exsiting code)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira