[
https://issues.apache.org/jira/browse/WICKET-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584101#comment-13584101
]
Martin Grigorov commented on WICKET-5037:
-----------------------------------------
I'm not sure this is a good idea.
Even now users complain that Wicket app requires at least three jars: -util,
-request, -core.
Additionally many of the models are component aware, i.e. they need a reference
to org.apache.wicket.Component, so they cannot be extracted in a separate jar.
> Model framework
> ---------------
>
> Key: WICKET-5037
> URL: https://issues.apache.org/jira/browse/WICKET-5037
> Project: Wicket
> Issue Type: Wish
> Components: wicket
> Affects Versions: 7.0
> Reporter: SoulSpirit
> Priority: Trivial
>
> Wicket models are powerful and very handy. You get used to them and you wish
> you could always use them, even outside of Wicket.
> There are many fields in which they could be used outside of a Wicket
> context, in particular PropertyModel, LoadableDetachableModel and
> StringResourceModel.
> It would be wonderful to have the model framework packaged in its own JAR,
> with no dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
