Re: javascript error jsf is not defined
Hi Jakob,
I guess I use the built-in facelets. At least this is the code from
faces-config:
view-handler
com.sun.facelets.FaceletViewHandler
/view-handler
Matthias
Original-Nachricht
Datum: Thu, 1 Apr 2010 19:53:11 +0200
Von: Jakob Korherr jakob.korh...@gmail.com
An: MyFaces Discussion users@myfaces.apache.org
Betreff: Re: javascript error jsf is not defined
Hi Matthias,
Are you using the built-in facelets or are you using facelets-1.1.x?
You're welcome! I'm glad I could help.
Danke - ebenfalls fröhliche Ostern :)
Jakob
2010/4/1 Matthias Leis matthias.l...@gmx.net
Hi Jakob,
I'm already using Facelets (and MyFaces 2.0).
I have no clue, why h:outputScript shouldn't be defined... anyway, I
imported the script as you suggested and it works perfectly! Many thanks
and
happy Easter! (oder einfach fröhliche Ostern! ;) )
Original-Nachricht
Datum: Thu, 1 Apr 2010 14:16:04 +0200
Von: Jakob Korherr jakob.korh...@gmail.com
An: MyFaces Discussion users@myfaces.apache.org
Betreff: Re: javascript error jsf is not defined
Hi Matthias,
You're using MyFaces 2.0 and JSP, right?
The problem is that h:outputScript only works for facelets and not for
JSP.
I would recommend that you use facelets instead of JSP, because in JSF
2.0
JSP is seen as a legacy technology which does not include many of the
new
features. Furthermore it is easy to change!
If you do want to use JSP, you will have to include the script
directly
rather than using h:outputScript. This will look something like this:
script type=text/javascript
src=/test-webapp/javax.faces.resource/jsf.js.jsf?ln=javax.faces/script
But note that my application prefix is test-webapp and my used
mapping
is
*.jsf - I guess you will have to change those settings!
Regards,
Jakob
2010/4/1 Matthias Leis matthias.l...@gmx.net
Hi Jakob,
thanks for your quick reply. I tried
h:outputScript name=jsf.js library=javax.faces target=head/
and I get
Tag Library supports namespace: http://java.sun.com/jsf/html, but no
tag
was defined for name: outputScript
I know, that outputScript is defined, but how to tell it JSF? ;) How
to
update my taglib?
I'm almost sorry for this question :(
Thanks!
Original-Nachricht
Datum: Thu, 1 Apr 2010 11:48:06 +0200
Von: Jakob Korherr jakob.korh...@gmail.com
An: MyFaces Discussion users@myfaces.apache.org
Betreff: Re: javascript error jsf is not defined
Hi Matthias,
If you have some javascript in onclick we have to use the
jsf.util.chain()
function to chain your javascript with the MyFaces javascript. For
that
to
work we need the JSF javascript library in the view. This include
_should_
happen automatically, but it seems that it does not.
I'll take a look at this one! For now you can include the
following
in
your
view to include the JSF javascript library manually and thus to
make
it
work:
h:outputScript name=jsf.js library=javax.faces
target=head/
Regards,
Jakob
2010/4/1 Matthias Leis matthias.l...@gmx.net
Hi,
I have this piece of code:
h:commandLink value=#{msg.adminPageLogFileTableDelete}
action=#{adminPage.deleteLogFile} onclick=confirm('Are you
sure?')/
When I click the link, I get an JavaScript error: jsf is not
defined
What does this mean?
I am using myfaces 2.0.0-beta-3
Any help is appreciated :)
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
--
Sicherer, schneller und einfacher. Die aktuellen Internet-Browser -
jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser
--
GMX.at - Österreichs FreeMail-Dienst mit über 2 Mio Mitgliedern
E-Mail, SMS mehr! Kostenlos: http://portal.gmx.net/de/go/atfreemail
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
Re: javascript error jsf is not defined
Am 07.04.10 08:14, schrieb Matthias Leis: Hi Jakob, I guess I use the built-in facelets. At least this is the code from faces-config: view-handler com.sun.facelets.FaceletViewHandler /view-handler Wrong view handler... the jsf2 one is not under com.sun, but under javax.faces.view.facelets and it is initialized automatically if you use myfaces and the jsf2 facelets (no further configuration is needed) Com sun is the old Facelet 1.x stuff and the new tags cannot work under it due to the extensions in the jsf2 lifecycle and view handler api. So it is either old facelets or the jsf2 one but not a mix of both, sort of a hard break introduced by the namespace change from com.sun into javax.facelets and due to the api changes, but better once a hard break from old habits than having endless pain :-) Basically if you run in a pure jsf2 environment you can start to use facelets without additional configuration on the faces-config side. Werner
Re: Missing/changed methods after migrating to MyFaces 1.2.8
Am 06.04.10 13:19, schrieb Seema Mani:
hi,
I'm facing a few issues after migrating to MyFaces 1.2.8 from MyFaces 1.1.7
1. In my custom tag handler class, extending HtmlMessageTag, there were
calls to setStringProperty method in the superclass. But these methods are
not existing now
2. In my custom tag handler class, extending HtmlCommandButtonTag, there
were calls to the setDisabled method, which had String argument. This method
now takes ValueExpression as the argument. But the values to be passed are
static like true and false
Please advise on how these can be resolved.
Thanks,
Seema
My guess is,this is due to the change to the unified el and a later JSP
version, the taglib tld file defines the type of the attribute.
(see the corresponding tld file in the sources for the example to the
HtmlMessageTag)
The entire direct conversion aspect via setStringProperty etc... is not
needed anymore
from the tld
attribute
description![CDATA[Specifies whether the detailed
information from the message should be shown.
Default to true.]]/description
nameshowDetail/name
deferred-value
typeboolean/type
/deferred-value
/attribute
from the tag handler
private ValueExpression _showDetail;
public void setShowDetail(ValueExpression showDetail)
{
_showDetail = showDetail;
}
protected void setProperties(UIComponent component)
{
if (!(component instanceof
javax.faces.component.html.HtmlMessage ))
{
throw new IllegalArgumentException(Component +
component.getClass().getName() + is no
javax.faces.component.html.HtmlMessage);
}
javax.faces.component.html.HtmlMessage comp =
(javax.faces.component.html.HtmlMessage) component;
super.setProperties(component);
if (_showDetail != null)
{
comp.setValueExpression(showDetail, _showDetail);
}
due to the incoming parameters being of type value expression and having
the type information already inside.
Not quite the area of my expertise but I hope I got it right.
Problem with setStringValue etc... generally is that this are methods
which were implementation specific (part of myfaces not the jsf api),
and bound to change if the el system itself was moved over to a more
global scope which happened between 1.1 and 1.2.
Werner
Re: Loading Gif Animated While Loading A Jsf Page
Thanks for the suggestions! Have a nice day, Vale -- View this message in context: http://old.nabble.com/Loading-Gif-Animated-While-Loading-A-Jsf-Page-tp28117980p28162529.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
WG: [Trinidad] Trinidad 1.2.13 shortcomings: create bug track entries for them?
Hi,
Reposted this as I think I got the wrong end of the mailing list for this
issue..;)
Recently we tried to update from 1.2.9 to 1.2.13 -btw we were testing the
releases in between and they seemed ok- and now it looks as if we were
stuck with this version. Because of the following effects, our application
did not work anymore as expected:
1 Trinidad's JS Object TrRequestQueue is not anymore found when we try to
address it in our Java Script i.e. it seems there is a new execution order
in command; the consequence, for instance, is that when we try to override
the alerError function to redirect the error to something else than the
not-so-nice JS Trinidad popup we cannot do this anymore; in our template
page we set
...
trh:head
title../title
meta
http-equiv=Content-Type
content=text/html; charset=UTF-8 /
...
script
src=#{request.contextPath}/js/ourJavaScript.js
type=text/javascript /
...
/trh:head
...
2 the tree tag rendering now works by generating duplicate IDs which
Trindad itself criticizes in its log; a closer look reveals that in 1.2.13
we now get a span for each node which always has the same ID as the tree
itself..
3 the Trinidad poller Component seems to have changed as well, because
after completing the setup idle interval time of, in our case, 5 minutes a
complete refresh is executed, which in our case, sometimes -depending on
the rsp. page- leads to redirect back to the URL of the browser's address
My question is rather organizational: should I open track entries in the
JIRA for each of these issues? Or are these effects due to some basic but
new configuration singular for 1.2.13 which we missed ??
Thanks,
Wolfgang.
PTA Programmier-Technische Arbeiten GmbH
Seckenheimer Str. 65-67, 68165 Mannheim
Amtsgericht Mannheim, HRB 1139
USt-IdNr.: DE 143 839 368
Geschäftsführer:
Dipl.-Ing. Peter Fischer
Dr. Harald W. Busch
Dipl.-Kfm. Knut Fischer
**
http://www.pta.de
Mit 1875 Erfahrungsberichten aus 41 Jahren erfolgreicher Projektarbeit!
**
PTA Programmier-Technische Arbeiten GmbH
Seckenheimer Str. 65-67, 68165 Mannheim
Amtsgericht Mannheim, HRB 1139
USt-IdNr.: DE 143 839 368
Geschaeftsfuehrer:
Dipl.-Ing. Peter Fischer
Dr. Harald W. Busch
Dipl.-Kfm. Knut Fischer
PTA Programmier-Technische Arbeiten GmbH
Seckenheimer Str. 65-67, 68165 Mannheim
Amtsgericht Mannheim, HRB 1139
USt-IdNr.: DE 143 839 368
Geschaeftsfuehrer:
Dipl.-Ing. Peter Fischer
Dr. Harald W. Busch
Dipl.-Kfm. Knut Fischer
Re: Loading Gif Animated While Loading A Jsf Page
Mike, Adrian, could you show your approaches in an example? 2010/4/7 vale_java_dev fabrizi_valent...@yahoo.it Thanks for the suggestions! Have a nice day, Vale -- View this message in context: http://old.nabble.com/Loading-Gif-Animated-While-Loading-A-Jsf-Page-tp28117980p28162529.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: javascript error jsf is not defined
You are right about the view handler. I forgot that JSF2 doesn't need afaces-config anymore. But I need it anyway for registering a phase listener. Anyway, if I remove the view handler from the faces-config, all I get from my webapp is a blank page and no errors. Do I have to define a view-handler if I use a faces-config file or does JSF just use the dafault view handler? Original-Nachricht Datum: Wed, 07 Apr 2010 08:54:02 +0200 Von: Werner Punz werner.p...@gmail.com An: users@myfaces.apache.org Betreff: Re: javascript error jsf is not defined Am 07.04.10 08:14, schrieb Matthias Leis: Hi Jakob, I guess I use the built-in facelets. At least this is the code from faces-config: view-handler com.sun.facelets.FaceletViewHandler /view-handler Wrong view handler... the jsf2 one is not under com.sun, but under javax.faces.view.facelets and it is initialized automatically if you use myfaces and the jsf2 facelets (no further configuration is needed) Com sun is the old Facelet 1.x stuff and the new tags cannot work under it due to the extensions in the jsf2 lifecycle and view handler api. So it is either old facelets or the jsf2 one but not a mix of both, sort of a hard break introduced by the namespace change from com.sun into javax.facelets and due to the api changes, but better once a hard break from old habits than having endless pain :-) Basically if you run in a pure jsf2 environment you can start to use facelets without additional configuration on the faces-config side. Werner -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
Re: javascript error jsf is not defined
Hi, In JSF 2.0 you don't have to configure a view handler. It will decide whether to use the new Facelets- or the JSP-ViewDeclarationLanguage in the default ViewHandlerImpl. Regards, Jakob 2010/4/7 Matthias Leis matthias.l...@gmx.net You are right about the view handler. I forgot that JSF2 doesn't need afaces-config anymore. But I need it anyway for registering a phase listener. Anyway, if I remove the view handler from the faces-config, all I get from my webapp is a blank page and no errors. Do I have to define a view-handler if I use a faces-config file or does JSF just use the dafault view handler? Original-Nachricht Datum: Wed, 07 Apr 2010 08:54:02 +0200 Von: Werner Punz werner.p...@gmail.com An: users@myfaces.apache.org Betreff: Re: javascript error jsf is not defined Am 07.04.10 08:14, schrieb Matthias Leis: Hi Jakob, I guess I use the built-in facelets. At least this is the code from faces-config: view-handler com.sun.facelets.FaceletViewHandler /view-handler Wrong view handler... the jsf2 one is not under com.sun, but under javax.faces.view.facelets and it is initialized automatically if you use myfaces and the jsf2 facelets (no further configuration is needed) Com sun is the old Facelet 1.x stuff and the new tags cannot work under it due to the extensions in the jsf2 lifecycle and view handler api. So it is either old facelets or the jsf2 one but not a mix of both, sort of a hard break introduced by the namespace change from com.sun into javax.facelets and due to the api changes, but better once a hard break from old habits than having endless pain :-) Basically if you run in a pure jsf2 environment you can start to use facelets without additional configuration on the faces-config side. Werner -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
Re: Loading Gif Animated While Loading A Jsf Page
Unfortunately, I cannot. On Wed, Apr 7, 2010 at 6:09 AM, Anton Gavazuk antongava...@gmail.com wrote: Mike, Adrian, could you show your approaches in an example? 2010/4/7 vale_java_dev fabrizi_valent...@yahoo.it Thanks for the suggestions! Have a nice day, Vale -- View this message in context: http://old.nabble.com/Loading-Gif-Animated-While-Loading-A-Jsf-Page-tp28117980p28162529.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Trinidad 1.2.13: another upgrade problem: UINodePropertyKey unserializable
Hi, Yet another problem here when trying to upgrade to 1.2.13: Certain tr:commandLink within a Trinidad table that are supposed to lead to Trinidad popup dialog show the dialog but the application crashes shortly thereafter with the log you can see attached below. In 1.2.9 this used to work perfectly! If this reminds anyone of any particular changes to 1.2.13, please do not hesitate to drop a brief hint. We are at a loss here! Best wishes, Wolfgang 14:51:18,780 ERROR [PropertyKey] Nicht serialisierbarer Wert: sortablemodel[javax.faces.model.listdatamo...@5e63b2] für Schlüssel: UINodePropertyKey[value,11] 14:51:18,832 ERROR [UIXComponentBase] Status für untergeordnete Komponenten von Komponente: coretable[org.apache.myfaces.trinidad.component.uixtable$rowkeyfacesbeanwrap...@d20d2a, id=table] konnte nicht gespeichert werden 14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete Komponenten von Komponente: HtmlRowLayout[UIXFacesBeanImpl, id=j_id36] konnte nicht gespeichert werden 14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete Komponenten von Komponente: CoreSubform[UINodeFacesBean, id=dataAreaDlgForm] konnte nicht gespeichert werden 14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete Komponenten von Komponente: CoreShowDetailItem[UINodeFacesBean, id=dataAreaDlgId] konnte nicht gespeichert werden 14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete Komponenten von Komponente: CorePanelAccordion[UIXFacesBeanImpl, id=mainPanelDlgAccordion] konnte nicht gespeichert werden 14:51:18,842 ERROR [UIXComponentBase] Status für untergeordnete Komponenten von Komponente: CoreForm[UIXFacesBeanImpl, id=MainFormDlg] konnte nicht gespeichert werden 14:51:18,842 ERROR [UIXComponentBase] Status für untergeordnete Komponenten von Komponente: HtmlBody[UIXFacesBeanImpl, id=j_id5] konnte nicht gespeichert werden 14:51:18,842 ERROR [UIXComponentBase] Status für untergeordnete Komponenten von Komponente: HtmlHtml[UIXFacesBeanImpl, id=j_id0] konnte nicht gespeichert werden 14:51:18,842 ERROR [viewhandler] Error Rendering View[/popup-overview-dialog.xhtml] java.lang.IllegalStateException: JDK Log (ws. Trinidad) erzeugt! at de.pta.ctrl.TrinidadLoggingRedirector$JDKLogHandler.init$_aroundBody2(TrinidadLoggingRedirector.java:172) at de.pta.ctrl.TrinidadLoggingRedirector$JDKLogHandler$AjcClosure3.run(TrinidadLoggingRedirector.java:1) at de.pta.aspect.ExceptionTracker.ajc$around$de_pta_aspect_ExceptionTracker$1$29c98745proceed(ExceptionTracker.aj:1) at de.pta.aspect.ExceptionTracker.ajc$around$de_pta_aspect_ExceptionTracker$1$29c98745(ExceptionTracker.aj:20) at de.pta.ctrl.TrinidadLoggingRedirector$JDKLogHandler.publish(TrinidadLoggingRedirector.java:172) at java.util.logging.Logger.log(Logger.java:452) at org.apache.myfaces.trinidad.logging.TrinidadLogger.doLog(TrinidadLogger.java:1540) at org.apache.myfaces.trinidad.logging.TrinidadLogger.log(TrinidadLogger.java:336) at org.apache.myfaces.trinidad.logging.TrinidadLogger.warning(TrinidadLogger.java:807) at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:905) at javax.faces.component.UIComponentBase.processSaveState(UIComponentBase.java:1119) at com.sun.faces.application.StateManagerImpl.saveSerializedView(StateManagerImpl.java:251) at org.jboss.seam.jsf.SeamStateManager.saveSerializedView(SeamStateManager.java:64) at org.apache.myfaces.trinidadinternal.application.StateManagerImpl.saveSerializedView(StateManagerImpl.java:165) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:615) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189) at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at de.pta.jsf.filter.DummyFilter.doFilter(DummyFilter.java:35) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at
Re: Trinidad 1.2.13: another upgrade problem: UINodePropertyKey unserializable
hi,
https://issues.apache.org/jira/browse/TRINIDAD-1245
introduced some improvements in the direction of not sticking illegal
stuff into the session.
(during that we also introduced those error messages:
* !-- UNSERIALIZABLE_PROPERTY_VALUE_NO_CONTAINER --
resource key=UNSERIALIZABLE_PROPERTY_VALUE_NO_CONTAINER
dnt=falseNicht serialisierbarer Wert: {0} für Schlüssel:
{1}/resource
* !-- COMPONENT_CHILDREN_SAVED_STATE_FAILED --
resource key=COMPONENT_CHILDREN_SAVED_STATE_FAILED
dnt=falseStatus für untergeordnete Komponenten von Komponente: {0}
konnte nicht gespeichert werden/resource
)
can you double check for the parameters ?
On Wed, Apr 7, 2010 at 4:01 PM, wolfgang.toep...@pta.de wrote:
Hi,
Yet another problem here when trying to upgrade to 1.2.13:
Certain tr:commandLink within a Trinidad table that are supposed to lead
to Trinidad popup dialog show the dialog but the application crashes
shortly thereafter with the
log you can see attached below.
In 1.2.9 this used to work perfectly!
If this reminds anyone of any particular changes to 1.2.13, please do not
hesitate to drop a brief hint.
We are at a loss here!
Best wishes,
Wolfgang
14:51:18,780 ERROR [PropertyKey] Nicht serialisierbarer Wert:
sortablemodel[javax.faces.model.listdatamo...@5e63b2] für Schlüssel:
UINodePropertyKey[value,11]
14:51:18,832 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente:
coretable[org.apache.myfaces.trinidad.component.uixtable$rowkeyfacesbeanwrap...@d20d2a,
id=table] konnte nicht gespeichert werden
14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: HtmlRowLayout[UIXFacesBeanImpl, id=j_id36]
konnte nicht gespeichert werden
14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: CoreSubform[UINodeFacesBean,
id=dataAreaDlgForm] konnte nicht gespeichert werden
14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: CoreShowDetailItem[UINodeFacesBean,
id=dataAreaDlgId] konnte nicht gespeichert werden
14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: CorePanelAccordion[UIXFacesBeanImpl,
id=mainPanelDlgAccordion] konnte nicht gespeichert werden
14:51:18,842 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: CoreForm[UIXFacesBeanImpl, id=MainFormDlg]
konnte nicht gespeichert werden
14:51:18,842 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: HtmlBody[UIXFacesBeanImpl, id=j_id5] konnte
nicht gespeichert werden
14:51:18,842 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: HtmlHtml[UIXFacesBeanImpl, id=j_id0] konnte
nicht gespeichert werden
14:51:18,842 ERROR [viewhandler] Error Rendering
View[/popup-overview-dialog.xhtml]
java.lang.IllegalStateException: JDK Log (ws. Trinidad) erzeugt!
at
de.pta.ctrl.TrinidadLoggingRedirector$JDKLogHandler.init$_aroundBody2(TrinidadLoggingRedirector.java:172)
at
de.pta.ctrl.TrinidadLoggingRedirector$JDKLogHandler$AjcClosure3.run(TrinidadLoggingRedirector.java:1)
at
de.pta.aspect.ExceptionTracker.ajc$around$de_pta_aspect_ExceptionTracker$1$29c98745proceed(ExceptionTracker.aj:1)
at
de.pta.aspect.ExceptionTracker.ajc$around$de_pta_aspect_ExceptionTracker$1$29c98745(ExceptionTracker.aj:20)
at
de.pta.ctrl.TrinidadLoggingRedirector$JDKLogHandler.publish(TrinidadLoggingRedirector.java:172)
at java.util.logging.Logger.log(Logger.java:452)
at
org.apache.myfaces.trinidad.logging.TrinidadLogger.doLog(TrinidadLogger.java:1540)
at
org.apache.myfaces.trinidad.logging.TrinidadLogger.log(TrinidadLogger.java:336)
at
org.apache.myfaces.trinidad.logging.TrinidadLogger.warning(TrinidadLogger.java:807)
at
org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:905)
at
javax.faces.component.UIComponentBase.processSaveState(UIComponentBase.java:1119)
at
com.sun.faces.application.StateManagerImpl.saveSerializedView(StateManagerImpl.java:251)
at
org.jboss.seam.jsf.SeamStateManager.saveSerializedView(SeamStateManager.java:64)
at
org.apache.myfaces.trinidadinternal.application.StateManagerImpl.saveSerializedView(StateManagerImpl.java:165)
at
com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:615)
at
javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
at
org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193)
at
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
at
Antwort: Re: Trinidad 1.2.13: another upgrade problem: UINodePropertyKey unserializable
Hi,
Thanks again for the info.
I will try to find out more by setting CHECK_STATE_SERIALIZATION which in
this case, as far as I understood, should
be the right approach, should not it?
The problem seems to be with the SortableModel object and the applied
UINodePropertyKey.
Best wishes
Wolfgang
Matthias Wessendorf mat...@apache.org
Gesendet von: mwessend...@gmail.com
07.04.2010 17:09
Bitte antworten an
MyFaces Discussion users@myfaces.apache.org
An
MyFaces Discussion users@myfaces.apache.org
Kopie
Thema
Re: Trinidad 1.2.13: another upgrade problem: UINodePropertyKey
unserializable
hi,
https://issues.apache.org/jira/browse/TRINIDAD-1245
introduced some improvements in the direction of not sticking illegal
stuff into the session.
(during that we also introduced those error messages:
* !-- UNSERIALIZABLE_PROPERTY_VALUE_NO_CONTAINER --
resource key=UNSERIALIZABLE_PROPERTY_VALUE_NO_CONTAINER
dnt=falseNicht serialisierbarer Wert: {0} für Schlüssel:
{1}/resource
* !-- COMPONENT_CHILDREN_SAVED_STATE_FAILED --
resource key=COMPONENT_CHILDREN_SAVED_STATE_FAILED
dnt=falseStatus für untergeordnete Komponenten von Komponente: {0}
konnte nicht gespeichert werden/resource
)
can you double check for the parameters ?
On Wed, Apr 7, 2010 at 4:01 PM, wolfgang.toep...@pta.de wrote:
Hi,
Yet another problem here when trying to upgrade to 1.2.13:
Certain tr:commandLink within a Trinidad table that are supposed to
lead
to Trinidad popup dialog show the dialog but the application crashes
shortly thereafter with the
log you can see attached below.
In 1.2.9 this used to work perfectly!
If this reminds anyone of any particular changes to 1.2.13, please do
not
hesitate to drop a brief hint.
We are at a loss here!
Best wishes,
Wolfgang
14:51:18,780 ERROR [PropertyKey] Nicht serialisierbarer Wert:
sortablemodel[javax.faces.model.listdatamo...@5e63b2] für Schlüssel:
UINodePropertyKey[value,11]
14:51:18,832 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente:
coretable[org.apache.myfaces.trinidad.component.uixtable$rowkeyfacesbeanwrap...@d20d2a,
id=table] konnte nicht gespeichert werden
14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: HtmlRowLayout[UIXFacesBeanImpl, id=j_id36]
konnte nicht gespeichert werden
14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: CoreSubform[UINodeFacesBean,
id=dataAreaDlgForm] konnte nicht gespeichert werden
14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: CoreShowDetailItem[UINodeFacesBean,
id=dataAreaDlgId] konnte nicht gespeichert werden
14:51:18,841 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: CorePanelAccordion[UIXFacesBeanImpl,
id=mainPanelDlgAccordion] konnte nicht gespeichert werden
14:51:18,842 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: CoreForm[UIXFacesBeanImpl, id=MainFormDlg]
konnte nicht gespeichert werden
14:51:18,842 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: HtmlBody[UIXFacesBeanImpl, id=j_id5] konnte
nicht gespeichert werden
14:51:18,842 ERROR [UIXComponentBase] Status für untergeordnete
Komponenten von Komponente: HtmlHtml[UIXFacesBeanImpl, id=j_id0] konnte
nicht gespeichert werden
14:51:18,842 ERROR [viewhandler] Error Rendering
View[/popup-overview-dialog.xhtml]
java.lang.IllegalStateException: JDK Log (ws. Trinidad) erzeugt!
at
de.pta.ctrl.TrinidadLoggingRedirector$JDKLogHandler.init$_aroundBody2(TrinidadLoggingRedirector.java:172)
at
de.pta.ctrl.TrinidadLoggingRedirector$JDKLogHandler$AjcClosure3.run(TrinidadLoggingRedirector.java:1)
at
de.pta.aspect.ExceptionTracker.ajc$around$de_pta_aspect_ExceptionTracker$1$29c98745proceed(ExceptionTracker.aj:1)
at
de.pta.aspect.ExceptionTracker.ajc$around$de_pta_aspect_ExceptionTracker$1$29c98745(ExceptionTracker.aj:20)
at
de.pta.ctrl.TrinidadLoggingRedirector$JDKLogHandler.publish(TrinidadLoggingRedirector.java:172)
at java.util.logging.Logger.log(Logger.java:452)
at
org.apache.myfaces.trinidad.logging.TrinidadLogger.doLog(TrinidadLogger.java:1540)
at
org.apache.myfaces.trinidad.logging.TrinidadLogger.log(TrinidadLogger.java:336)
at
org.apache.myfaces.trinidad.logging.TrinidadLogger.warning(TrinidadLogger.java:807)
at
org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:905)
at
javax.faces.component.UIComponentBase.processSaveState(UIComponentBase.java:1119)
at
com.sun.faces.application.StateManagerImpl.saveSerializedView(StateManagerImpl.java:251)
at
org.jboss.seam.jsf.SeamStateManager.saveSerializedView(SeamStateManager.java:64)
at
org.apache.myfaces.trinidadinternal.application.StateManagerImpl.saveSerializedView(StateManagerImpl.java:165)
at
Re: javascript error jsf is not defined
Actually afaik you still need a faces-config, but in many cases it can be left blank or you just have a few lines of xml because you wont have too many artifacts anymore which still need xml registration. Most of the day to day stuff is now annotations. But there are exceptions, which is a little bit annoying. Werner Am 07.04.10 13:56, schrieb Matthias Leis: You are right about the view handler. I forgot that JSF2 doesn't need afaces-config anymore. But I need it anyway for registering a phase listener. Anyway, if I remove the view handler from the faces-config, all I get from my webapp is a blank page and no errors. Do I have to define a view-handler if I use a faces-config file or does JSF just use the dafault view handler? Original-Nachricht Datum: Wed, 07 Apr 2010 08:54:02 +0200 Von: Werner Punzwerner.p...@gmail.com An: users@myfaces.apache.org Betreff: Re: javascript error jsf is not defined Am 07.04.10 08:14, schrieb Matthias Leis: Hi Jakob, I guess I use the built-in facelets. At least this is the code from faces-config: view-handler com.sun.facelets.FaceletViewHandler /view-handler Wrong view handler... the jsf2 one is not under com.sun, but under javax.faces.view.facelets and it is initialized automatically if you use myfaces and the jsf2 facelets (no further configuration is needed) Com sun is the old Facelet 1.x stuff and the new tags cannot work under it due to the extensions in the jsf2 lifecycle and view handler api. So it is either old facelets or the jsf2 one but not a mix of both, sort of a hard break introduced by the namespace change from com.sun into javax.facelets and due to the api changes, but better once a hard break from old habits than having endless pain :-) Basically if you run in a pure jsf2 environment you can start to use facelets without additional configuration on the faces-config side. Werner
RE: [TRINIDAD] Family and component type for SelectRangeChoiceRenderer
Carsten, I am working on a similar problem, can you please post your xml addition to the faces-config.xml that get the renderer to see you renderKit? Thanks, Keith Carsten Pieper wrote: If anyone is interested, here's the solution to the problem. I did exactly what Harald advised (writing our own TableRenderer whose inner private class NavBar extends MySelectRangeChoiceRenderer). But as TableRenderer is an abstract class I also had to write our own version of the DesktopTableRenderer which now extends our TableRenderer. In our CoreRenderKit's constructor the only thing I had to add is this addRenderer(org.apache.myfaces.trinidad.Table, org.apache.myfaces.trinidad.Table, new DesktopTableRenderer()); Note that there's no need to add a renderer for our SelectRangeChoiceRenderer (i.e. MySelectRangeChoiceRenderer). The reason for this most probably is, that it's not a real component but more of a sub-component of the table... Cheers, Carsten Carsten Pieper wrote: Harald wrote: I.e. the renderer org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.TableRenderer has a static private class NavBar extends SelectRangeChoiceBarRenderer That's a very good hint. So probably I'm just writing our own TableRenderer and put our stuff directly into the private NavBar class. -- View this message in context: http://old.nabble.com/-TRINIDAD--Family-and-component-type-for-SelectRangeChoiceRenderer-tp26498105p28167772.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Facing error after Richfaces upgarde.
The id is for your richfaces component.
My suggestion would be to either try downgrading richfaces or
upgrading ONLY richfaces and nothing else to determine if it's only
caused by richfaces.
On Mon, Apr 5, 2010 at 8:29 AM, nilakandan.v...@cognizant.com wrote:
All,
I'm getting the following exception when I try to access my
application.
I have recently updated the following components in my application
weblogic8.1 to weblogic 10.3
myfaces 1.1.5 to 1.2.8
richfaces 3.0.1 to 3.3.2
tomahawk 1.1.5 to 12_1.1.10
Struts tiles to tiles 2.0.7
Exception while calling encodeEnd on component : {Component-Path :
[Class: org.ajax4jsf.component.AjaxViewRoot,ViewId:
/webContent/jsp/searchManager/search/searchManagerMain.jsp][Class:
org.apache.myfaces.custom.document.Document,Id: j_id_id1][Class:
org.apache.myfaces.custom.document.DocumentBody,Id: j_id_id9][Class:
javax.faces.component.html.HtmlForm,Id: searchManagerForm][Class:
org.apache.myfaces.custom.div.Div,Id: div_searchContainer][Class:
org.apache.myfaces.custom.div.Div,Id: j_id_id15][Class:
javax.faces.component.UINamingContainer,Id: subView_searchj_id_1][Class:
org.apache.myfaces.component.html.ext.HtmlPanelGrid,Id: j_id_id2pc2]}
Caused by:
javax.faces.FacesException - Component for target tSuggest not found in
SuggestionBox tSuggestBoxpc1
PFB, the sample code I used in my app.
t:popup id=tooltipT
style=#{(uiQSP.quickSearchListController.selectedT==null||uiQSP.quickSe
archListController.selectedT=='')?null:'border:1px solid
#00;bgcolor:#FF;width:100px;background-color:#ff'}
closePopupOnExitingElement=true
closePopupOnExitingPopup=true
displayAtDistanceX=10 displayAtDistanceY=10
rendered=true
a4j:region id=tRegion
t:inputTextHelp
value=#{uiQSP.quickSearchListController.selectedTA} id=tSuggest
size=40 maxlength=255
/t:inputTextHelp
rich:suggestionbox id=tSuggestBox for=tSuggest
style =font-size:12px tokens= frequency=0 selfRendered=true
ignoreDupResponses=true
rules=#{uiQSP.rules}
suggestionAction=#{uiQSP.autocompleteT}
var=result
fetchValue=#{result.tName}
first=#{uiQSP.intFirst}
minChars=#{uiQSP.minchars}
shadowOpacity=#{uiQSP.shadowOpacity}
border=#{uiQSP.border} width=#{uiQSP.width}
height=#{uiQSP.height}
shadowDepth=#{uiQSP.shadowDepth}
cellpadding=#{uiQSP.cellpadding}
h:column
h:outputText value=#{result.tName} /
/h:column
a4j:support event=onselect
action=#{uiQSP.getXXX}
reRender=tooltipT,tx,ty,qname,qc,qmdc/a4j:support
/rich:suggestionbox
/a4j:region
f:facet name=popup
t:div
rendered=#{!(uiQSP.quickSearchListController.selectedT==null||uiQSP.qui
ckSearchListController.selectedT=='')}
t:panelGrid columns=2
t:outputText value=T:
style=font-weight: bold; font-size:
10; /
t:outputText
value=#{uiQSP.quickSearchListController.selectedT}
style=font-size:10; white-space: nowrap; /
/t:panelGrid
/t:div
/f:facet
/t:popup
Please let me know what will be the root cause of this issue.
Thanks Regards,
Nila
This e-mail and any files transmitted with it are for the sole use of the
intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply
e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding, printing
or copying of this email or any action taken in reliance on this e-mail is
strictly prohibited and may be unlawful.
