Hi,

It seems Form.appendDefaultButtonField now depends on ClientInfo which have not been implemented for portlets. You might override appendDefaultButtonField, or implement the ClientInfo for portlets (see WebClientInfo). Patches are always welcome.

See the source for more information.

Janne

On 25.6.2007, at 19.04, manunabble wrote:


Dear Janne,

I am testing a little only-1-page portlet (Wicket 1.2.3), and when loading the portlet in the container (Liferay Portal) I get the following error:

<error>
WicketMessage: ClientInfo not yet implemented
Root cause:
wicket.WicketRuntimeException: ClientInfo not yet implemented
at
wicket.protocol.http.portlet.PortletRequestCycle.newClientInfo (PortletRequestCycle.java:99)
at wicket.Session.getClientInfo(Session.java:323)
at wicket.markup.html.form.Form.appendDefaultButtonField(Form.java: 518)
at wicket.markup.html.form.Form.onComponentTagBody(Form.java:769)
at wicket.Component.renderComponent(Component.java:1719)
at wicket.MarkupContainer.onRender(MarkupContainer.java:927)
at wicket.markup.html.form.Form.onRender(Form.java:844)
at wicket.Component.render(Component.java:1533)
at wicket.MarkupContainer.renderNext(MarkupContainer.java:1334)
at wicket.MarkupContainer.renderComponentTagBody (MarkupContainer.java:982)
at wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:917)
at wicket.Component.renderComponent(Component.java:1719)
at wicket.MarkupContainer.onRender(MarkupContainer.java:927)
at wicket.Component.render(Component.java:1533)
at wicket.Component.render(Component.java:1499)
...
</error>

I've been checking wicket-javadoc to read about PortletRequestCycle and
ClientInfo, but cannot get much information there.

Would you mind telling me why may this be happening, I mean, why it finds "ClientInfo not implemented yet"? How can this be fixed cause it seems to be
internally managed by Wicket.
--
View this message in context: http://www.nabble.com/ClientInfo-not- yet-implemented-%28portlet%29-tf3977367.html#a11290125
Sent from the Wicket - Dev mailing list archive at Nabble.com.


Reply via email to