[
https://issues.apache.org/jira/browse/WICKET-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969486#action_12969486
]
Ronald Tetsuo Miura commented on WICKET-3036:
---------------------------------------------
AFAIK these classes are used in specific components, like captcha, or non-core
classes, like DynamicImageResource. If you want your application to run on GAE,
simply don't use them. Create your own alternatives, using GAE's native APIs
(http://code.google.com/intl/en/appengine/docs/java/images/) - which obviously
couldn't be added to wicket-core.
A dependency path I've found, that could cause some trouble is
Application->DefaultButtonImageResourceFactory->DefaultButtonImageResource->java.awt.Color,
but I don't know in what situation this class could be loaded (I haven't had
any problem with it yet). Still, replacing it with an alternative
implementation (in your application) shouldn't be a problem.
One dependency that is really painful is javax.swing.TreeModel, used by
AbstractTree. This is a completely unnecessary dependency, in a much more
critical component, and I think it's worth replacing in wicket-core.
> Remove dependancy on Java.AWT.*, Javax.Swing.*. classes
> -------------------------------------------------------
>
> Key: WICKET-3036
> URL: https://issues.apache.org/jira/browse/WICKET-3036
> Project: Wicket
> Issue Type: Improvement
> Components: wicket, wicket-examples
> Affects Versions: 1.4.11, 1.5-M1
> Reporter: Clint Checketts
> Priority: Minor
>
> Instead of leveraging the existing classes in Java.AWT.*, Javax.Swing.*
> Wicket could create its own equivalents or repackage the existing ones.
> The motivation behind this is that Google's App Engine blacklists those
> packages for web development.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
