Re: [ANNOUNCE] MyFaces Core v2.0.0-alpha Release
Matthias: i have an another topic. Why Tomahawk, Tobago and Trinidad are not merge in one project? 2009/12/10 Matthias Wessendorf : > Thanks for using myfaces since 2006. I am sure you will like the 2.0 version. > If you don't like the process of developement, here is a tip: > This is open source which means you are actually able to make a change here! > > Greetings! > Matthias > > 2009/12/10 周恩 : >> >> As a jsf fans and a java programmer since 1999, I think jsf implements >> provided by apache is disordered and poor maintained!!! lack of plan, >> stability, continuity and stability!!! Mybe something is good in this >> version, but you can find nothing in next version!The project team >> especially the manager is irresponsible!!! >> >> >> >> I use myfaces 1.1.1 from 2006(in a product), but I am looking for another >> jsf implement now(btw, which one is better?), the feeling is not so good. >> >> >> >> Sorry for my poor english and my angry. >> >> >> >>> > Date: Tue, 1 Dec 2009 09:46:51 +0800 >>> > Subject: Re: [ANNOUNCE] MyFaces Core v2.0.0-alpha Release >>> > From: dait...@gmail.com >>> > To: users@myfaces.apache.org >>> > >>> > Hi, >>> > >>> > Just want to know if MyFaces Core 2.0.0 has passed the TCK? If not , is >>> > there any plan for it? >>> > >>> > Thanks! >>> > >>> > 2009/12/1 Leonardo Uribe >>> > >>> > > The Apache MyFaces team is pleased to announce the release of MyFaces >>> > > Core >>> > > 2.0.0-alpha. >>> > > >>> > > MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified >>> > > by >>> > > JSR-314. >>> > > >>> > > MyFaces Core 2.0.0-alpha is available in both binary and source >>> > > distributions. >>> > > >>> > > * http://myfaces.apache.org/download.html >>> > > >>> > > MyFaces Core is also available in the central Maven repository under >>> > > Group >>> > > ID "org.apache.myfaces.core". >>> > > >>> > > Release Notes - MyFaces Core - Version 2.0.0-alpha >>> > > >>> > > Sub-task >>> > > >>> > > * [MYFACES-2174] - MyFaces 2.0 AJAX API extension proposal >>> > > * [MYFACES-2191] - Move the myfaces params into the context >>> > > * [MYFACES-2195] - rename xhrcore_xxx to xhrcore._xxx >>> > > * [MYFACES-2200] - Send events and errors at the various xhr stages >>> > > * [MYFACES-2223] - switch viewstate replacement from id to name >>> > > * [MYFACES-2238] - offer extension point for AJAX Javascript >>> > > * [MYFACES-2240] - typo in javascript build script and target folder >>> > > doesn't fit the spec >>> > > * [MYFACES-2257] - trigger external scripts after AJAX reload >>> > > * [MYFACES-2311] - Implement tag handler >>> > > * [MYFACES-2312] - Implement tag handler >>> > > * [MYFACES-2313] - Implement tag handler >>> > > * [MYFACES-2314] - Implement tag handler >>> > > * [MYFACES-2315] - Implement tag handler >>> > > * [MYFACES-2316] - Implement tag handler >>> > > * [MYFACES-2317] - Implement tag handler >>> > > * [MYFACES-2318] - Implement tag handler >>> > > * [MYFACES-2319] - Implement tag handler >>> > > * [MYFACES-2320] - Implement tag handler >>> > > * [MYFACES-2324] - Add ViewDeclarationLanguage.retargetAttachedObjects >>> > > and ViewDeclarationLanguage.retargetMethodExpressions >>> > > * [MYFACES-2325] - Add Composite Renderer class >>> > > * [MYFACES-2331] - Implement Composite Component Attributes ELResolver >>> > > (jsf 2.0 spec section 5.6.2.2) and add implicit object "cc" and >>> > > "component" >>> > > * [MYFACES-2362] - Move default validator registration from >>> > > UIInput.validateValue to ComponentTagHandlerDelegate >>> > > >>> > > Bug >>> > > >>> > > * [MYFACES-2083] - FacesContext contains several unnecessary methods >>> > > * [MYFACES-2131] - Import to internal Sun class >>> > > * [MYFACES-2146] - Bug in UIViewRoot causes Exception in >>> > > popComponentFromEL() >>> > > * [MYFACES-2147] - NoSuchMethodException when instantiating SystemEvent >>> > > objects >>> > > * [MYFACES-2287] - getting the myfaces 1.2 simple example app running on >>> > > 2.0 impl >>> > > * [MYFACES-2296] - Annotation scanning bugs >>> > > * [MYFACES-2357] - currency validation does not fall through to the >>> > > default JVM local when a default locale is not specified in faces-config >>> > > * [MYFACES-2358] - System event system not working >>> > > * [MYFACES-2359] - ComponentSystemEvents are not globally dispatched >>> > > * [MYFACES-2360] - Facelets JSTL escapeXML function not escaping '>' >>> > > * [MYFACES-2381] - Broken link: "Core JSF-2.0" >>> > > * [MYFACES-2384] - @FacesBehavior not handled correctly >>> > > * [MYFACES-2386] - Refactor Bean Validation "constants" to >>> > > package-private class >>> > > * [MYFACES-2387] - component state not being restored when >>> > > ValueChangeListener is attached >>> > > * [MYFACES-2390] - h:graphic image doesn't handle library attribue >>> > > * [MYFACES-2391] - classpath resources not checking for valid version >>> > > pattern >>> > > * [MYFACES-2393] - graphicImage tag does not handle resource EL >>> > > expr
RE: 100% CPU Usage and blocking concurrent Threads when using t:saveState
For me, this clearly looks like concurrent usage of the request map.
All the servlet scopes (session, request, …) are not thread safe and one has
to assure that they are not accessed at the same time by multiple threads.
This turns out to be hard as e.g. there is no "standard" how to synchronize
against the session map. As a side note: I often wonder why this does not
lead to much more problems in the wild …
Anyway, in your case it seems the internal datastructure of the request map
is damaged - which in fact is strange as I do not know when the request map
will be accessed by multiple threads.
Sorry that this is not a solution, but it should give you a clue where to
look next …
Ciao,
Mario
Von: Jan Baudisch [mailto:jan.baudi...@gmx.net]
Gesendet: Donnerstag, 10. Dezember 2009 08:02
An: MyFaces Discussion
Betreff: 100% CPU Usage and blocking concurrent Threads when using
t:saveState
Hello MyFaces Community,
we are using MyFaces 1.2.0 with Tomahawk Sandbox 1.1.5 and have the
problem, that once in a while we get 100% CPU Usage and blocking concurrent
threads because of using t:saveState
A thread dump shows that the threads always stops at
at java.util.TreeMap.put(TreeMap.java:545)
at
org.apache.myfaces.custom.redirectTracker.RedirectTrackerManager.addSaveStat
eBean(RedirectTrackerManager.java:306)
at
org.apache.myfaces.custom.redirectTracker.RedirectTrackerVariableResolver.re
solveVariable(RedirectTrackerVariableResolver.java:50)
(The complete thread dump is attached). The problem shows up on one system
with heavy concurrent usage and JxBrowser as client.
After we kill these threads using Lambda Probe, the CPU Usage normalizes.
The problem occurs in that method:
...
public void addSaveStateBean(String expressionString, Object value)
{
if(log.isDebugEnabled())
log.debug("addSaveStateBean: " + expressionString + " value=" +
value);
requestBeanMap.put(expressionString, value);
}
...
private final Map requestBeanMap = new TreeMap(); ...
As the problem is really severe for us, any hints are highly appreciated.
Many thanks in advance,
-- Jan
smime.p7s
Description: S/MIME cryptographic signature
Re: [ANNOUNCE] MyFaces Core v2.0.0-alpha Release
Thanks for using myfaces since 2006. I am sure you will like the 2.0 version. If you don't like the process of developement, here is a tip: This is open source which means you are actually able to make a change here! Greetings! Matthias 2009/12/10 周恩 : > > As a jsf fans and a java programmer since 1999, I think jsf implements > provided by apache is disordered and poor maintained!!! lack of plan, > stability, continuity and stability!!! Mybe something is good in this > version, but you can find nothing in next version!The project team especially > the manager is irresponsible!!! > > > > I use myfaces 1.1.1 from 2006(in a product), but I am looking for another jsf > implement now(btw, which one is better?), the feeling is not so good. > > > > Sorry for my poor english and my angry. > > > >> > Date: Tue, 1 Dec 2009 09:46:51 +0800 >> > Subject: Re: [ANNOUNCE] MyFaces Core v2.0.0-alpha Release >> > From: dait...@gmail.com >> > To: users@myfaces.apache.org >> > >> > Hi, >> > >> > Just want to know if MyFaces Core 2.0.0 has passed the TCK? If not , is >> > there any plan for it? >> > >> > Thanks! >> > >> > 2009/12/1 Leonardo Uribe >> > >> > > The Apache MyFaces team is pleased to announce the release of MyFaces >> > > Core >> > > 2.0.0-alpha. >> > > >> > > MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified by >> > > JSR-314. >> > > >> > > MyFaces Core 2.0.0-alpha is available in both binary and source >> > > distributions. >> > > >> > > * http://myfaces.apache.org/download.html >> > > >> > > MyFaces Core is also available in the central Maven repository under >> > > Group >> > > ID "org.apache.myfaces.core". >> > > >> > > Release Notes - MyFaces Core - Version 2.0.0-alpha >> > > >> > > Sub-task >> > > >> > > * [MYFACES-2174] - MyFaces 2.0 AJAX API extension proposal >> > > * [MYFACES-2191] - Move the myfaces params into the context >> > > * [MYFACES-2195] - rename xhrcore_xxx to xhrcore._xxx >> > > * [MYFACES-2200] - Send events and errors at the various xhr stages >> > > * [MYFACES-2223] - switch viewstate replacement from id to name >> > > * [MYFACES-2238] - offer extension point for AJAX Javascript >> > > * [MYFACES-2240] - typo in javascript build script and target folder >> > > doesn't fit the spec >> > > * [MYFACES-2257] - trigger external scripts after AJAX reload >> > > * [MYFACES-2311] - Implement tag handler >> > > * [MYFACES-2312] - Implement tag handler >> > > * [MYFACES-2313] - Implement tag handler >> > > * [MYFACES-2314] - Implement tag handler >> > > * [MYFACES-2315] - Implement tag handler >> > > * [MYFACES-2316] - Implement tag handler >> > > * [MYFACES-2317] - Implement tag handler >> > > * [MYFACES-2318] - Implement tag handler >> > > * [MYFACES-2319] - Implement tag handler >> > > * [MYFACES-2320] - Implement tag handler >> > > * [MYFACES-2324] - Add ViewDeclarationLanguage.retargetAttachedObjects >> > > and ViewDeclarationLanguage.retargetMethodExpressions >> > > * [MYFACES-2325] - Add Composite Renderer class >> > > * [MYFACES-2331] - Implement Composite Component Attributes ELResolver >> > > (jsf 2.0 spec section 5.6.2.2) and add implicit object "cc" and >> > > "component" >> > > * [MYFACES-2362] - Move default validator registration from >> > > UIInput.validateValue to ComponentTagHandlerDelegate >> > > >> > > Bug >> > > >> > > * [MYFACES-2083] - FacesContext contains several unnecessary methods >> > > * [MYFACES-2131] - Import to internal Sun class >> > > * [MYFACES-2146] - Bug in UIViewRoot causes Exception in >> > > popComponentFromEL() >> > > * [MYFACES-2147] - NoSuchMethodException when instantiating SystemEvent >> > > objects >> > > * [MYFACES-2287] - getting the myfaces 1.2 simple example app running on >> > > 2.0 impl >> > > * [MYFACES-2296] - Annotation scanning bugs >> > > * [MYFACES-2357] - currency validation does not fall through to the >> > > default JVM local when a default locale is not specified in faces-config >> > > * [MYFACES-2358] - System event system not working >> > > * [MYFACES-2359] - ComponentSystemEvents are not globally dispatched >> > > * [MYFACES-2360] - Facelets JSTL escapeXML function not escaping '>' >> > > * [MYFACES-2381] - Broken link: "Core JSF-2.0" >> > > * [MYFACES-2384] - @FacesBehavior not handled correctly >> > > * [MYFACES-2386] - Refactor Bean Validation "constants" to >> > > package-private class >> > > * [MYFACES-2387] - component state not being restored when >> > > ValueChangeListener is attached >> > > * [MYFACES-2390] - h:graphic image doesn't handle library attribue >> > > * [MYFACES-2391] - classpath resources not checking for valid version >> > > pattern >> > > * [MYFACES-2393] - graphicImage tag does not handle resource EL >> > > expressions properly >> > > * [MYFACES-2394] - ResourceDependency annotations not being handled >> > > properly if target attribute is set >> > > * [MYFACES-2397] - f:ajax attributes execute and render should take space >> > > delimited clientIds >> > > * [MYFACES-239
RE: [ANNOUNCE] MyFaces Core v2.0.0-alpha Release
As a jsf fans and a java programmer since 1999, I think jsf implements provided by apache is disordered and poor maintained!!! lack of plan, stability, continuity and stability!!! Mybe something is good in this version, but you can find nothing in next version!The project team especially the manager is irresponsible!!! I use myfaces 1.1.1 from 2006(in a product), but I am looking for another jsf implement now(btw, which one is better?), the feeling is not so good. Sorry for my poor english and my angry. > > Date: Tue, 1 Dec 2009 09:46:51 +0800 > > Subject: Re: [ANNOUNCE] MyFaces Core v2.0.0-alpha Release > > From: dait...@gmail.com > > To: users@myfaces.apache.org > > > > Hi, > > > > Just want to know if MyFaces Core 2.0.0 has passed the TCK? If not , is > > there any plan for it? > > > > Thanks! > > > > 2009/12/1 Leonardo Uribe > > > > > The Apache MyFaces team is pleased to announce the release of MyFaces Core > > > 2.0.0-alpha. > > > > > > MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified by > > > JSR-314. > > > > > > MyFaces Core 2.0.0-alpha is available in both binary and source > > > distributions. > > > > > > * http://myfaces.apache.org/download.html > > > > > > MyFaces Core is also available in the central Maven repository under Group > > > ID "org.apache.myfaces.core". > > > > > > Release Notes - MyFaces Core - Version 2.0.0-alpha > > > > > > Sub-task > > > > > > * [MYFACES-2174] - MyFaces 2.0 AJAX API extension proposal > > > * [MYFACES-2191] - Move the myfaces params into the context > > > * [MYFACES-2195] - rename xhrcore_xxx to xhrcore._xxx > > > * [MYFACES-2200] - Send events and errors at the various xhr stages > > > * [MYFACES-2223] - switch viewstate replacement from id to name > > > * [MYFACES-2238] - offer extension point for AJAX Javascript > > > * [MYFACES-2240] - typo in javascript build script and target folder > > > doesn't fit the spec > > > * [MYFACES-2257] - trigger external scripts after AJAX reload > > > * [MYFACES-2311] - Implement tag handler > > > * [MYFACES-2312] - Implement tag handler > > > * [MYFACES-2313] - Implement tag handler > > > * [MYFACES-2314] - Implement tag handler > > > * [MYFACES-2315] - Implement tag handler > > > * [MYFACES-2316] - Implement tag handler > > > * [MYFACES-2317] - Implement tag handler > > > * [MYFACES-2318] - Implement tag handler > > > * [MYFACES-2319] - Implement tag handler > > > * [MYFACES-2320] - Implement tag handler > > > * [MYFACES-2324] - Add ViewDeclarationLanguage.retargetAttachedObjects > > > and ViewDeclarationLanguage.retargetMethodExpressions > > > * [MYFACES-2325] - Add Composite Renderer class > > > * [MYFACES-2331] - Implement Composite Component Attributes ELResolver > > > (jsf 2.0 spec section 5.6.2.2) and add implicit object "cc" and > > > "component" > > > * [MYFACES-2362] - Move default validator registration from > > > UIInput.validateValue to ComponentTagHandlerDelegate > > > > > > Bug > > > > > > * [MYFACES-2083] - FacesContext contains several unnecessary methods > > > * [MYFACES-2131] - Import to internal Sun class > > > * [MYFACES-2146] - Bug in UIViewRoot causes Exception in > > > popComponentFromEL() > > > * [MYFACES-2147] - NoSuchMethodException when instantiating SystemEvent > > > objects > > > * [MYFACES-2287] - getting the myfaces 1.2 simple example app running on > > > 2.0 impl > > > * [MYFACES-2296] - Annotation scanning bugs > > > * [MYFACES-2357] - currency validation does not fall through to the > > > default JVM local when a default locale is not specified in faces-config > > > * [MYFACES-2358] - System event system not working > > > * [MYFACES-2359] - ComponentSystemEvents are not globally dispatched > > > * [MYFACES-2360] - Facelets JSTL escapeXML function not escaping '>' > > > * [MYFACES-2381] - Broken link: "Core JSF-2.0" > > > * [MYFACES-2384] - @FacesBehavior not handled correctly > > > * [MYFACES-2386] - Refactor Bean Validation "constants" to > > > package-private class > > > * [MYFACES-2387] - component state not being restored when > > > ValueChangeListener is attached > > > * [MYFACES-2390] - h:graphic image doesn't handle library attribue > > > * [MYFACES-2391] - classpath resources not checking for valid version > > > pattern > > > * [MYFACES-2393] - graphicImage tag does not handle resource EL > > > expressions properly > > > * [MYFACES-2394] - ResourceDependency annotations not being handled > > > properly if target attribute is set > > > * [MYFACES-2397] - f:ajax attributes execute and render should take space > > > delimited clientIds > > > * [MYFACES-2398] - no spaces in html-output of f:ajax with render and > > > execute attributes with more than one target > > > * [MYFACES-2402] - Fix conditional navigation > > > * [MYFACES-2404] - JspViewDeclarationLanguageStrategy is always the > > > default strategy, so it should always return true on handles() method > > > * [MYFACES-2405] - f:ajax renderer not handling multiple IDs prope
RE: [ANNOUNCE] MyFaces Core v2.0.0-alpha Release
As a jsf fans and a java programmer since 1999, I think jsf implements provided by apche is disordered and poor maintained!!! lack of plan, stability, continuity and stability!!! I use myfaces 1.1.1 from 2006(in a product), but I am looking for another jsf implement now, the feeling is not so good. Pardon me for my poor english. > Date: Tue, 1 Dec 2009 09:46:51 +0800 > Subject: Re: [ANNOUNCE] MyFaces Core v2.0.0-alpha Release > From: dait...@gmail.com > To: users@myfaces.apache.org > > Hi, > > Just want to know if MyFaces Core 2.0.0 has passed the TCK? If not , is > there any plan for it? > > Thanks! > > 2009/12/1 Leonardo Uribe > > > The Apache MyFaces team is pleased to announce the release of MyFaces Core > > 2.0.0-alpha. > > > > MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified by > > JSR-314. > > > > MyFaces Core 2.0.0-alpha is available in both binary and source > > distributions. > > > > * http://myfaces.apache.org/download.html > > > > MyFaces Core is also available in the central Maven repository under Group > > ID "org.apache.myfaces.core". > > > > Release Notes - MyFaces Core - Version 2.0.0-alpha > > > > Sub-task > > > > * [MYFACES-2174] - MyFaces 2.0 AJAX API extension proposal > > * [MYFACES-2191] - Move the myfaces params into the context > > * [MYFACES-2195] - rename xhrcore_xxx to xhrcore._xxx > > * [MYFACES-2200] - Send events and errors at the various xhr stages > > * [MYFACES-2223] - switch viewstate replacement from id to name > > * [MYFACES-2238] - offer extension point for AJAX Javascript > > * [MYFACES-2240] - typo in javascript build script and target folder > > doesn't fit the spec > > * [MYFACES-2257] - trigger external scripts after AJAX reload > > * [MYFACES-2311] - Implement tag handler > > * [MYFACES-2312] - Implement tag handler > > * [MYFACES-2313] - Implement tag handler > > * [MYFACES-2314] - Implement tag handler > > * [MYFACES-2315] - Implement tag handler > > * [MYFACES-2316] - Implement tag handler > > * [MYFACES-2317] - Implement tag handler > > * [MYFACES-2318] - Implement tag handler > > * [MYFACES-2319] - Implement tag handler > > * [MYFACES-2320] - Implement tag handler > > * [MYFACES-2324] - Add ViewDeclarationLanguage.retargetAttachedObjects > > and ViewDeclarationLanguage.retargetMethodExpressions > > * [MYFACES-2325] - Add Composite Renderer class > > * [MYFACES-2331] - Implement Composite Component Attributes ELResolver > > (jsf 2.0 spec section 5.6.2.2) and add implicit object "cc" and "component" > > * [MYFACES-2362] - Move default validator registration from > > UIInput.validateValue to ComponentTagHandlerDelegate > > > > Bug > > > > * [MYFACES-2083] - FacesContext contains several unnecessary methods > > * [MYFACES-2131] - Import to internal Sun class > > * [MYFACES-2146] - Bug in UIViewRoot causes Exception in > > popComponentFromEL() > > * [MYFACES-2147] - NoSuchMethodException when instantiating SystemEvent > > objects > > * [MYFACES-2287] - getting the myfaces 1.2 simple example app running on > > 2.0 impl > > * [MYFACES-2296] - Annotation scanning bugs > > * [MYFACES-2357] - currency validation does not fall through to the > > default JVM local when a default locale is not specified in faces-config > > * [MYFACES-2358] - System event system not working > > * [MYFACES-2359] - ComponentSystemEvents are not globally dispatched > > * [MYFACES-2360] - Facelets JSTL escapeXML function not escaping '>' > > * [MYFACES-2381] - Broken link: "Core JSF-2.0" > > * [MYFACES-2384] - @FacesBehavior not handled correctly > > * [MYFACES-2386] - Refactor Bean Validation "constants" to > > package-private class > > * [MYFACES-2387] - component state not being restored when > > ValueChangeListener is attached > > * [MYFACES-2390] - h:graphic image doesn't handle library attribue > > * [MYFACES-2391] - classpath resources not checking for valid version > > pattern > > * [MYFACES-2393] - graphicImage tag does not handle resource EL > > expressions properly > > * [MYFACES-2394] - ResourceDependency annotations not being handled > > properly if target attribute is set > > * [MYFACES-2397] - f:ajax attributes execute and render should take space > > delimited clientIds > > * [MYFACES-2398] - no spaces in html-output of f:ajax with render and > > execute attributes with more than one target > > * [MYFACES-2402] - Fix conditional navigation > > * [MYFACES-2404] - JspViewDeclarationLanguageStrategy is always the > > default strategy, so it should always return true on handles() method > > * [MYFACES-2405] - f:ajax renderer not handling multiple IDs properly > > * [MYFACES-2406] - Create a view with viewId is null should be possible > > * [MYFACES-2408] - UIComponent.subscribeToEvent and unsubscribeToEvent > > should throw NullPointerException when eventClass or componentListener is > > null > > * [MYFACES-2415] - EnumConverter should only conver to String valid enum > > values > > * [MYFACES-2416] - h:outputLabel does not han
Re: pop up for delete confirmation
Cagatay,
I'm really impressed with your PrimeFaces.
Luka Surija
On 12/09/2009 05:45 PM, Cagatay Civici wrote:
There's a special component for this in PrimeFaces called confirmDialog
integrated with command components.
http://97.107.138.40:8080/prime-showcase/ui/confirmDialog.jsf
That will work smoothly with Tomahawk.
On Wed, Dec 9, 2009 at 4:43 PM, Grant Smith wrote:
I use RichFace's ModelPanel for this...
On Wed, Dec 9, 2009 at 8:39 AM, wrote:
So that's the second person who is using the regular old javascript
confirm dialog. Doesn't it seem odd that there is no tomahawk popup
component? My leader seems to think that we shouldn't use this because
it
is ancient. I wish he could come up with a better excuse than that.
However, does anyone an idea for a better looking component?
Pat
Luka Surija
09/12/2009 01:01 PM
Please respond to
"MyFaces Discussion"
To
MyFaces Discussion
cc
Subject
Re: pop up for delete confirmation
onclick="return(confirm('#{msg.AreYouSure}'));"
Luka Surija
On 12/03/2009 12:02 PM, Anton Gavazuk wrote:
I'm using the basic javascript...
2009/11/30
I am using the Tomahawk set of tags for this project. I need a pop to
confirm the deletion of a record. There doesn't seem to be any
concept
of
a popup in JSF or Tomahawk. I can use a basic javascript cofirm popup
and
functionaly it works perfect but the color scheme doesn't match my
application and it doesn't look good. Just wondering what everyone
else
does to confirm a delete?
Pat
--
Grant Smith
Re: I'm having problems integrating myfaces 1.2.6 with SAP Java Server WebXMLParser
Hmm interresting. Generally the webapp mapping is in the default
namespace is it not? I don't know if J2EE is spec'd this way but most
webapp that I've seen are done this way.
I'm not a bit fan of using getLocalName in general becuase it can lead
to conflicts. That said, if someone defines a web-xml element in
thier schema, they should be shot. ;)
Write up a bug and submit a patch and maybe we can get it in.
Scott
Sent from my iPhone
On Dec 9, 2009, at 2:31 PM, wrote:
Hi,
I'm having problems integrating myfaces 1.2.6 with SAP Java
Server (Java 1.5)
The problem , I found was in the code for
org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser parse()
method.
the parse method does the following
InputSource is = createContextInputSource(null,
"/WEB-INF/web.xml");
if (is == null)
{
URL url = this._context.getResource("/WEB-INF/web.xml");
log.debug("No web-xml found at : " + ((url == null) ? "
null " : url.toString()));
return this._webXml;
}
Document document = db.parse(is);
Element webAppElem = document.getDocumentElement();
if ((webAppElem == null) ||
(!(webAppElem.getNodeName().equals("web-app"
throw new FacesException("No valid web-app root element
found!");
*
but the JDK 1.5 implementation is namespace aware so the return
of getNodeName is in our system ns1:web-app
I think the implementation should do getLocalName() instead of
getNodeName ...
Does anyone have a suggestion to how to get arround this... I'm
sure someone else has a system where the web.xml file has namespaces
in
it ...
Thank you and sorry if this question is not posted at the right
place... if so please redirect me to the right list.
Thanks again.
Thierry Dagnino
I'm having problems integrating myfaces 1.2.6 with SAP Java Server WebXMLParser
Hi,
I'm having problems integrating myfaces 1.2.6 with SAP Java
Server (Java 1.5)
The problem , I found was in the code for
org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser parse()
method.
the parse method does the following
InputSource is = createContextInputSource(null,
"/WEB-INF/web.xml");
if (is == null)
{
URL url = this._context.getResource("/WEB-INF/web.xml");
log.debug("No web-xml found at : " + ((url == null) ? "
null " : url.toString()));
return this._webXml;
}
Document document = db.parse(is);
Element webAppElem = document.getDocumentElement();
if ((webAppElem == null) ||
(!(webAppElem.getNodeName().equals("web-app"
throw new FacesException("No valid web-app root element
found!");
*
but the JDK 1.5 implementation is namespace aware so the return
of getNodeName is in our system ns1:web-app
I think the implementation should do getLocalName() instead of
getNodeName ...
Does anyone have a suggestion to how to get arround this... I'm
sure someone else has a system where the web.xml file has namespaces in
it ...
Thank you and sorry if this question is not posted at the right
place... if so please redirect me to the right list.
Thanks again.
Thierry Dagnino
Re: [TRINIDAD]Suppressing Validation during PartialPageRequest
Hi Ricardo, Did you try immediate = "true" in your selectOneChoice-dropdown? Thanks Mamallan Ricardo Rog wrote: Hello, I want to change the state of a navigationBar via partial page request in dependency of a value chosen in a selectOneChoice-dropdown. In the same form are some required-fields. Whenever I enter the form (all required fields are blank) and change the drop-down I get validation errors and the necessary change of the navigationBar is prohibited. How can I suppress the validation for this event only, so the navigationBar gets updated, but when I try to navigate then validation should happen. With kind regards Ricardo Rog
Re: pop up for delete confirmation
There's a special component for this in PrimeFaces called confirmDialog
integrated with command components.
http://97.107.138.40:8080/prime-showcase/ui/confirmDialog.jsf
That will work smoothly with Tomahawk.
On Wed, Dec 9, 2009 at 4:43 PM, Grant Smith wrote:
> I use RichFace's ModelPanel for this...
>
> On Wed, Dec 9, 2009 at 8:39 AM, wrote:
>
> > So that's the second person who is using the regular old javascript
> > confirm dialog. Doesn't it seem odd that there is no tomahawk popup
> > component? My leader seems to think that we shouldn't use this because
> it
> > is ancient. I wish he could come up with a better excuse than that.
> > However, does anyone an idea for a better looking component?
> >
> > Pat
> >
> >
> >
> >
> >
> > Luka Surija
> > 09/12/2009 01:01 PM
> > Please respond to
> > "MyFaces Discussion"
> >
> >
> > To
> > MyFaces Discussion
> > cc
> >
> > Subject
> > Re: pop up for delete confirmation
> >
> >
> >
> >
> >
> >
> > onclick="return(confirm('#{msg.AreYouSure}'));"
> >
> > Luka Surija
> >
> >
> >
> > On 12/03/2009 12:02 PM, Anton Gavazuk wrote:
> > > I'm using the basic javascript...
> > >
> > > 2009/11/30
> > >
> > >
> > >> I am using the Tomahawk set of tags for this project. I need a pop to
> > >> confirm the deletion of a record. There doesn't seem to be any
> concept
> > of
> > >> a popup in JSF or Tomahawk. I can use a basic javascript cofirm popup
> > and
> > >> functionaly it works perfect but the color scheme doesn't match my
> > >> application and it doesn't look good. Just wondering what everyone
> > else
> > >> does to confirm a delete?
> > >>
> > >> Pat
> > >>
> > >
> >
> >
>
>
> --
> Grant Smith
>
Re: pop up for delete confirmation
I use RichFace's ModelPanel for this...
On Wed, Dec 9, 2009 at 8:39 AM, wrote:
> So that's the second person who is using the regular old javascript
> confirm dialog. Doesn't it seem odd that there is no tomahawk popup
> component? My leader seems to think that we shouldn't use this because it
> is ancient. I wish he could come up with a better excuse than that.
> However, does anyone an idea for a better looking component?
>
> Pat
>
>
>
>
>
> Luka Surija
> 09/12/2009 01:01 PM
> Please respond to
> "MyFaces Discussion"
>
>
> To
> MyFaces Discussion
> cc
>
> Subject
> Re: pop up for delete confirmation
>
>
>
>
>
>
> onclick="return(confirm('#{msg.AreYouSure}'));"
>
> Luka Surija
>
>
>
> On 12/03/2009 12:02 PM, Anton Gavazuk wrote:
> > I'm using the basic javascript...
> >
> > 2009/11/30
> >
> >
> >> I am using the Tomahawk set of tags for this project. I need a pop to
> >> confirm the deletion of a record. There doesn't seem to be any concept
> of
> >> a popup in JSF or Tomahawk. I can use a basic javascript cofirm popup
> and
> >> functionaly it works perfect but the color scheme doesn't match my
> >> application and it doesn't look good. Just wondering what everyone
> else
> >> does to confirm a delete?
> >>
> >> Pat
> >>
> >
>
>
--
Grant Smith
Re: pop up for delete confirmation
even if it completely differs from your design it just does what is required
in simple way and you dont have to worry "how will it look/behave in Opera,
Chrome"
2009/12/9
> So that's the second person who is using the regular old javascript
> confirm dialog. Doesn't it seem odd that there is no tomahawk popup
> component? My leader seems to think that we shouldn't use this because it
> is ancient. I wish he could come up with a better excuse than that.
> However, does anyone an idea for a better looking component?
>
> Pat
>
>
>
>
>
> Luka Surija
> 09/12/2009 01:01 PM
> Please respond to
> "MyFaces Discussion"
>
>
> To
> MyFaces Discussion
> cc
>
> Subject
> Re: pop up for delete confirmation
>
>
>
>
>
>
> onclick="return(confirm('#{msg.AreYouSure}'));"
>
> Luka Surija
>
>
>
> On 12/03/2009 12:02 PM, Anton Gavazuk wrote:
> > I'm using the basic javascript...
> >
> > 2009/11/30
> >
> >
> >> I am using the Tomahawk set of tags for this project. I need a pop to
> >> confirm the deletion of a record. There doesn't seem to be any concept
> of
> >> a popup in JSF or Tomahawk. I can use a basic javascript cofirm popup
> and
> >> functionaly it works perfect but the color scheme doesn't match my
> >> application and it doesn't look good. Just wondering what everyone
> else
> >> does to confirm a delete?
> >>
> >> Pat
> >>
> >
>
>
AW: [TRINIDAD]Suppressing Validation during PartialPageRequest
Hello, should work if you put the drop-down in an own subform. e.g. Another solution could be to make the selectOneChoice autoSubmit="true" and immediate="true", just test what better fits your needs. Regards Markus -Ursprüngliche Nachricht- Von: Ricardo Rog [mailto:ricardo@softproject.de] Gesendet: Mittwoch, 9. Dezember 2009 15:36 An: users@myfaces.apache.org Betreff: [TRINIDAD]Suppressing Validation during PartialPageRequest Hello, I want to change the state of a navigationBar via partial page request in dependency of a value chosen in a selectOneChoice-dropdown. In the same form are some required-fields. Whenever I enter the form (all required fields are blank) and change the drop-down I get validation errors and the necessary change of the navigationBar is prohibited. How can I suppress the validation for this event only, so the navigationBar gets updated, but when I try to navigate then validation should happen. With kind regards Ricardo Rog
Re: pop up for delete confirmation
So that's the second person who is using the regular old javascript
confirm dialog. Doesn't it seem odd that there is no tomahawk popup
component? My leader seems to think that we shouldn't use this because it
is ancient. I wish he could come up with a better excuse than that.
However, does anyone an idea for a better looking component?
Pat
Luka Surija
09/12/2009 01:01 PM
Please respond to
"MyFaces Discussion"
To
MyFaces Discussion
cc
Subject
Re: pop up for delete confirmation
onclick="return(confirm('#{msg.AreYouSure}'));"
Luka Surija
On 12/03/2009 12:02 PM, Anton Gavazuk wrote:
> I'm using the basic javascript...
>
> 2009/11/30
>
>
>> I am using the Tomahawk set of tags for this project. I need a pop to
>> confirm the deletion of a record. There doesn't seem to be any concept
of
>> a popup in JSF or Tomahawk. I can use a basic javascript cofirm popup
and
>> functionaly it works perfect but the color scheme doesn't match my
>> application and it doesn't look good. Just wondering what everyone
else
>> does to confirm a delete?
>>
>> Pat
>>
>
Re: pop up for delete confirmation
onclick="return(confirm('#{msg.AreYouSure}'));"
Luka Surija
On 12/03/2009 12:02 PM, Anton Gavazuk wrote:
I'm using the basic javascript...
2009/11/30
I am using the Tomahawk set of tags for this project. I need a pop to
confirm the deletion of a record. There doesn't seem to be any concept of
a popup in JSF or Tomahawk. I can use a basic javascript cofirm popup and
functionaly it works perfect but the color scheme doesn't match my
application and it doesn't look good. Just wondering what everyone else
does to confirm a delete?
Pat
Why is t:selectOneRadio ignoring style, styleClass, and disabledClass?
Hi, I'm using MyFaces 1.1.6 with Tomahawk 1.1.9. I have this element on my page ... but sadly, what is rendered is below. Yes No I say "sadly" because notice that the style and class elements disappeared. Where did they go and how can I get them back? Thanks, - Dave -- View this message in context: http://old.nabble.com/Why-is-t%3AselectOneRadio-ignoring-style%2C-styleClass%2C-and-disabledClass--tp26711863p26711863.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: pages not rendered anymore after update from 1.1.6 to 1.2.8
I started this thread so I keep you up to date with my improvements of the migration. Some pages are now working basically with Tiles 2.0.5. 1) Migrated to Tiles2 according this guide: http://tiles.apache.org/migration/index.html 2) Renamed my tiles-definitions file to tiles.xml! Other names defined in the web.xml are not working. Unfortunately I had another name which cost me quite some hours. 3) I had to add commons-discovery-0.4.jar to the libs Not every project can migrate to Facelets easily. This means also some migration and QA effort. My project is under heavy development and started 4 years ago with Tiles. Facelets was a beta "0.1" at this time and it was not obvious at that it would become a standard. Sooner or later I will migrate to Facelets but right now this is no alternative. Michael -Original Message- From: Leonardo Uribe [mailto:lu4...@gmail.com] Sent: Mittwoch, 9. Dezember 2009 04:31 To: MyFaces Discussion Subject: Re: pages not rendered anymore after update from 1.1.6 to 1.2.8 Hi The example available here: http://svn.apache.org/repos/asf/myfaces/tomahawk/trunk/examples/tiles/ works with jsf 1.2 and tomahawk12-1.1.x (to execute it try mvn clean -Djsf=12 -Dtomahawk=12 jetty:run) Note that use jsf 1.2 and tomahawk-1.1.x does not work, because some changes in ViewHandler where added. I ignore if richfaces introduce some side effects (and that's the reason why does not work) but maybe this is the case. regards, Leonardo Uribe 2009/12/8 Richard Yee > I'd suggest using facelets instead of Tiles. Tiles was never designed > to work with JSF. Facelets provides similar templating capability and > was designed to improve on shortcomings of JSP and JSF. Facelets is > also part of JSF 2.0 > > -Richard > > > On Tue, Dec 8, 2009 at 8:24 AM, Michael Heinen > wrote: > > Thanks Richard, I tried this finally with a simple page in this project. > > > > TILES is the culprit. > > My simple page is now rendered with tomahawk tags > > after I removed context param > org.ajax4jsf.VIEW_HANDLERS=org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl > from web.xml. > > > > The content of is NOT rendered at all as soon as I add the above > context param for tiles again. > > Sample jsp: > > > > <%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h"%> > > <%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f"%> > > <%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t"%> > > > > hello > > world value="09"/> > > > > > > > > Output: hello > > The tag is not processed at all with Tiles. > > > > Does anybody know what to do with tiles and JSF 1.2 (myFaces 1.2.8, > tomahawk12_1.1.9 and richfaces 3.3.2)? > > Debugging all the frameworks together is really time consuming > > > > Michael > > > > > > -Original Message- > > From: Richard Yee [mailto:richard.k@gmail.com] > > Sent: Dienstag, 8. Dezember 2009 16:09 > > To: MyFaces Discussion > > Subject: Re: pages not rendered anymore after update from 1.1.6 to 1.2.8 > > > > Have you tried just having a page with a JSF outputText tag to see if > > that works? (No tiles or Richfaces) > > > > I would start from there and then add other tags to narrow down where > > the problem is. > > > > -R > > > > >
[TRINIDAD]Suppressing Validation during PartialPageRequest
Hello, I want to change the state of a navigationBar via partial page request in dependency of a value chosen in a selectOneChoice-dropdown. In the same form are some required-fields. Whenever I enter the form (all required fields are blank) and change the drop-down I get validation errors and the necessary change of the navigationBar is prohibited. How can I suppress the validation for this event only, so the navigationBar gets updated, but when I try to navigate then validation should happen. With kind regards Ricardo Rog
resolve "el-String" to facelets-function
Hi, i want to resolve an el-String that represents a facelets-function, so i want to invoke the corresponding method. How can i do this? Exampe: // method public static String computeSomething(String param); // faclets-configuration computeSomething package.MyClass My Environment: - jsf 1.1 - myfaces - facelets - trinidad (1.0.10) Some background information: I want to implement an "el-aware"-Weblet, that resolves el-expressions (facelets-functions only makes sense here). Weblets does this does this for weblet-functions (PackagedWeblet). I want to use some some Triniad-Skin-Selektors within my javascript. Can you give me some hints? Best regards Daniel -- View this message in context: http://old.nabble.com/resolve-%22el-String%22-to-facelets-function-tp26709395p26709395.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
orchestra & richfaces - multiple instances of beans are created in conversation scope
Hi I am trying to Use richfaces with orchestra... However I have a problem using the conversation scopes... When I load a jsf page for the first time not one but three instances of the backing bean (which is in the conversation scope) are created... Also I have a with a tag in it... when I change the value of the select box there another 3 instances of the bean are created... I checked the source of the html page and it seems that the conversationContext variable isn't passed to the server... In other components on the same page the conversationContext variable is present... I am using RichFaces 3.3.2 SR1 Orchstra 1.3.1 Spring 2.5.6 I found a mail where someone had a similar problem and it was suggsted it might be a configuration issue in the web.xml file.. Here is my web.xml file: Code: http://java.sun.com/xml/ns/javaee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd";> [removed] [removed] javax.faces.DEFAULT_SUFFIX .xhtml facelets.REFRESH_PERIOD 2 facelets.DEVELOPMENT true javax.faces.STATE_SAVING_METHOD client com.sun.faces.validateXml true com.sun.faces.verifyObjects true log4jConfigLocation /WEB-INF/classes/log4j.properties contextConfigLocation /WEB-INF/applicationContext-jpa.xml org.springframework.web.context.ContextLoaderListener org.springframework.web.context.request.RequestContextListener org.apache.myfaces.orchestra.conversation.servlet.ConversationManagerSessionListener org.richfaces.SKIN classic org.ajax4jsf.VIEW_HANDLERS com.sun.facelets.FaceletViewHandler RichFaces Filter richfaces org.ajax4jsf.Filter richfaces Faces Servlet REQUEST FORWARD INCLUDE Faces Servlet javax.faces.webapp.FacesServlet 1 Faces Servlet *.jsf BASIC
