[
https://issues.apache.org/jira/browse/TAP5-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871731#action_12871731
]
Nicolas Delsaux commented on TAP5-1171:
---------------------------------------
As all JavaFX objects extend the FXBase root class, it could be possible to
mimic behaviour of TAP5 830.
It can be done witouth prior knowledge of JavaFX presence, by simply checking
if object class implements FXObject (indeed, Antoine, as JavaFX objects may
sometimes be subclasses of Java objects, the inheritance from FXBase is not
always true, which IS the case of the implementation of FXObject). So a code
like this one
try {
if(Class.forName("com.sun.javafx.runtime.FXObject").isAssignableFrom(myObject.getClass()))
{
// Speciic JavaFX code goes here
}
} catch(ClassNotFoundException cnfe) {
// this code surely isn't JavaFX code
}
could be added where TAP5-830 handles synthetic method removall from Groovy.
However, I wonder how will Tapestry-IOC grow if all languages supported by the
Java platform need their specific hacks to handle correctly local methods.
> Tapestry should ignore FXBase methods in JavaFX module classes
> --------------------------------------------------------------
>
> Key: TAP5-1171
> URL: https://issues.apache.org/jira/browse/TAP5-1171
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.2.0
> Reporter: Antoine Mischler
> Assignee: Howard M. Lewis Ship
> Attachments: InjectionTest-src.zip, log.txt
>
>
> JavaFX classes always extends the com.sun.javafx.runtime.FXBase class. For
> module classes written in JavaFX, Tapestry complains that it doesn't
> recognize the public methods from FXBase. These methods should be ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
