OK, there are huge differences between pax-wicket and wicket-osgi.
Only some for example:
feature | pax-wicket
| wicket-osgi
infrastructure | http-service
| war-deployer
injection | blueprint & spring beans and services | services
only via @Inject
configuration | fully based on osgi-services |
web.xml and jetty (war-deployer)
classloading | full support; also of internal packages via
delegating classloader | simple classloader depending on dynamic
imports somewhere |
...
Currently wicket-osgi is not much enhancement over the classical
"pack-a-war-and-throw-it-to-pax-web-war-deployer-approach". But if all
you require is the old approach without a war and injection via
blueprint this may also be a solution. I try to nail down the
differences and enhance the "introduction" page to pax-wicket a little
bit more to make it's features clear. I hope I reach the author and
that we find a way to combine the efforts.
Thanks again for the information and kind regards,
Andreas
On Sun, Jul 3, 2011 at 8:31 PM, Andreas Pieber <anpie...@gmail.com> wrote:
> Thanks for the info Toni. I'll give it a shot tomorrow
>
> On Jul 3, 2011 8:16 PM, "Toni Menzel" <t...@okidokiteam.com> wrote:
>> Hi,
>>
>> i notices recent progress on Pax Wicket (which is just awesome, thanks!).
>> Now, i came along this : https://github.com/wicketstuff/core/wiki/Osgi
>>
>> Which in turn led me to this:
>> https://github.com/wicketstuff/core/issues/46#issuecomment-1493913
>>
>> Good info.
>
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
