You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by sl...@clearstream.com on 2004/11/25 17:50:42 UTC

Myfaces Components examples with Sun RI 1.1.01 inside Weblogic 8.1sp3 errors

I tried Myfaces Components examples with Sun RI 1.1.01 inside Weblogic 
8.1sp3.

Some worked fine (SortTable, Tab Pane, Tree), but many didn't. I could fix 
a few examples by removing the name attribute from the h:form and 
replacing it by id.
But some examples aren't working like the calendar.

I get the following error.
Any clue?
Are MyFaces components working with Sun RI?

Regards,

Stephane Lemaire

<25 nov. 2004 17 h 36 CET> <Error> <HTTP> <BEA-101020> 
<[ServletContext(id=26114
569,name=ApacheComponents,context-path=/ApacheComponents)] Servlet failed 
with E
xception
java.lang.IllegalStateException: Duplicate component ID 
'calendarForm2:_id8' fou
nd in view.
        at 
com.sun.faces.application.StateManagerImpl.removeTransientChildrenAnd
Facets(StateManagerImpl.java:173)
        at 
com.sun.faces.application.StateManagerImpl.removeTransientChildrenAnd
Facets(StateManagerImpl.java:181)
        at 
com.sun.faces.application.StateManagerImpl.removeTransientChildrenAnd
Facets(StateManagerImpl.java:181)
        at 
com.sun.faces.application.StateManagerImpl.removeTransientChildrenAnd
Facets(StateManagerImpl.java:199)
        at 
com.sun.faces.application.StateManagerImpl.removeTransientChildrenAnd
Facets(StateManagerImpl.java:181)
        at 
com.sun.faces.application.StateManagerImpl.saveSerializedView(StateMa
nagerImpl.java:85)
        at 
com.sun.faces.taglib.jsf_core.ViewTag.doAfterBody(ViewTag.java:169)
        at jsp_servlet.__calendar._jspService(calendar.jsp:94)
        at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
        at 
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:996)



-----------------------------------------
Visit us at http://www.clearstream.com
IMPORTANT MESSAGE    Internet communications are not secure and therefore
Clearstream International does not accept legal responsibility for the
contents of this message.    The information contained in this e-mail is
confidential and may be legally privileged. It is intended solely for the
addressee. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it,
is prohibited and may be unlawful. Any views expressed in this e-mail are
those of the individual sender, except where the sender specifically states
them to be the views of Clearstream International or of any of its
affiliates or subsidiaries.    END OF DISCLAIMER