Thats not completely correct.
The current Wicket implementation depends on the PortletBridge
implementation and is not 286 ready. Athough it has some 286 features
like the resourceUrl, that part of the implementation depends on the
PortletBridge implementation. Work is in progress to make Wicket more
jsr-286 compliant, but at this point there is not a final solution or a
timeframe for a final solution.
Peter Eriksson wrote:
Hello everybody,
In my day job I use WebSphere Portal, working as a consultant, and I have
been using JSF in portlet development and really found it quite painful. The
version of WebSphere Portal is 6.0 and that uses JSF 1.1 and I know things
have improved somewhat in more recent versions of JSF, but that is not
really helping much. Now to my question, I have been trying out Wicket and I
find it very nice to work with compared to JSF and I really would like to
use it in WebSphere Portal, so is anybody out there using it with WebSphere
Portal 6? I have read a few postings regarding portal support and understood
that it depends on how and if the PortletBridge is implemented in the
Portlet container of the vendor in question. WebSphere Portal 6.0 is JSR168
compliant and I know that the upcoming release WebSphere Portal 6.1 is going
to be JSR286 compliant and that Wicket support should be working in a JSR286
environment without problem, or have I misunderstood something?
Best Regards,
/Peter Eriksson
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
