-Igor
On 3/6/06, David Leangen <[EMAIL PROTECTED]
> wrote:
> How much work would it be, and how 'intrusive' is it for non-osgi
> users?
Well, I guess that depends on what you mean by "intrusive".
In keeping with OSGi principles, there are no particular requirements
upon the individual classes. So, the classes that are already in the
project (or "bundle" in OSGi speak) are hardly changed at all.
However, we would need to add a few classes to the project. I didn't
count the number of additional classes, but the package would more than
triple, I think.
People who don't use OSGi can ignore them, but it would otherwise
"pollute" the project for people who don't need them.
So.... given the above and the fact that the quickstart is also intended
for people unfamiliar with Wicket to get up-and-running quickly, I guess
I wouldn't recommend having them together in a standard way unless we
can figure out a clever way of doing it.
It would be cool if Wicket came with OSGi support itself. ;-)
That way, the quickstart could stay just as tiny as it is now.
> i.e. can it be in one package without biting one another?
Yes, no problem there, I think, notwithstanding the above problem.
Let me know.
Cheers,
Dave
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
