[
http://issues.ops4j.org/browse/PAXWICKET-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871#action_13871
]
Andreas Pieber commented on PAXWICKET-18:
-----------------------------------------
Thanks for helping me out with this david! A solution outside of pax-wicket
(e.g. fragment bundles) also sound fine to me (well at least with fragments
you're able to explicitly define which classes, where...) but then we/I have to
document it :)
> Registration of IClassResolver is backwards
> -------------------------------------------
>
> Key: PAXWICKET-18
> URL: http://issues.ops4j.org/browse/PAXWICKET-18
> Project: Pax Wicket
> Issue Type: Bug
> Reporter: David Leangen
> Assignee: Edward Yakop
> Fix For: 1.0.0.RELEASE
>
>
> Pax-wicket requires one to register an IClassResolver for (for example)
> library bundles using a property with the relevant application name. However,
> this is all backwards.
> An application can know about a library, but a library should not need to
> know anything about which applications will use it. I.e. the library should
> be a dependency of the app, and not the other way around.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
