Link within a tree2 without a submit?

[Lars Hagrot]

I am using the Tomahawk tree2 component and do not want any server requests 
when the user clicks on a node. Instead I want to call a javascript method. 
 
Is it possible to declare a commandLink that does not resultat in a form submit 
but a  
href="javascript:foo(param);" ? 
 
Currently I am using a very ugly solution with   the verbatim tag in 
combination with a -tag like 
 

); ">
  
 
 
Regards
Lars Hagrot

Re: [Trinidad] plugins build broken?

[Matthias Wessendorf]

I am not seeing this, but I saw it in the past.
Strange...

On 6/1/07, Adam Winer <[EMAIL PROTECTED]> wrote:

I've seen this before - it's a bug in qdox, apparently, but I
don't know how or why it goes away.

-- Adam



On 5/31/07, Laurie Harper <[EMAIL PROTECTED]> wrote:
> I just tried upgrading to the latest Maven and have the same error. For
> now, I've hacked my local poms to require 1.0.1-incubating-SNAPSHOT of
> this plugin as a work-around. I'll repost the build error to the dev
> list for further attention.
>
> L.
>
> Laurie Harper wrote:
> > I just tried checking out the current trunk from its new home and found
> > I can't build it :-( I get a failure building the plugins, which then
> > leads to a failure to build the 'trinidad' module.
> >
> > The failure is in the build for the Apache Trinidad Maven XRTS Plugin
> > and looks like either an issue with qdox or an issue with the plugin
> > code being processed by qdox.
> >
> > What do I need to do to get this working? I've tried 'mvn -cpu install'
> > with no improvement; am I using too old a version of Maven?
> >
> > L.
> >
> >
> > [EMAIL PROTECTED] java -version
> > java version "1.5.0_05"
> > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-83)
> > Java HotSpot(TM) Client VM (build 1.5.0_05-48, mixed mode, sharing)
> >
> > [EMAIL PROTECTED] mvn --version
> > Maven version: 2.0.4-maestro-1.0.1
> >
> > [EMAIL PROTECTED] svn info
> > Path: .
> > URL:
http://svn.apache.org/repos/asf/myfaces/trinidad/trunk/plugins
> > Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
> > Revision: 542764
> > Node Kind: directory
> > Schedule: normal
> > Last Changed Author: mmarinschek
> > Last Changed Rev: 538505
> > Last Changed Date: 2007-05-16 05:53:47 -0400 (Wed, 16 May 2007)
> > Properties Last Updated: 2007-05-30 02:14:05 -0400 (Wed, 30 May 2007)
> >
> > [EMAIL PROTECTED] pwd
> >
/Users/laurie/Zotech/projects/projectiva/trinidad/plugins
> >
> > [EMAIL PROTECTED] mvn install
> > [INFO] Scanning for projects...
> > [INFO] Reactor build order:
> > [INFO]   Apache Trinidad Maven Plugin Parent
> > [INFO]   Apache Trinidad Maven Faces Plugin
> > [INFO]   Apache Trinidad Maven Javacc Plugin
> > [INFO]   Apache Trinidad Maven i18n Plugin
> > [INFO]   Apache Trinidad Maven JDev Plugin
> > [INFO]   Apache Trinidad Maven Javascript Plugin
> > [INFO]   Apache Trinidad Maven XRTS Plugin
> > [INFO]   Apache Trinidad Maven Tag Documentation Report
> > [INFO]   Apache MyFaces Trinidad Archetype
> >
> > 
> >
> >

> >
> > [INFO] Building Apache Trinidad Maven XRTS Plugin
> > [INFO]task-segment: [install]
> > [INFO]
> >

> >
> > [INFO] [plugin:descriptor]
> > [INFO] Using 2 extractors.
> > [INFO] Applying extractor for language: java
> > [INFO]
> >

> > [ERROR] FATAL ERROR
> > [INFO]
> >

> > [INFO] syntax error @[199,67] in
> >
file:/Users/laurie/src/business/agile/projects/projectiva/trinidad/plugins/maven-xrts-plugin/src/main/java/org/apache/myfaces/trinidadbuild/plugin/xrts/XRTSParser.java
> >
> > [INFO]
> >

> > [INFO] Trace
> > com.thoughtworks.qdox.parser.ParseException: syntax
error @[199,67] in
> >
file:/Users/laurie/src/business/agile/projects/projectiva/trinidad/plugins/maven-xrts-plugin/src/main/java/org/apache/myfaces/trinidadbuild/plugin/xrts/XRTSParser.java
> >
> > at
> >
com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504)
> > at
> >
com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:610)
> > at
com.thoughtworks.qdox.parser.impl.Parser.parse
(Parser.java:488)
> > at
> >
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:296)
> > at
> >
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312)
> > at
> >
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:308)
> > at
> >
com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:365)
> > at
> >
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk
(DirectoryScanner.java:43)
> >
> > at
> >
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
> >
> > at
> >
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk
(DirectoryScanner.java:34)
> >
> > at
> >
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
> >
> > at
> >
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk
(DirectoryScanner.java:34)
> >
> > at
> >
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
> >
> > at
> >
com.thoughtworks.qdox.directorywalker.Directo

Problem setting enctype to a form within a form

[Goda, Sunil]

Guys,
 
I have a page1.jsp containing a subview with includes another page
dynamically.Now, sometimes the included page may contain
multipart/form-data i.e a inputFileUpload component.
 
My problem is where do I specify the form's
enctype="multipart/form-data" for the included page.
 
I have tried 3 possible options :
1) Setting the enctype in including page ,page1.jsp.
2) Putting a h:form element in the subview tag and set the enctype.
3) Puttting a h:form element in the included page and set the enctype..
 
But nothing works.I have found the t:subForm a possible solution , but
we'd prefer something that is released.
 
I'd appreciate your help.
 

Regards,
Sunil G
Kenexa Technologies,India.

Re: Tomahawk sandbox component submitOnEvent and Trinidad components

[Martin Marinschek]

Mario,

have you got any clue on this?

regards,

Martin

On 5/31/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:




Hi,

just a short question: Does the Tomahawk sandbox component submitOnEvent
collaborate
with Trinidad components?

I'm afraid it simply doesn't… Or am I missing some configuration gimmick?

For your information, our environment also includes Facelets…

Thanks in advance,
Carsten



--

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Re: [Trinidad] Note to tr:input... generated HTML

[Adam Winer]

Ah, that bug got fixed a day or two ago.  That is,
you don't have to specify INLINE for pages to work.
INLINE is still much cooler than the default. :)

-- Adam


On 5/31/07, Petr Kotek <[EMAIL PROTECTED]> wrote:


Yes, I must insert into trinidad-config.xml line:
INLINE
Without it, commandButton with action binding do nothing.

Peter

Adam Winer wrote:
> Just to confirm - you're using INLINE client-validation?
> I agree, the spacing would be better handled with CSS.
>
> -- Adam
>
>
> On 5/31/07, Petr Kotek <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> I have a little note to HTML code, generated by tr:input components in
>> label area. This code has changed in some latest release (I think) and
>> now look as:
>>
>> 
>>   > nowrap="nowrap">
>> 
>> 
>>   > class="AFErrorIconStyle">X
>> 
>>  
>> Order No:
>>   
>>   
>> 
>>
>> For next styling of label (for example for its vertical alignment
before
>> multi line text input) I have big problems with " " included in
>> code. I think, that it will be better to avoid this " " (generally
>> - all hard coded formating) and space between icon and text realize by
>> right margin in icon element in base style?
>>
>> Thanks for Your opinion,
>> Peter
>>
>

--

Petr Kotek
CRC Data spol. s r.o.
U krčské vodárny 26 - vývojové pracoviště
140 00 Praha 4
tel: +420 241 442 464
fax: +420 241 442 645
GSM: +420 602 339 057
www.crcdata.cz

Re: [Trinidad] plugins build broken?

[Adam Winer]

I've seen this before - it's a bug in qdox, apparently, but I
don't know how or why it goes away.

-- Adam


On 5/31/07, Laurie Harper <[EMAIL PROTECTED]> wrote:


I just tried upgrading to the latest Maven and have the same error. For
now, I've hacked my local poms to require 1.0.1-incubating-SNAPSHOT of
this plugin as a work-around. I'll repost the build error to the dev
list for further attention.

L.

Laurie Harper wrote:
> I just tried checking out the current trunk from its new home and found
> I can't build it :-( I get a failure building the plugins, which then
> leads to a failure to build the 'trinidad' module.
>
> The failure is in the build for the Apache Trinidad Maven XRTS Plugin
> and looks like either an issue with qdox or an issue with the plugin
> code being processed by qdox.
>
> What do I need to do to get this working? I've tried 'mvn -cpu install'
> with no improvement; am I using too old a version of Maven?
>
> L.
>
>
> [EMAIL PROTECTED] java -version
> java version "1.5.0_05"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-83)
> Java HotSpot(TM) Client VM (build 1.5.0_05-48, mixed mode, sharing)
>
> [EMAIL PROTECTED] mvn --version
> Maven version: 2.0.4-maestro-1.0.1
>
> [EMAIL PROTECTED] svn info
> Path: .
> URL: http://svn.apache.org/repos/asf/myfaces/trinidad/trunk/plugins
> Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
> Revision: 542764
> Node Kind: directory
> Schedule: normal
> Last Changed Author: mmarinschek
> Last Changed Rev: 538505
> Last Changed Date: 2007-05-16 05:53:47 -0400 (Wed, 16 May 2007)
> Properties Last Updated: 2007-05-30 02:14:05 -0400 (Wed, 30 May 2007)
>
> [EMAIL PROTECTED] pwd
> /Users/laurie/Zotech/projects/projectiva/trinidad/plugins
>
> [EMAIL PROTECTED] mvn install
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO]   Apache Trinidad Maven Plugin Parent
> [INFO]   Apache Trinidad Maven Faces Plugin
> [INFO]   Apache Trinidad Maven Javacc Plugin
> [INFO]   Apache Trinidad Maven i18n Plugin
> [INFO]   Apache Trinidad Maven JDev Plugin
> [INFO]   Apache Trinidad Maven Javascript Plugin
> [INFO]   Apache Trinidad Maven XRTS Plugin
> [INFO]   Apache Trinidad Maven Tag Documentation Report
> [INFO]   Apache MyFaces Trinidad Archetype
>
> 
>
>

>
> [INFO] Building Apache Trinidad Maven XRTS Plugin
> [INFO]task-segment: [install]
> [INFO]
>

>
> [INFO] [plugin:descriptor]
> [INFO] Using 2 extractors.
> [INFO] Applying extractor for language: java
> [INFO]
> 
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] syntax error @[199,67] in
>
file:/Users/laurie/src/business/agile/projects/projectiva/trinidad/plugins/maven-xrts-plugin/src/main/java/org/apache/myfaces/trinidadbuild/plugin/xrts/XRTSParser.java
>
> [INFO]
> 
> [INFO] Trace
> com.thoughtworks.qdox.parser.ParseException: syntax error @[199,67] in
>
file:/Users/laurie/src/business/agile/projects/projectiva/trinidad/plugins/maven-xrts-plugin/src/main/java/org/apache/myfaces/trinidadbuild/plugin/xrts/XRTSParser.java
>
> at
> com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504)
> at
> com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:610)
> at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java
:488)
> at
> com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:296)
> at
> com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312)
> at
> com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:308)
> at
> com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java
:365)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(
DirectoryScanner.java:43)
>
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(
DirectoryScanner.java:34)
>
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(
DirectoryScanner.java:34)
>
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(
DirectoryScanner.java:34)
>
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(
DirectoryScanner.java:34)
>
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(
DirectoryScanner.java:34)
>
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(
DirectoryScanner.java:34)
>
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(
DirectoryScanner.java:34)
>
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(
DirectoryScanner.java:52)
>
> at
> com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java

Re: Strange Trinidad behaviour after upgrading to JBoss 4.2.0

[Chris Lowe]

If I set CACHE_VIEW_ROOT to false the problem goes away.


On 5/31/07, Chris Lowe <[EMAIL PROTECTED]> wrote:


I take it back - it's now even stranger!

First click that fires validation works.  Click again and the duplication
starts happening as before.

On 5/31/07, Chris Lowe <[EMAIL PROTECTED]> wrote:
>
> I've just done an update to my environment:
>
> Update to latest Ajax4Jsf snapshot from 
http://maven.exadel.com/org/ajax4jsf/ajax4jsf/
>
> Update to latest Seam snapshot (CVS) and reconfigured filters in-line
> with new version (many of the Seam filters + Ajax4Jsf have been rolled into
> one);
> Changed ALTERNATE_VIEW_HANDLER from:
>
> 
> org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
> 
> org.jboss.seam.ui.facelet.SeamFaceletViewHandler
> 
> 
>
> To
>
> 
> org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
> 
> com.sun.facelets.FaceletViewHandler
> 
>
> USE_APPLICATION_VIEW_CACHE and CACHE_VIEW_ROOT are both true.
>
> My app now does not exhibit the duplication problems.
>
> That was a strange one!
>
> On 5/31/07, Adam Winer <[EMAIL PROTECTED]> wrote:
> >
> > Well, we've got a lot of variables here.  It's a little
> > suspicious to me hearing that an Ajax4JSF filter is
> > now required, when this behavior doesn't appear to
> > be reproducing for other users of Trinidad 1.2.
> >
> > I'd try, for example, the same page without Ajax4JSF
> > installed - if that means taking Seam out of the picture
> > for that one page, OK.
> >
> > I'd also try deploying the same app to Glassfish -
> > if it reproduces there, then we know it's not JBoss
> > specific.
> >
> > BTW, USE_APPLICATION_VIEW_CACHE=false
> > is the default, so setting that won't change anything.
> > Another random thing to try is setting
> > org.apache.myfaces.trinidad.CACHE_VIEW_ROOT
> > to false.  That will be a change from the default.
> > It throws away an extremely valuable optimization,
> > but it also might help point out where things are going
> > wrong.
> >
> > -- Adam
> >
> >
> > On 5/30/07, Chris Lowe < [EMAIL PROTECTED]> wrote:
> > > Is there anything I can do to help narrow this down?
> > >
> > >
> > >
> > > On 5/30/07, Adam Winer < [EMAIL PROTECTED]> wrote:
> > > > Hrm, that looks like the same version as Glassfish!  I
> > > > didn't know they were using the RI.  So scrap that theory!
> > > > It still *might* be something wrong in JBoss (maybe their
> > > > implementation of JspIdConsumer in the JSP engine?),
> > > > but this is more puzzling.
> > > >
> > > > -- Adam
> > > >
> > > >
> > > > On 5/30/07, Chris Lowe < [EMAIL PROTECTED] > wrote:
> > > > > Thanks for the reply Adam.
> > > > >
> > > > > Do you happen to know what version of JSF Glassfish is using?
> > > > >
> > > > > From jsf-api.jar that is with JBoss 4.2.0.GA, the manifest
> > states:
> > > > >
> > > > > Manifest-Version: 1.0
> > > > > Specification-Title: JavaServer Faces
> > > > > Created-By: 1.5.0_04-b05 (Sun Microsystems Inc.)
> > > > > Ant-Version: Apache Ant 1.6.5
> > > > > Implementation-Title: Sun Microsystems JavaServer Faces
> > Implementation
> > > > > Specification-Vendor: JBoss ( http://www.jboss.org/ )
> > > > > Specification-Version: 1.2MR1
> > > > > Implementation-Vendor-Id: com.sun
> > > > > Extension-Name: javax.faces
> > > > > Implementation-Version: 1.2_04-b10-p01
> > > > > Implementation-Vendor: Sun Microsystems, Inc.
> > > > > Implementation-URL: http://www.jboss.org/
> > > > > Cheers,
> > > > >
> > > > > Chris.
> > > > >
> > > > >
> > > > >
> > > > > On 5/30/07, Adam Winer <[EMAIL PROTECTED]> wrote:
> > > > > > I suspect that there's something wrong with
> > > > > > the implementation of JSF 1.2 used by JBoss, probably
> > > > > > in that implementation's UIComponentClassicTagBase
> > > > > > code or something similar.  The behavior you're describing
> > > > > > doesn't occur with Glassfish.
> > > > > >
> > > > > > -- Adam
> > > > > >
> > > > > >
> > > > > > On 5/30/07, Chris Lowe < [EMAIL PROTECTED] >
> > wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > I have a project that is running Trinidad and I recently
> > upgraded to
> > > > > JBoss
> > > > > > > 4.2.0.GA.  As part of this upgrade I also migrated to JSF
> > 1.2 (the
> > > > > latest
> > > > > > > Seam version requires me to do this).  Ever since then,
> > whenever I
> > > > > submit a
> > > > > > > form that fails validation, the form renders the correct
> > validation
> > > > > messages
> > > > > > > but I get some weird rendering of the form. It's actually
> > like the
> > > > > previous
> > > > > > > HTML doesn't get cleared and the new form + validation
> > errors gets
> > > > > tacked
> > > > > > > onto the end - I'm literally seeing double. If I click my
> > submit
> > > button
> > > > > > > again, then a third instance will be tacked onto the bottom,
> > and so
> > > on.
> > > > > If
> > > > > > > at this point I simply refresh the page, then everything
> > resets back
> > > to
> > > > > > > normal. If I use the applicatio

Re: tomahawk 1.1.5 and JSF 1.2/Tomcat 6

[rlubke]

What's the exact version of the RI you're using?


martind wrote:
> 
> I would like to use tomahawk 1.1.5 with JSF 1.2 RI inside Tomcat 6. Is
> this combinatiion supported? I have tried to load the tomahawk
> examples, but I get an exception when loading the first page:
> 
> May 31, 2007 8:37:33 PM com.sun.faces.config.ConfigureListener configure
> SEVERE: null MessageFactory
> java.lang.ClassCastException:
> org.apache.myfaces.renderkit.html.util.ExtensionsPhaseListener cannot
> be cast to javax.faces.event.PhaseListener
> at
> com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:885)
> at
> com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:536)
> at
> com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:436)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
> at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
> at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
> 
>at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
> 
>at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
> ...
> 
> I have followed instructions on MyFaces pages, including setting up
> the extensions filter.
> 
> Martin
> 
> 

-- 
View this message in context: 
http://www.nabble.com/tomahawk-1.1.5-and-JSF-1.2-Tomcat-6-tf3848875.html#a10902930
Sent from the MyFaces - Users mailing list archive at Nabble.com.

Re: Strange Trinidad behaviour after upgrading to JBoss 4.2.0

[Chris Lowe]

I take it back - it's now even stranger!

First click that fires validation works.  Click again and the duplication
starts happening as before.

On 5/31/07, Chris Lowe <[EMAIL PROTECTED]> wrote:


I've just done an update to my environment:

Update to latest Ajax4Jsf snapshot from 
http://maven.exadel.com/org/ajax4jsf/ajax4jsf/

Update to latest Seam snapshot (CVS) and reconfigured filters in-line with
new version (many of the Seam filters + Ajax4Jsf have been rolled into one);
Changed ALTERNATE_VIEW_HANDLER from:


org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER

org.jboss.seam.ui.facelet.SeamFaceletViewHandler



To


org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER

com.sun.facelets.FaceletViewHandler


USE_APPLICATION_VIEW_CACHE and CACHE_VIEW_ROOT are both true.

My app now does not exhibit the duplication problems.

That was a strange one!

On 5/31/07, Adam Winer <[EMAIL PROTECTED]> wrote:
>
> Well, we've got a lot of variables here.  It's a little
> suspicious to me hearing that an Ajax4JSF filter is
> now required, when this behavior doesn't appear to
> be reproducing for other users of Trinidad 1.2.
>
> I'd try, for example, the same page without Ajax4JSF
> installed - if that means taking Seam out of the picture
> for that one page, OK.
>
> I'd also try deploying the same app to Glassfish -
> if it reproduces there, then we know it's not JBoss
> specific.
>
> BTW, USE_APPLICATION_VIEW_CACHE=false
> is the default, so setting that won't change anything.
> Another random thing to try is setting
> org.apache.myfaces.trinidad.CACHE_VIEW_ROOT
> to false.  That will be a change from the default.
> It throws away an extremely valuable optimization,
> but it also might help point out where things are going
> wrong.
>
> -- Adam
>
>
> On 5/30/07, Chris Lowe < [EMAIL PROTECTED]> wrote:
> > Is there anything I can do to help narrow this down?
> >
> >
> >
> > On 5/30/07, Adam Winer <[EMAIL PROTECTED]> wrote:
> > > Hrm, that looks like the same version as Glassfish!  I
> > > didn't know they were using the RI.  So scrap that theory!
> > > It still *might* be something wrong in JBoss (maybe their
> > > implementation of JspIdConsumer in the JSP engine?),
> > > but this is more puzzling.
> > >
> > > -- Adam
> > >
> > >
> > > On 5/30/07, Chris Lowe < [EMAIL PROTECTED] > wrote:
> > > > Thanks for the reply Adam.
> > > >
> > > > Do you happen to know what version of JSF Glassfish is using?
> > > >
> > > > From jsf-api.jar that is with JBoss 4.2.0.GA, the manifest states:
> > > >
> > > > Manifest-Version: 1.0
> > > > Specification-Title: JavaServer Faces
> > > > Created-By: 1.5.0_04-b05 (Sun Microsystems Inc.)
> > > > Ant-Version: Apache Ant 1.6.5
> > > > Implementation-Title: Sun Microsystems JavaServer Faces
> Implementation
> > > > Specification-Vendor: JBoss (http://www.jboss.org/ )
> > > > Specification-Version: 1.2MR1
> > > > Implementation-Vendor-Id: com.sun
> > > > Extension-Name: javax.faces
> > > > Implementation-Version: 1.2_04-b10-p01
> > > > Implementation-Vendor: Sun Microsystems, Inc.
> > > > Implementation-URL: http://www.jboss.org/
> > > > Cheers,
> > > >
> > > > Chris.
> > > >
> > > >
> > > >
> > > > On 5/30/07, Adam Winer <[EMAIL PROTECTED]> wrote:
> > > > > I suspect that there's something wrong with
> > > > > the implementation of JSF 1.2 used by JBoss, probably
> > > > > in that implementation's UIComponentClassicTagBase
> > > > > code or something similar.  The behavior you're describing
> > > > > doesn't occur with Glassfish.
> > > > >
> > > > > -- Adam
> > > > >
> > > > >
> > > > > On 5/30/07, Chris Lowe < [EMAIL PROTECTED] > wrote:
> > > > > > Hello,
> > > > > >
> > > > > > I have a project that is running Trinidad and I recently
> upgraded to
> > > > JBoss
> > > > > > 4.2.0.GA.  As part of this upgrade I also migrated to JSF 1.2(the
> > > > latest
> > > > > > Seam version requires me to do this).  Ever since then,
> whenever I
> > > > submit a
> > > > > > form that fails validation, the form renders the correct
> validation
> > > > messages
> > > > > > but I get some weird rendering of the form. It's actually like
> the
> > > > previous
> > > > > > HTML doesn't get cleared and the new form + validation errors
> gets
> > > > tacked
> > > > > > onto the end - I'm literally seeing double. If I click my
> submit
> > button
> > > > > > again, then a third instance will be tacked onto the bottom,
> and so
> > on.
> > > > If
> > > > > > at this point I simply refresh the page, then everything
> resets back
> > to
> > > > > > normal. If I use the application without causing validation
> errors
> > then
> > > > > > everything works as normal. I get the same behaviour on
> FireFox and
> > IE
> > > > and
> > > > > > there are no exceptions in the logs.
> > > > > >
> > > > > > I tried updating the Trinidad build to
> > > > trinidad-*-1.2-07-may-SNAPSHOT.jar ,
> > > > > > but to no avail.
> > > > > >
> > > > > > I eventually tracked the strange beha

RE: Change valueBinding of t:dataTable based on condition

[hermod.opstvedt]

Hi
 
You should look at Clay in the Shale project. This is a piece of cake using 
symbols in Clay.
 
Hermod

-Original Message-
From: Rønnevik, Eivind [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 31, 2007 2:24 PM
To: MyFaces Discussion
Subject: Change valueBinding of t:dataTable based on condition



Hi!

 

I was just curious, is there any way I can change the value of a dataTable 
based on different conditions?

 

I'll try to give a simple example to explain what I want. :)

 

Let's say I use the graphicImage tag, in the value property I could either 
write the path to the image

Tomahawk sandbox component submitOnEvent and Trinidad components

[carsten.pieper]

Hi,

just a short question: Does the Tomahawk sandbox component submitOnEvent
collaborate
with Trinidad components?

I'm afraid it simply doesn't... Or am I missing some configuration gimmick?

For your information, our environment also includes Facelets...

Thanks in advance,
Carsten

Re: Strange Trinidad behaviour after upgrading to JBoss 4.2.0

[Chris Lowe]

I've just done an update to my environment:

Update to latest Ajax4Jsf snapshot from
http://maven.exadel.com/org/ajax4jsf/ajax4jsf/
Update to latest Seam snapshot (CVS) and reconfigured filters in-line with
new version (many of the Seam filters + Ajax4Jsf have been rolled into one);
Changed ALTERNATE_VIEW_HANDLER from:

   
   org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER

   org.jboss.seam.ui.facelet.SeamFaceletViewHandler

   

To

   
   org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER

   com.sun.facelets.FaceletViewHandler
   

USE_APPLICATION_VIEW_CACHE and CACHE_VIEW_ROOT are both true.

My app now does not exhibit the duplication problems.

That was a strange one!

On 5/31/07, Adam Winer <[EMAIL PROTECTED]> wrote:


Well, we've got a lot of variables here.  It's a little
suspicious to me hearing that an Ajax4JSF filter is
now required, when this behavior doesn't appear to
be reproducing for other users of Trinidad 1.2.

I'd try, for example, the same page without Ajax4JSF
installed - if that means taking Seam out of the picture
for that one page, OK.

I'd also try deploying the same app to Glassfish -
if it reproduces there, then we know it's not JBoss
specific.

BTW, USE_APPLICATION_VIEW_CACHE=false
is the default, so setting that won't change anything.
Another random thing to try is setting
org.apache.myfaces.trinidad.CACHE_VIEW_ROOT
to false.  That will be a change from the default.
It throws away an extremely valuable optimization,
but it also might help point out where things are going
wrong.

-- Adam


On 5/30/07, Chris Lowe <[EMAIL PROTECTED]> wrote:
> Is there anything I can do to help narrow this down?
>
>
>
> On 5/30/07, Adam Winer <[EMAIL PROTECTED]> wrote:
> > Hrm, that looks like the same version as Glassfish!  I
> > didn't know they were using the RI.  So scrap that theory!
> > It still *might* be something wrong in JBoss (maybe their
> > implementation of JspIdConsumer in the JSP engine?),
> > but this is more puzzling.
> >
> > -- Adam
> >
> >
> > On 5/30/07, Chris Lowe < [EMAIL PROTECTED]> wrote:
> > > Thanks for the reply Adam.
> > >
> > > Do you happen to know what version of JSF Glassfish is using?
> > >
> > > From jsf-api.jar that is with JBoss 4.2.0.GA, the manifest states:
> > >
> > > Manifest-Version: 1.0
> > > Specification-Title: JavaServer Faces
> > > Created-By: 1.5.0_04-b05 (Sun Microsystems Inc.)
> > > Ant-Version: Apache Ant 1.6.5
> > > Implementation-Title: Sun Microsystems JavaServer Faces
Implementation
> > > Specification-Vendor: JBoss (http://www.jboss.org/)
> > > Specification-Version: 1.2MR1
> > > Implementation-Vendor-Id: com.sun
> > > Extension-Name: javax.faces
> > > Implementation-Version: 1.2_04-b10-p01
> > > Implementation-Vendor: Sun Microsystems, Inc.
> > > Implementation-URL: http://www.jboss.org/
> > > Cheers,
> > >
> > > Chris.
> > >
> > >
> > >
> > > On 5/30/07, Adam Winer <[EMAIL PROTECTED]> wrote:
> > > > I suspect that there's something wrong with
> > > > the implementation of JSF 1.2 used by JBoss, probably
> > > > in that implementation's UIComponentClassicTagBase
> > > > code or something similar.  The behavior you're describing
> > > > doesn't occur with Glassfish.
> > > >
> > > > -- Adam
> > > >
> > > >
> > > > On 5/30/07, Chris Lowe < [EMAIL PROTECTED]> wrote:
> > > > > Hello,
> > > > >
> > > > > I have a project that is running Trinidad and I recently
upgraded to
> > > JBoss
> > > > > 4.2.0.GA.  As part of this upgrade I also migrated to JSF 1.2(the
> > > latest
> > > > > Seam version requires me to do this).  Ever since then, whenever
I
> > > submit a
> > > > > form that fails validation, the form renders the correct
validation
> > > messages
> > > > > but I get some weird rendering of the form. It's actually like
the
> > > previous
> > > > > HTML doesn't get cleared and the new form + validation errors
gets
> > > tacked
> > > > > onto the end - I'm literally seeing double. If I click my submit
> button
> > > > > again, then a third instance will be tacked onto the bottom, and
so
> on.
> > > If
> > > > > at this point I simply refresh the page, then everything resets
back
> to
> > > > > normal. If I use the application without causing validation
errors
> then
> > > > > everything works as normal. I get the same behaviour on FireFox
and
> IE
> > > and
> > > > > there are no exceptions in the logs.
> > > > >
> > > > > I tried updating the Trinidad build to
> > > trinidad-*-1.2-07-may-SNAPSHOT.jar,
> > > > > but to no avail.
> > > > >
> > > > > I eventually tracked the strange behaviour down to my usage of
> > > ,
> > > > > if I use a vanilla body tag then the page duplication problem
goes.
> > > > > However, I still get similar issues with  - the
> instance
> > > of
> > > > > the link is duplicated with each form submission that causes a
> > > validation
> > > > > error.  Changing to  again, resolves this issue.
> > > > >
> > > > > Has anyone come across this before?
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Chr

tomahawk 1.1.5 and JSF 1.2/Tomcat 6

[Martin Dubuc]

I would like to use tomahawk 1.1.5 with JSF 1.2 RI inside Tomcat 6. Is
this combinatiion supported? I have tried to load the tomahawk
examples, but I get an exception when loading the first page:

May 31, 2007 8:37:33 PM com.sun.faces.config.ConfigureListener configure
SEVERE: null MessageFactory
java.lang.ClassCastException:
org.apache.myfaces.renderkit.html.util.ExtensionsPhaseListener cannot
be cast to javax.faces.event.PhaseListener
   at 
com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:885)
   at 
com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:536)
   at 
com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:436)
   at 
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
   at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
   at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
   at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)

  at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)

  at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
   at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
   at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
...

I have followed instructions on MyFaces pages, including setting up
the extensions filter.

Martin

Re: Format the itemLabel i selectItem

[Mike Kienenberger]

The Tomahawk selectItems tag  will give you far more
control over how the items are constructed.

http://myfaces.apache.org/tomahawk/selectItems.html

On 5/28/07, Pich <[EMAIL PROTECTED]> wrote:


Hi!

I have a f:selectOneMenu and a couple of f:selectItem tags. I use the
itemLabel and itemValue attributes. Is it possible for format the output of
the itemLabel in the outcoming drop down?

The drop down is presenting account numbers and these should be presented in
a specific way. I do not want this presentation logic in my model and I am
hoping it is possible to perform such formating of the itemLabel using JSF
tags.

Best regards

Pich
--
View this message in context: 
http://www.nabble.com/Format-the-itemLabel-i-selectItem-tf3827190.html#a10834012
Sent from the MyFaces - Users mailing list archive at Nabble.com.

Re: [Trinidad] plugins build broken?

[Laurie Harper]

I just tried upgrading to the latest Maven and have the same error. For 
now, I've hacked my local poms to require 1.0.1-incubating-SNAPSHOT of 
this plugin as a work-around. I'll repost the build error to the dev 
list for further attention.


L.

Laurie Harper wrote:
I just tried checking out the current trunk from its new home and found 
I can't build it :-( I get a failure building the plugins, which then 
leads to a failure to build the 'trinidad' module.


The failure is in the build for the Apache Trinidad Maven XRTS Plugin 
and looks like either an issue with qdox or an issue with the plugin 
code being processed by qdox.


What do I need to do to get this working? I've tried 'mvn -cpu install' 
with no improvement; am I using too old a version of Maven?


L.


[EMAIL PROTECTED] java -version
java version "1.5.0_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-83)
Java HotSpot(TM) Client VM (build 1.5.0_05-48, mixed mode, sharing)

[EMAIL PROTECTED] mvn --version
Maven version: 2.0.4-maestro-1.0.1

[EMAIL PROTECTED] svn info
Path: .
URL: http://svn.apache.org/repos/asf/myfaces/trinidad/trunk/plugins
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 542764
Node Kind: directory
Schedule: normal
Last Changed Author: mmarinschek
Last Changed Rev: 538505
Last Changed Date: 2007-05-16 05:53:47 -0400 (Wed, 16 May 2007)
Properties Last Updated: 2007-05-30 02:14:05 -0400 (Wed, 30 May 2007)

[EMAIL PROTECTED] pwd
/Users/laurie/Zotech/projects/projectiva/trinidad/plugins

[EMAIL PROTECTED] mvn install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Apache Trinidad Maven Plugin Parent
[INFO]   Apache Trinidad Maven Faces Plugin
[INFO]   Apache Trinidad Maven Javacc Plugin
[INFO]   Apache Trinidad Maven i18n Plugin
[INFO]   Apache Trinidad Maven JDev Plugin
[INFO]   Apache Trinidad Maven Javascript Plugin
[INFO]   Apache Trinidad Maven XRTS Plugin
[INFO]   Apache Trinidad Maven Tag Documentation Report
[INFO]   Apache MyFaces Trinidad Archetype



 


[INFO] Building Apache Trinidad Maven XRTS Plugin
[INFO]task-segment: [install]
[INFO] 
 


[INFO] [plugin:descriptor]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO] 


[ERROR] FATAL ERROR
[INFO] 

[INFO] syntax error @[199,67] in 
file:/Users/laurie/src/business/agile/projects/projectiva/trinidad/plugins/maven-xrts-plugin/src/main/java/org/apache/myfaces/trinidadbuild/plugin/xrts/XRTSParser.java 

[INFO] 


[INFO] Trace
com.thoughtworks.qdox.parser.ParseException: syntax error @[199,67] in 
file:/Users/laurie/src/business/agile/projects/projectiva/trinidad/plugins/maven-xrts-plugin/src/main/java/org/apache/myfaces/trinidadbuild/plugin/xrts/XRTSParser.java 

at 
com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504)
at 
com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:610)

at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:488)
at 
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:296)
at 
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312)
at 
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:308)
at 
com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:365)
at 
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43) 

at 
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) 

at 
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) 

at 
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) 

at 
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) 

at 
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) 

at 
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) 

at 
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) 

at 
com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52) 

at 
com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:362)
at 
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:477) 

at 
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:69) 

at 
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(

[Swiss JSF Users] JSF Special-Interest-Group Switzerland

[Jesse Alexander \(KSFD 121\)]

JSF is proving more and more competitive each day. A increasing number
of 
companies are developing applications based on JSF.
Often the same questions/problems/hints are valid for almost all users
of 
JSF. Internationally some active communities have been established. Last

year a first encounter of JSF-entusiasts created the idea of "JSFDays
Europe", 
a conference that allows to get in touch with the main players int he 
JSF-universe and to meet also informally. This first encounter took
place 
in Munich, was organized on very short notice during the Oktoberfest. An

intense session with the JSF expert group lead Ed Burns allowed the
users 
to voice their wishes for JSF 2.0 and regognize the "approachability" of

the JSF-people at Sun. Within Switzerland so far the contacts between
the 
users are rather sporadic and more on a one-to-one basis.

Hopefully some contacts have been added during the Jazoon-conference. We

would like to go one step further and establish the networking between 
Swiss-JSF users. An active community can help in solving problems or
even 
create components that are usefull for some or all members. And in 
Switzerland we encounter some problems (like i18n, as most of our 
applications need to be available in multiple languages) that other
international users do not encounter or encounter later or to a lesser
extent.

The JSF-specification is driven by requirements that are brought to the 
Expert Group discussing the specifications. So far much input has come 
from framework-architects, appserver-providers and tool-creators. It's 
about time the actual users let hear their voices as well. Although the 
expert group members can be contacted and have proven to be very 
responsive, requirements coming from an official user-group have more 
importance.

Establishing a "JSF user group" as a independant community or a 
"special interest group" under the umbrella of the 
"JUGS (Java User Group Switzerland)" could be the outcome of this
meeting.

The underline the importance of "interaction" and communication for the 
community, we propose short presentations with much space for
discussion.

Date: Thursday, 2007-06-28 (right after the end of Jazoon 07)
Place: Zurich, close to the location of Jazoon 07 (but not yet defined) 

Agenda:
- 16:30 - 17:30: HTTP-GET interface into JSF-applications
Presenter: Ed Burns
Abstract: First ideas on the upcoming GET-interface into 
JSF-applications. ...
  30 minutes presentation, 30 minutes discussion on 
these ideas and their implications on the applications

- 17:30 - 18:30 (resp. open end): JSF, Quo Vadis?
Presenter: Ed Burns, Alexander Jesse
Abstract: 
- Where is JSF heading? The Expert Group is forming and
discussing 
the next version of the JSF-spec right now. 
What are the ideas driving the EG? 
- Where is JSF heading in Switzerland? Can we say a User Group
is 
forming right now? What could be the plans of this group? Should

it participate in the "JSFDays Europe" initiative?

In order to plan the upcoming first meeting (room,...) we would
appreciate 
feedback from all interested people. Also from those that cannot come to

the first meeting, but would welcome the foundation of the 
JSF Special-Interest-Group Switzerland.

Re: [Tobago] How to make tobago pages printable

[Arvid Hülsebus]

Hello,

I think we need to enhance the page renderer to allow themes to specifiy 
the media attribute of a stylesheet. If have your own theme you could 
overwrite the stylesheet inclusion mechanism in the page renderer 
yourself as workaround.


Regards,
Arvid

H. Swaczinna wrote:

Hi,

nobody had the need to print a Tobago page from the browser?

I tried to add my own css style files for printing but I found no way. The 
tc:style tag generates only style file
references for media="screen". If the tc:style tag has a media attribute the 
problem can be solved.


Regards
Helmut


- Original Message - 
From: "H. Swaczinna" <[EMAIL PROTECTED]>

To: 
Sent: Wednesday, May 23, 2007 3:26 PM
Subject: [Tobago] How to make tobago pages printable


  

Hi,

when I print a tobago page every style information is lost. This is 
because

in the stylesheet references the
media attribute is set to "screen". Is there somewhere a switch to set 
this

to "print"?

Regards
Helmut




  

Memory leak issues with MyFaces 1.1.3?

[ohfaces]

Hi,

I have a customer-facing application that is running on IBM JVM 1.5 and
Oracle App Server 10.1.3. The app uses MyFaces 1.1.3 release and has been in
production since the last 3-4 months.
The load tests prior to production went fine with the samples provided by
the client, but now in production we are observing memory leak scenarios
possibly due to the MyFaces JSPStateManagerImpl / it's handling of the
internal SerializedViewCollection objects or it's interaction with the
Apache Commons library.
What we observed on heapdumps is that the MyFaces JSPStateManagerImpl takes
a huge amount of heap on running the app for 3-4 days and eventually takes a
lot of the memory on the heap making it less available for the rest of the
app.

Here's the results from one of the heapdump attached as an image to this
mail.



Also, on looking at the instance counts of the MyFaces SerializedKey we see
that it keeps on increasing with time despite turning Serialization off and
reducing the number of cached views in session to 4.

Is it possible that these settings do not have any effect on Myfaces 1.1.3
and has such a memory leak been reported earlier?

We plan on updating to MyFaces 1.1.5 - to see if this fixes the issue with
the JSPStateManagerImpl  but it's still up in the air.

Thanks in advance! http://www.nabble.com/file/p10900138/heapdump.gif 
-- 
View this message in context: 
http://www.nabble.com/Memory-leak-issues-with-MyFaces-1.1.3--tf3848348.html#a10900138
Sent from the MyFaces - Users mailing list archive at Nabble.com.

Re: t:panelTabbedPane and data validation

[Mike Kienenberger]

I think the behavior of the component changes depending on whether
you're using server-side or client-side tabbing.

If you're using client-side tabbing, then I believe all tabs are
generated and all values are validated.  If you're using server-side
tabbing, then I think only the current tab is actually rendered to the
browser.

It's been awhile since I've used tabs, but I believe that's the situation.

Don't know what the process for switching to the first panel with an
error would be.



On 5/29/07, David Delbecq <[EMAIL PROTECTED]> wrote:

Hello,

i have a form with the following structure:

form
 + inputText
 + panelTabbedPane
   + panelTab
 + input (required="true")
   + panelTab
 + input (required="true")
 + commandButton
 + messages

If i am in second tab and i click the submit button, the fields in first
tab are not validated (there is nothing in h:messages). However, if i go
back to first tab and click the submit button, then i get the validation
error message. Is there a way to have all fields of panelTabbedPane
validated (instead of only current panel) and have panelTabbedPane show
the first panel with an error?

Re: Reset dataScroller

[Mike Kienenberger]

Are you asking how to resubmit the form when the menu changes?

If so, see here:

http://wiki.apache.org/myfaces/SubmitPageOnValueChange

As it states at the top, the simplest way to do this is with a
submitOnEvent component, typically inside of a subForm component.
Both of these components are currently in the sandbox, but are
production-quality.  (No one's gotten around yet to promoting them to
Tomahawk).












On 5/31/07, Michael Böckling <[EMAIL PROTECTED]> wrote:

Wow, it seems you are doing the exact same thing as me, even my bean has the
same name! :D
I was afraid that this would have to be the solution... Oh boy.


I have a second issue, however, thats a bit related to this. To avoid having
to reset the UI, I do a full page reload, e.g. when I change the displayed
rows per page of my dataTable. That way, my dataScrollers stay in sync as
well.

I have a h:selectOneMenu to change this number, and I would like to trigger
an auto-submit when it changes its value. For now, it works only using a
commandButton, but that just look right. I tried to register the
oamSubmitForm() with  the 'onchange' event on the h:selectOneMenu, but that
does not work, for whatever reason. I guess its because h:selectOneMenu
isn't a actionSource.

Is there a way to do this properly? This seems to be one of the easiest
things, yet I can't do it.


And thanks for your help so far, Mike! That was great!



Michael


> -Ursprüngliche Nachricht-
> Von: Mike Kienenberger [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 31. Mai 2007 20:18
> An: MyFaces Discussion
> Betreff: Re: Reset dataScroller
>
>
> See here for ideas:
>
> https://issues.apache.org/jira/browse/TOMAHAWK-548
>
> No one's been motivated enough yet to submit patches.
>
> On 5/31/07, Michael Böckling <[EMAIL PROTECTED]> wrote:
> > Hi!
> >
> > I have a problem with t:dataScroller, it does not reset
> itself when the
> > underlying data model changes. When I click on the "first" button,
> > everything is well again. Is there a way to do this
> programmatically? In
> > JavaScript or in a backing bean?
> >
> > Thanks for any help!
> >
> >
> > Michael
> >
> >
> > --
> > Michael Böckling
> > Java Engineer
> > dmc digital media center GmbH
> > Rommelstraße 11
> > 70376 Stuttgart (Germany)
> > Telefon: +49 711 601747-0
> > Telefax: +49 711 601747-141
> > E-Mail: [EMAIL PROTECTED]
> > Internet: www.dmc.de
> >
> > Handelsregister: AG Stuttgart HRB 18974
> > Geschäftsführer: Andreas Magg, Daniel Rebhorn, Andreas Schwend
> >
> > -
> > Besseres E-Business.
> > dmc ist die kreative Vernetzung von Agentur, Systemhaus und
> Service. Seit
> > über 10 Jahren entwickeln und realisieren wir zukunftweisende und
> > erfolgreiche E-Business-Lösungen. Zu unseren langjährigen
> Kunden zählen
> > neckermann.de, Kodak und Telekom Training.
> >
> > dmc auf Platz 8 im aktuellen New Media Service Ranking.
> > Als inhabergeführte und netzwerkunabhängige Agentur gehören
> wir mit einem
> > Umsatz von 13,50 Mio. Euro zu den Top 10 der
> erfolgreichsten New Media
> > Dienstleister in Deutschland.
> >
>

AW: Reset dataScroller

[Michael Böckling]

Wow, it seems you are doing the exact same thing as me, even my bean has the
same name! :D
I was afraid that this would have to be the solution... Oh boy.


I have a second issue, however, thats a bit related to this. To avoid having
to reset the UI, I do a full page reload, e.g. when I change the displayed
rows per page of my dataTable. That way, my dataScrollers stay in sync as
well.

I have a h:selectOneMenu to change this number, and I would like to trigger
an auto-submit when it changes its value. For now, it works only using a
commandButton, but that just look right. I tried to register the
oamSubmitForm() with  the 'onchange' event on the h:selectOneMenu, but that
does not work, for whatever reason. I guess its because h:selectOneMenu
isn't a actionSource. 

Is there a way to do this properly? This seems to be one of the easiest
things, yet I can't do it.


And thanks for your help so far, Mike! That was great!



Michael


> -Ursprüngliche Nachricht-
> Von: Mike Kienenberger [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 31. Mai 2007 20:18
> An: MyFaces Discussion
> Betreff: Re: Reset dataScroller
> 
> 
> See here for ideas:
> 
> https://issues.apache.org/jira/browse/TOMAHAWK-548
> 
> No one's been motivated enough yet to submit patches.
> 
> On 5/31/07, Michael Böckling <[EMAIL PROTECTED]> wrote:
> > Hi!
> >
> > I have a problem with t:dataScroller, it does not reset 
> itself when the
> > underlying data model changes. When I click on the "first" button,
> > everything is well again. Is there a way to do this 
> programmatically? In
> > JavaScript or in a backing bean?
> >
> > Thanks for any help!
> >
> >
> > Michael
> >
> >
> > --
> > Michael Böckling
> > Java Engineer
> > dmc digital media center GmbH
> > Rommelstraße 11
> > 70376 Stuttgart (Germany)
> > Telefon: +49 711 601747-0
> > Telefax: +49 711 601747-141
> > E-Mail: [EMAIL PROTECTED]
> > Internet: www.dmc.de
> >
> > Handelsregister: AG Stuttgart HRB 18974
> > Geschäftsführer: Andreas Magg, Daniel Rebhorn, Andreas Schwend
> >
> > -
> > Besseres E-Business.
> > dmc ist die kreative Vernetzung von Agentur, Systemhaus und 
> Service. Seit
> > über 10 Jahren entwickeln und realisieren wir zukunftweisende und
> > erfolgreiche E-Business-Lösungen. Zu unseren langjährigen 
> Kunden zählen
> > neckermann.de, Kodak und Telekom Training.
> >
> > dmc auf Platz 8 im aktuellen New Media Service Ranking.
> > Als inhabergeführte und netzwerkunabhängige Agentur gehören 
> wir mit einem
> > Umsatz von 13,50 Mio. Euro zu den Top 10 der 
> erfolgreichsten New Media
> > Dienstleister in Deutschland.
> >
> 

Re: Reset dataScroller

[Mike Kienenberger]

See here for ideas:

https://issues.apache.org/jira/browse/TOMAHAWK-548

No one's been motivated enough yet to submit patches.

On 5/31/07, Michael Böckling <[EMAIL PROTECTED]> wrote:

Hi!

I have a problem with t:dataScroller, it does not reset itself when the
underlying data model changes. When I click on the "first" button,
everything is well again. Is there a way to do this programmatically? In
JavaScript or in a backing bean?

Thanks for any help!


Michael


--
Michael Böckling
Java Engineer
dmc digital media center GmbH
Rommelstraße 11
70376 Stuttgart (Germany)
Telefon: +49 711 601747-0
Telefax: +49 711 601747-141
E-Mail: [EMAIL PROTECTED]
Internet: www.dmc.de

Handelsregister: AG Stuttgart HRB 18974
Geschäftsführer: Andreas Magg, Daniel Rebhorn, Andreas Schwend

-
Besseres E-Business.
dmc ist die kreative Vernetzung von Agentur, Systemhaus und Service. Seit
über 10 Jahren entwickeln und realisieren wir zukunftweisende und
erfolgreiche E-Business-Lösungen. Zu unseren langjährigen Kunden zählen
neckermann.de, Kodak und Telekom Training.

dmc auf Platz 8 im aktuellen New Media Service Ranking.
Als inhabergeführte und netzwerkunabhängige Agentur gehören wir mit einem
Umsatz von 13,50 Mio. Euro zu den Top 10 der erfolgreichsten New Media
Dienstleister in Deutschland.

Reset dataScroller

[Michael Böckling]

Hi!

I have a problem with t:dataScroller, it does not reset itself when the
underlying data model changes. When I click on the "first" button,
everything is well again. Is there a way to do this programmatically? In
JavaScript or in a backing bean?

Thanks for any help!


Michael


-- 
Michael Böckling
Java Engineer
dmc digital media center GmbH 
Rommelstraße 11 
70376 Stuttgart (Germany) 
Telefon: +49 711 601747-0
Telefax: +49 711 601747-141 
E-Mail: [EMAIL PROTECTED] 
Internet: www.dmc.de 

Handelsregister: AG Stuttgart HRB 18974
Geschäftsführer: Andreas Magg, Daniel Rebhorn, Andreas Schwend

-
Besseres E-Business.
dmc ist die kreative Vernetzung von Agentur, Systemhaus und Service. Seit
über 10 Jahren entwickeln und realisieren wir zukunftweisende und
erfolgreiche E-Business-Lösungen. Zu unseren langjährigen Kunden zählen
neckermann.de, Kodak und Telekom Training.

dmc auf Platz 8 im aktuellen New Media Service Ranking.
Als inhabergeführte und netzwerkunabhängige Agentur gehören wir mit einem
Umsatz von 13,50 Mio. Euro zu den Top 10 der erfolgreichsten New Media
Dienstleister in Deutschland.

Re: [Trinidad] Weblogic + Debug

[Francisco Passos]

Tried today's nightly build and the error no longer appears.

Thank you.
Francisco

On 5/30/07, Francisco Passos <[EMAIL PROTECTED]> wrote:


Excellent news!

Thank you,
Francisco

On 5/30/07, Adam Winer <[EMAIL PROTECTED]> wrote:
>
> http://issues.apache.org/jira/browse/TRINIDAD-44
>
> Fixed.
>
> -- Adam
>
>
> On 5/29/07, Francisco Passos < [EMAIL PROTECTED]> wrote:
> > Thank you.
> >
> > Are there plans to address this bug soon?
> >
> >
> > On 5/29/07, Adam Winer <[EMAIL PROTECTED] > wrote:
> > > Looks like a (minor) bug in Trinidad.  Code should be clearing
> > > RenderingContext.setCurrentClientId () but isn't, and the
> > assert
> > > is catching that.  We should be running our tests with asserts
> > > enabled, IMO, which I think would have caught this particular
> > > problem.
> > >
> > >
> > > -- Adam
> > >
> > >
> > > On 5/29/07, Francisco Passos < [EMAIL PROTECTED]> wrote:
> > > > Good afternoon.
> > > >
> > > > I'm developing an application with Trinidad on Weblogic
> Application
> > Server
> > > > 9.2.
> > > >
> > > > It works fine in normal circumstances, but whenever I start
> weblogic in
> > > > debug mode (to attach by socket in Eclipse), pages cease to render
> and
> > this
> > > > error is presented instead.
> > > >
> > > >
> > > >
> > > > Error 500--Internal Server Error
> > > > java.lang.AssertionError
> > > >  at
> > > >
> >
> 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.CommandButtonRenderer.encodeAll
> > > > (CommandButtonRenderer.java :75)
> > > >  at
> > > >
> > org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(
> CoreRenderer.java:184)
> > > >  at
> > > >
> > org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(
> UIXComponentBase.java:701)
> > > >
> > > >  at
> > > >
> > org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild (
> CoreRenderer.java:263)
> > > >  at
> > > >
> >
> 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelGroupLayoutRenderer.encodeChild
> > (PanelGroupLayoutRenderer.java:177)
> > > >
> > > >  at
> > > >
> >
> 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelGroupLayoutRenderer._encodeChildren
> (PanelGroupLayoutRenderer.java:143)
> > > >  at
> > > >
> >
> 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelGroupLayoutRenderer.encodeAll
> > > > (PanelGroupLayoutRenderer.java:95)
> > > >  at
> > > >
> > org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd (
> CoreRenderer.java:184)
> > > >  at
> > > >
> > org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd
> > (UIXComponentBase.java:701)
> > > >
> > > >  at
> > > >
> >
> org.apache.myfaces.trinidadinternal.uinode.UIComponentUINode._renderComponent
> (UIComponentUINode.java:336)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.uinode.UIComponentUINode.render
> > (UIComponentUINode.java:278)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.uinode.UIComponentUINode.render(
> UIComponentUINode.java:255)
> > > >  at
> > > >
> >
> 
org.apache.myfaces.trinidadinternal.ui.composite.ContextPoppingUINode$ContextPoppingRenderer.render
> > (ContextPoppingUINode.java
> > > > :235)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseUINode.render (
> BaseUINode.java:357)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseUINode.render(
> BaseUINode.java
> > :312)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseRenderer.renderChild
> > > > (BaseRenderer.java:424)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseRenderer.renderNamedChild(
> BaseRenderer.java
> > :396)
> > > >  at
> > > >
> >
> 
org.apache.myfaces.trinidadinternal.ui.laf.base.desktop.FooterRenderer.postrender
> (FooterRenderer.java
> > > > :80)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseRenderer.render (
> BaseRenderer.java
> > :94)
> > > >  at
> > > >
> >
> org.apache.myfaces.trinidadinternal.ui.laf.base.xhtml.XhtmlLafRenderer.render
> (XhtmlLafRenderer.java:83)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseUINode.render
> > > > (BaseUINode.java :357)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseUINode.render(
> BaseUINode.java :312)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseRenderer.renderChild(
> BaseRenderer.java:424)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseRenderer.renderIndexedChild
> > > > (BaseRenderer.java:342)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseRenderer.renderIndexedChild
> (BaseRenderer.java:234)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseRenderer.renderContent(
> BaseRenderer.java:141)
> > > >
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.BaseRenderer.render (
> BaseRenderer.java:92)
> > > >  at
> > > >
> >
> org.apache.myfaces.trinidadinternal.ui.laf.base.xhtml.XhtmlLafRenderer.render
> (XhtmlLafRenderer.java:83)
> > > >  at
> > > >
> > org.apache.myfaces.trinidadinternal.ui.Base

Re: [Trinidad] Note to tr:input... generated HTML

[Petr Kotek]

Yes, I must insert into trinidad-config.xml line:
INLINE
Without it, commandButton with action binding do nothing.

Peter

Adam Winer wrote:

Just to confirm - you're using INLINE client-validation?
I agree, the spacing would be better handled with CSS.

-- Adam


On 5/31/07, Petr Kotek <[EMAIL PROTECTED]> wrote:

Hi,

I have a little note to HTML code, generated by tr:input components in
label area. This code has changed in some latest release (I think) and
now look as:


  


  class="AFErrorIconStyle">X


 
Order No:
  
  


For next styling of label (for example for its vertical alignment before
multi line text input) I have big problems with " " included in
code. I think, that it will be better to avoid this " " (generally
- all hard coded formating) and space between icon and text realize by
right margin in icon element in base style?

Thanks for Your opinion,
Peter





--

Petr Kotek
CRC Data spol. s r.o.
U krčské vodárny 26 - vývojové pracoviště
140 00 Praha 4
tel: +420 241 442 464
fax: +420 241 442 645
GSM: +420 602 339 057
www.crcdata.cz 

Re: argument type mismatch when setting property with updateActionListener

[gazlm]

Hmmm, sounds like conversion may be a little overcomplicated for me right
now...

I'm not using Facelets at the mo, I'm going to try them out after I've got
to grips with JSF, so I think I'll just take the easy option and change the
bean API to use Number.

Thanks again.


Mike Kienenberger wrote:
> 
> Well, the problem is that javax.faces.Integer converts a string to an
> integer.
> You'd need to convert a Long to an integer.
> 
> I haven't actually used a converter on updateActionListener, but I'd
> think a Long to Integer converter should work.
> 
> If you're using facelets, you can write your own functions for doing
> conversion:
> 
> #{myFunctions:convertLongToInt(yourvalue)}
> 
> Realistically, since JSF generates Doubles and Longs, your best bet is
> to make your accessor be of type Number and then convert it in your
> bean code if you want it to be of a particular format.
> 
> Thus, when you have control over the bean api, make your type Number.
> 
> For those cases where  you don't,  you could put a wrapper accessor on
> your bean, either via subclassing or delegating.
> 
> public Number getPageNumber() { return new Integer(getPageNum()); }
> public void setPageNumber(Number number) { setPageNum(number.intValue());
> }
> 
> 
> On 5/31/07, gazlm <[EMAIL PROTECTED]> wrote:
>>
>> Cheers, Mike, that eases my confusion a little. I thought I might have
>> been
>> doing something wrong...
>>
>> Is it possible to convert the EL return value to the right type? The
>> updateActionListener docs state "An optional Converter may be associated
>> with this listener, and if present will be invoked to convert the value
>> to
>> the datatype expected by the target property."
>>
>> I tried using converter="javax.faces.Integer" to force the conversion to
>> an
>> int, but this got me nowhere at all.
>>
>> I'm pretty new to JSF, and I have the feeling I'm barking up the wrong
>> tree
>> - any help appreciated.
>>
>> Cheers,
>>
>>
>> Mike Kienenberger wrote:
>> >
>> >> Is it expected behaviour for an EL arithmetic expression to always
>> return
>> >> a
>> >> Long?
>> >
>> > Yes.  Or a Double if the value cannot be represented as a Long.
>> >
>> >
>> >
>> > On 5/31/07, gazlm <[EMAIL PROTECTED]> wrote:
>> >>
>> >> I have a problem with type conversions when using updateActionListener
>> to
>> >> set
>> >> an int property in a backing bean...
>> >>
>> >> I'm using a bean which has properties pageNum and numPages, and I have
>> >> command links that refresh the page, with an updateActionListener
>> >> changing
>> >> the value of the pageNum property.
>> >>
>> >> If I use the updateActionListener like this:
>> >>
>> >> 
>> >>
>> >> then I have no problems, but if I try to do something like this:
>> >>
>> >> > >> value="#{bean.pageNum+1}"
>> >> />
>> >>
>> >> then I get an exception:
>> >>
>> >> javax.faces.el.EvaluationException: Exception setting property
>> helloCount
>> >> of
>> >> base with class demo.GetNameBean, caused by an argument type mismatch.
>> >> The
>> >> full stack trace is attached below.
>> >>
>> >> From debugging through the code while running, it seems that when I do
>> >> any
>> >> arithmetic in a JSF EL expression, the result is a Long, which can't
>> be
>> >> used
>> >> as an argument when the required type is int.
>> >>
>> >> If I change my bean to accept a Long instead of an int, the problem
>> goes
>> >> away, but that doesn't seem ideal to me...
>> >>
>> >> Does anyone else have this problem?
>> >> Is it expected behaviour for an EL arithmetic expression to always
>> return
>> >> a
>> >> Long?
>> >>
>> >> Cheers.
>> >>
>> >> ERROR [[/testMyFaces].[Faces Servlet]:http-8080-Processor25] -
>> >> Servlet.service() for servlet Faces Servlet threw exception
>> >> javax.faces.el.EvaluationException: Exception setting property pageNum
>> of
>> >> base with class com.gaz.Bean
>> >> at
>> >>
>> org.apache.myfaces.el.PropertyResolverImpl.setValue(PropertyResolverImpl.java:185)
>> >> at
>> >>
>> org.apache.myfaces.el.ValueBindingImpl.setValue(ValueBindingImpl.java:275)
>> >> at
>> >>
>> org.apache.myfaces.custom.updateactionlistener.UpdateActionListener.processAction(UpdateActionListener.java:156)
>> >> at
>> >> javax.faces.event.ActionEvent.processListener(ActionEvent.java:48)
>> >> at
>> >>
>> javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:484)
>> >> at
>> javax.faces.component.UICommand.broadcast(UICommand.java:75)
>> >> at
>> >>
>> javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94)
>> >> at
>> >>
>> javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168)
>> >> at
>> >>
>> org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
>> >> at
>> >>
>> org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
>> >> at
>> javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
>> >> at
>> >>
>> org.apache.ca

Re: [Trinidad] Table navigation

[Stéphane Poirier]

Thanks for the quick answer and explainations! Beeing not very comfortable
with jsf phases (shame on me!), I decided to keep searching and I found
something very interresting which solved my problem and sounds like a clean
way to use the framework. Here's my information source:
http://mail-archives.apache.org/mod_mbox/myfaces-users/200612.mbox/[EMAIL 
PROTECTED]
...using my table bean in a "request" scope solves the serialization problem
while still making navigation work. Using the method described in this link
allows the control of data exchanged by pages using the pageFlowScope (oh my
own Beans). Problem solved!

Thanks for the help!

On 5/30/07, Chris Lowe <[EMAIL PROTECTED]> wrote:


Hello,

I think that quote came from me, which is a bit of a coincidence as I only
just switched from the old trinidad mailing list to myfaces a few hours ago.

To be honest, I've not used table pagination or server clustering so I'm
not even certain if the technique will work for you.  However here is
(hopefully) a better explanation...

The quote basically means:

Store your table data in a list rather than a DataModel. So when you call
getSomeDataModel() instead of using a cached instance of the DataModel that
is saved against the page bean, create a new instance each time and populate
if from a cached *list*.  There is one problem to this and that is when a
user clicks on a link in the table, then at INVOKE_APPLICATION the table's
data model needs to work out which row was clicked.  To do that properly it
needs a DataModel instance that was based on exactly the same list that was
used at time when the page was rendered. Otherwise it can't find the row and
you're table action may not be called. Hence use a cached version of list at
RESTORE_VIEW.

Later, if your table action results in the data model being changed then
you want the table to show the current data.  Reusing the cached list is no
good at this point since the table action may have deleted instances
or items may have been edited etc.  So refresh the list and store to cache
so that getSomeDataModel() will have an updated list when it is called
during RENDER_RESPONSE.

in pseudo code this translates to something like (it's been a while since
I looked this):

DataModel getSomeDataModel() {
  return new DataModel(getList());
}

List getList() {
  return getSessionBean().getCachedList();
}

// does your page backing bean have a method of getting at JSF lifecycle
events?  E.g. in Java Studio Creator you get this:
void beforePhase(PhaseEvent evt) {
  if (evt.getPhaseId() == PhaseId.RENDER_RESPONSE) {
List list = refreshList();
getSessionBean().setCachedList(list);
  }
}


Hopefully that helps?

Cheers,

Chris.


On 5/30/07, Stéphane Poirier <[EMAIL PROTECTED] > wrote:
>
> Hi,
>
> My problem is simple, yet I can't solve it : I have 2 pages in my web
> application. "Page 1" contains a  with page navigation (a
> scroller) with items. Clicking on a item leads to "Page 2" which displays
> the detail of the clicked item. A bean is associated to each page. I used to
> store the DataModel in my "Page 1" Bean and to fetch the current row
> (getRowData) in my "Page 2" and display the data. The problem is the my
> cluster requires serializable components... DataModel is not.
>
> I've seen a plenty of solutions but they are not detailed enought for me
> to understand how to implant them. I would like to know the "right" way to
> do this.
>
> A solution I've heard of (not clear enought for me):
>
> > > A general JSF solution to this would be to store your data model (or
> > > whatever collection that drives the datamodel) in a session bean which
> > will
> > > serve as a data cache between requests. In the restore view phase - use
>
> > the
> > > cached version; in prerender phase refresh the cached list.  It ain't
> > pretty
> > > - but it worked for me.
>
>
> Thanks in advance!
>

Re: [Trinidad] GWT Integration

[Adam Winer]

Ah, I see.  You're using "server" state saving, so using the
underlying JSF implementation to save state.  The
Trinidad StateManager (used for client state saving) doesn't
use colons.

-- Adam


On 5/30/07, D. Cardon <[EMAIL PROTECTED]> wrote:

I was looking at the StateManagerImpl class of the com.sun.faces.application 
package, line number
116 in jsf-impl-1.2_03.  It seems like it uses a ':' separator character in 
restoring the view...

Anyway, it turns out I was able to get it working anyway.  After looking at the 
HTML generated,
some process inserted the view state variable as a hidden input of my GWT 
component's 'span'
element.  So, I just used GWT to find that element and add it to the request 
parameters on a GWT
event.  The HTML of the input looked like this:



So, as you can see, the colon is being used here in some way or another.  I'm 
not sure exactly
what role it plays, but it certainly appears to be necessary.

Thanks for your help!

--David


--- Adam Winer <[EMAIL PROTECTED]> wrote:

> That doesn't sound right - we don't expect a colon at all
> in the state token.  What line of code are you looking at?
>
> -- Adam
>
>
> On 5/30/07, D. Cardon <[EMAIL PROTECTED]> wrote:
> > Adam,
> >
> > Thanks for the info!
> >
> > Since I'm using the trunk, the org.apache.myfaces.trinidad.faces.STATE is 
what needs to be
> sent
> > (at least, that's what's listed in my CoreResponseStateManager class).
> >
> > So, I now have the GWT request send that variable set to its component's 
id.  I.e., the GWT
> widget
> > in the component tree looks like this:
> >
> > 
> >
> > When the GWT request is issued, then 
org.apache.myfaces.trinidad.faces.STATE=!j_id29 is sent.
> > However, this causes an index out of bounds error in the StateManagerImpl 
class--apparently,
> it is
> > looking for a string value that looks like:
> >
> > someId:anotherId
> >
> > Since the value I send does not have a colon in it, then I've confused it.  
I couldn't figure
> out
> > what the StateManager is expecting, even after some searching around.  As 
far as my
> requirements,
> > all I really need is for just the GWT component to be constructed on the 
postback.
> >
> > So, how should I format the state string in the request so that trinidad / 
JSF will understand
> it?
> >
> > Thanks again for your help,
> >
> > --David
> >
> > --- Adam Winer <[EMAIL PROTECTED]> wrote:
> >
> > > The Trinidad 1.2 code sends javax.faces.ViewState (the 1.2 spec
> > > requires this), but the trunk doesn't, instead sending
> > > org.apache.myfaces.trinidad.faces.STATE.  If you're using JSF 1.2,
> > > you could (and should) use the Trinidad 1.2 code.
> > >
> > > -- Adam
> > >
> > >
> > >
> > > On 5/29/07, D. Cardon <[EMAIL PROTECTED]> wrote:
> > > > Thanks for your response, I looked into it and found out that when 
G4JSF builds its
> request,
> > > it
> > > > send the javax.faces.ViewState variable in the request.  Do I need to 
have it send
> something
> > > > different for Trinidad?
> > > >
> > > > --David
> > > >
> > > > --- Adam Winer <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > If there's no tree, I suspect that the state parameter is
> > > > > not getting submitted.  Check the G4JSF code to see if
> > > > > it has hardcoded a list of request parameters to submit.
> > > > >
> > > > > -- Adam
> > > > >
> > > > >
> > > > > On 5/29/07, D. Cardon <[EMAIL PROTECTED]> wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > I'm using MyFaces Trinidad and am integrating the Google Web 
Toolkit (GWT) to work
> along
> > > with
> > > > > it.
> > > > > > I am using the G4JSF project along with some of my own 
modifications.  So far,
> everything
> > > on
> > > > > the
> > > > > > client side is working just fine, but I am having difficulty 
communicating with the
> server
> > > > > when
> > > > > > the GWT fires an event.  Since the G4JSF project works just fine 
without Trinidad, I
> > > figured a
> > > > > > little  enlightenment on Trinidad's workings would be very helpful.
> > > > > >
> > > > > > Here's the part of the process that is having problems:
> > > > > >
> > > > > > 1. The G4JSF project latches correctly onto the GWT event, which is 
correctly parsed
> from
> > > the
> > > > > > client's request.
> > > > > >
> > > > > > 2. G4JSF implements a phase listener, which propagates the GWT 
event after the Restore
> > > View
> > > > > phase
> > > > > > has completed.
> > > > > >
> > > > > > 3. After the restore view phase completes, the phase listener's 
code correctly runs,
> but
> > > the
> > > > > > component tree is not "restored".  That is, there IS a view root 
available, but it has
> no
> > > > > > children.  So, when "invokeOnComponent" is called on the 
facesContext.getViewRoot(),
> the
> > > GWT
> > > > > event
> > > > > > never makes it to the GWT component.  Also, I noticed that the
> > > > > > 
org.apache.myfaces.trinidadinternal.context.AdfFacesPhaseListener.POSTBACK variable in
> the
> > > > > request
> > > > > > is set to 'false'.
> > > > > >

Re: [Trinidad] Note to tr:input... generated HTML

[Adam Winer]

Just to confirm - you're using INLINE client-validation?
I agree, the spacing would be better handled with CSS.

-- Adam


On 5/31/07, Petr Kotek <[EMAIL PROTECTED]> wrote:

Hi,

I have a little note to HTML code, generated by tr:input components in
label area. This code has changed in some latest release (I think) and
now look as:


  


  X

 
Order No:
  
  


For next styling of label (for example for its vertical alignment before
multi line text input) I have big problems with " " included in
code. I think, that it will be better to avoid this " " (generally
- all hard coded formating) and space between icon and text realize by
right margin in icon element in base style?

Thanks for Your opinion,
Peter

Re: Strange Trinidad behaviour after upgrading to JBoss 4.2.0

[Adam Winer]

Well, we've got a lot of variables here.  It's a little
suspicious to me hearing that an Ajax4JSF filter is
now required, when this behavior doesn't appear to
be reproducing for other users of Trinidad 1.2.

I'd try, for example, the same page without Ajax4JSF
installed - if that means taking Seam out of the picture
for that one page, OK.

I'd also try deploying the same app to Glassfish -
if it reproduces there, then we know it's not JBoss
specific.

BTW, USE_APPLICATION_VIEW_CACHE=false
is the default, so setting that won't change anything.
Another random thing to try is setting
org.apache.myfaces.trinidad.CACHE_VIEW_ROOT
to false.  That will be a change from the default.
It throws away an extremely valuable optimization,
but it also might help point out where things are going
wrong.

-- Adam


On 5/30/07, Chris Lowe <[EMAIL PROTECTED]> wrote:

Is there anything I can do to help narrow this down?



On 5/30/07, Adam Winer <[EMAIL PROTECTED]> wrote:
> Hrm, that looks like the same version as Glassfish!  I
> didn't know they were using the RI.  So scrap that theory!
> It still *might* be something wrong in JBoss (maybe their
> implementation of JspIdConsumer in the JSP engine?),
> but this is more puzzling.
>
> -- Adam
>
>
> On 5/30/07, Chris Lowe < [EMAIL PROTECTED]> wrote:
> > Thanks for the reply Adam.
> >
> > Do you happen to know what version of JSF Glassfish is using?
> >
> > From jsf-api.jar that is with JBoss 4.2.0.GA, the manifest states:
> >
> > Manifest-Version: 1.0
> > Specification-Title: JavaServer Faces
> > Created-By: 1.5.0_04-b05 (Sun Microsystems Inc.)
> > Ant-Version: Apache Ant 1.6.5
> > Implementation-Title: Sun Microsystems JavaServer Faces Implementation
> > Specification-Vendor: JBoss (http://www.jboss.org/)
> > Specification-Version: 1.2MR1
> > Implementation-Vendor-Id: com.sun
> > Extension-Name: javax.faces
> > Implementation-Version: 1.2_04-b10-p01
> > Implementation-Vendor: Sun Microsystems, Inc.
> > Implementation-URL: http://www.jboss.org/
> > Cheers,
> >
> > Chris.
> >
> >
> >
> > On 5/30/07, Adam Winer <[EMAIL PROTECTED]> wrote:
> > > I suspect that there's something wrong with
> > > the implementation of JSF 1.2 used by JBoss, probably
> > > in that implementation's UIComponentClassicTagBase
> > > code or something similar.  The behavior you're describing
> > > doesn't occur with Glassfish.
> > >
> > > -- Adam
> > >
> > >
> > > On 5/30/07, Chris Lowe < [EMAIL PROTECTED]> wrote:
> > > > Hello,
> > > >
> > > > I have a project that is running Trinidad and I recently upgraded to
> > JBoss
> > > > 4.2.0.GA.  As part of this upgrade I also migrated to JSF 1.2 (the
> > latest
> > > > Seam version requires me to do this).  Ever since then, whenever I
> > submit a
> > > > form that fails validation, the form renders the correct validation
> > messages
> > > > but I get some weird rendering of the form. It's actually like the
> > previous
> > > > HTML doesn't get cleared and the new form + validation errors gets
> > tacked
> > > > onto the end - I'm literally seeing double. If I click my submit
button
> > > > again, then a third instance will be tacked onto the bottom, and so
on.
> > If
> > > > at this point I simply refresh the page, then everything resets back
to
> > > > normal. If I use the application without causing validation errors
then
> > > > everything works as normal. I get the same behaviour on FireFox and
IE
> > and
> > > > there are no exceptions in the logs.
> > > >
> > > > I tried updating the Trinidad build to
> > trinidad-*-1.2-07-may-SNAPSHOT.jar,
> > > > but to no avail.
> > > >
> > > > I eventually tracked the strange behaviour down to my usage of
> > ,
> > > > if I use a vanilla body tag then the page duplication problem goes.
> > > > However, I still get similar issues with  - the
instance
> > of
> > > > the link is duplicated with each form submission that causes a
> > validation
> > > > error.  Changing to  again, resolves this issue.
> > > >
> > > > Has anyone come across this before?
> > > >
> > > > Cheers,
> > > >
> > > > Chris.
> > > >
> > >
> >
> >
>

Re: java.lang.IllegalArgumentException: Value is no String

[Andrew Robinson]

Menu is the same as well:

public class HtmlSelectOneMenu
 extends org.apache.myfaces.component.html.ext.HtmlSelectOneMenu
{
 /**
  * @see javax.faces.component.UIInput#setSubmittedValue(java.lang.Object)
  */
 @Override
 public void setSubmittedValue(Object submittedValue)
 {
   if (submittedValue == RendererUtils.NOTHING ||
 submittedValue ==
org.apache.myfaces.shared_impl.renderkit.RendererUtils.NOTHING)
 submittedValue = null;
   super.setSubmittedValue(submittedValue);
 }
}


On 5/31/07, Andrew Robinson <[EMAIL PROTECTED]> wrote:

Yes, I extended the myfaces class to fix the bug:

public class HtmlSelectOneRadio
  extends org.apache.myfaces.component.html.ext.HtmlSelectOneRadio
{
  /**
   * @see javax.faces.component.UIInput#setSubmittedValue(java.lang.Object)
   */
  @Override
  public void setSubmittedValue(Object submittedValue)
  {
if (submittedValue == RendererUtils.NOTHING ||
  submittedValue ==
org.apache.myfaces.shared_impl.renderkit.RendererUtils.NOTHING)
  submittedValue = null;
super.setSubmittedValue(submittedValue);
  }
}

On 5/30/07, Celso Nishioka <[EMAIL PROTECTED]> wrote:
> Andrew, I'm having the same issue.
>
> Did you get it solved?
>
> Thanks.
>
>
> On 11/29/06, Andrew Robinson < [EMAIL PROTECTED]> wrote:
> > No that hasn't changed, I just checked the source. If you look at the
> > stack trace, somehow the value is an instance of
> >
> "org.apache.myfaces.shared_tomahawk.renderkit.RendererUtils$1"
> -- it
> > is not null inside the
> "RendererUtils.getConvertedStringValue" method.
> >
> > How in the world that happened is beyond me.
> >
> > -Andrew
> >
> > On 11/29/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
> > > Andrew,
> > >
> > > Looking at the current code, it shouldn't throw that against a null
> > > value. Maybe they've changed this since your version? Perhaps you could
> > > try with the nightlies just to see if the same behavior happens?
> > >
> > > RenderUtils
> > > 
> > > public static String
> getConvertedStringValue(FacesContext context,
> > >
> UIComponent component,
> > > Converter converter, Object value) {
> > >  if (converter == null) {
> > >  if (value == null) {
> > >  return "";
> > >  }
> > >  else if (value instanceof String) {
> > >  return (String) value;
> > >  }
> > >  else {
> > >  throw new IllegalArgumentException(
> > >  "Value is no String (class=" +
> > > value.getClass().getName() + ", value=" + value + ") and component "
> > >  + component.getClientId (context) + "with path:
> "
> > >  + getPathToComponent(component)
> > >  + " does not have a Converter");
> > >  }
> > >  }
> > >
> > >  return converter.getAsString(context, component, value);
> > >  }
> > > ---
> > >
> > > Maybe your version is missing the lines:
> > >
> > > if (value == null) {
> > > return "";
> > > }
> > >
> > > Regards,
> > >
> > > Jeff Bischoff
> > > Kenneth L Kurz & Associates, Inc.
> > >
> > > Andrew Robinson wrote:
> > > > Yes that is correct, it was always null but only failed to render the
> > > > 3rd request.
> > > >
> > > > On 11/29/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
> > > >> Well the reason it doesn't work is because of the null.
> > > >>
> > > >> Are you saying it was set to null the whole time, and only failed on
> the
> > > >> 3rd request (after having canceled the dialog once)?
> > > >>
> > > >> Regards,
> > > >>
> > > >> Jeff Bischoff
> > > >> Kenneth L Kurz & Associates, Inc.
> > > >>
> > > >> Andrew Robinson wrote:
> > > >> > Found a work around -->
> > > >> > if " value.typeText" is set to one of the values instead of null I
> > > >> > don't get the exception. What I don't understand is why it works
> the
> > > >> > other times but not the 3rd AJAX call.
> > > >> >
> > > >> > On 11/29/06, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> > > >> >> I am getting a bit stuck on this one exception. I have two
> > > >> >> selectOneRadio components within an included facelet (source file)
> > > >> >> that bind to a property on a facelet attribute. The value is a
> custom
> > > >> >> bean with string properties and the select items have string
> values,
> > > >> >> so no converter should be needed. What is odd is that this
> behavior is
> > > >> >> not constant.
> > > >> >>
> > > >> >> Setup:
> > > >> >> index.xhtml defines this component:
> > > >> >>  > > >> >>   id="liveReportFilterDlg"
> > > >> >>   ajaxZone="reportListZone"
> > > >> >>
> rendered="#{liveReportBean.filterDialogVisible}"
> > > >> >>
> onAcceptListener="#{liveReportBean.filterDialogAccepted}"
> > > >> >>   onCancelListener="#{
> liveReportBean.filterDialogCanceled}"
> > > >> >>   value="#{liveReportBean.filter}" />
> > > >> >>
> > > >> >> It is this "value" that I us

Re: java.lang.IllegalArgumentException: Value is no String

[Andrew Robinson]

Yes, I extended the myfaces class to fix the bug:

public class HtmlSelectOneRadio
 extends org.apache.myfaces.component.html.ext.HtmlSelectOneRadio
{
 /**
  * @see javax.faces.component.UIInput#setSubmittedValue(java.lang.Object)
  */
 @Override
 public void setSubmittedValue(Object submittedValue)
 {
   if (submittedValue == RendererUtils.NOTHING ||
 submittedValue ==
org.apache.myfaces.shared_impl.renderkit.RendererUtils.NOTHING)
 submittedValue = null;
   super.setSubmittedValue(submittedValue);
 }
}

On 5/30/07, Celso Nishioka <[EMAIL PROTECTED]> wrote:

Andrew, I'm having the same issue.

Did you get it solved?

Thanks.


On 11/29/06, Andrew Robinson < [EMAIL PROTECTED]> wrote:
> No that hasn't changed, I just checked the source. If you look at the
> stack trace, somehow the value is an instance of
>
"org.apache.myfaces.shared_tomahawk.renderkit.RendererUtils$1"
-- it
> is not null inside the
"RendererUtils.getConvertedStringValue" method.
>
> How in the world that happened is beyond me.
>
> -Andrew
>
> On 11/29/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
> > Andrew,
> >
> > Looking at the current code, it shouldn't throw that against a null
> > value. Maybe they've changed this since your version? Perhaps you could
> > try with the nightlies just to see if the same behavior happens?
> >
> > RenderUtils
> > 
> > public static String
getConvertedStringValue(FacesContext context,
> >
UIComponent component,
> > Converter converter, Object value) {
> >  if (converter == null) {
> >  if (value == null) {
> >  return "";
> >  }
> >  else if (value instanceof String) {
> >  return (String) value;
> >  }
> >  else {
> >  throw new IllegalArgumentException(
> >  "Value is no String (class=" +
> > value.getClass().getName() + ", value=" + value + ") and component "
> >  + component.getClientId (context) + "with path:
"
> >  + getPathToComponent(component)
> >  + " does not have a Converter");
> >  }
> >  }
> >
> >  return converter.getAsString(context, component, value);
> >  }
> > ---
> >
> > Maybe your version is missing the lines:
> >
> > if (value == null) {
> > return "";
> > }
> >
> > Regards,
> >
> > Jeff Bischoff
> > Kenneth L Kurz & Associates, Inc.
> >
> > Andrew Robinson wrote:
> > > Yes that is correct, it was always null but only failed to render the
> > > 3rd request.
> > >
> > > On 11/29/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
> > >> Well the reason it doesn't work is because of the null.
> > >>
> > >> Are you saying it was set to null the whole time, and only failed on
the
> > >> 3rd request (after having canceled the dialog once)?
> > >>
> > >> Regards,
> > >>
> > >> Jeff Bischoff
> > >> Kenneth L Kurz & Associates, Inc.
> > >>
> > >> Andrew Robinson wrote:
> > >> > Found a work around -->
> > >> > if " value.typeText" is set to one of the values instead of null I
> > >> > don't get the exception. What I don't understand is why it works
the
> > >> > other times but not the 3rd AJAX call.
> > >> >
> > >> > On 11/29/06, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> > >> >> I am getting a bit stuck on this one exception. I have two
> > >> >> selectOneRadio components within an included facelet (source file)
> > >> >> that bind to a property on a facelet attribute. The value is a
custom
> > >> >> bean with string properties and the select items have string
values,
> > >> >> so no converter should be needed. What is odd is that this
behavior is
> > >> >> not constant.
> > >> >>
> > >> >> Setup:
> > >> >> index.xhtml defines this component:
> > >> >>  > >> >>   id="liveReportFilterDlg"
> > >> >>   ajaxZone="reportListZone"
> > >> >>
rendered="#{liveReportBean.filterDialogVisible}"
> > >> >>
onAcceptListener="#{liveReportBean.filterDialogAccepted}"
> > >> >>   onCancelListener="#{
liveReportBean.filterDialogCanceled}"
> > >> >>   value="#{liveReportBean.filter}" />
> > >> >>
> > >> >> It is this "value" that I use within the
> > >> "liveReportFilterDialog.xhtml":
> > >> >>
> > >> >>> >> >> id="#{id}TypeOptions"
> > >> >> value="#{ value.typeText}"
> > >> >> layout="pageDirection"
> > >> >> required="true">
> > >> >>  > >> >>   itemLabel="#{
msg.liverep_filterdlg_typefilter_graph}"
> > >> >>   itemValue="osoft/livechart" />
> > >> >>  > >> >>
itemLabel="#{msg.liverep_filterdlg_typefilter_report }"
> > >> >>   itemValue="osoft/livereport" />
> > >> >>  > >> >>
itemLabel="#{msg.liverep_filterdlg_typefilter_schedule }"
> > >> >>   itemValue="osoft/liveschedule" />
> > >> >>   
> > >> >>
> > >> >> The other radio is:
> > >> >>
> > >> >>> >> >> layout="pageDirection">
> > >> >>  > >> >>   itemValue="ALL" />
> > >> >>  > >> 

Re: argument type mismatch when setting property with updateActionListener

[Mike Kienenberger]

Well, the problem is that javax.faces.Integer converts a string to an integer.
You'd need to convert a Long to an integer.

I haven't actually used a converter on updateActionListener, but I'd
think a Long to Integer converter should work.

If you're using facelets, you can write your own functions for doing conversion:

#{myFunctions:convertLongToInt(yourvalue)}

Realistically, since JSF generates Doubles and Longs, your best bet is
to make your accessor be of type Number and then convert it in your
bean code if you want it to be of a particular format.

Thus, when you have control over the bean api, make your type Number.

For those cases where  you don't,  you could put a wrapper accessor on
your bean, either via subclassing or delegating.

public Number getPageNumber() { return new Integer(getPageNum()); }
public void setPageNumber(Number number) { setPageNum(number.intValue()); }


On 5/31/07, gazlm <[EMAIL PROTECTED]> wrote:


Cheers, Mike, that eases my confusion a little. I thought I might have been
doing something wrong...

Is it possible to convert the EL return value to the right type? The
updateActionListener docs state "An optional Converter may be associated
with this listener, and if present will be invoked to convert the value to
the datatype expected by the target property."

I tried using converter="javax.faces.Integer" to force the conversion to an
int, but this got me nowhere at all.

I'm pretty new to JSF, and I have the feeling I'm barking up the wrong tree
- any help appreciated.

Cheers,


Mike Kienenberger wrote:
>
>> Is it expected behaviour for an EL arithmetic expression to always return
>> a
>> Long?
>
> Yes.  Or a Double if the value cannot be represented as a Long.
>
>
>
> On 5/31/07, gazlm <[EMAIL PROTECTED]> wrote:
>>
>> I have a problem with type conversions when using updateActionListener to
>> set
>> an int property in a backing bean...
>>
>> I'm using a bean which has properties pageNum and numPages, and I have
>> command links that refresh the page, with an updateActionListener
>> changing
>> the value of the pageNum property.
>>
>> If I use the updateActionListener like this:
>>
>> 
>>
>> then I have no problems, but if I try to do something like this:
>>
>> > value="#{bean.pageNum+1}"
>> />
>>
>> then I get an exception:
>>
>> javax.faces.el.EvaluationException: Exception setting property helloCount
>> of
>> base with class demo.GetNameBean, caused by an argument type mismatch.
>> The
>> full stack trace is attached below.
>>
>> From debugging through the code while running, it seems that when I do
>> any
>> arithmetic in a JSF EL expression, the result is a Long, which can't be
>> used
>> as an argument when the required type is int.
>>
>> If I change my bean to accept a Long instead of an int, the problem goes
>> away, but that doesn't seem ideal to me...
>>
>> Does anyone else have this problem?
>> Is it expected behaviour for an EL arithmetic expression to always return
>> a
>> Long?
>>
>> Cheers.
>>
>> ERROR [[/testMyFaces].[Faces Servlet]:http-8080-Processor25] -
>> Servlet.service() for servlet Faces Servlet threw exception
>> javax.faces.el.EvaluationException: Exception setting property pageNum of
>> base with class com.gaz.Bean
>> at
>> 
org.apache.myfaces.el.PropertyResolverImpl.setValue(PropertyResolverImpl.java:185)
>> at
>> org.apache.myfaces.el.ValueBindingImpl.setValue(ValueBindingImpl.java:275)
>> at
>> 
org.apache.myfaces.custom.updateactionlistener.UpdateActionListener.processAction(UpdateActionListener.java:156)
>> at
>> javax.faces.event.ActionEvent.processListener(ActionEvent.java:48)
>> at
>> javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:484)
>> at javax.faces.component.UICommand.broadcast(UICommand.java:75)
>> at
>> javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94)
>> at
>> javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168)
>> at
>> 
org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
>> at
>> org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
>> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
>> at
>> 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>> at
>> 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>> at
>> 
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
>> at
>> 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>> at
>> 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>> at
>> 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>> at
>> 
org.apache.catalina.core.StandardContextValve.invoke(StandardConte

Re: argument type mismatch when setting property with updateActionListener

[gazlm]

Cheers, Mike, that eases my confusion a little. I thought I might have been
doing something wrong...

Is it possible to convert the EL return value to the right type? The
updateActionListener docs state "An optional Converter may be associated
with this listener, and if present will be invoked to convert the value to
the datatype expected by the target property."

I tried using converter="javax.faces.Integer" to force the conversion to an
int, but this got me nowhere at all.

I'm pretty new to JSF, and I have the feeling I'm barking up the wrong tree
- any help appreciated.

Cheers,


Mike Kienenberger wrote:
> 
>> Is it expected behaviour for an EL arithmetic expression to always return
>> a
>> Long?
> 
> Yes.  Or a Double if the value cannot be represented as a Long.
> 
> 
> 
> On 5/31/07, gazlm <[EMAIL PROTECTED]> wrote:
>>
>> I have a problem with type conversions when using updateActionListener to
>> set
>> an int property in a backing bean...
>>
>> I'm using a bean which has properties pageNum and numPages, and I have
>> command links that refresh the page, with an updateActionListener
>> changing
>> the value of the pageNum property.
>>
>> If I use the updateActionListener like this:
>>
>> 
>>
>> then I have no problems, but if I try to do something like this:
>>
>> > value="#{bean.pageNum+1}"
>> />
>>
>> then I get an exception:
>>
>> javax.faces.el.EvaluationException: Exception setting property helloCount
>> of
>> base with class demo.GetNameBean, caused by an argument type mismatch.
>> The
>> full stack trace is attached below.
>>
>> From debugging through the code while running, it seems that when I do
>> any
>> arithmetic in a JSF EL expression, the result is a Long, which can't be
>> used
>> as an argument when the required type is int.
>>
>> If I change my bean to accept a Long instead of an int, the problem goes
>> away, but that doesn't seem ideal to me...
>>
>> Does anyone else have this problem?
>> Is it expected behaviour for an EL arithmetic expression to always return
>> a
>> Long?
>>
>> Cheers.
>>
>> ERROR [[/testMyFaces].[Faces Servlet]:http-8080-Processor25] -
>> Servlet.service() for servlet Faces Servlet threw exception
>> javax.faces.el.EvaluationException: Exception setting property pageNum of
>> base with class com.gaz.Bean
>> at
>> org.apache.myfaces.el.PropertyResolverImpl.setValue(PropertyResolverImpl.java:185)
>> at
>> org.apache.myfaces.el.ValueBindingImpl.setValue(ValueBindingImpl.java:275)
>> at
>> org.apache.myfaces.custom.updateactionlistener.UpdateActionListener.processAction(UpdateActionListener.java:156)
>> at
>> javax.faces.event.ActionEvent.processListener(ActionEvent.java:48)
>> at
>> javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:484)
>> at javax.faces.component.UICommand.broadcast(UICommand.java:75)
>> at
>> javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94)
>> at
>> javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168)
>> at
>> org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
>> at
>> org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
>> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>> at
>> org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>> at
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>> at
>> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>> at
>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>> at
>> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
>> at
>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>> at j

Re: [ Tobago ] get Sheet Object Referance when page submitted with actionListener

[Volker Weber]

Hi Madan,

see this thread:

http://www.nabble.com/-Tobago--using-value-from-tc%3Alink-on-server-tf3466446.html


Regards,
   Volker

2007/5/31, Madan Narra <[EMAIL PROTECTED]>:

Hi All,

I have an Array which is set to render a sheet in the Tobago Page.

I have a button which does a navigation.

In order to so some action before navigating, i placed
actionListener="#{bean.method}" , immediate="true" for .

As i set immediate="true", the variables are not set into the bean

Now i need to get the instance of the Array object which is set to
 in method(ActionEvent event) .

How can i proceed with this ?

--
Regards,
Madan N

Re: Will myFaces 1.0_9 work with JSF 1.2?

[Mike Kienenberger]

Supposedly 1.1 and 1.2 are backward-compatible.It should work
fine, but there will probably be unforseen issues :-)

On 5/15/07, Robert Lin <[EMAIL PROTECTED]> wrote:





Hi,



I'm planning to upgrade to JSF 1.2, but I still have myFaces 1.0 and would
like to wait until myFaces 1.2 is officially released to upgrade myFaces.  I
was wondering if this kind of setup will work, will there be any potential
problems?



Thanks.



__



Robert I. Lin

Software Engineer | NextLabs, Inc. (formerly Blue Jungle, Inc.) | San Mateo,
CA

(650) 577-9101 Ext. 225

http://www.nextlabs.com

http://www.linkedin.com/in/robertlin

Re: Change valueBinding of t:dataTable based on condition

[Mike Kienenberger]

Your  understanding of value binding syntax is incorrect.

Try this:

 wrote:





Hi!



I was just curious, is there any way I can change the value of a dataTable
based on different conditions?



I'll try to give a simple example to explain what I want. :)



Let's say I use the graphicImage tag, in the value property I could either
write the path to the image

Re: argument type mismatch when setting property with updateActionListener

[Mike Kienenberger]

Is it expected behaviour for an EL arithmetic expression to always return a
Long?


Yes.  Or a Double if the value cannot be represented as a Long.



On 5/31/07, gazlm <[EMAIL PROTECTED]> wrote:


I have a problem with type conversions when using updateActionListener to set
an int property in a backing bean...

I'm using a bean which has properties pageNum and numPages, and I have
command links that refresh the page, with an updateActionListener changing
the value of the pageNum property.

If I use the updateActionListener like this:



then I have no problems, but if I try to do something like this:



then I get an exception:

javax.faces.el.EvaluationException: Exception setting property helloCount of
base with class demo.GetNameBean, caused by an argument type mismatch. The
full stack trace is attached below.

From debugging through the code while running, it seems that when I do any
arithmetic in a JSF EL expression, the result is a Long, which can't be used
as an argument when the required type is int.

If I change my bean to accept a Long instead of an int, the problem goes
away, but that doesn't seem ideal to me...

Does anyone else have this problem?
Is it expected behaviour for an EL arithmetic expression to always return a
Long?

Cheers.

ERROR [[/testMyFaces].[Faces Servlet]:http-8080-Processor25] -
Servlet.service() for servlet Faces Servlet threw exception
javax.faces.el.EvaluationException: Exception setting property pageNum of
base with class com.gaz.Bean
at
org.apache.myfaces.el.PropertyResolverImpl.setValue(PropertyResolverImpl.java:185)
at
org.apache.myfaces.el.ValueBindingImpl.setValue(ValueBindingImpl.java:275)
at
org.apache.myfaces.custom.updateactionlistener.UpdateActionListener.processAction(UpdateActionListener.java:156)
at javax.faces.event.ActionEvent.processListener(ActionEvent.java:48)
at
javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:484)
at javax.faces.component.UICommand.broadcast(UICommand.java:75)
at 
javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94)
at 
javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168)
at
org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
at
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.faces.el.EvaluationException: Bean: com.gaz.Bean, property:
pageNum
at
org.apache.myfaces.el.PropertyResolverImpl.setProperty(PropertyResolverImpl.java:410)
at
org.apache.myfaces.el.PropertyResolverImpl.setValue(PropertyResolverImpl.java:173)
... 27 more
Caused by: java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.myfaces.el.PropertyResolverImpl.setProperty(PropertyResolverImpl.java:406)
... 28 more

--
View this message in context: 
http://www.nabble.com/argument-type-mismatch-when-setting-property-with-updateActi

argument type mismatch when setting property with updateActionListener

[gazlm]

I have a problem with type conversions when using updateActionListener to set
an int property in a backing bean...

I'm using a bean which has properties pageNum and numPages, and I have
command links that refresh the page, with an updateActionListener changing
the value of the pageNum property.

If I use the updateActionListener like this:



then I have no problems, but if I try to do something like this:



then I get an exception:

javax.faces.el.EvaluationException: Exception setting property helloCount of
base with class demo.GetNameBean, caused by an argument type mismatch. The
full stack trace is attached below.

>From debugging through the code while running, it seems that when I do any
arithmetic in a JSF EL expression, the result is a Long, which can't be used
as an argument when the required type is int.

If I change my bean to accept a Long instead of an int, the problem goes
away, but that doesn't seem ideal to me...

Does anyone else have this problem?
Is it expected behaviour for an EL arithmetic expression to always return a
Long?

Cheers.

ERROR [[/testMyFaces].[Faces Servlet]:http-8080-Processor25] -
Servlet.service() for servlet Faces Servlet threw exception
javax.faces.el.EvaluationException: Exception setting property pageNum of
base with class com.gaz.Bean
at
org.apache.myfaces.el.PropertyResolverImpl.setValue(PropertyResolverImpl.java:185)
at
org.apache.myfaces.el.ValueBindingImpl.setValue(ValueBindingImpl.java:275)
at
org.apache.myfaces.custom.updateactionlistener.UpdateActionListener.processAction(UpdateActionListener.java:156)
at javax.faces.event.ActionEvent.processListener(ActionEvent.java:48)
at
javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:484)
at javax.faces.component.UICommand.broadcast(UICommand.java:75)
at 
javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94)
at 
javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168)
at
org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
at
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.faces.el.EvaluationException: Bean: com.gaz.Bean, property:
pageNum
at
org.apache.myfaces.el.PropertyResolverImpl.setProperty(PropertyResolverImpl.java:410)
at
org.apache.myfaces.el.PropertyResolverImpl.setValue(PropertyResolverImpl.java:173)
... 27 more
Caused by: java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.myfaces.el.PropertyResolverImpl.setProperty(PropertyResolverImpl.java:406)
... 28 more

-- 
View this message in context: 
http://www.nabble.com/argument-type-mismatch-when-setting-property-with-updateActionListener-tf3846565.html#a10894017
Sent from the MyFaces - Users mailing list archive at Nabble.com.

About donate drag and drop components to myfaces sandbox

[Rogerio Pereira]

Hi guys!

I'll donate my draggable and droppable containers to myfaces sandbox, the
patches will be sent to Jira ASAP!

--
Yours truly (Atenciosamente),

Rogério (_rogerio_)
http://faces.eti.br

"Faça a diferença! Ajude o seu país a crescer, não retenha conhecimento,
distribua e aprenda mais." (http://faces.eti.br/?p=45)

panelNavigation2 collapses when choosing one menu choice but not another?

[Bjørn T Johansen]

I have a panelNavigation2 menu with 4 menu choices and when I choose one of 
them, the menu stays open
and the selected choice is highlighted. But if I choose a different menu 
choice, the new page is displayed but the
menu is collapsed. I can't find any difference between those two choices, they 
do exactly the same, so why does the
menu collapse, what am I missing?


Regards,

BTJ

-- 
---
Bjørn T Johansen

[EMAIL PROTECTED]
---
Someone wrote:
"I understand that if you play a Windows CD backwards you hear strange Satanic 
messages"
To which someone replied:
"It's even worse than that; play it forwards and it installs Windows"
---

Re: This code works in all other browsers than Firefox, why?

[Bjørn T Johansen]

I removed the jscookmenu and started using panelnavigation2 instead and then I 
noticed that now the submit by using
the enter key is suddenly working using Firefox Something fishy with the 
jscookmenu or?

BTJ

On Tue, 29 May 2007 15:30:43 +0100
"Bruno Aranda" <[EMAIL PROTECTED]> wrote:

> Are you getting any javascript error? Can you give it a shot with
> firebug (useful firefox plugin). Maybe you can see what is
> happening...
> 
> Cheers,
> 
> Bruno
> 
> On 29/05/07, Bjørn T Johansen <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > 
> >
> > 
> > 
> >  > src="/nibstoreweb/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11804471/navmenu.jscookmenu.HtmlJSCookMenuRenderer/JSCookMenu.js">
> >  > src="/nibstoreweb/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11804471/navmenu.jscookmenu.HtmlJSCookMenuRenderer/MyFacesHack.js">
> > 
> >  > src="/nibstoreweb/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11804471/navmenu.jscookmenu.HtmlJSCookMenuRenderer/ThemeOffice/theme.js">
> >
> >  > href="/nibstoreweb/css/jscookmenu/ThemeOffice/theme.css" type="text/css" />
> > 
> > 
> > 
> > 
> >  > href="/nibstoreweb/css/stylesheet.css"/>
> > NIB
> >  > SRC="/nibstoreweb/secure/common/common.js">
> >
> > 
> >
> >
> >
> > 
> >
> >
> >  > action="/nibstoreweb/secure/article/findarticle.faces" 
> > enctype="application/x-www-form-urlencoded"> > border="0" cellpadding="3" cellspacing="1" width="100%"> > width="60%"> > type="text/javascript"> > id="menu_formMenu_mainMenu_menu">
> >  > width="30%"> > name="menu:formMenu_SUBMIT"
> > value="1" />   > name="jscook_action" /> > type="text/javascript"> > id="javax.faces.ViewState"
> > value="8EgC7hvJoXWgMHaUZxk5rx66APlnNueyP32ajDxbvc/i5akMf2jX5eYYlouo1lab4HNkKYGMn9PoWi1WBRzb471RJkmy5UcKOQcojsE1dBwUY9zw1xhkTA=="
> >  />
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >   
> > 
> >   
> >
> >
> >
> >   
> > 
> > 
> >   
> >
> >> name="content:formFindArticle" method="post"
> > action="/nibstoreweb/secure/article/findarticle.faces" 
> > enctype="application/x-www-form-urlencoded"> > id="content:formFindArticle:popupArticleGroupSubmitBtn"
> > name="content:formFindArticle:popupArticleGroupSubmitBtn" type="submit" 
> > value="popupArticleGroupSubmit"
> > onclick="if(typeof
> > window.clearFormHiddenParams_content_formFindArticle!='undefined'){clearFormHiddenParams_content_formFindArticle('content:formFindArticle');}if(typeof
> > window.getScrolling!='undefined'){oamSetHiddenInput('content:formFindArticle','autoScroll',getScrolling());}"
> > style="display:none" /> 
> >
> >  > name="content:formFindArticle:popupSupplierSubmitBtn" type="submit" 
> > value="popupSupplierSubmit"
> > onclick="if(typeof
> > window.clearFormHiddenParams_content_formFindArticle!='undefined'){clearFormHiddenParams_content_formFindArticle('content:formFindArticle');}if(typeof
> > window.getScrolling!='undefined'){oamSetHiddenInput('content:formFindArticle','autoScroll',getScrolling());}"
> > style="display:none" /> > cellspacing="0

Re: Change valueBinding of t:dataTable based on condition

[eric . jung]

Use the rendered attribuet.





Rønnevik, Eivind <[EMAIL PROTECTED]> 
05/31/2007 08:24 AM
Please respond to
"MyFaces Discussion" 


To
"MyFaces Discussion" 
cc

Subject
Change valueBinding of t:dataTable based on condition






Hi!
 
I was just curious, is there any way I can change the value of a dataTable 
based on different conditions?
 
I?ll try to give a simple example to explain what I want. :)
 
Let?s say I use the graphicImage tag, in the value property I could either 
write the path to the image

Re: [Tobago] How to make tobago pages printable

[H. Swaczinna]

Hi,

nobody had the need to print a Tobago page from the browser?

I tried to add my own css style files for printing but I found no way. The 
tc:style tag generates only style file
references for media="screen". If the tc:style tag has a media attribute the 
problem can be solved.

Regards
Helmut


- Original Message - 
From: "H. Swaczinna" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, May 23, 2007 3:26 PM
Subject: [Tobago] How to make tobago pages printable


> Hi,
>
> when I print a tobago page every style information is lost. This is 
> because
> in the stylesheet references the
> media attribute is set to "screen". Is there somewhere a switch to set 
> this
> to "print"?
>
> Regards
> Helmut
>

[COMMUNITY] Ernst Fastl - Committer

[Matthias Wessendorf]

Congratulations to Ernst Fastl for becoming the newest Myfaces committer !

Ernst has provided patches and enhancements to Tomahawk (ajax-stuff)
and has been active on the mailing list to help other users on how to
get up to speed.

Thanks Ernst, and welcome to the team!

--
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org

Change valueBinding of t:dataTable based on condition

[Rønnevik , Eivind]

Hi!

 

I was just curious, is there any way I can change the value of a dataTable 
based on different conditions?

 

I'll try to give a simple example to explain what I want. :)

 

Let's say I use the graphicImage tag, in the value property I could either 
write the path to the image

[ Tobago ] get Sheet Object Referance when page submitted with actionListener

[Madan Narra]

Hi All,

I have an Array which is set to render a sheet in the Tobago Page.

I have a button which does a navigation.

In order to so some action before navigating, i placed actionListener="#{
bean.method}" , immediate="true" for .

As i set immediate="true", the variables are not set into the bean

Now i need to get the instance of the Array object which is set to
 in method(ActionEvent event) .

How can i proceed with this ?

--
Regards,
Madan N

Re: t:dojoInitializer makes IE doesn't render a page

[Werner Punz]

Juan Ignacio Sánchez Lara schrieb:
> I have a working JSP, but when I include   or
> , Internet
> Explorer tells me "Internet Explorer can't open the site .
> Operation cancelled" ("Internet Explorer no puede abrir el sitio .
> Operación anulada"). I've tried it with both IE 7 and 6. Firefox loads ok.
>  
> Any ideas??
>  
> 
Only one...
if you use xhtml in combination with a  tag
if you replace that one with a  it should work.
Somehow the combination of this tag and dojo tag parsing causes ie in
every version to choke.

I hope this solves your problems,

Werner

Re: t:dojoInitializer makes IE doesn't render a page

[Juan Ignacio Sánchez Lara]

My fault once more, I didn't open body tag :$.

On 5/31/07, Juan Ignacio Sánchez Lara <[EMAIL PROTECTED]> wrote:


I have a working JSP, but when I include   or 
, Internet Explorer tells me
"Internet Explorer can't open the site . Operation cancelled"
("Internet Explorer no puede abrir el sitio . Operación anulada"). I've
tried it with both IE 7 and 6. Firefox loads ok.

Any ideas??



--
Juan Ignacio Sánchez Lara
Ingeniero Informático + Técnico de Sistemas

Diario: http://juanignaciosl.blogspot.com
Ideas + Ingeniería del Software: http://iiso.blogspot.com/

Fotos (todas): http://www.flickr.com/photos/juanignaciosl
Fotos (selección): http://jpgmag.com/people/juanignaciosl





--
Juan Ignacio Sánchez Lara
Ingeniero Informático + Técnico de Sistemas

Diario: http://juanignaciosl.blogspot.com
Ideas + Ingeniería del Software: http://iiso.blogspot.com/

Fotos (todas): http://www.flickr.com/photos/juanignaciosl
Fotos (selección): http://jpgmag.com/people/juanignaciosl

Re: What change with JSF 1.1 to JSF 1.2?

[David Steinkopff]

Hi Alexander,

OK, and setValue, getValue and getTyp are required for run-time, sure?
If that case, I only modified my PropertyResolver in some linies and it
works.

regards
David

2007/5/31, Jesse Alexander (KSFD 121) <[EMAIL PROTECTED]>:


 Hi David

- list: Sure, you can add as mny as you want. The first one that can
satisfy the request marks it and thechain ends...
  Nice, cause every Resolver does one task (separation of concerns)
  That is also why you found so many ELResolvers floating around...

regards
Alexander

 --
*From:* David Steinkopff [mailto:[EMAIL PROTECTED]
*Sent:* Thursday, May 31, 2007 10:19 AM
*To:* MyFaces Discussion
*Subject:* Re: What change with JSF 1.1 to JSF 1.2?

Hi Alexander,

I prefer more to decorat, becauce I need only some PropertyResolver
methods. ELResolver works like PropertyResolver and VariableResolver
together and to implement both is more as I needed in my case.
What do you mean with list? It is possible to add more than one resolver?

regards
David

2007/5/31, Jesse Alexander (KSFD 121) < [EMAIL PROTECTED]
>:
>
>  As Adam I recommend to rewrite to the ELResolvers, if you do not
> absolutely need the backward compatibility.
>
> As for writing or decorating...
> With the ELResolver the handling is very easy when you start from
> scratch (== not decorating). And then you just add your
> ELResolver to the list...
>
> regards
> Alexander
>
>  --
> *From:* David Steinkopff [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, May 31, 2007 9:00 AM
> *To:* MyFaces Discussion
> *Subject:* Re: What change with JSF 1.1 to JSF 1.2?
>
>  Hi,
>
> I dont need all features of ELResolvers, for me only important is
> setValue, getValue and maybe isReadonly to connect a custom data system. In
> this way was PropertyResolver more than enough for me.
> JSF 1.1 have only one implementation of  PropertyResolver and JSF 1.2have 
with ELResolver more than one. Which implementation I can use for a
> decorator or what implementation is common standard in JSF 1.2?
>
> Regards
> David
>
>
> 2007/5/30, Adam Winer < [EMAIL PROTECTED]>:
> >
> > FYI, I strongly recommend that developers who are moving up
> > to JSF 1.2 rewrite PropertyResolvers and VariableResolvers
> > as ELResolvers.
> >
> > Backwards compatibility for registered (programatic or via
> > faces-config.xml ) VariableResolver and PropertyResolvers has
> > been a major nightmare for the reference implementation,
> > and I'd be amazed if MyFaces 1.2 didn't have some bugs
> > here.  And, even if it's perfect, there's a slight performance
> > hit associated with using legacy EL APIs.
> >
> > -- Adam
> >
> >
> >
> > On 5/30/07, Jesse Alexander (KSFD 121)
> > < [EMAIL PROTECTED]> wrote:
> > >
> > >
> > > The PropertyResolver is ONLY DEPRECATED. It still can be accessed,
> > although
> > > a compiler might throw warnings
> > >
> > > regards
> > > Alexander
> > >
> > >  
> > >  From: David Steinkopff [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, May 30, 2007 11:04 AM
> > > To: MyFaces Discussion
> > > Subject: Re: What change with JSF 1.1 to JSF 1.2?
> > >
> > >
> > > Hi Martin,
> > >
> > > current is my PropertyResolver a decorator of the
> > PropertyResolverImpl from
> > > MyFaces. Would it neccessary to wright a new decorator for the
> > ELResolver
> > > implementation? Or I can use the PropertyResolver in JSF 1.2 in face
> > of
> > > deprecated?
> > >
> > > Regards
> > > David
> > >
> > >
> > > 2007/5/30, Martin Marinschek < [EMAIL PROTECTED]>:
> > > > It _should_ work out of the box - everything else would be a bug.
> > Also
> > > > the property-resolver should work, it would be integrated into the
> > > > el-resolver-chain...
> > > >
> > > > regards,
> > > >
> > > > Martin
> > > >
> > > > On 5/30/07, David Steinkopff < [EMAIL PROTECTED]>
> > wrote:
> > > > > Hello,
> > > > >
> > > > > I ´m reading interested in this mailing list and I see that JSF
> > 1.2
> > > > > implementation from MyFaces is coming soon.
> > > > > Now I ask me the question, what changes must I attend if I
> > immigrate a
> > > JSF
> > > > > 1.1 application with own PropertyResolver and PhaseListener?
> > > > >
> > > > > regards
> > > > > David
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > http://www.irian.at
> > > >
> > > > Your JSF powerhouse -
> > > > JSF Consulting, Development and
> > > > Courses in English and German
> > > >
> > > > Professional Support for Apache MyFaces
> > > >
> > >
> > >
> >
>
>

date format for t:inputCalendar

[sandipp]

Hi All.

I am using  tag.I want to display date in mm/dd/yy format.
i.e. if i select 1 May 2005 ,it should display as 05/01/05.

But with my below code its showing as 5/1/05 (what about 0 in case of 5 and
1)



where msg= variable for my property file

where in property file I have defined stratDateformat as,MM/dd/
kk\:mm\:ss


Can anybody help me in this


 
Sandip

-- 
View this message in context: 
http://www.nabble.com/date-format-for-t%3AinputCalendar-tf3845671.html#a10890963
Sent from the MyFaces - Users mailing list archive at Nabble.com.

t:dojoInitializer makes IE doesn't render a page

[Juan Ignacio Sánchez Lara]

I have a working JSP, but when I include   or
, Internet Explorer tells me
"Internet Explorer can't open the site . Operation cancelled"
("Internet Explorer no puede abrir el sitio . Operación anulada"). I've
tried it with both IE 7 and 6. Firefox loads ok.

Any ideas??



--
Juan Ignacio Sánchez Lara
Ingeniero Informático + Técnico de Sistemas

Diario: http://juanignaciosl.blogspot.com
Ideas + Ingeniería del Software: http://iiso.blogspot.com/

Fotos (todas): http://www.flickr.com/photos/juanignaciosl
Fotos (selección): http://jpgmag.com/people/juanignaciosl

Re: java.lang.IllegalArgumentException: Value is no String

[Celso Nishioka]

Andrew, I'm having the same issue.

Did you get it solved?

Thanks.

On 11/29/06, Andrew Robinson <[EMAIL PROTECTED]> wrote:


No that hasn't changed, I just checked the source. If you look at the
stack trace, somehow the value is an instance of
"org.apache.myfaces.shared_tomahawk.renderkit.RendererUtils$1" -- it
is not null inside the "RendererUtils.getConvertedStringValue" method.

How in the world that happened is beyond me.

-Andrew

On 11/29/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
> Andrew,
>
> Looking at the current code, it shouldn't throw that against a null
> value. Maybe they've changed this since your version? Perhaps you could
> try with the nightlies just to see if the same behavior happens?
>
> RenderUtils
> 
> public static String getConvertedStringValue(FacesContext context,
>   UIComponent component,
> Converter converter, Object value) {
>  if (converter == null) {
>  if (value == null) {
>  return "";
>  }
>  else if (value instanceof String) {
>  return (String) value;
>  }
>  else {
>  throw new IllegalArgumentException(
>  "Value is no String (class=" +
> value.getClass().getName() + ", value=" + value + ") and component "
>  + component.getClientId(context) + "with path:
"
>  + getPathToComponent(component)
>  + " does not have a Converter");
>  }
>  }
>
>  return converter.getAsString(context, component, value);
>  }
> ---
>
> Maybe your version is missing the lines:
>
> if (value == null) {
> return "";
> }
>
> Regards,
>
> Jeff Bischoff
> Kenneth L Kurz & Associates, Inc.
>
> Andrew Robinson wrote:
> > Yes that is correct, it was always null but only failed to render the
> > 3rd request.
> >
> > On 11/29/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
> >> Well the reason it doesn't work is because of the null.
> >>
> >> Are you saying it was set to null the whole time, and only failed on
the
> >> 3rd request (after having canceled the dialog once)?
> >>
> >> Regards,
> >>
> >> Jeff Bischoff
> >> Kenneth L Kurz & Associates, Inc.
> >>
> >> Andrew Robinson wrote:
> >> > Found a work around -->
> >> > if "value.typeText" is set to one of the values instead of null I
> >> > don't get the exception. What I don't understand is why it works
the
> >> > other times but not the 3rd AJAX call.
> >> >
> >> > On 11/29/06, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> >> >> I am getting a bit stuck on this one exception. I have two
> >> >> selectOneRadio components within an included facelet (source file)
> >> >> that bind to a property on a facelet attribute. The value is a
custom
> >> >> bean with string properties and the select items have string
values,
> >> >> so no converter should be needed. What is odd is that this
behavior is
> >> >> not constant.
> >> >>
> >> >> Setup:
> >> >> index.xhtml defines this component:
> >> >>  >> >>   id="liveReportFilterDlg"
> >> >>   ajaxZone="reportListZone"
> >> >>   rendered="#{liveReportBean.filterDialogVisible}"
> >> >>   onAcceptListener="#{liveReportBean.filterDialogAccepted
}"
> >> >>   onCancelListener="#{liveReportBean.filterDialogCanceled
}"
> >> >>   value="#{liveReportBean.filter}" />
> >> >>
> >> >> It is this "value" that I use within the
> >> "liveReportFilterDialog.xhtml":
> >> >>
> >> >>>> >> id="#{id}TypeOptions"
> >> >> value="#{value.typeText}"
> >> >> layout="pageDirection"
> >> >> required="true">
> >> >>  >> >>   itemLabel="#{msg.liverep_filterdlg_typefilter_graph}"
> >> >>   itemValue="osoft/livechart" />
> >> >>  >> >>   itemLabel="#{msg.liverep_filterdlg_typefilter_report}"
> >> >>   itemValue="osoft/livereport" />
> >> >>  >> >>   itemLabel="#{msg.liverep_filterdlg_typefilter_schedule}"
> >> >>   itemValue="osoft/liveschedule" />
> >> >>   
> >> >>
> >> >> The other radio is:
> >> >>
> >> >>>> >> layout="pageDirection">
> >> >>  >> >>   itemValue="ALL" />
> >> >>  >> >>   itemValue="CURRENT_USER" />
> >> >>   
> >> >>
> >> >>
> >> >> This dialog is usually not rendered, I change the value that the
> >> >> rendered attribte points to in an AJAX call ActionListener method.
> >> >> When I click the show, it works. Then, I click the cancel (close
the
> >> >> dialog), still okay, but when I try to open the dialog again (3rd
AJAX
> >> >> call) I get the following exception:
> >> >> java.lang.IllegalArgumentException: Value is no String
> >> >> (class=
org.apache.myfaces.shared_tomahawk.renderkit.RendererUtils$1,
> >> >>
> >> value=
[EMAIL PROTECTED])
> >>
> >> >>
> >> >> and component
> >> >>
> >>
zfpPanel:liveReportFilterDlgDialogControl:_gridBagPanelID_3:liveReportFilterDlgTypeOptionsw

RE: What change with JSF 1.1 to JSF 1.2?

[Jesse Alexander \(KSFD 121\)]

Hi David
 
- list: Sure, you can add as mny as you want. The first one that can satisfy 
the request marks it and thechain ends...
  Nice, cause every Resolver does one task (separation of concerns)
  That is also why you found so many ELResolvers floating around...
 
regards
Alexander



From: David Steinkopff [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 31, 2007 10:19 AM
To: MyFaces Discussion
Subject: Re: What change with JSF 1.1 to JSF 1.2?


Hi Alexander,

I prefer more to decorat, becauce I need only some PropertyResolver methods. 
ELResolver works like PropertyResolver and VariableResolver together and to 
implement both is more as I needed in my case. 
What do you mean with list? It is possible to add more than one resolver? 

regards
David


2007/5/31, Jesse Alexander (KSFD 121) < [EMAIL PROTECTED]  >: 

As Adam I recommend to rewrite to the ELResolvers, if you do not 
absolutely need the backward compatibility.
 
As for writing or decorating...
With the ELResolver the handling is very easy when you start from 
scratch (== not decorating). And then you just add your 
ELResolver to the list...
 
regards
Alexander



From: David Steinkopff [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 31, 2007 9:00 AM 

To: MyFaces Discussion
Subject: Re: What change with JSF 1.1 to JSF 1.2?



Hi,

I dont need all features of ELResolvers, for me only important is 
setValue, getValue and maybe isReadonly to connect a custom data system. In 
this way was PropertyResolver more than enough for me.
JSF 1.1 have only one implementation of  PropertyResolver and JSF 1.2 
have with ELResolver more than one. Which implementation I can use for a 
decorator or what implementation is common standard in JSF 1.2? 

Regards
David



2007/5/30, Adam Winer < [EMAIL PROTECTED]>: 

FYI, I strongly recommend that developers who are moving up
to JSF 1.2 rewrite PropertyResolvers and VariableResolvers
as ELResolvers.

Backwards compatibility for registered (programatic or via
faces-config.xml ) VariableResolver and PropertyResolvers has
been a major nightmare for the reference implementation,
and I'd be amazed if MyFaces 1.2 didn't have some bugs
here.  And, even if it's perfect, there's a slight performance 
hit associated with using legacy EL APIs.

-- Adam



On 5/30/07, Jesse Alexander (KSFD 121)
< [EMAIL PROTECTED]  > wrote: 
>
>
> The PropertyResolver is ONLY DEPRECATED. It still can be 
accessed, although
> a compiler might throw warnings
>
> regards
> Alexander
>
>   
>  From: David Steinkopff [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 30, 2007 11:04 AM 
> To: MyFaces Discussion
> Subject: Re: What change with JSF 1.1 to JSF 1.2?
>
>
> Hi Martin,
>
> current is my PropertyResolver a decorator of the 
PropertyResolverImpl from
> MyFaces. Would it neccessary to wright a new decorator for 
the ELResolver 
> implementation? Or I can use the PropertyResolver in JSF 1.2 
in face of
> deprecated?
>
> Regards
> David
>
>
> 2007/5/30, Martin Marinschek < [EMAIL PROTECTED] 
 >:
> > It _should_ work out of the box - everything else would be 
a bug. Also
> > the property-resolver should work, it would be integrated 
into the
> > el-resolver-chain... 
> >
> > regards,
> >
> > Martin
> >
> > On 5/30/07, David Steinkopff < [EMAIL PROTECTED]> wrote: 
> > > Hello,
> > >
> > > I ´m reading interested in this mailing list and I see 
that JSF 1.2
> > > implementation from MyFaces is coming soon.
> > > Now I ask me the question, what changes must I attend if 
I immigrate a 
> JSF
> > > 1.1 application with own PropertyResolver and 
PhaseListener?
> > >
> > > regards
> > > D

Error using Ajax4JSF with myFaces

[Laurentiu Trica]

Hi

I am trying to use Ajax4JSF with myFaces and I get this error:

2007-05-30 18:14:53,406 | ERROR org.apache.catalina.core
.ContainerBase.[Catalina].[localhost].[/].[Faces Servlet] - Servlet.service()
for servlet Faces Servlet threw exception
java.lang.NullPointerException
   at org.ajax4jsf.framework.ajax.AjaxViewHandler.createView(
AjaxViewHandler.java:78)
   at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute (
RestoreViewExecutor.java:83)
   at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(
LifecycleImpl.java:95)
   at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java
:70)
   at javax.faces.webapp.FacesServlet.service (FacesServlet.java:213)
   at org.apache.myfaces.webapp.MyFacesServlet.service(MyFacesServlet.java
:77)
   at org.kobit.ofam.gui.jsf.OFAMFacesServlet.service(OFAMFacesServlet.java
:54)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (
ApplicationFilterChain.java:252)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(
ApplicationFilterChain.java:173)
   at org.apache.catalina.core.ApplicationDispatcher.invoke(
ApplicationDispatcher.java :672)
   at org.apache.catalina.core.ApplicationDispatcher.processRequest(
ApplicationDispatcher.java:465)
   at org.apache.catalina.core.ApplicationDispatcher.doForward(
ApplicationDispatcher.java:398)
   at org.apache.catalina.core.ApplicationDispatcher.forward (
ApplicationDispatcher.java:301)
   at org.apache.catalina.core.StandardHostValve.custom(
StandardHostValve.java:363)
   at org.apache.catalina.core.StandardHostValve.status(
StandardHostValve.java:284)
   at org.apache.catalina.core.StandardHostValve.throwable (
StandardHostValve.java:228)
   at org.apache.catalina.core.StandardHostValve.invoke(
StandardHostValve.java:134)
   at org.apache.catalina.valves.ErrorReportValve.invoke(
ErrorReportValve.java:105)
   at org.apache.catalina.core.StandardEngineValve.invoke (
StandardEngineValve.java:107)
   at org.apache.catalina.connector.CoyoteAdapter.service(
CoyoteAdapter.java:148)
   at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:869)
   at org.apache.coyote.http11.Http11BaseProtocol$Http11Conne
ctionHandler.processConnection (Http11BaseProtocol.java:664)
   at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(
PoolTcpEndpoint.java:527)
   at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(
LeaderFollowerWorkerThread.java :80)
   at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
ThreadPool.java:684)
   at java.lang.Thread.run(Thread.java:595)

What is more bizarre is that the same project works with Ajax4JSF on one
particular computer that has the same svn project...
Have you encountered this before? Can you help me get rid of this?

--
Best regards,
Laurentiu
www.codebeat.ro

Re: What change with JSF 1.1 to JSF 1.2?

[David Steinkopff]

Hi Alexander,

I prefer more to decorat, becauce I need only some PropertyResolver methods.
ELResolver works like PropertyResolver and VariableResolver together and to
implement both is more as I needed in my case.
What do you mean with list? It is possible to add more than one resolver?

regards
David

2007/5/31, Jesse Alexander (KSFD 121) <[EMAIL PROTECTED]>:


 As Adam I recommend to rewrite to the ELResolvers, if you do not
absolutely need the backward compatibility.

As for writing or decorating...
With the ELResolver the handling is very easy when you start from scratch
(== not decorating). And then you just add your
ELResolver to the list...

regards
Alexander

 --
*From:* David Steinkopff [mailto:[EMAIL PROTECTED]
*Sent:* Thursday, May 31, 2007 9:00 AM
*To:* MyFaces Discussion
*Subject:* Re: What change with JSF 1.1 to JSF 1.2?

Hi,

I dont need all features of ELResolvers, for me only important is
setValue, getValue and maybe isReadonly to connect a custom data system. In
this way was PropertyResolver more than enough for me.
JSF 1.1 have only one implementation of  PropertyResolver and JSF 1.2 have
with ELResolver more than one. Which implementation I can use for a
decorator or what implementation is common standard in JSF 1.2?

Regards
David


2007/5/30, Adam Winer < [EMAIL PROTECTED]>:
>
> FYI, I strongly recommend that developers who are moving up
> to JSF 1.2 rewrite PropertyResolvers and VariableResolvers
> as ELResolvers.
>
> Backwards compatibility for registered (programatic or via
> faces-config.xml ) VariableResolver and PropertyResolvers has
> been a major nightmare for the reference implementation,
> and I'd be amazed if MyFaces 1.2 didn't have some bugs
> here.  And, even if it's perfect, there's a slight performance
> hit associated with using legacy EL APIs.
>
> -- Adam
>
>
>
> On 5/30/07, Jesse Alexander (KSFD 121)
> < [EMAIL PROTECTED]> wrote:
> >
> >
> > The PropertyResolver is ONLY DEPRECATED. It still can be accessed,
> although
> > a compiler might throw warnings
> >
> > regards
> > Alexander
> >
> >  
> >  From: David Steinkopff [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, May 30, 2007 11:04 AM
> > To: MyFaces Discussion
> > Subject: Re: What change with JSF 1.1 to JSF 1.2?
> >
> >
> > Hi Martin,
> >
> > current is my PropertyResolver a decorator of the PropertyResolverImpl
> from
> > MyFaces. Would it neccessary to wright a new decorator for the
> ELResolver
> > implementation? Or I can use the PropertyResolver in JSF 1.2 in face
> of
> > deprecated?
> >
> > Regards
> > David
> >
> >
> > 2007/5/30, Martin Marinschek < [EMAIL PROTECTED]>:
> > > It _should_ work out of the box - everything else would be a bug.
> Also
> > > the property-resolver should work, it would be integrated into the
> > > el-resolver-chain...
> > >
> > > regards,
> > >
> > > Martin
> > >
> > > On 5/30/07, David Steinkopff < [EMAIL PROTECTED]>
> wrote:
> > > > Hello,
> > > >
> > > > I ´m reading interested in this mailing list and I see that JSF
> 1.2
> > > > implementation from MyFaces is coming soon.
> > > > Now I ask me the question, what changes must I attend if I
> immigrate a
> > JSF
> > > > 1.1 application with own PropertyResolver and PhaseListener?
> > > >
> > > > regards
> > > > David
> > > >
> > >
> > >
> > > --
> > >
> > > http://www.irian.at
> > >
> > > Your JSF powerhouse -
> > > JSF Consulting, Development and
> > > Courses in English and German
> > >
> > > Professional Support for Apache MyFaces
> > >
> >
> >
>

[Trinidad] Note to tr:input... generated HTML

[Petr Kotek]

Hi,

I have a little note to HTML code, generated by tr:input components in 
label area. This code has changed in some latest release (I think) and 
now look as:



 nowrap="nowrap">

   
   
 X
   
    
   Order No:
 
 


For next styling of label (for example for its vertical alignment before 
multi line text input) I have big problems with " " included in 
code. I think, that it will be better to avoid this " " (generally 
- all hard coded formating) and space between icon and text realize by 
right margin in icon element in base style?


Thanks for Your opinion,
Peter

RE: What change with JSF 1.1 to JSF 1.2?

[Jesse Alexander \(KSFD 121\)]

As Adam I recommend to rewrite to the ELResolvers, if you do not absolutely 
need the backward compatibility.
 
As for writing or decorating...
With the ELResolver the handling is very easy when you start from scratch (== 
not decorating). And then you just add your 
ELResolver to the list...
 
regards
Alexander



From: David Steinkopff [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 31, 2007 9:00 AM
To: MyFaces Discussion
Subject: Re: What change with JSF 1.1 to JSF 1.2?


Hi,

I dont need all features of ELResolvers, for me only important is setValue, 
getValue and maybe isReadonly to connect a custom data system. In this way was 
PropertyResolver more than enough for me.
JSF 1.1 have only one implementation of  PropertyResolver and JSF 1.2 have with 
ELResolver more than one. Which implementation I can use for a decorator or 
what implementation is common standard in JSF 1.2? 

Regards
David



2007/5/30, Adam Winer < [EMAIL PROTECTED]>: 

FYI, I strongly recommend that developers who are moving up
to JSF 1.2 rewrite PropertyResolvers and VariableResolvers
as ELResolvers.

Backwards compatibility for registered (programatic or via
faces-config.xml ) VariableResolver and PropertyResolvers has
been a major nightmare for the reference implementation,
and I'd be amazed if MyFaces 1.2 didn't have some bugs
here.  And, even if it's perfect, there's a slight performance 
hit associated with using legacy EL APIs.

-- Adam



On 5/30/07, Jesse Alexander (KSFD 121)
< [EMAIL PROTECTED]  > wrote: 
>
>
> The PropertyResolver is ONLY DEPRECATED. It still can be accessed, 
although
> a compiler might throw warnings
>
> regards
> Alexander
>
>   
>  From: David Steinkopff [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 30, 2007 11:04 AM 
> To: MyFaces Discussion
> Subject: Re: What change with JSF 1.1 to JSF 1.2?
>
>
> Hi Martin,
>
> current is my PropertyResolver a decorator of the 
PropertyResolverImpl from
> MyFaces. Would it neccessary to wright a new decorator for the 
ELResolver 
> implementation? Or I can use the PropertyResolver in JSF 1.2 in face 
of
> deprecated?
>
> Regards
> David
>
>
> 2007/5/30, Martin Marinschek < [EMAIL PROTECTED]  >:
> > It _should_ work out of the box - everything else would be a bug. 
Also
> > the property-resolver should work, it would be integrated into the
> > el-resolver-chain... 
> >
> > regards,
> >
> > Martin
> >
> > On 5/30/07, David Steinkopff < [EMAIL PROTECTED]> wrote: 
> > > Hello,
> > >
> > > I ´m reading interested in this mailing list and I see that JSF 
1.2
> > > implementation from MyFaces is coming soon.
> > > Now I ask me the question, what changes must I attend if I 
immigrate a 
> JSF
> > > 1.1 application with own PropertyResolver and PhaseListener?
> > >
> > > regards
> > > David
> > >
> >
> >
> > --
> >
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and 
> > Courses in English and German
> > 
> > Professional Support for Apache MyFaces
> >
>
>