How to create backing bean like bundle

[Dave]

I have a Map (name --> value), and prefer to access values (from JSF page) 
using "#{myMap.Foo}"  where Foo is the key, which is the same as how to access 
resource bundle "#{bundle.Foo}".  
   
  There are 100+ values in the map, and I do not like to write 100+ getter 
methods. Please help. Thanks!
   
  David

   
-
 Check out  the hottest 2008 models today at Yahoo! Autos.

Re: [Trinidad] inputText: autocomplete="off" ?!

[Stephen Friedrich]

Well, I did try, but I am too stupid.
How do I get a new attribute to be recognized? I just don't understand how the 
taglib generation works.
I edited
   
trinidad/trinidad-build/src/main/resources/META-INF/maven-faces-plugin/components/trinidad/core/CoreInputText.xml
and added a propety:

  
  
  autoComplete
  boolean
  true


I changed the SimpleInputTextRenderer.

Finally I tried adding an attribute to UIConstants (to be safe in case it is 
magically used somewhere):
  public static final AttributeKey AUTO_COMPLETE_ATTR = new 
AttributeKey("autoComplete");

Yet after doing
   mvn clean
   mvn install
I get the following error during renderer test:
java.lang.NullPointerException
at 
org.apache.myfaces.trinidad.bean.FacesBeanImpl._checkNotListKey(FacesBeanImpl.java:472)
at 
org.apache.myfaces.trinidad.bean.FacesBeanImpl.getProperty(FacesBeanImpl.java:55)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.SimpleInputTextRenderer.getAutoComplete(SimpleInputTextRenderer.java:769)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.SimpleInputTextRenderer.renderAllAttributes(SimpleInputTextRenderer.java:235)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.SimpleInputTextRenderer.encodeAllAsElement(SimpleInputTextRenderer.java:129)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.SimpleInputListOfValuesRenderer.renderTextField(SimpleInputListOfValuesRenderer.java:197)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.SimpleInputColorRenderer.renderTextField(SimpleInputColorRenderer.java:189)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.SimpleInputListOfValuesRenderer.encodeAllAsElement(SimpleInputListOfValuesRenderer.java:154)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.SimpleInputColorRenderer.encodeAllAsElement(SimpleInputColorRenderer.java:168)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.FormElementRenderer.encodeAll(FormElementRenderer.java:109)
at 
org.apache.myfaces.trinidad.render.CoreRenderer.delegateRenderer(CoreRenderer.java:330)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.InputLabelAndMessageRenderer.encodeAll(InputLabelAndMessageRenderer.java:119)
at 
org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:220)
at 
org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:710)
at 
org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:69)
at 
org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:64)
at 
org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:294)
at 
org.apache.myfaces.trinidad.render.CoreRenderer.encodeAllChildren(CoreRenderer.java:316)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.renderContent(PanelPartialRootRenderer.java:64)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.renderContent(BodyRenderer.java:139)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.encodeAll(PanelPartialRootRenderer.java:119)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.encodeAll(BodyRenderer.java:79)
at 
org.apache.myfaces.trinidad.render.CoreRenderer.delegateRenderer(CoreRenderer.java:330)
at 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer.encodeAll(DocumentRenderer.java:80)
at 
org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:220)
at 
org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:710)
at 
org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:69)
at 
org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:64)
at 
org.apache.myfaces.trinidadinternal.renderkit.RenderUtils.encodeRecursive(RenderUtils.java:47)
at 
org.apache.myfaces.trinidadinternal.renderkit.RenderKitTestCase$BaseTest.renderRoot(RenderKitTestCase.java:213)
at 
org.apache.myfaces.trinidadinternal.renderkit.RenderKitTestCase$RendererTest.runTest(RenderKitTestCase.java:361)

Any comments? Pointers to development documentation?


Stephen Friedrich wrote:

Do you mind to file an enhancement request ?


Thanks for the answer. I'll try and create a patch and submit it with a
jira issue.



On 9/26/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote:
Is there any reason that Trinidad's inputText tag does not support an 

autocomplete

attribute to disable completion in the browser?

That should be very easy to implement as it should only be passed through to 

html, right?

Re: [Trinidad] after - possible to remove?

[Adam Winer]

Wrap the two images in an af:group or af:panelGroupLayout.

-- Adam


On 9/28/07, Chris Hane <[EMAIL PROTECTED]> wrote:
> I have a column that displays two images in it.  I would like the images to
> be displayed side/by side.  However, a  element is being inserted
> between the images.
>
> Thoughts on how I can format this so that the div is not displayed?
>
> Thanks,
> Chris
>
> Here is the XHTML (facelets):
>
> 
> 
>  
>
>
> ...And this is the html produced:
>
> 
> 
> 
> 
> 
>
>

Re: [Trinidad] after - possible to remove?

[Andrew Robinson]

The quick way would be to put this in your skin:

af|column::cell-text .OraTableBorder DIV {
  display: none;
}

On 9/28/07, Chris Hane <[EMAIL PROTECTED]> wrote:
> I have a column that displays two images in it.  I would like the images to
> be displayed side/by side.  However, a  element is being inserted
> between the images.
>
> Thoughts on how I can format this so that the div is not displayed?
>
> Thanks,
> Chris
>
> Here is the XHTML (facelets):
>
> 
> 
>  
>
>
> ...And this is the html produced:
>
> 
> 
> 
> 
> 
>
>

[Trinidad] after - possible to remove?

[Chris Hane]

I have a column that displays two images in it.  I would like the images to 
be displayed side/by side.  However, a  element is being inserted 
between the images.


Thoughts on how I can format this so that the div is not displayed?

Thanks,
Chris

Here is the XHTML (facelets):


   
   


...And this is the html produced:


   
   
   

Re: [core] display label from resource bundle in validation message

[Volker Weber]

Hi Thomas,

f:loadBundle stores the bundle in request-scope,
you can use the loadBundle from sandbox as replacement:
http://myfaces.apache.org/sandbox/apidocs/org/apache/myfaces/custom/loadbundle/LoadBundleTag.html


Regards,
Volker



2007/9/28, Thomas Fischer <[EMAIL PROTECTED]>:
>
> Hi all,
>
> We have an input field that looks like:
>
>  id="street"
> required="true"
> value="#{someController.street}"
> binding="#{someController.streetInput}"
> label="street" />
>
> If the "required" validation fails, the label is be replaced into
> placeholder {0} of the validation message "{0}: Validation Error: Value is
> required."
>
> Trying to internationalize the application, we now load the label from a
> resource bundle:
>
> 
>  id="street"
> required="true"
> value="#{someController.street}"
> binding="#{someController.streetInput}"
> label="#{labels['label.address.street']}" />
>
> Now, the label is not correctly replaced in the message; instead "null" is
> inserted into the placeholder. We have checked that the label is accessed
> correctly, the same expression in an outputText does find the message.
>
> I assume the following happens: The label replacement takes place in the
> processValidations phase (when the validation fails). In this phase. the
> message bundle is not yet registered (this happens in the
> renderResponsePhase when the jsp page with the loadBundle is executed).
>
> I have also found the following remark in the class
> org.apache.myfaces.taglib.core.LoadBundleTag, which points in the same
> direction:
>  * TODO:
>  * We should find a way to save loaded bundles in the state, because
> otherwise
>  * on the next request the bundle map will not be present before the render
> phase
>  * and value bindings that reference to the bundle will always log annoying
>  * "Variable 'xxx' could not be resolved" error messages.
>
> Does anybody have an idea how one could achieve this ?
>
> Regards
>
> Thomas
>
>
>

Tomahawk Input Disabled

[daniel ccss]

Hi all,

I have one question, how I can I dynamically stablish the disable or
readonly value of a tomahawk input with a bean variable that is true or
false??

for example:

in the bean:

isDisabled = true

in the jsp

Re: Errors and Messages

[daniel ccss]

Anyone??

On 9/26/07, daniel ccss <[EMAIL PROTECTED]> wrote:
>
> Thanks, but how can I have two  messages??
>
> On 9/26/07, Kito D. Mann <[EMAIL PROTECTED] > wrote:
> >
> >*From:* daniel ccss [mailto:[EMAIL PROTECTED]
> > *Sent:* Wednesday, September 26, 2007 10:26 AM
> > *To:* MyFaces Discussion
> > *Subject:* Errors and Messages
> >
> >
> >
> > Hi all,
> >
> > I need to use a different style for showing messages and errors.
> >
> > For my messages I use this in my bean 
> > FacesContext.getCurrentInstance().addMessage(null,
> > new FacesMessage(message)); And this in the JSP   > styleClass="messages"/>
> >
> > How can display errors in this way using a different style.
> >
> >
> >
> > Look at the  tag – there's an errorClass property.
> >
> > ~~~
> > Kito D. Mann - Author, JavaServer Faces in Action
> > http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
> > http://www.JSFCentral.com  - JavaServer
> > Faces FAQ, news, and info
> >
> >
> >
> > * Sign up for the JSF Central newsletter!
> > http://oi.vresp.com/?fid=ac048d0e17 *
> >
> >
> >
> >
> >
> >
> >
>
>

RE: [Trinidad] trinidad 1.2.1 w/ ajax4jsf, richfaces and facelets possible?

[Alan Romaniuc]

Any success doing that? I am using trinidad 1.2.2 and ajax4jsf 1.1.1 ,
but no success.

Any help?

Thai Dang Vu wrote:
> Hi everybody,
>
> I'd like to ask if it is possible to use trinidad 1.2.1 with richfaces
> 3.1.0 (which includes ajax4jsf) and facelets.
>
> This is my 1st day learning trinidad so I haven't got time to try
> different ways to configure the web.xml file to make trinidad and
> ajax4jsf work togeter.
>
> If you have an existing example using both richfaces 3.1.0 and
trinidad,
> could I have a copy of all your configuration files (web.xml,
> faces-config.xml, trinidad-config.xml) and the name of all the jar
files
> in WEB-INF/lib?

Re: Trinidad rendererKit error

[Matthias Wessendorf]

and what's with ?

template.xhtml



On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Re,
>
> I have only one form tag in mei xhtml file.
> I put the trinidad stuff in another much more smaller
> xhtml file, to be sure having only this one form tag.
> But same error.
>
> You can view the xhtml here: http://nopaste.info/48d9a6aca3.html
>
>
> >Is it possible,
> >that you have a  inside a  ?
>
> >-Matthias
>
> >On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > > Re Matthias,
> > >
> > > I went several times through the Facelets_with_Trinidad tutorial, but
> I got
> > > always the rendererKit Error.
> > > I checked all config files again but I guess they should be ok.
> > > I put the ViewHandler out of the faces-config and now I got another
> > > error:
> > > 
> > > 28.09.2007 16:50:17 com.sun.facelets.FaceletViewHandler
> handleRenderException
> > > SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
> > > java.lang.NullPointerException
> > > at
> > > org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.FormRenderer.encodeEnd(FormRenderer.java:206)
> > > at
> > > org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:224)
> > > at
> > > org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeEnd(HtmlFormRenderer.java:63)
> > > at
> > > javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:539)
> > > --
> > >
> > > my Faces-Config:
> > > =
> > > 
> > > 
> > > 
> > > org.apache.myfaces.trinidad.core
> > > 
> > > 
> > >
> > >
> > > my Web.xml
> > > 
> > >  
> > > 
> > > 
> > > org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
> > > com.sun.facelets.FaceletViewHandler
> > > 
> > >
> > > 
> > > 
> > > org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE
> > > false
> > > 
> > >
> > > 
> > > 
> > > org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
> > > true
> > > 
> > >
> > > 
> > > 
> > > org.apache.myfaces.trinidad.CHANGE_PERSISTENCE
> > > session
> > > 
> > > 
> > >
> > >
> > >  
> > > 
> > > trinidad
> > > 
> > > org.apache.myfaces.trinidad.webapp.TrinidadFilter
> > > 
> > >
> > > 
> > > trinidad
> > > faces
> > > 
> > > 
> > >
> > >
> > > 
> > > 
> > > resources
> > > 
> > > org.apache.myfaces.trinidad.webapp.ResourceServlet
> > > 
> > > 
> > >
> > >
> > > my Pom.xml
> > > 
> > > 
> > > 
> > > org.apache.myfaces.trinidad
> > > trinidad-api
> > > 1.0.2
> > > compile
> > > 
> > >
> > > 
> > > org.apache.myfaces.trinidad
> > > trinidad-impl
> > > 1.0.2
> > > compile
> > > 
> > > 
> > >
> >> > > Hi Wolfgang,
> >> > >
> >> > > don't specify the ViewHandler inside the faces-config.xml
> >> > > Do it inside the web.xml:
> >> > >
> >> > > 
> >> > >   
> >> > > org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
> >> > >   com.sun.facelets.FaceletViewHandler
> >> > > 
> >> > >
> >> > >
> >> > > for more see here:
> >> > > http://wiki.apache.org/myfaces/Facelets_with_Trinidad
> >> > >
> >> > > -Matthias
> >> > >
> >> > > On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >>> > >> Hi,
> >>> > >>
> >>> > >> if I put the default rendererKit into my faces-config.xml then
> >>> > >> I got the following error:
> >>> > >>
> >>> > >> ---
> >>> > >> 28.09.2007 16:13:43
> >>> > >> org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit
> >>> > >> createResponseWriter
> >>> > >> SCHWERWIEGEND: No RenderingContext has been created.
> >>> > >> 28.09.2007 16:13:43 com.sun.facelets.FaceletViewHandler
> > > handleRenderException
> >>> > >> SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
> >>> > >> java.lang.IllegalStateException: No RenderingContext
> >>> > >> at
> >>> > >> org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer.java:193)
> >>> > >> at
> >>> > >> org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:56)
> >>> > >> at
> >>> > >> javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:515)
> >>> > >> --
> >>> > >>
> >>> > >>
> >>> > >> But if I remove the default rendererKit, Trinidad throws
> >>> > >> of course the following error:
> >>> > >>
> >>> > >> ---
> >>> > >> 28.09.2007 16:19:41
> org.apache.myfaces.trinidad.component.UIXComponentBase
> >>> > >> _getRendererImpl
> >>> > >> WARNUNG: Could not find renderer for CoreForm[UIXFacesBea

Re: Trinidad rendererKit error

[wkluge]

Hi,

really strange I removed the tr:form tags and now
it seems to work! I have no idea why this is now working.
Because how you can see I have no other form tag inside my
xhtml file.

Hope everything concerning trinidad will work now! ;)

Thanks for you help again.

Cheers Wolfgang


>Re,

>I have only one form tag in mei xhtml file.
>I put the trinidad stuff in another much more smaller
>xhtml file, to be sure having only this one form tag.
>But same error.

>You can view the xhtml here: http://nopaste.info/48d9a6aca3.html


> >Is it possible,
> >that you have a  inside a  ?

> >-Matthias

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

>> > > Re Matthias,
>> > >
>> > > I went several times through the Facelets_with_Trinidad tutorial, but
I got
>> > > always the rendererKit Error.
>> > > I checked all config files again but I guess they should be ok.
>> > > I put the ViewHandler out of the faces-config and now I got another
>> > > error:
>> > > 
>> > > 28.09.2007 16:50:17 com.sun.facelets.FaceletViewHandler
handleRenderException
>> > > SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
>> > > java.lang.NullPointerException
>> > > at
>> > > org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.FormRenderer.encodeEnd(FormRenderer.java:206)
>> > > at
>> > > org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:224)
>> > > at
>> > > org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeEnd(HtmlFormRenderer.java:63)
>> > > at
>> > > javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:539)
>> > > --
>> > >
>> > > my Faces-Config:
>> > > =
>> > > 
>> > > 
>> > > 
>> > > org.apache.myfaces.trinidad.core
>> > > 
>> > > 
>> > >
>> > >
>> > > my Web.xml
>> > > 
>> > >  
>> > > 
>> > > 
>> > > org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
>> > > com.sun.facelets.FaceletViewHandler
>> > > 
>> > >
>> > > 
>> > > 
>> > > org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE
>> > > false
>> > > 
>> > >
>> > > 
>> > > 
>> > > org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
>> > > true
>> > > 
>> > >
>> > > 
>> > > 
>> > > org.apache.myfaces.trinidad.CHANGE_PERSISTENCE
>> > > session
>> > > 
>> > > 
>> > >
>> > >
>> > >  
>> > > 
>> > > trinidad
>> > > 
>> > > org.apache.myfaces.trinidad.webapp.TrinidadFilter
>> > > 
>> > >
>> > > 
>> > > trinidad
>> > > faces
>> > > 
>> > > 
>> > >
>> > >
>> > > 
>> > > 
>> > > resources
>> > > 
>> > > org.apache.myfaces.trinidad.webapp.ResourceServlet
>> > > 
>> > > 
>> > >
>> > >
>> > > my Pom.xml
>> > > 
>> > > 
>> > > 
>> > > org.apache.myfaces.trinidad
>> > > trinidad-api
>> > > 1.0.2
>> > > compile
>> > > 
>> > >
>> > > 
>> > > org.apache.myfaces.trinidad
>> > > trinidad-impl
>> > > 1.0.2
>> > > compile
>> > > 
>> > > 
>> > >
 >> > > Hi Wolfgang,
 >> > >
 >> > > don't specify the ViewHandler inside the faces-config.xml
 >> > > Do it inside the web.xml:
 >> > >
 >> > > 
 >> > >   
 >> > > org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
 >> > >   com.sun.facelets.FaceletViewHandler
 >> > > 
 >> > >
 >> > >
 >> > > for more see here:
 >> > > http://wiki.apache.org/myfaces/Facelets_with_Trinidad
 >> > >
 >> > > -Matthias
 >> > >
 >> > > On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> >>> > >> Hi,
>> >>> > >>
>> >>> > >> if I put the default rendererKit into my faces-config.xml
then
>> >>> > >> I got the following error:
>> >>> > >>
>> >>> > >> ---
>> >>> > >> 28.09.2007 16:13:43
>> >>> > >> org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit
>> >>> > >> createResponseWriter
>> >>> > >> SCHWERWIEGEND: No RenderingContext has been created.
>> >>> > >> 28.09.2007 16:13:43 com.sun.facelets.FaceletViewHandler
>> > > handleRenderException
>> >>> > >> SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
>> >>> > >> java.lang.IllegalStateException: No RenderingContext
>> >>> > >> at
>> >>> > >> org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer.java:193)
>> >>> > >> at
>> >>> > >> org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:56)
>> >>> > >> at
>> >>> > >> javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:515)
>> >>> > >> --

Re: Trinidad rendererKit error

[wkluge]

Re,

I have only one form tag in mei xhtml file.
I put the trinidad stuff in another much more smaller
xhtml file, to be sure having only this one form tag.
But same error.

You can view the xhtml here: http://nopaste.info/48d9a6aca3.html


>Is it possible,
>that you have a  inside a  ?

>-Matthias

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

> > Re Matthias,
> >
> > I went several times through the Facelets_with_Trinidad tutorial, but
I got
> > always the rendererKit Error.
> > I checked all config files again but I guess they should be ok.
> > I put the ViewHandler out of the faces-config and now I got another
> > error:
> > 
> > 28.09.2007 16:50:17 com.sun.facelets.FaceletViewHandler
handleRenderException
> > SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
> > java.lang.NullPointerException
> > at
> > org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.FormRenderer.encodeEnd(FormRenderer.java:206)
> > at
> > org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:224)
> > at
> > org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeEnd(HtmlFormRenderer.java:63)
> > at
> > javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:539)
> > --
> >
> > my Faces-Config:
> > =
> > 
> > 
> > 
> > org.apache.myfaces.trinidad.core
> > 
> > 
> >
> >
> > my Web.xml
> > 
> >  
> > 
> > 
> > org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
> > com.sun.facelets.FaceletViewHandler
> > 
> >
> > 
> > 
> > org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE
> > false
> > 
> >
> > 
> > 
> > org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
> > true
> > 
> >
> > 
> > 
> > org.apache.myfaces.trinidad.CHANGE_PERSISTENCE
> > session
> > 
> > 
> >
> >
> >  
> > 
> > trinidad
> > 
> > org.apache.myfaces.trinidad.webapp.TrinidadFilter
> > 
> >
> > 
> > trinidad
> > faces
> > 
> > 
> >
> >
> > 
> > 
> > resources
> > 
> > org.apache.myfaces.trinidad.webapp.ResourceServlet
> > 
> > 
> >
> >
> > my Pom.xml
> > 
> > 
> > 
> > org.apache.myfaces.trinidad
> > trinidad-api
> > 1.0.2
> > compile
> > 
> >
> > 
> > org.apache.myfaces.trinidad
> > trinidad-impl
> > 1.0.2
> > compile
> > 
> > 
> >
>> > > Hi Wolfgang,
>> > >
>> > > don't specify the ViewHandler inside the faces-config.xml
>> > > Do it inside the web.xml:
>> > >
>> > > 
>> > >   
>> > > org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
>> > >   com.sun.facelets.FaceletViewHandler
>> > > 
>> > >
>> > >
>> > > for more see here:
>> > > http://wiki.apache.org/myfaces/Facelets_with_Trinidad
>> > >
>> > > -Matthias
>> > >
>> > > On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>> > >> Hi,
>>> > >>
>>> > >> if I put the default rendererKit into my faces-config.xml then
>>> > >> I got the following error:
>>> > >>
>>> > >> ---
>>> > >> 28.09.2007 16:13:43
>>> > >> org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit
>>> > >> createResponseWriter
>>> > >> SCHWERWIEGEND: No RenderingContext has been created.
>>> > >> 28.09.2007 16:13:43 com.sun.facelets.FaceletViewHandler
> > handleRenderException
>>> > >> SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
>>> > >> java.lang.IllegalStateException: No RenderingContext
>>> > >> at
>>> > >> org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer.java:193)
>>> > >> at
>>> > >> org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:56)
>>> > >> at
>>> > >> javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:515)
>>> > >> --
>>> > >>
>>> > >>
>>> > >> But if I remove the default rendererKit, Trinidad throws
>>> > >> of course the following error:
>>> > >>
>>> > >> ---
>>> > >> 28.09.2007 16:19:41
org.apache.myfaces.trinidad.component.UIXComponentBase
>>> > >> _getRendererImpl
>>> > >> WARNUNG: Could not find renderer for CoreForm[UIXFacesBeanImpl,
id=_id97]
>>> > >> rendererType = org.apache.myfaces.trinidad.Form
>>> > >> 28.09.2007 16:19:41
org.apache.myfaces.trinidad.component.UIXComponentBase
>>> > >> _getRendererImpl
>>> > >> WARNUNG: Could not find renderer for
>>> > >> CoreInputText[UIXEditableFacesBeanImpl, id=input1] rendererType =
>>> > >> org.apache.myfaces.trinidad.Text
>>> > >> 28.09.2007 16:19:41
org.apache.myfaces.trinidad.component.UIXComponen

RE: Trinidad rendererKit error

[Edward Steel]

This tends to happen to me when I have nested forms. Check you have one
form and s within it if required.

Regards
Edd


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 28 September 2007 17:02
To: MyFaces Discussion
Subject: Re: Trinidad rendererKit error

Re Matthias,

I went several times through the Facelets_with_Trinidad tutorial, but I
got always the rendererKit Error.
I checked all config files again but I guess they should be ok.
I put the ViewHandler out of the faces-config and now I got another
error:

28.09.2007 16:50:17 com.sun.facelets.FaceletViewHandler
handleRenderException
SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
java.lang.NullPointerException
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.FormRenderer.en
codeEnd(FormRenderer.java:206)
at
org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.j
ava:224)
at
org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer
.encodeEnd(HtmlFormRenderer.java:63)
at
javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:539
)
--

my Faces-Config:
=



org.apache.myfaces.trinidad.core




my Web.xml

 

 
org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
com.sun.facelets.FaceletViewHandler



 
org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE
false



 
org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
true



 
org.apache.myfaces.trinidad.CHANGE_PERSISTENCE
session




 

trinidad
 
org.apache.myfaces.trinidad.webapp.TrinidadFilter



trinidad
faces






resources
 
org.apache.myfaces.trinidad.webapp.ResourceServlet




my Pom.xml



org.apache.myfaces.trinidad
trinidad-api
1.0.2
compile



org.apache.myfaces.trinidad
trinidad-impl
1.0.2
compile



> Hi Wolfgang,
>
> don't specify the ViewHandler inside the faces-config.xml Do it inside

> the web.xml:
>
> 
>
org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
>   com.sun.facelets.FaceletViewHandler
> 
>
>
> for more see here:
> http://wiki.apache.org/myfaces/Facelets_with_Trinidad
>
> -Matthias
>
> On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> if I put the default rendererKit into my faces-config.xml then I got 
>> the following error:
>>
>> -
>> --
>> 28.09.2007 16:13:43
>> org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit
>> createResponseWriter
>> SCHWERWIEGEND: No RenderingContext has been created.
>> 28.09.2007 16:13:43 com.sun.facelets.FaceletViewHandler
handleRenderException
>> SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
>> java.lang.IllegalStateException: No RenderingContext
>> at
>>
org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer
.java:193)
>> at
>>
org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer
.encodeBegin(HtmlFormRenderer.java:56)
>> at
>> javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.jav
>> a:515)
>> --
>>
>>
>> But if I remove the default rendererKit, Trinidad throws of course 
>> the following error:
>>
>> ---
>> 28.09.2007 16:19:41 
>> org.apache.myfaces.trinidad.component.UIXComponentBase
>> _getRendererImpl
>> WARNUNG: Could not find renderer for CoreForm[UIXFacesBeanImpl, 
>> id=_id97] rendererType = org.apache.myfaces.trinidad.Form
>> 28.09.2007 16:19:41 
>> org.apache.myfaces.trinidad.component.UIXComponentBase
>> _getRendererImpl
>> WARNUNG: Could not find renderer for
>> CoreInputText[UIXEditableFacesBeanImpl, id=input1] rendererType = 
>> org.apache.myfaces.trinidad.Text
>> 28.09.2007 16:19:41 
>> org.apache.myfaces.trinidad.component.UIXComponentBase
>> _getRendererImpl
>> WARNUNG: Could not find renderer for 
>> CoreCommandButton[UIXFacesBeanImpl,
>> id=button1] rendererType = org.apache.myfaces.trinidad.Button
>> ---
>>
>>
>> my faces-config.xml looks, how you can imagine, like this:
>> --
>> 
>>
com.sun.facelets.FaceletViewHandler
>> 
>>
>> 
>> 
>> 
>> org.apache.myfaces.trinidad.core
>> 
>> 
>> ---
>>
>>
>> Any suggestions?
>> Thanks a lot!
>>
>> Wolfgang
>>
>>
>
>






This message should be regarded as confidential. If you have received this 
email in error please notify the sender and destroy it immediately.
Statements of intent shall

Re: Trinidad rendererKit error

[Matthias Wessendorf]

Is it possible,
that you have a  inside a  ?

-Matthias

On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Re Matthias,
>
> I went several times through the Facelets_with_Trinidad tutorial, but I got
> always the rendererKit Error.
> I checked all config files again but I guess they should be ok.
> I put the ViewHandler out of the faces-config and now I got another
> error:
> 
> 28.09.2007 16:50:17 com.sun.facelets.FaceletViewHandler handleRenderException
> SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
> java.lang.NullPointerException
> at
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.FormRenderer.encodeEnd(FormRenderer.java:206)
> at
> org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:224)
> at
> org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeEnd(HtmlFormRenderer.java:63)
> at
> javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:539)
> --
>
> my Faces-Config:
> =
> 
> 
> 
> org.apache.myfaces.trinidad.core
> 
> 
>
>
> my Web.xml
> 
>  
> 
> 
> org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
> com.sun.facelets.FaceletViewHandler
> 
>
> 
> 
> org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE
> false
> 
>
> 
> 
> org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
> true
> 
>
> 
> 
> org.apache.myfaces.trinidad.CHANGE_PERSISTENCE
> session
> 
> 
>
>
>  
> 
> trinidad
> 
> org.apache.myfaces.trinidad.webapp.TrinidadFilter
> 
>
> 
> trinidad
> faces
> 
> 
>
>
> 
> 
> resources
> 
> org.apache.myfaces.trinidad.webapp.ResourceServlet
> 
> 
>
>
> my Pom.xml
> 
> 
> 
> org.apache.myfaces.trinidad
> trinidad-api
> 1.0.2
> compile
> 
>
> 
> org.apache.myfaces.trinidad
> trinidad-impl
> 1.0.2
> compile
> 
> 
>
> > Hi Wolfgang,
> >
> > don't specify the ViewHandler inside the faces-config.xml
> > Do it inside the web.xml:
> >
> > 
> >   
> > org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
> >   com.sun.facelets.FaceletViewHandler
> > 
> >
> >
> > for more see here:
> > http://wiki.apache.org/myfaces/Facelets_with_Trinidad
> >
> > -Matthias
> >
> > On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >> Hi,
> >>
> >> if I put the default rendererKit into my faces-config.xml then
> >> I got the following error:
> >>
> >> ---
> >> 28.09.2007 16:13:43
> >> org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit
> >> createResponseWriter
> >> SCHWERWIEGEND: No RenderingContext has been created.
> >> 28.09.2007 16:13:43 com.sun.facelets.FaceletViewHandler
> handleRenderException
> >> SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
> >> java.lang.IllegalStateException: No RenderingContext
> >> at
> >> org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer.java:193)
> >> at
> >> org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:56)
> >> at
> >> javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:515)
> >> --
> >>
> >>
> >> But if I remove the default rendererKit, Trinidad throws
> >> of course the following error:
> >>
> >> ---
> >> 28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
> >> _getRendererImpl
> >> WARNUNG: Could not find renderer for CoreForm[UIXFacesBeanImpl, id=_id97]
> >> rendererType = org.apache.myfaces.trinidad.Form
> >> 28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
> >> _getRendererImpl
> >> WARNUNG: Could not find renderer for
> >> CoreInputText[UIXEditableFacesBeanImpl, id=input1] rendererType =
> >> org.apache.myfaces.trinidad.Text
> >> 28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
> >> _getRendererImpl
> >> WARNUNG: Could not find renderer for CoreCommandButton[UIXFacesBeanImpl,
> >> id=button1] rendererType = org.apache.myfaces.trinidad.Button
> >> ---
> >>
> >>
> >> my faces-config.xml looks, how you can imagine, like this:
> >> --
> >> 
> >> com.sun.facelets.FaceletViewHandler
> >> 
> >>
> >> 
> >> 
> >> 
> >> org.apache.myfaces.trinidad.core
> >> 
> >> 
> >> ---
> >>
> >>
> >> Any suggestions?
> >> Thanks a lot!
> >>
> >> Wolfgang

Re: Trinidad rendererKit error

[wkluge]

Re Matthias,

I went several times through the Facelets_with_Trinidad tutorial, but I got
always the rendererKit Error.
I checked all config files again but I guess they should be ok.
I put the ViewHandler out of the faces-config and now I got another
error:

28.09.2007 16:50:17 com.sun.facelets.FaceletViewHandler handleRenderException
SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
java.lang.NullPointerException
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.FormRenderer.encodeEnd(FormRenderer.java:206)
at
org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:224)
at
org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeEnd(HtmlFormRenderer.java:63)
at
javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:539)
--

my Faces-Config:
=



org.apache.myfaces.trinidad.core




my Web.xml

 


org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
com.sun.facelets.FaceletViewHandler




org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE
false




org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
true



org.apache.myfaces.trinidad.CHANGE_PERSISTENCE
session




 

trinidad

org.apache.myfaces.trinidad.webapp.TrinidadFilter



trinidad
faces






resources

org.apache.myfaces.trinidad.webapp.ResourceServlet




my Pom.xml



org.apache.myfaces.trinidad
trinidad-api
1.0.2
compile



org.apache.myfaces.trinidad
trinidad-impl
1.0.2
compile



> Hi Wolfgang,
>
> don't specify the ViewHandler inside the faces-config.xml
> Do it inside the web.xml:
>
> 
>   org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
>   com.sun.facelets.FaceletViewHandler
> 
>
>
> for more see here:
> http://wiki.apache.org/myfaces/Facelets_with_Trinidad
>
> -Matthias
>
> On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> if I put the default rendererKit into my faces-config.xml then
>> I got the following error:
>>
>> ---
>> 28.09.2007 16:13:43
>> org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit
>> createResponseWriter
>> SCHWERWIEGEND: No RenderingContext has been created.
>> 28.09.2007 16:13:43 com.sun.facelets.FaceletViewHandler
handleRenderException
>> SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
>> java.lang.IllegalStateException: No RenderingContext
>> at
>> org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer.java:193)
>> at
>> org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:56)
>> at
>> javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:515)
>> --
>>
>>
>> But if I remove the default rendererKit, Trinidad throws
>> of course the following error:
>>
>> ---
>> 28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
>> _getRendererImpl
>> WARNUNG: Could not find renderer for CoreForm[UIXFacesBeanImpl, id=_id97]
>> rendererType = org.apache.myfaces.trinidad.Form
>> 28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
>> _getRendererImpl
>> WARNUNG: Could not find renderer for
>> CoreInputText[UIXEditableFacesBeanImpl, id=input1] rendererType =
>> org.apache.myfaces.trinidad.Text
>> 28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
>> _getRendererImpl
>> WARNUNG: Could not find renderer for CoreCommandButton[UIXFacesBeanImpl,
>> id=button1] rendererType = org.apache.myfaces.trinidad.Button
>> ---
>>
>>
>> my faces-config.xml looks, how you can imagine, like this:
>> --
>> 
>> com.sun.facelets.FaceletViewHandler
>> 
>>
>> 
>> 
>> 
>> org.apache.myfaces.trinidad.core
>> 
>> 
>> ---
>>
>>
>> Any suggestions?
>> Thanks a lot!
>>
>> Wolfgang
>>
>>
>
>

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Matthias Wessendorf]

U are asking, because JSF 1.2 has it ?

On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> No,
>
> http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_subform.html
>
> -Matze
>
> On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > Does the subform then have a prependId attribute?
> >
> > regards,
> >
> > Martin
> >
> > On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > > On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > > > @Stephen: tr:subform is a naming-container? ok. interesting. wonder why.
> > >
> > > that allows you to reuse IDs inside your subforms.
> > >
> > > >
> > > > @Matze: Why would he want to update the full form?
> > > I tried and it only worked that way. Isn't the real question, why
> > > using two forms in one page?
> > > Tobago, for instance has only one form, that is rendered with their
> > >  component.
> > >
> > > I think now, that Stephen uses a subForm, this solution is IMO more 
> > > correct.
> > >
> > > -M
> > > >
> > > > regards,
> > > >
> > > > Martin
> > > >
> > > > On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > > > > On 9/28/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote:
> > > > > > Thanks a lot for all the answers.
> > > > > > The duplicate id on form was actually a left-over from 
> > > > > > trial-and-error.
> > > > > > I still don't understand why it did not work (without an id at the 
> > > > > > form).
> > > > > > Sure, PPR works across forms, does it?
> > > > >
> > > > > I think you need to say partialTriggers="departments" on the second 
> > > > > form.
> > > > >
> > > > > -M
> > > > >
> > > > > >
> > > > > > Anyway this version works fine:
> > > > > >
> > > > > > |
> > > > > > |
> > > > > > | > > > > > |
> > > > > > value="#{scoreEntryHome.department}" autoSubmit="true">
> > > > > > |
> > > > > > | > > > > > value="#{scoreEntryHome.allowedDepartments}"
> > > > > > |var="department" 
> > > > > > label="#{department.name}"/>
> > > > > > |
> > > > > > |
> > > > > > |
> > > > > > |
> > > > > > | > > > > > value="#{scoreEntryHome.scoreEntries}"
> > > > > > |  partialTriggers=":selectForm:departments">
> > > > > >
> > > > > > Can somebody please add it to the tag docs that 
> > > > > > tr:selectOneChoice's autoSubmit does PPR?!
> > > > > >
> > > > > > Also it should be possible to switch to regular submit.
> > > > > > E.g. server-side error logs are more useful - an exception during a 
> > > > > > PPR request is logged, but without giving the nested, original 
> > > > > > exception.
> > > > > > Also currently individual component messages are not shown as a 
> > > > > > result of PPR.
> > > > > >
> > > > > > > tr:form isn't a namingcontainer
> > > > > >
> > > > > > On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > > > > > > Hi Stephen,
> > > > > > >
> > > > > > > do this:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > > > > > > >
> > > > > > > value="#{scoreEntryHome.department}"
> > > > > > >autoSubmit="true">
> > > > > > >
> > > > > > > > > > > > > value="#{scoreEntryHome.allowedDepartments}"
> > > > > > >   var="department" 
> > > > > > > label="#{department.name}"/>
> > > > > > >
> > > > > > >
> > > > > > > > > > > > >  action="#{scoreEntryHome.save}"/>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > > > > > > > value="#{scoreEntryHome.scoreEntries}"
> > > > > > >  
> > > > > > > partialTriggers="::departmentForm:departments">
> > > > > > >
> > > > > > >
> > > > > > > > > > > > > value="#{scoreEntry.name}"/>
> > > > > > >
> > > > > > >
> > > > > > > with :: you can get out of your naming-container up one level and 
> > > > > > > then
> > > > > > > back in again with : and name.
> > > > > > >
> > > > > > > regards,
> > > > > > >
> > > > > > > Martin
> > > > > > >
> > > > > > > On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> > > > > > > > You might try not using multiple forms and also not having the 
> > > > > > > > form
> > > > > > > > id="departments" and the selectOneChoice also set to 
> > > > > > > > "departments"
> > > > > > > >
> > > > > > > > -Richard
> > > > > > > >
> > > > > > > > Stephen Friedrich wrote:
> > > > > > > > > It seems that autoSubmit from a tr:selectOneChoice always 
> > > > > > > > > uses PPR.
> > > > > > > > > I can't get other components to update, though. This is what 
> > > > > > > > > I tried:
> > > > > > > > >
> > > > > > > > >   
> > > > > > > > >> > > > > > > > label="Department"
> > > > > > > > >   
> > > > > > > > > value="#{scoreEntryHome.department}"
> > > >

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Matthias Wessendorf]

No,

http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_subform.html

-Matze

On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> Does the subform then have a prependId attribute?
>
> regards,
>
> Martin
>
> On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > > @Stephen: tr:subform is a naming-container? ok. interesting. wonder why.
> >
> > that allows you to reuse IDs inside your subforms.
> >
> > >
> > > @Matze: Why would he want to update the full form?
> > I tried and it only worked that way. Isn't the real question, why
> > using two forms in one page?
> > Tobago, for instance has only one form, that is rendered with their
> >  component.
> >
> > I think now, that Stephen uses a subForm, this solution is IMO more correct.
> >
> > -M
> > >
> > > regards,
> > >
> > > Martin
> > >
> > > On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > > > On 9/28/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote:
> > > > > Thanks a lot for all the answers.
> > > > > The duplicate id on form was actually a left-over from 
> > > > > trial-and-error.
> > > > > I still don't understand why it did not work (without an id at the 
> > > > > form).
> > > > > Sure, PPR works across forms, does it?
> > > >
> > > > I think you need to say partialTriggers="departments" on the second 
> > > > form.
> > > >
> > > > -M
> > > >
> > > > >
> > > > > Anyway this version works fine:
> > > > >
> > > > > |
> > > > > |
> > > > > | > > > > |value="#{scoreEntryHome.department}" 
> > > > > autoSubmit="true">
> > > > > |
> > > > > | > > > > value="#{scoreEntryHome.allowedDepartments}"
> > > > > |var="department" 
> > > > > label="#{department.name}"/>
> > > > > |
> > > > > |
> > > > > |
> > > > > |
> > > > > | > > > > value="#{scoreEntryHome.scoreEntries}"
> > > > > |  partialTriggers=":selectForm:departments">
> > > > >
> > > > > Can somebody please add it to the tag docs that tr:selectOneChoice's 
> > > > > autoSubmit does PPR?!
> > > > >
> > > > > Also it should be possible to switch to regular submit.
> > > > > E.g. server-side error logs are more useful - an exception during a 
> > > > > PPR request is logged, but without giving the nested, original 
> > > > > exception.
> > > > > Also currently individual component messages are not shown as a 
> > > > > result of PPR.
> > > > >
> > > > > > tr:form isn't a namingcontainer
> > > > >
> > > > > On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > > > > > Hi Stephen,
> > > > > >
> > > > > > do this:
> > > > > >
> > > > > >
> > > > > >
> > > > > > > > > > >value="#{scoreEntryHome.department}"
> > > > > >autoSubmit="true">
> > > > > >
> > > > > > > > > > > value="#{scoreEntryHome.allowedDepartments}"
> > > > > >   var="department" 
> > > > > > label="#{department.name}"/>
> > > > > >
> > > > > >
> > > > > > > > > > >  action="#{scoreEntryHome.save}"/>
> > > > > >
> > > > > >
> > > > > >
> > > > > > > > > > > value="#{scoreEntryHome.scoreEntries}"
> > > > > >  partialTriggers="::departmentForm:departments">
> > > > > >
> > > > > >
> > > > > > > > > > > value="#{scoreEntry.name}"/>
> > > > > >
> > > > > >
> > > > > > with :: you can get out of your naming-container up one level and 
> > > > > > then
> > > > > > back in again with : and name.
> > > > > >
> > > > > > regards,
> > > > > >
> > > > > > Martin
> > > > > >
> > > > > > On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> > > > > > > You might try not using multiple forms and also not having the 
> > > > > > > form
> > > > > > > id="departments" and the selectOneChoice also set to "departments"
> > > > > > >
> > > > > > > -Richard
> > > > > > >
> > > > > > > Stephen Friedrich wrote:
> > > > > > > > It seems that autoSubmit from a tr:selectOneChoice always uses 
> > > > > > > > PPR.
> > > > > > > > I can't get other components to update, though. This is what I 
> > > > > > > > tried:
> > > > > > > >
> > > > > > > >   
> > > > > > > >> > > > > > > label="Department"
> > > > > > > >   
> > > > > > > > value="#{scoreEntryHome.department}"
> > > > > > > >   autoSubmit="true">
> > > > > > > >
> > > > > > > >> > > > value="#{scoreEntryHome.allowedDepartments}"
> > > > > > > >  var="department"
> > > > > label="#{department.name}"/>
> > > > > > > >   
> > > > > > > >
> > > > > > > >> > > > > > > action="#{scoreEntryHome.save}"/>
> > > > > > > >  

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Martin Marinschek]

Does the subform then have a prependId attribute?

regards,

Martin

On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > @Stephen: tr:subform is a naming-container? ok. interesting. wonder why.
>
> that allows you to reuse IDs inside your subforms.
>
> >
> > @Matze: Why would he want to update the full form?
> I tried and it only worked that way. Isn't the real question, why
> using two forms in one page?
> Tobago, for instance has only one form, that is rendered with their
>  component.
>
> I think now, that Stephen uses a subForm, this solution is IMO more correct.
>
> -M
> >
> > regards,
> >
> > Martin
> >
> > On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > > On 9/28/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote:
> > > > Thanks a lot for all the answers.
> > > > The duplicate id on form was actually a left-over from trial-and-error.
> > > > I still don't understand why it did not work (without an id at the 
> > > > form).
> > > > Sure, PPR works across forms, does it?
> > >
> > > I think you need to say partialTriggers="departments" on the second form.
> > >
> > > -M
> > >
> > > >
> > > > Anyway this version works fine:
> > > >
> > > > |
> > > > |
> > > > | > > > |value="#{scoreEntryHome.department}" 
> > > > autoSubmit="true">
> > > > |
> > > > | > > > value="#{scoreEntryHome.allowedDepartments}"
> > > > |var="department" 
> > > > label="#{department.name}"/>
> > > > |
> > > > |
> > > > |
> > > > |
> > > > | > > > value="#{scoreEntryHome.scoreEntries}"
> > > > |  partialTriggers=":selectForm:departments">
> > > >
> > > > Can somebody please add it to the tag docs that tr:selectOneChoice's 
> > > > autoSubmit does PPR?!
> > > >
> > > > Also it should be possible to switch to regular submit.
> > > > E.g. server-side error logs are more useful - an exception during a PPR 
> > > > request is logged, but without giving the nested, original exception.
> > > > Also currently individual component messages are not shown as a result 
> > > > of PPR.
> > > >
> > > > > tr:form isn't a namingcontainer
> > > >
> > > > On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > > > > Hi Stephen,
> > > > >
> > > > > do this:
> > > > >
> > > > >
> > > > >
> > > > > > > > >value="#{scoreEntryHome.department}"
> > > > >autoSubmit="true">
> > > > >
> > > > > > > > > value="#{scoreEntryHome.allowedDepartments}"
> > > > >   var="department" 
> > > > > label="#{department.name}"/>
> > > > >
> > > > >
> > > > > > > > >  action="#{scoreEntryHome.save}"/>
> > > > >
> > > > >
> > > > >
> > > > > > > > > value="#{scoreEntryHome.scoreEntries}"
> > > > >  partialTriggers="::departmentForm:departments">
> > > > >
> > > > >
> > > > > > > > > value="#{scoreEntry.name}"/>
> > > > >
> > > > >
> > > > > with :: you can get out of your naming-container up one level and then
> > > > > back in again with : and name.
> > > > >
> > > > > regards,
> > > > >
> > > > > Martin
> > > > >
> > > > > On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> > > > > > You might try not using multiple forms and also not having the form
> > > > > > id="departments" and the selectOneChoice also set to "departments"
> > > > > >
> > > > > > -Richard
> > > > > >
> > > > > > Stephen Friedrich wrote:
> > > > > > > It seems that autoSubmit from a tr:selectOneChoice always uses 
> > > > > > > PPR.
> > > > > > > I can't get other components to update, though. This is what I 
> > > > > > > tried:
> > > > > > >
> > > > > > >   
> > > > > > >> > > > > >   value="#{scoreEntryHome.department}"
> > > > > > >   autoSubmit="true">
> > > > > > >
> > > > > > >> > > value="#{scoreEntryHome.allowedDepartments}"
> > > > > > >  var="department"
> > > > label="#{department.name}"/>
> > > > > > >   
> > > > > > >
> > > > > > >> > > > > > action="#{scoreEntryHome.save}"/>
> > > > > > >   
> > > > > > >
> > > > > > >   
> > > > > > >> > > value="#{scoreEntryHome.scoreEntries}"
> > > > > > > partialTriggers="departments">
> > > > > > >
> > > > > > >   
> > > > > > >> > > > > > value="#{scoreEntry.name}"/>
> > > > > > >   
> > > > > > >
> > > > > > > On the server scoreEntryHome.setDepartment() gets correctly 
> > > > > > > called with
> > > > the
> > > > > > > newly selected department, but the table won't update.
> > > 

Re: Trinidad rendererKit error

[Matthias Wessendorf]

Hi Wolfgang,

don't specify the ViewHandler inside the faces-config.xml
Do it inside the web.xml:


  org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
  com.sun.facelets.FaceletViewHandler



for more see here:
http://wiki.apache.org/myfaces/Facelets_with_Trinidad

-Matthias

On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi,
>
> if I put the default rendererKit into my faces-config.xml then
> I got the following error:
>
> ---
> 28.09.2007 16:13:43
> org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit
> createResponseWriter
> SCHWERWIEGEND: No RenderingContext has been created.
> 28.09.2007 16:13:43 com.sun.facelets.FaceletViewHandler handleRenderException
> SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
> java.lang.IllegalStateException: No RenderingContext
> at
> org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer.java:193)
> at
> org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:56)
> at
> javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:515)
> --
>
>
> But if I remove the default rendererKit, Trinidad throws
> of course the following error:
>
> ---
> 28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
> _getRendererImpl
> WARNUNG: Could not find renderer for CoreForm[UIXFacesBeanImpl, id=_id97]
> rendererType = org.apache.myfaces.trinidad.Form
> 28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
> _getRendererImpl
> WARNUNG: Could not find renderer for
> CoreInputText[UIXEditableFacesBeanImpl, id=input1] rendererType =
> org.apache.myfaces.trinidad.Text
> 28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
> _getRendererImpl
> WARNUNG: Could not find renderer for CoreCommandButton[UIXFacesBeanImpl,
> id=button1] rendererType = org.apache.myfaces.trinidad.Button
> ---
>
>
> my faces-config.xml looks, how you can imagine, like this:
> --
> 
> com.sun.facelets.FaceletViewHandler
> 
>
> 
> 
> 
> org.apache.myfaces.trinidad.core
> 
> 
> ---
>
>
> Any suggestions?
> Thanks a lot!
>
> Wolfgang
>
>


-- 
Matthias Wessendorf

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

Trinidad rendererKit error

[wkluge]

Hi,

if I put the default rendererKit into my faces-config.xml then
I got the following error:

---
28.09.2007 16:13:43
org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit
createResponseWriter
SCHWERWIEGEND: No RenderingContext has been created.
28.09.2007 16:13:43 com.sun.facelets.FaceletViewHandler handleRenderException
SCHWERWIEGEND: Error Rendering View[/homePage.xhtml]
java.lang.IllegalStateException: No RenderingContext
at
org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer.java:193)
at
org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:56)
at
javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:515)
--


But if I remove the default rendererKit, Trinidad throws
of course the following error:

---
28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
_getRendererImpl
WARNUNG: Could not find renderer for CoreForm[UIXFacesBeanImpl, id=_id97]
rendererType = org.apache.myfaces.trinidad.Form
28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
_getRendererImpl
WARNUNG: Could not find renderer for
CoreInputText[UIXEditableFacesBeanImpl, id=input1] rendererType =
org.apache.myfaces.trinidad.Text
28.09.2007 16:19:41 org.apache.myfaces.trinidad.component.UIXComponentBase
_getRendererImpl
WARNUNG: Could not find renderer for CoreCommandButton[UIXFacesBeanImpl,
id=button1] rendererType = org.apache.myfaces.trinidad.Button
---


my faces-config.xml looks, how you can imagine, like this:
--

com.sun.facelets.FaceletViewHandler





org.apache.myfaces.trinidad.core


---


Any suggestions?
Thanks a lot!

Wolfgang

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Matthias Wessendorf]

On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> @Stephen: tr:subform is a naming-container? ok. interesting. wonder why.

that allows you to reuse IDs inside your subforms.

>
> @Matze: Why would he want to update the full form?
I tried and it only worked that way. Isn't the real question, why
using two forms in one page?
Tobago, for instance has only one form, that is rendered with their
 component.

I think now, that Stephen uses a subForm, this solution is IMO more correct.

-M
>
> regards,
>
> Martin
>
> On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > On 9/28/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote:
> > > Thanks a lot for all the answers.
> > > The duplicate id on form was actually a left-over from trial-and-error.
> > > I still don't understand why it did not work (without an id at the form).
> > > Sure, PPR works across forms, does it?
> >
> > I think you need to say partialTriggers="departments" on the second form.
> >
> > -M
> >
> > >
> > > Anyway this version works fine:
> > >
> > > |
> > > |
> > > | > > |value="#{scoreEntryHome.department}" 
> > > autoSubmit="true">
> > > |
> > > | > > value="#{scoreEntryHome.allowedDepartments}"
> > > |var="department" 
> > > label="#{department.name}"/>
> > > |
> > > |
> > > |
> > > |
> > > | > > value="#{scoreEntryHome.scoreEntries}"
> > > |  partialTriggers=":selectForm:departments">
> > >
> > > Can somebody please add it to the tag docs that tr:selectOneChoice's 
> > > autoSubmit does PPR?!
> > >
> > > Also it should be possible to switch to regular submit.
> > > E.g. server-side error logs are more useful - an exception during a PPR 
> > > request is logged, but without giving the nested, original exception.
> > > Also currently individual component messages are not shown as a result of 
> > > PPR.
> > >
> > > > tr:form isn't a namingcontainer
> > >
> > > On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > > > Hi Stephen,
> > > >
> > > > do this:
> > > >
> > > >
> > > >
> > > > > > >value="#{scoreEntryHome.department}"
> > > >autoSubmit="true">
> > > >
> > > > > > > value="#{scoreEntryHome.allowedDepartments}"
> > > >   var="department" 
> > > > label="#{department.name}"/>
> > > >
> > > >
> > > > > > >  action="#{scoreEntryHome.save}"/>
> > > >
> > > >
> > > >
> > > > > > > value="#{scoreEntryHome.scoreEntries}"
> > > >  partialTriggers="::departmentForm:departments">
> > > >
> > > >
> > > > > > > value="#{scoreEntry.name}"/>
> > > >
> > > >
> > > > with :: you can get out of your naming-container up one level and then
> > > > back in again with : and name.
> > > >
> > > > regards,
> > > >
> > > > Martin
> > > >
> > > > On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> > > > > You might try not using multiple forms and also not having the form
> > > > > id="departments" and the selectOneChoice also set to "departments"
> > > > >
> > > > > -Richard
> > > > >
> > > > > Stephen Friedrich wrote:
> > > > > > It seems that autoSubmit from a tr:selectOneChoice always uses PPR.
> > > > > > I can't get other components to update, though. This is what I 
> > > > > > tried:
> > > > > >
> > > > > >   
> > > > > >> > > > >   value="#{scoreEntryHome.department}"
> > > > > >   autoSubmit="true">
> > > > > >
> > > > > >> > value="#{scoreEntryHome.allowedDepartments}"
> > > > > >  var="department"
> > > label="#{department.name}"/>
> > > > > >   
> > > > > >
> > > > > >> > > > > action="#{scoreEntryHome.save}"/>
> > > > > >   
> > > > > >
> > > > > >   
> > > > > >> > value="#{scoreEntryHome.scoreEntries}"
> > > > > > partialTriggers="departments">
> > > > > >
> > > > > >   
> > > > > >> > > > > value="#{scoreEntry.name}"/>
> > > > > >   
> > > > > >
> > > > > > On the server scoreEntryHome.setDepartment() gets correctly called 
> > > > > > with
> > > the
> > > > > > newly selected department, but the table won't update.
> > > > > >
> > > > > > I added the "Update" button just for testing, and of course it works
> > > fine.
> > > > > >
> > > > > > What am I doing wrong this time? ;-)
> > > > > >
> > > > > > Alternatively: Is there a way to disable PPR for autoSubmit?
> > > > > > Oh, and additionally: It should be documented in the tag description
> > > that
> > > > > > autoSubmit does PPR.
> > > > > >
> > > > > > (Trinidad 1.0.2, MyFaces 1.1.5, Face

Re: [Trinidad] tr:iterator

[Francisco Passos]

Hello there.

I tried ui:repeat and the same happened. Before I tried t:dataList, I
realized I was using a facelet and conditionally including two other pages
which both had this code. I figured it might be causing some problems, so I
switched them both to compositions with the original page. The problem
ceased.

Thank you for your help!
Francisco

On 9/27/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
>
> May I also suggest to look at t:dataList?
>
> regards,
>
> Martin
>
> On 9/28/07, William Gosse <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > I've seen tr:iterator not behave well when laying out commandLinks
> > horizontally.  I've had much better luck with the Facelets ui:repeat tag
> for
> > this kind of stuff.  Unfortunately it doesn't have a varStatus.
> >
> >
> >
> >  
> >
> >
> > From: Francisco Passos [mailto:[EMAIL PROTECTED]
> >  Sent: Thursday, September 27, 2007 12:42 PM
> >  To: MyFaces Discussion
> >  Subject: [Trinidad] tr:iterator
> >
> >
> >
> >
> > Good afternoon!
> >
> >  I'm using tr:iterator to present various commandLinks on a page.
> >  The problem is: they are always duplicated. I've checked and the list
> on
> > the bean only has 2 elements. However 4 links are generated. Here's the
> > xhtml:
> >
> >   > var="grupoAtributos" binding="#{fichaBean.tabNavigationPane}"
> > varStatus="status">
> >
> >  
> >
> >   > partialSubmit="true" selected="#{grupoAtributos.igrupoid eq
> > fichaBean.selectedGroupId}" actionListener="#{fichaBean.refreshIt}">
> >   > to="#{fichaBean.selectedGroupId}" />
> >  
> >
> >  
> >
> >
> >  Does anyone know why this happens and what I can do to avoid it?
> >
> >  Thank you,
> >  Francisco Passos
> > The information transmitted herewith is sensitive information of
> Chordiant
> > Software or its customers and is intended only for use to the individual
> or
> > entity to which it is addressed. If the reader of this message is not
> the
> > intended recipient, you are hereby notified that any review,
> retransmission,
> > dissemination, distribution, copying or other use of, or taking of any
> > action in reliance upon, this information is strictly prohibited. If you
> > have received this communication in error, please contact the sender and
> > delete the material from your computer.
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Martin Marinschek]

@Stephen: tr:subform is a naming-container? ok. interesting. wonder why.

@Matze: Why would he want to update the full form?

regards,

Martin

On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> On 9/28/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote:
> > Thanks a lot for all the answers.
> > The duplicate id on form was actually a left-over from trial-and-error.
> > I still don't understand why it did not work (without an id at the form).
> > Sure, PPR works across forms, does it?
>
> I think you need to say partialTriggers="departments" on the second form.
>
> -M
>
> >
> > Anyway this version works fine:
> >
> > |
> > |
> > | > |value="#{scoreEntryHome.department}" 
> > autoSubmit="true">
> > |
> > | > |var="department" 
> > label="#{department.name}"/>
> > |
> > |
> > |
> > |
> > | > value="#{scoreEntryHome.scoreEntries}"
> > |  partialTriggers=":selectForm:departments">
> >
> > Can somebody please add it to the tag docs that tr:selectOneChoice's 
> > autoSubmit does PPR?!
> >
> > Also it should be possible to switch to regular submit.
> > E.g. server-side error logs are more useful - an exception during a PPR 
> > request is logged, but without giving the nested, original exception.
> > Also currently individual component messages are not shown as a result of 
> > PPR.
> >
> > > tr:form isn't a namingcontainer
> >
> > On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > > Hi Stephen,
> > >
> > > do this:
> > >
> > >
> > >
> > > > >value="#{scoreEntryHome.department}"
> > >autoSubmit="true">
> > >
> > > > >   var="department" 
> > > label="#{department.name}"/>
> > >
> > >
> > > > >  action="#{scoreEntryHome.save}"/>
> > >
> > >
> > >
> > > > > value="#{scoreEntryHome.scoreEntries}"
> > >  partialTriggers="::departmentForm:departments">
> > >
> > >
> > >
> > >
> > >
> > > with :: you can get out of your naming-container up one level and then
> > > back in again with : and name.
> > >
> > > regards,
> > >
> > > Martin
> > >
> > > On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> > > > You might try not using multiple forms and also not having the form
> > > > id="departments" and the selectOneChoice also set to "departments"
> > > >
> > > > -Richard
> > > >
> > > > Stephen Friedrich wrote:
> > > > > It seems that autoSubmit from a tr:selectOneChoice always uses PPR.
> > > > > I can't get other components to update, though. This is what I tried:
> > > > >
> > > > >   
> > > > >> > > >   value="#{scoreEntryHome.department}"
> > > > >   autoSubmit="true">
> > > > >
> > > > >> value="#{scoreEntryHome.allowedDepartments}"
> > > > >  var="department"
> > label="#{department.name}"/>
> > > > >   
> > > > >
> > > > >> > > > action="#{scoreEntryHome.save}"/>
> > > > >   
> > > > >
> > > > >   
> > > > >> value="#{scoreEntryHome.scoreEntries}"
> > > > > partialTriggers="departments">
> > > > >
> > > > >   
> > > > >> > > > value="#{scoreEntry.name}"/>
> > > > >   
> > > > >
> > > > > On the server scoreEntryHome.setDepartment() gets correctly called 
> > > > > with
> > the
> > > > > newly selected department, but the table won't update.
> > > > >
> > > > > I added the "Update" button just for testing, and of course it works
> > fine.
> > > > >
> > > > > What am I doing wrong this time? ;-)
> > > > >
> > > > > Alternatively: Is there a way to disable PPR for autoSubmit?
> > > > > Oh, and additionally: It should be documented in the tag description
> > that
> > > > > autoSubmit does PPR.
> > > > >
> > > > > (Trinidad 1.0.2, MyFaces 1.1.5, Facelets from VCS, Seam 1.2.1 on 
> > > > > Tomcat
> > 5.5.17)
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > >
> > > http://www.irian.at
> > >
> > > Your JSF powerhouse -
> > > JSF Consulting, Development and
> > > Courses in English and German
> > >
> > > Professional Support for Apache MyFaces
> > >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > further stuff:
> > blog: http://matthiaswessendorf.wordpress.com/
> > mail: matzew-at-apache-dot-org
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>


-- 

http://www.irian.at

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

Professional Support for Apache MyFaces

RE: [Trinidad] IE rendering issues.

[Darren McEntee]

Hi, 

 

Can anyone help me find a work around for this issue, caused by the
Trinidad bug?

I can't seem to find anything in the archives. (Details below...)

 

Thanks,

Darren.

 

 

-Original Message-
From: Danny Robinson [mailto:[EMAIL PROTECTED] 
Sent: 11 September 2007 16:39
To: MyFaces Discussion
Subject: Re: [Trinidad] IE rendering issues.

 

 

Darren

 

That's a known reported (sorry I don't have the issue number to hand)

issue that we hope to fix very soon.  Check the archives for possible

workarounds.

 

Danny

 

 

On 9/11/07, Darren McEntee <[EMAIL PROTECTED]> wrote:

> Hi,

> 

> I have some issues with rendering input fields in IE when they have

> validators or required attribute is set.

> 

> The page contains several fields and partial page rendered is used.

> 

> On a redisplay of the page, with drop downs etc. correctly updated,

> there is a 'padded' space under the validated fields (dates and a

> required drop down). This 'padded' space is where I would expect

> validation messages to appear. There are no validation errors so I
would

> not expect this space to appear.

> 

> Is this down to IE handling/mishandling the default Trinidad css? Or
is

> there some other configuration required?

> 

> Works fine in Firefox.

> 

> 

> 

> Thanks,

> 

> Darren.

> 

> 

> Please consider the environment before printing this email
 
P Please consider the environment before printing this email
_ 
 
1. The information contained in this E-mail, including any files transmitted 
with it, is confidential and may be legally privileged. This E-mail is intended 
only for the personal attention of the stated addressee(s). Any access to this 
E-mail, including any files transmitted with it, by any other person is 
unauthorised. If you are not an addressee, you must not disclose, copy, 
circulate or in any other way use or rely on the information contained in this 
E-mail or any files transmitted with it. Such unauthorised use may be unlawful. 
If you have received this E-mail in error, please inform the sender immediately 
and delete it and all copies from your system. You may not forward this E-mail 
without the permission of the sender.
 
2. The views expressed in this E-mail are those of the author, and do not 
necessarily represent the views of AMT-SYBEX. Internet communications are not 
secure and AMT-SYBEX cannot, therefore, accept legal responsibility for the 
contents of this message nor for any damage caused by viruses.
 
AMT-SYBEX Limited is a UK company, registration number GB03036807 at address 
The Spirella Building, Bridge Road, Letchworth, SG6 4ET. 
AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at address 
Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ.
For more information on the AMT-SYBEX Group visit http://www.amt-sybex.com
_

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Matthias Wessendorf]

On 9/28/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote:
> Thanks a lot for all the answers.
> The duplicate id on form was actually a left-over from trial-and-error.
> I still don't understand why it did not work (without an id at the form).
> Sure, PPR works across forms, does it?

I think you need to say partialTriggers="departments" on the second form.

-M

>
> Anyway this version works fine:
>
> |
> |
> | |value="#{scoreEntryHome.department}" 
> autoSubmit="true">
> |
> | |var="department" label="#{department.name}"/>
> |
> |
> |
> |
> | |  partialTriggers=":selectForm:departments">
>
> Can somebody please add it to the tag docs that tr:selectOneChoice's 
> autoSubmit does PPR?!
>
> Also it should be possible to switch to regular submit.
> E.g. server-side error logs are more useful - an exception during a PPR 
> request is logged, but without giving the nested, original exception.
> Also currently individual component messages are not shown as a result of PPR.
>
> > tr:form isn't a namingcontainer
>
> On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > Hi Stephen,
> >
> > do this:
> >
> >
> >
> > >value="#{scoreEntryHome.department}"
> >autoSubmit="true">
> >
> > >   var="department" label="#{department.name}"/>
> >
> >
> > >  action="#{scoreEntryHome.save}"/>
> >
> >
> >
> > >  partialTriggers="::departmentForm:departments">
> >
> >
> >
> >
> >
> > with :: you can get out of your naming-container up one level and then
> > back in again with : and name.
> >
> > regards,
> >
> > Martin
> >
> > On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> > > You might try not using multiple forms and also not having the form
> > > id="departments" and the selectOneChoice also set to "departments"
> > >
> > > -Richard
> > >
> > > Stephen Friedrich wrote:
> > > > It seems that autoSubmit from a tr:selectOneChoice always uses PPR.
> > > > I can't get other components to update, though. This is what I tried:
> > > >
> > > >   
> > > >> > >   value="#{scoreEntryHome.department}"
> > > >   autoSubmit="true">
> > > >
> > > >value="#{scoreEntryHome.allowedDepartments}"
> > > >  var="department"
> label="#{department.name}"/>
> > > >   
> > > >
> > > >> > > action="#{scoreEntryHome.save}"/>
> > > >   
> > > >
> > > >   
> > > >value="#{scoreEntryHome.scoreEntries}"
> > > > partialTriggers="departments">
> > > >
> > > >   
> > > >   
> > > >   
> > > >
> > > > On the server scoreEntryHome.setDepartment() gets correctly called with
> the
> > > > newly selected department, but the table won't update.
> > > >
> > > > I added the "Update" button just for testing, and of course it works
> fine.
> > > >
> > > > What am I doing wrong this time? ;-)
> > > >
> > > > Alternatively: Is there a way to disable PPR for autoSubmit?
> > > > Oh, and additionally: It should be documented in the tag description
> that
> > > > autoSubmit does PPR.
> > > >
> > > > (Trinidad 1.0.2, MyFaces 1.1.5, Facelets from VCS, Seam 1.2.1 on Tomcat
> 5.5.17)
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> >
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>


-- 
Matthias Wessendorf

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

Re: output formatting ? ?

[Chetan Bob]

hi NABA and All

The issue is that i want the text to be shown in the format it was entered
i.e. with carriage return and newline. The text got saved to database with
that formatting but when i fetch that text and tried to display the
formatting of newline is lost and get displayed with 

and this text data was collected in database using lebel and text contains
newline and carriage return



Thanks

Chetu


NABA w

Chetan Bob wrote:
> 
>  Hi  
> 
> I m getting some text from and saving it to database .then while
> displaying it using h:outputText 
> the formatting  at the time of entering text is lost and output is withut
> carriage return 
> 
> 
> 
> is also not working 
> 
> What can be solution please reply 
> 

-- 
View this message in context: 
http://www.nabble.com/output-formatting--tf4507760.html#a12941751
Sent from the MyFaces - Users mailing list archive at Nabble.com.

[core] display label from resource bundle in validation message

[Thomas Fischer]

Hi all,

We have an input field that looks like:



If the "required" validation fails, the label is be replaced into
placeholder {0} of the validation message "{0}: Validation Error: Value is
required."

Trying to internationalize the application, we now load the label from a
resource bundle:




Now, the label is not correctly replaced in the message; instead "null" is
inserted into the placeholder. We have checked that the label is accessed
correctly, the same expression in an outputText does find the message.

I assume the following happens: The label replacement takes place in the
processValidations phase (when the validation fails). In this phase. the
message bundle is not yet registered (this happens in the
renderResponsePhase when the jsp page with the loadBundle is executed).

I have also found the following remark in the class
org.apache.myfaces.taglib.core.LoadBundleTag, which points in the same
direction:
 * TODO:
 * We should find a way to save loaded bundles in the state, because
otherwise
 * on the next request the bundle map will not be present before the render
phase
 * and value bindings that reference to the bundle will always log annoying
 * "Variable 'xxx' could not be resolved" error messages.

Does anybody have an idea how one could achieve this ?

Regards

Thomas

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Stephen Friedrich]

Because as opposed to tr:form, tr:subform _is_ a naming container.

I still don't get why my original attempt did not work.


> Oh, right. Wonder why Stephen's solution finally works then?
> regards,

> Martin

On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> tr:form isn't a namingcontainer
>
> On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > Hi Stephen,
> >
> > do this:
> >
> >
> >
> > >value="#{scoreEntryHome.department}"
> >autoSubmit="true">
> >
> > >   var="department" 
label="#{department.name}"/>
> >
> >
> > >  action="#{scoreEntryHome.save}"/>
> >
> >
> >
> > >  partialTriggers="::departmentForm:departments">
> >
> >
> >
> >
> >
> > with :: you can get out of your naming-container up one level and then
> > back in again with : and name.
> >
> > regards,
> >
> > Martin
> >
> > On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> > > You might try not using multiple forms and also not having the form
> > > id="departments" and the selectOneChoice also set to "departments"
> > >
> > > -Richard
> > >
> > > Stephen Friedrich wrote:
> > > > It seems that autoSubmit from a tr:selectOneChoice always uses PPR.
> > > > I can't get other components to update, though. This is what I tried:
> > > >
> > > >   
> > > >> > >   value="#{scoreEntryHome.department}"
> > > >   autoSubmit="true">
> > > >
> > > >> > >  var="department" 
label="#{department.name}"/>
> > > >   
> > > >
> > > >> > > action="#{scoreEntryHome.save}"/>
> > > >   
> > > >
> > > >   
> > > >> > > partialTriggers="departments">
> > > >
> > > >   
> > > >   
> > > >   
> > > >
> > > > On the server scoreEntryHome.setDepartment() gets correctly called with 
the
> > > > newly selected department, but the table won't update.
> > > >
> > > > I added the "Update" button just for testing, and of course it works 
fine.
> > > >
> > > > What am I doing wrong this time? ;-)
> > > >
> > > > Alternatively: Is there a way to disable PPR for autoSubmit?
> > > > Oh, and additionally: It should be documented in the tag description 
that
> > > > autoSubmit does PPR.
> > > >
> > > > (Trinidad 1.0.2, MyFaces 1.1.5, Facelets from VCS, Seam 1.2.1 on Tomcat 
5.5.17)
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> >
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>


-- 

http://www.irian.at

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

Professional Support for Apache MyFaces

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Martin Marinschek]

Oh, right. Wonder why Stephen's solution finally works then?

regards,

Martin

On 9/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> tr:form isn't a namingcontainer
>
> On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > Hi Stephen,
> >
> > do this:
> >
> >
> >
> > >value="#{scoreEntryHome.department}"
> >autoSubmit="true">
> >
> > >   var="department" label="#{department.name}"/>
> >
> >
> > >  action="#{scoreEntryHome.save}"/>
> >
> >
> >
> > >  partialTriggers="::departmentForm:departments">
> >
> >
> >
> >
> >
> > with :: you can get out of your naming-container up one level and then
> > back in again with : and name.
> >
> > regards,
> >
> > Martin
> >
> > On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> > > You might try not using multiple forms and also not having the form
> > > id="departments" and the selectOneChoice also set to "departments"
> > >
> > > -Richard
> > >
> > > Stephen Friedrich wrote:
> > > > It seems that autoSubmit from a tr:selectOneChoice always uses PPR.
> > > > I can't get other components to update, though. This is what I tried:
> > > >
> > > >   
> > > >> > >   value="#{scoreEntryHome.department}"
> > > >   autoSubmit="true">
> > > >
> > > >> > > value="#{scoreEntryHome.allowedDepartments}"
> > > >  var="department" 
> > > > label="#{department.name}"/>
> > > >   
> > > >
> > > >> > > action="#{scoreEntryHome.save}"/>
> > > >   
> > > >
> > > >   
> > > >> > > value="#{scoreEntryHome.scoreEntries}"
> > > > partialTriggers="departments">
> > > >
> > > >   
> > > >   
> > > >   
> > > >
> > > > On the server scoreEntryHome.setDepartment() gets correctly called with 
> > > > the
> > > > newly selected department, but the table won't update.
> > > >
> > > > I added the "Update" button just for testing, and of course it works 
> > > > fine.
> > > >
> > > > What am I doing wrong this time? ;-)
> > > >
> > > > Alternatively: Is there a way to disable PPR for autoSubmit?
> > > > Oh, and additionally: It should be documented in the tag description 
> > > > that
> > > > autoSubmit does PPR.
> > > >
> > > > (Trinidad 1.0.2, MyFaces 1.1.5, Facelets from VCS, Seam 1.2.1 on Tomcat 
> > > > 5.5.17)
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> >
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>


-- 

http://www.irian.at

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

Professional Support for Apache MyFaces

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Stephen Friedrich]

Thanks a lot for all the answers.
The duplicate id on form was actually a left-over from trial-and-error.
I still don't understand why it did not work (without an id at the form).
Sure, PPR works across forms, does it?

Anyway this version works fine:

|
|
|
| 
|
|
|
|
|
|

Can somebody please add it to the tag docs that tr:selectOneChoice's autoSubmit 
does PPR?!

Also it should be possible to switch to regular submit.
E.g. server-side error logs are more useful - an exception during a PPR request 
is logged, but without giving the nested, original exception.
Also currently individual component messages are not shown as a result of PPR.

> tr:form isn't a namingcontainer

On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> Hi Stephen,
>
> do this:
>
>
>
>value="#{scoreEntryHome.department}"
>autoSubmit="true">
>
>   var="department" label="#{department.name}"/>
>
>
>  action="#{scoreEntryHome.save}"/>
>
>
>
>  partialTriggers="::departmentForm:departments">
>
>
>
>
>
> with :: you can get out of your naming-container up one level and then
> back in again with : and name.
>
> regards,
>
> Martin
>
> On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> > You might try not using multiple forms and also not having the form
> > id="departments" and the selectOneChoice also set to "departments"
> >
> > -Richard
> >
> > Stephen Friedrich wrote:
> > > It seems that autoSubmit from a tr:selectOneChoice always uses PPR.
> > > I can't get other components to update, though. This is what I tried:
> > >
> > >   
> > >> >   value="#{scoreEntryHome.department}"
> > >   autoSubmit="true">
> > >
> > >> >  var="department" 
label="#{department.name}"/>
> > >   
> > >
> > >> > action="#{scoreEntryHome.save}"/>
> > >   
> > >
> > >   
> > >> > partialTriggers="departments">
> > >
> > >   
> > >   
> > >   
> > >
> > > On the server scoreEntryHome.setDepartment() gets correctly called with 
the
> > > newly selected department, but the table won't update.
> > >
> > > I added the "Update" button just for testing, and of course it works 
fine.
> > >
> > > What am I doing wrong this time? ;-)
> > >
> > > Alternatively: Is there a way to disable PPR for autoSubmit?
> > > Oh, and additionally: It should be documented in the tag description 
that
> > > autoSubmit does PPR.
> > >
> > > (Trinidad 1.0.2, MyFaces 1.1.5, Facelets from VCS, Seam 1.2.1 on Tomcat 
5.5.17)
> > >
> > >
> > >
> >
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>


-- 
Matthias Wessendorf

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

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Matthias Wessendorf]

tr:form isn't a namingcontainer

On 9/28/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> Hi Stephen,
>
> do this:
>
>
>
>value="#{scoreEntryHome.department}"
>autoSubmit="true">
>
>   var="department" label="#{department.name}"/>
>
>
>  action="#{scoreEntryHome.save}"/>
>
>
>
>  partialTriggers="::departmentForm:departments">
>
>
>
>
>
> with :: you can get out of your naming-container up one level and then
> back in again with : and name.
>
> regards,
>
> Martin
>
> On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> > You might try not using multiple forms and also not having the form
> > id="departments" and the selectOneChoice also set to "departments"
> >
> > -Richard
> >
> > Stephen Friedrich wrote:
> > > It seems that autoSubmit from a tr:selectOneChoice always uses PPR.
> > > I can't get other components to update, though. This is what I tried:
> > >
> > >   
> > >> >   value="#{scoreEntryHome.department}"
> > >   autoSubmit="true">
> > >
> > >> >  var="department" label="#{department.name}"/>
> > >   
> > >
> > >> > action="#{scoreEntryHome.save}"/>
> > >   
> > >
> > >   
> > >> > value="#{scoreEntryHome.scoreEntries}"
> > > partialTriggers="departments">
> > >
> > >   
> > >   
> > >   
> > >
> > > On the server scoreEntryHome.setDepartment() gets correctly called with 
> > > the
> > > newly selected department, but the table won't update.
> > >
> > > I added the "Update" button just for testing, and of course it works fine.
> > >
> > > What am I doing wrong this time? ;-)
> > >
> > > Alternatively: Is there a way to disable PPR for autoSubmit?
> > > Oh, and additionally: It should be documented in the tag description that
> > > autoSubmit does PPR.
> > >
> > > (Trinidad 1.0.2, MyFaces 1.1.5, Facelets from VCS, Seam 1.2.1 on Tomcat 
> > > 5.5.17)
> > >
> > >
> > >
> >
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>


-- 
Matthias Wessendorf

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

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Martin Marinschek]

Hi Stephen,

do this:


   
   

   
   

   
   

   
   

   
   
   

with :: you can get out of your naming-container up one level and then
back in again with : and name.

regards,

Martin

On 9/28/07, Richard Yee <[EMAIL PROTECTED]> wrote:
> You might try not using multiple forms and also not having the form
> id="departments" and the selectOneChoice also set to "departments"
>
> -Richard
>
> Stephen Friedrich wrote:
> > It seems that autoSubmit from a tr:selectOneChoice always uses PPR.
> > I can't get other components to update, though. This is what I tried:
> >
> >   
> >>   value="#{scoreEntryHome.department}"
> >   autoSubmit="true">
> >
> >>  var="department" label="#{department.name}"/>
> >   
> >
> >> action="#{scoreEntryHome.save}"/>
> >   
> >
> >   
> >> partialTriggers="departments">
> >
> >   
> >   
> >   
> >
> > On the server scoreEntryHome.setDepartment() gets correctly called with the
> > newly selected department, but the table won't update.
> >
> > I added the "Update" button just for testing, and of course it works fine.
> >
> > What am I doing wrong this time? ;-)
> >
> > Alternatively: Is there a way to disable PPR for autoSubmit?
> > Oh, and additionally: It should be documented in the tag description that
> > autoSubmit does PPR.
> >
> > (Trinidad 1.0.2, MyFaces 1.1.5, Facelets from VCS, Seam 1.2.1 on Tomcat 
> > 5.5.17)
> >
> >
> >
>
>


-- 

http://www.irian.at

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

Professional Support for Apache MyFaces

Re: [Trinidad] selectOneChoice with autoSubmit problem

[Richard Yee]

You might try not using multiple forms and also not having the form 
id="departments" and the selectOneChoice also set to "departments"


-Richard

Stephen Friedrich wrote:

It seems that autoSubmit from a tr:selectOneChoice always uses PPR.
I can't get other components to update, though. This is what I tried:


		value="#{scoreEntryHome.department}"

autoSubmit="true">

		   var="department" label="#{department.name}"/>



		  action="#{scoreEntryHome.save}"/>





	  
	




On the server scoreEntryHome.setDepartment() gets correctly called with the 
newly selected department, but the table won't update.


I added the "Update" button just for testing, and of course it works fine.

What am I doing wrong this time? ;-)

Alternatively: Is there a way to disable PPR for autoSubmit?
Oh, and additionally: It should be documented in the tag description that 
autoSubmit does PPR.


(Trinidad 1.0.2, MyFaces 1.1.5, Facelets from VCS, Seam 1.2.1 on Tomcat 5.5.17)


  

[Trinidad] selectOneChoice with autoSubmit problem

[Stephen Friedrich]

It seems that autoSubmit from a tr:selectOneChoice always uses PPR.
I can't get other components to update, though. This is what I tried:












  




On the server scoreEntryHome.setDepartment() gets correctly called with the 
newly selected department, but the table won't update.

I added the "Update" button just for testing, and of course it works fine.

What am I doing wrong this time? ;-)

Alternatively: Is there a way to disable PPR for autoSubmit?
Oh, and additionally: It should be documented in the tag description that 
autoSubmit does PPR.

(Trinidad 1.0.2, MyFaces 1.1.5, Facelets from VCS, Seam 1.2.1 on Tomcat 5.5.17)

Re: Java heap space

[Angel Miralles Arevalo]

It's done. Moreover, I have a memory in use indicator (Myeclipse). Although 
there is a lot of memory without used, i get a java heap space.


- Mensaje original 
De: David Uebelacker <[EMAIL PROTECTED]>
Para: MyFaces Discussion 
Enviado: viernes, 28 de septiembre, 2007 12:31:01
Asunto: Re: Java heap space


Hi,

i think you can add a VM Argument like -Xmx512m to the jboss debug
configuration in eclipse, where 512 is the amount ob mb the vm should use
as maximum memory. In Addition you can give eclipse more memory, by
starting it with the this Argument: -vmargs -Xmx512m.

I think your default JBoss startup configuration is configured with more
memory than your start up configuration in your eclipse environment.

Regards,

David

> hi everybody, can some tell me why you get a java heap space if you are
> using myeclipse?
>
> 11:50:28,274 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces
> Servlet threw exception
> java.lang.OutOfMemoryError: Java heap space
>
> If I start up jBoss without Myeclipse there aren't errors. Page get charge
> without problems. The page has a large amount of data: tree2, tabbedPane,
> several dataTables inside and all is showing at the same time...
>
> I'm using myfaces1.1.5, tomahawk1.1.5.
>
> Thanks in advanced!!!
>
>
>
> 
> Sé un Mejor Amante del Cine
> ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!
> http://advision.webevents.yahoo.com/reto/entretenimiento.html


-- 
David Uebelacker
mailto:[EMAIL PROTECTED]
http://david.uebelacker.eu/


   

Sé un Mejor Amante del Cine 
¿Quieres saber cómo? ¡Deja que otras personas te ayuden!
http://advision.webevents.yahoo.com/reto/entretenimiento.html

Re: Java heap space

[David Uebelacker]

Hi,

i think you can add a VM Argument like -Xmx512m to the jboss debug
configuration in eclipse, where 512 is the amount ob mb the vm should use
as maximum memory. In Addition you can give eclipse more memory, by
starting it with the this Argument: -vmargs -Xmx512m.

I think your default JBoss startup configuration is configured with more
memory than your start up configuration in your eclipse environment.

Regards,

David

> hi everybody, can some tell me why you get a java heap space if you are
> using myeclipse?
>
> 11:50:28,274 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces
> Servlet threw exception
> java.lang.OutOfMemoryError: Java heap space
>
> If I start up jBoss without Myeclipse there aren't errors. Page get charge
> without problems. The page has a large amount of data: tree2, tabbedPane,
> several dataTables inside and all is showing at the same time...
>
> I'm using myfaces1.1.5, tomahawk1.1.5.
>
> Thanks in advanced!!!
>
>
>
> 
> Sé un Mejor Amante del Cine
> ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!
> http://advision.webevents.yahoo.com/reto/entretenimiento.html


-- 
David Uebelacker
mailto:[EMAIL PROTECTED]
http://david.uebelacker.eu/

RE: Page blank problem : Hi David!

[Arvind Pandey]

Hi David !
   We have 12 different users connected to server through 12 different
browsers on different m/c.
   I think then they should not share the same session.

   In our application, in web.xml we have the configuration as below:

  
State saving method: "client" or "server" (= default) See
JSF Specification 2.5.3
javax.faces.STATE_SAVING_METHOD
server
  

  
Only applicable if state saving method is "server" (=
default). Defines the amount (default = 20) of the  latest views 
are stored
in session.
org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION
50
  

  Increasing the value of NUMBER_OF_VIEWS_IN_SESSION to 100 or something
higher than 50 will solve my problem?
  We don't want to change STATE_SAVING_METHOD to client due to some reason.
  Can u pls suggest some idea which will be helpful for me?

thanks & regards
Arvind Pandey


-Original Message-
From: David Delbecq [mailto:[EMAIL PROTECTED]
Sent: Friday, September 28, 2007 1:29 PM
To: MyFaces Discussion
Subject: Re: Page blank problem


Are all gui in same session? Would explain, because myface has a limited
list (20), AFAIK, of view state. If 8 out of 12 GUIS do 3 AJAX requests,
they make 24 "recent" view state, pushing the 4 other GUIs to position
25,26,27 and 28. When an action is invoked (AJAX or other) on one of
those 4 GUIS, there is no state to restore, an JSF starts a "create new
view" cycle. And action is ignored, a brand new page for that view id is
returned.

This all should not happen in state saving is client, because there is
no limit other than browser cache size for this.

Note: AJAX4JSF has a Log component you can put in page. It can be very
usefull to track errors.


En l'instant précis du 28/09/07 07:22, Arvind Pandey s'exprimait en ces
termes:
> Hi all,
>
>I am using myfaces 1.1.5 with ajax4jsf on JBoss 4.x .
> Everything works fine if we have one GUI connected to server. But with
> several GUIs
> (I have tested for 12 GUIs) connected to server, few GUIs go blank. May be
> due to
> Ajax call it goes blank, but I am not sure.
>   can anyone please help me regarding this issue?
>   Any suggestion will be appreciated.
>
> thanks & regards...
> Arvind Pandey
>
> Disclaimer: The information contained in this e-mail and attachments if
any are privileged and confidential and are intended for the individual(s)
or entity(ies) named in this e-mail. If the reader or recipient is not the
intended recipient, or employee or agent responsible for delivering to the
intended recipient, you are hereby notified that dissemination, distribution
or copying of this communication or attachments thereof is strictly
prohibited. IF YOU RECEIVE this communication in error, please immediately
notify the sender and return the original message.
>


--
http://www.noooxml.org/


Disclaimer: The information contained in this e-mail and attachments if any are 
privileged and confidential and are intended for the individual(s) or 
entity(ies) named in this e-mail. If the reader or recipient is not the 
intended recipient, or employee or agent responsible for delivering to the 
intended recipient, you are hereby notified that dissemination, distribution or 
copying of this communication or attachments thereof is strictly prohibited. IF 
YOU RECEIVE this communication in error, please immediately notify the sender 
and return the original message.

RE: Page blank problem: Hi David

[Arvind Pandey]

Hi David !
   In our application, in web.xml we have the configuration as below:

  
State saving method: "client" or "server" (= default) See
JSF Specification 2.5.3
javax.faces.STATE_SAVING_METHOD
server
  

  
Only applicable if state saving method is "server" (=
default). Defines the amount (default = 20) of the  latest views 
are stored
in session.
org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION
50
  

  Increasing the value of NUMBER_OF_VIEWS_IN_SESSION to 100 or something
higher than 50 will solve my problem?
  We don't want to change STATE_SAVING_METHOD to client due to some reason.
  Can u pls suggest some idea which will be helpful for me?

thanks & regards
Arvind Pandey


-Original Message-
From: David Delbecq [mailto:[EMAIL PROTECTED]
Sent: Friday, September 28, 2007 1:29 PM
To: MyFaces Discussion
Subject: Re: Page blank problem


Are all gui in same session? Would explain, because myface has a limited
list (20), AFAIK, of view state. If 8 out of 12 GUIS do 3 AJAX requests,
they make 24 "recent" view state, pushing the 4 other GUIs to position
25,26,27 and 28. When an action is invoked (AJAX or other) on one of
those 4 GUIS, there is no state to restore, an JSF starts a "create new
view" cycle. And action is ignored, a brand new page for that view id is
returned.

This all should not happen in state saving is client, because there is
no limit other than browser cache size for this.

Note: AJAX4JSF has a Log component you can put in page. It can be very
usefull to track errors.


En l'instant précis du 28/09/07 07:22, Arvind Pandey s'exprimait en ces
termes:
> Hi all,
>
>I am using myfaces 1.1.5 with ajax4jsf on JBoss 4.x .
> Everything works fine if we have one GUI connected to server. But with
> several GUIs
> (I have tested for 12 GUIs) connected to server, few GUIs go blank. May be
> due to
> Ajax call it goes blank, but I am not sure.
>   can anyone please help me regarding this issue?
>   Any suggestion will be appreciated.
>
> thanks & regards...
> Arvind Pandey
>
> Disclaimer: The information contained in this e-mail and attachments if
any are privileged and confidential and are intended for the individual(s)
or entity(ies) named in this e-mail. If the reader or recipient is not the
intended recipient, or employee or agent responsible for delivering to the
intended recipient, you are hereby notified that dissemination, distribution
or copying of this communication or attachments thereof is strictly
prohibited. IF YOU RECEIVE this communication in error, please immediately
notify the sender and return the original message.
>


--
http://www.noooxml.org/


Disclaimer: The information contained in this e-mail and attachments if any are 
privileged and confidential and are intended for the individual(s) or 
entity(ies) named in this e-mail. If the reader or recipient is not the 
intended recipient, or employee or agent responsible for delivering to the 
intended recipient, you are hereby notified that dissemination, distribution or 
copying of this communication or attachments thereof is strictly prohibited. IF 
YOU RECEIVE this communication in error, please immediately notify the sender 
and return the original message.

Java heap space

[Angel Miralles Arevalo]

hi everybody, can some tell me why you get a java heap space if you are using 
myeclipse?

11:50:28,274 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces 
Servlet threw exception
java.lang.OutOfMemoryError: Java heap space

If I start up jBoss without Myeclipse there aren't errors. Page get charge 
without problems. The page has a large amount of data: tree2, tabbedPane, 
several dataTables inside and all is showing at the same time...

I'm using myfaces1.1.5, tomahawk1.1.5.

Thanks in advanced!!!


   

Sé un Mejor Amante del Cine 
¿Quieres saber cómo? ¡Deja que otras personas te ayuden!
http://advision.webevents.yahoo.com/reto/entretenimiento.html

Re: Orchestra: Target unreachable

[Simon Kitching]

 alberto <[EMAIL PROTECTED]> schrieb:
> I am trying ORchestra on Myfaces 1.2, Tomcat 6, Facelets, Spring  2.0.6.
> 
> I have a 
> 
> 
> in my welcome.xhtml
> 
> When I submit I get:
> 
> value="#{userListBean.user.username}": Target Unreachable, identifier 
> 'userListBean' resolved to nullAm I missing some config in faces-config? The 
> only entry there is the view handler for facelets.

I would guess that you've missed some Spring config in the web.xml file.

Orchestra needs to hook into the bean definition and lookup process to work, 
and JSF doesn't provide enough hooks. Therefore Orchestra requires some 
external IOC container to be used - eg Spring.

This error message looks like you've got Spring correctly hooked up so that if 
"userListBean" isn't found in the standard JSF beans.xml file then Spring's 
config is checked. However in this case, "userListBean" cannot be found by 
Spring either.

Have you followed the setup instructions here?
http://myfaces.apache.org/orchestra/myfaces-orchestra-core/installation.html

Regards,

Simon

Spring WebFlow and Orchestra (was Re: Orchestra Question / another solution?)

[Simon Kitching]

The WebFlow docs state that persistence management is one of the major features 
of the most recent release (WebFlow Milestone 1):
  http://www.springframework.org/node/510

See the section:
 Web Flow 2.0 M1 New and Noteworthy

It's good to head that you're familiar with WebFlow; I have been looking at it 
recently and intend to create a Wiki page comparing it against Orchestra as 
there is definitely some overlap. If you could take some time to look at that 
page (when it's done) and correct it that would be great...

Cheers,

Simon

 Martin Marinschek <[EMAIL PROTECTED]> schrieb:
> I wouldn't call spring-webflow too complicated in comparison to
> Orchestra - but what you can't do with spring-webflow is to handle the
> underlying JPA-persistence context out of the box, you can do that
> with Orchestra.
> 
> regards,
> 
> Martin
> 
> On 9/28/07, Simon Kitching <[EMAIL PROTECTED]> wrote:
> > See here for information about conversations:
> > http://myfaces.apache.org/orchestra/myfaces-orchestra-core/conversation.html
> >
> > If all you want is Spring DI and AOP for your beans, then you don't need 
> > Orchestra. However Spring core doesn't give you conversation scopes by 
> > default.
> >
> > Copnversation scopes are *really really* useful, however, and many projects 
> > are looking at providing conversation scopes in some way. Spring WebFlow is 
> > one example, but it seems quite complicated to me; IMO Orchestra is simpler 
> > to use with JSF.
> >
> > Regards, Simon

Re: Orchestra Question / another solution?

[Martin Dames]

Hey,

thank you guys. That helped a lot. Actually I missed that explanation  
on your page. You could make a link on the front page under each  
"conversation" word. That would help! :-)


So now I have an idea what is it all about. Thank you. I'll dive into  
that deeper later when I am coming to the persistence layer.


Martin.


Am 28.09.2007 um 10:59 schrieb Simon Kitching:


See here for information about conversations:
http://myfaces.apache.org/orchestra/myfaces-orchestra-core/ 
conversation.html


If all you want is Spring DI and AOP for your beans, then you don't  
need Orchestra. However Spring core doesn't give you conversation  
scopes by default.


Copnversation scopes are *really really* useful, however, and many  
projects are looking at providing conversation scopes in some way.  
Spring WebFlow is one example, but it seems quite complicated to  
me; IMO Orchestra is simpler to use with JSF.


Regards, Simon

 Martin Dames <[EMAIL PROTECTED]> schrieb:

Hey Matthias,

hmm... I don't understand the conversation (dialog, wizard) scope
exactly. Is this a pretty common scope or an orchestra own name?

As the hightlights says:

"
It utilizes the powerful Spring bean configuration mechanism instead
of JSF's managed-bean facility. The release of Spring 2.0 made it
possible to define custom bean scopes in Spring. If a JSF Managed
bean is declared in Spring using the Orchestra "conversation" scope,
then when that bean is referenced from a JSF EL expression it is
automatically created within that conversation scope. It is not
necessary for non-conversation-scoped managed beans to be declared
via Spring, although we do recommend it: request and session scopes
are also supported and you benefit from having one common syntax for
defining the beans of your application, from the AOP features Spring
provides, and from Spring's other advanced features.
"

Orchestra can be used to don't declare managed-beans in the faces-
context.xml.

That is actually what I want.. I don't have some "JSF" beans and some
spring beans in two seperate different syntax conf files. I just want
to use spring DI. Then I can handle all the beans with the aop, and
other spring stuff.

So, the question is now... what are the benefit of the conversation
scope? and what is it exactly?

Thank you very much!

Am 28.09.2007 um 10:07 schrieb Matthias Wessendorf:


Hi Martin,

Cagatay's blog is about using Spring's bean facility to *declare*
Managed Beans.
No need for a declaration of your managed beans inside the
faces-config.xml file.

Orchestra is about providing a conversion (wizard) scope, that is
between request and session.
See the Orchestra docs ([1]) for more

-M

[1] http://myfaces.apache.org/orchestra/index.html

On 9/28/07, Martin Dames <[EMAIL PROTECTED]> wrote:

Hey all,

I saw yesterday the following solution for using spring app context
for managing beans in jsf:

http://cagataycivici.wordpress.com/2007/09/10/using-spring-to- 
manage-

jsf-beans/

So this is the same solution as orchestra offers, right?

Where are the benefits of using an extra lib (orchestra) instead of
just doing the solution above?

When I am using the conversation scope, can I use the session or
request scope at the same time? (Ok, this would be a spring  
question

I think)

Re: Orchestra Question / another solution?

[Martin Marinschek]

I wouldn't call spring-webflow too complicated in comparison to
Orchestra - but what you can't do with spring-webflow is to handle the
underlying JPA-persistence context out of the box, you can do that
with Orchestra.

regards,

Martin

On 9/28/07, Simon Kitching <[EMAIL PROTECTED]> wrote:
> See here for information about conversations:
> http://myfaces.apache.org/orchestra/myfaces-orchestra-core/conversation.html
>
> If all you want is Spring DI and AOP for your beans, then you don't need 
> Orchestra. However Spring core doesn't give you conversation scopes by 
> default.
>
> Copnversation scopes are *really really* useful, however, and many projects 
> are looking at providing conversation scopes in some way. Spring WebFlow is 
> one example, but it seems quite complicated to me; IMO Orchestra is simpler 
> to use with JSF.
>
> Regards, Simon
>
>  Martin Dames <[EMAIL PROTECTED]> schrieb:
> > Hey Matthias,
> >
> > hmm... I don't understand the conversation (dialog, wizard) scope
> > exactly. Is this a pretty common scope or an orchestra own name?
> >
> > As the hightlights says:
> >
> > "
> > It utilizes the powerful Spring bean configuration mechanism instead
> > of JSF's managed-bean facility. The release of Spring 2.0 made it
> > possible to define custom bean scopes in Spring. If a JSF Managed
> > bean is declared in Spring using the Orchestra "conversation" scope,
> > then when that bean is referenced from a JSF EL expression it is
> > automatically created within that conversation scope. It is not
> > necessary for non-conversation-scoped managed beans to be declared
> > via Spring, although we do recommend it: request and session scopes
> > are also supported and you benefit from having one common syntax for
> > defining the beans of your application, from the AOP features Spring
> > provides, and from Spring's other advanced features.
> > "
> >
> > Orchestra can be used to don't declare managed-beans in the faces-
> > context.xml.
> >
> > That is actually what I want.. I don't have some "JSF" beans and some
> > spring beans in two seperate different syntax conf files. I just want
> > to use spring DI. Then I can handle all the beans with the aop, and
> > other spring stuff.
> >
> > So, the question is now... what are the benefit of the conversation
> > scope? and what is it exactly?
> >
> > Thank you very much!
> >
> > Am 28.09.2007 um 10:07 schrieb Matthias Wessendorf:
> >
> > > Hi Martin,
> > >
> > > Cagatay's blog is about using Spring's bean facility to *declare*
> > > Managed Beans.
> > > No need for a declaration of your managed beans inside the
> > > faces-config.xml file.
> > >
> > > Orchestra is about providing a conversion (wizard) scope, that is
> > > between request and session.
> > > See the Orchestra docs ([1]) for more
> > >
> > > -M
> > >
> > > [1] http://myfaces.apache.org/orchestra/index.html
> > >
> > > On 9/28/07, Martin Dames <[EMAIL PROTECTED]> wrote:
> > >> Hey all,
> > >>
> > >> I saw yesterday the following solution for using spring app context
> > >> for managing beans in jsf:
> > >>
> > >> http://cagataycivici.wordpress.com/2007/09/10/using-spring-to-manage-
> > >> jsf-beans/
> > >>
> > >> So this is the same solution as orchestra offers, right?
> > >>
> > >> Where are the benefits of using an extra lib (orchestra) instead of
> > >> just doing the solution above?
> > >>
> > >> When I am using the conversation scope, can I use the session or
> > >> request scope at the same time? (Ok, this would be a spring question
> > >> I think)
>
>


-- 

http://www.irian.at

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

Professional Support for Apache MyFaces

Orchestra: Target unreachable

[alberto]

I am trying ORchestra on Myfaces 1.2, Tomcat 6, Facelets, Spring  2.0.6.

I have a 


in my welcome.xhtml

When I submit I get:

value="#{userListBean.user.username}": Target Unreachable, identifier 
'userListBean' resolved to nullAm I missing some config in faces-config? The 
only entry there is the view handler for facelets.

Re: Orchestra Question / another solution?

[Simon Kitching]

See here for information about conversations:
http://myfaces.apache.org/orchestra/myfaces-orchestra-core/conversation.html

If all you want is Spring DI and AOP for your beans, then you don't need 
Orchestra. However Spring core doesn't give you conversation scopes by default.

Copnversation scopes are *really really* useful, however, and many projects are 
looking at providing conversation scopes in some way. Spring WebFlow is one 
example, but it seems quite complicated to me; IMO Orchestra is simpler to use 
with JSF.

Regards, Simon

 Martin Dames <[EMAIL PROTECTED]> schrieb:
> Hey Matthias,
> 
> hmm... I don't understand the conversation (dialog, wizard) scope  
> exactly. Is this a pretty common scope or an orchestra own name?
> 
> As the hightlights says:
> 
> "
> It utilizes the powerful Spring bean configuration mechanism instead  
> of JSF's managed-bean facility. The release of Spring 2.0 made it  
> possible to define custom bean scopes in Spring. If a JSF Managed  
> bean is declared in Spring using the Orchestra "conversation" scope,  
> then when that bean is referenced from a JSF EL expression it is  
> automatically created within that conversation scope. It is not  
> necessary for non-conversation-scoped managed beans to be declared  
> via Spring, although we do recommend it: request and session scopes  
> are also supported and you benefit from having one common syntax for  
> defining the beans of your application, from the AOP features Spring  
> provides, and from Spring's other advanced features.
> "
> 
> Orchestra can be used to don't declare managed-beans in the faces- 
> context.xml.
> 
> That is actually what I want.. I don't have some "JSF" beans and some  
> spring beans in two seperate different syntax conf files. I just want  
> to use spring DI. Then I can handle all the beans with the aop, and  
> other spring stuff.
> 
> So, the question is now... what are the benefit of the conversation  
> scope? and what is it exactly?
> 
> Thank you very much!
> 
> Am 28.09.2007 um 10:07 schrieb Matthias Wessendorf:
> 
> > Hi Martin,
> >
> > Cagatay's blog is about using Spring's bean facility to *declare*  
> > Managed Beans.
> > No need for a declaration of your managed beans inside the
> > faces-config.xml file.
> >
> > Orchestra is about providing a conversion (wizard) scope, that is
> > between request and session.
> > See the Orchestra docs ([1]) for more
> >
> > -M
> >
> > [1] http://myfaces.apache.org/orchestra/index.html
> >
> > On 9/28/07, Martin Dames <[EMAIL PROTECTED]> wrote:
> >> Hey all,
> >>
> >> I saw yesterday the following solution for using spring app context
> >> for managing beans in jsf:
> >>
> >> http://cagataycivici.wordpress.com/2007/09/10/using-spring-to-manage-
> >> jsf-beans/
> >>
> >> So this is the same solution as orchestra offers, right?
> >>
> >> Where are the benefits of using an extra lib (orchestra) instead of
> >> just doing the solution above?
> >>
> >> When I am using the conversation scope, can I use the session or
> >> request scope at the same time? (Ok, this would be a spring question
> >> I think)

Re: Orchestra Question / another solution?

[Mario Ivankovits]

Hi!
> So, the question is now... what are the benefit of the conversation
> scope? and what is it exactly?
There is not need to use Orchestra just do declare beans in spring. This
is something spring provides out of the box.

The conversation scope is a scope between request and session.
Means - you can hold state between requests. For example, you can put
the backing bean for your JSF page into conversation scope and do not
have to use things like t:saveState to have the values on the next request.
Also the persistence context will be synchronized with the lifetime of
your conversation so that you can gain the full advantage of e.g. lazy
loading - it just makes all the persistence things really easy.

Hmmm  There is alot to read on the web-page. If it is too boring,
please have a look at the source of our examples.

Ciao,
Mario

Re: Orchestra Question / another solution?

[Martin Dames]

Hey Matthias,

hmm... I don't understand the conversation (dialog, wizard) scope  
exactly. Is this a pretty common scope or an orchestra own name?


As the hightlights says:

"
It utilizes the powerful Spring bean configuration mechanism instead  
of JSF's managed-bean facility. The release of Spring 2.0 made it  
possible to define custom bean scopes in Spring. If a JSF Managed  
bean is declared in Spring using the Orchestra "conversation" scope,  
then when that bean is referenced from a JSF EL expression it is  
automatically created within that conversation scope. It is not  
necessary for non-conversation-scoped managed beans to be declared  
via Spring, although we do recommend it: request and session scopes  
are also supported and you benefit from having one common syntax for  
defining the beans of your application, from the AOP features Spring  
provides, and from Spring's other advanced features.

"

Orchestra can be used to don't declare managed-beans in the faces- 
context.xml.


That is actually what I want.. I don't have some "JSF" beans and some  
spring beans in two seperate different syntax conf files. I just want  
to use spring DI. Then I can handle all the beans with the aop, and  
other spring stuff.


So, the question is now... what are the benefit of the conversation  
scope? and what is it exactly?


Thank you very much!

Am 28.09.2007 um 10:07 schrieb Matthias Wessendorf:


Hi Martin,

Cagatay's blog is about using Spring's bean facility to *declare*  
Managed Beans.

No need for a declaration of your managed beans inside the
faces-config.xml file.

Orchestra is about providing a conversion (wizard) scope, that is
between request and session.
See the Orchestra docs ([1]) for more

-M

[1] http://myfaces.apache.org/orchestra/index.html

On 9/28/07, Martin Dames <[EMAIL PROTECTED]> wrote:

Hey all,

I saw yesterday the following solution for using spring app context
for managing beans in jsf:

http://cagataycivici.wordpress.com/2007/09/10/using-spring-to-manage-
jsf-beans/

So this is the same solution as orchestra offers, right?

Where are the benefits of using an extra lib (orchestra) instead of
just doing the solution above?

When I am using the conversation scope, can I use the session or
request scope at the same time? (Ok, this would be a spring question
I think)

Thank you!




--
Matthias Wessendorf

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

selectionChange facet doesn't work on my sheet???

[Zied Hamdi]

Hi,

I've followed the description in the issue
http://issues.apache.org/jira/browse/TOBAGO-84
But it doesn't work, in addition the bug is still open, does it mean this
was only a proposition for a solution?

Regards,
Zied

Trinidad Refresh parent window page after dialog closed

[pdt_p]

Hi...

I have a page. inside that page i have an iframe. inside that iframe, i have
a command link which will popup a window. the action for that command link
is "dialog:." and I have specified the returnListener.
What I am trying to do is, I would like to completely refresh the page that
will include the iframe and the iframe's parent window.

In my returnListener, I have forward the page to it self like Simon Lessard
mention on the other post.

public void redirectToSelf(ReturnEvent ev)
{
  FacesContext context = FacesContext.getCurrentInstance();
  ExternalContext eContext = context.getExternalContext();

  String contextPath = eContext.getRequestContextPath();
  String servletPath = eContext.getRequestServletPath();
  String viewId = context.getViewRoot().getViewId();
  eContext.sendRedirect(eContext.encodeActionUrl(contextPath + servletPath +
viewId));
}


If I specified that in my returnListener, it will only refresh the iframe
since the viewid in ViewRoot will definately the iframe's url because the
command link is in the iframe page.

my question: 
How do I refresh the whole page include the iframe's parent window?
any idea?

Thank you very much.

Regards,

pdt

-- 
View this message in context: 
http://www.nabble.com/Trinidad-Refresh-parent-window-page-after-dialog-closed-tf4533093.html#a12936564
Sent from the MyFaces - Users mailing list archive at Nabble.com.

Re: Orchestra Question / another solution?

[Matthias Wessendorf]

Hi Martin,

Cagatay's blog is about using Spring's bean facility to *declare* Managed Beans.
No need for a declaration of your managed beans inside the
faces-config.xml file.

Orchestra is about providing a conversion (wizard) scope, that is
between request and session.
See the Orchestra docs ([1]) for more

-M

[1] http://myfaces.apache.org/orchestra/index.html

On 9/28/07, Martin Dames <[EMAIL PROTECTED]> wrote:
> Hey all,
>
> I saw yesterday the following solution for using spring app context
> for managing beans in jsf:
>
> http://cagataycivici.wordpress.com/2007/09/10/using-spring-to-manage-
> jsf-beans/
>
> So this is the same solution as orchestra offers, right?
>
> Where are the benefits of using an extra lib (orchestra) instead of
> just doing the solution above?
>
> When I am using the conversation scope, can I use the session or
> request scope at the same time? (Ok, this would be a spring question
> I think)
>
> Thank you!
>


-- 
Matthias Wessendorf

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

Re: Page blank problem

[David Delbecq]

Are all gui in same session? Would explain, because myface has a limited
list (20), AFAIK, of view state. If 8 out of 12 GUIS do 3 AJAX requests,
they make 24 "recent" view state, pushing the 4 other GUIs to position
25,26,27 and 28. When an action is invoked (AJAX or other) on one of
those 4 GUIS, there is no state to restore, an JSF starts a "create new
view" cycle. And action is ignored, a brand new page for that view id is
returned.

This all should not happen in state saving is client, because there is
no limit other than browser cache size for this.

Note: AJAX4JSF has a Log component you can put in page. It can be very
usefull to track errors.


En l'instant précis du 28/09/07 07:22, Arvind Pandey s'exprimait en ces
termes:
> Hi all,
>
>I am using myfaces 1.1.5 with ajax4jsf on JBoss 4.x .
> Everything works fine if we have one GUI connected to server. But with
> several GUIs
> (I have tested for 12 GUIs) connected to server, few GUIs go blank. May be
> due to
> Ajax call it goes blank, but I am not sure.
>   can anyone please help me regarding this issue?
>   Any suggestion will be appreciated.
>
> thanks & regards...
> Arvind Pandey
>
> Disclaimer: The information contained in this e-mail and attachments if any 
> are privileged and confidential and are intended for the individual(s) or 
> entity(ies) named in this e-mail. If the reader or recipient is not the 
> intended recipient, or employee or agent responsible for delivering to the 
> intended recipient, you are hereby notified that dissemination, distribution 
> or copying of this communication or attachments thereof is strictly 
> prohibited. IF YOU RECEIVE this communication in error, please immediately 
> notify the sender and return the original message.
>   


-- 
http://www.noooxml.org/

Orchestra Question / another solution?

[Martin Dames]

Hey all,

I saw yesterday the following solution for using spring app context  
for managing beans in jsf:


http://cagataycivici.wordpress.com/2007/09/10/using-spring-to-manage- 
jsf-beans/


So this is the same solution as orchestra offers, right?

Where are the benefits of using an extra lib (orchestra) instead of  
just doing the solution above?


When I am using the conversation scope, can I use the session or  
request scope at the same time? (Ok, this would be a spring question  
I think)


Thank you!

Re: [jira] Commented: (MYFACES-1714) submitted (or local) values are not erasable after conversion or validation error

[Zied Hamdi]

Yes Volker,

It's surely a good candidate for a common project: I started with a4j and
fastly gave up: no JSF Lifecycle, I had to use json to communicate with
components, a real nightmare. For me, the two most important added values of
Tobago are:

  - native JSF lifecycle and component approch with ajax.
  - extended component approch in the view layer thanks to layouts and
predefined css styles that let us write html as we'd write Swing or SWT app
(even if no custumisation is done, the look is correct).

Both are definetly candidates to comons JSF projets, the second seems a
lillte complicated seen the posts about compatibility with Trinidad (due to
the layouting mecanism).

Zied

2007/9/27, Matthias Wessendorf <[EMAIL PROTECTED]>:
>
> I agree with volker.
>
> -Matthias
>
> On 9/25/07, Volker Weber <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > just to put my 2¢ here and to show the advantages of tobago ;-)
> >
> > In tobago the ajax requests are full integrated into the lifecycle.
> > We did this by taking and extending a copy of the Lifecycle impl from
> myfaces.
> > All phases are execuded as on normal requests execpt the process*
> > methods are not invoked on UIViewRoot but on the relevant component in
> > case of ajax.
> >
> > I think such a Lifecycle approach is mutch better than the
> > PhaseListener way where all further lifecycle phases are bypassed.
> >
> > May be a candidate for a jsf-commons project?
> >
> >
> > Regards,
> > Volker
> >
> >
> >
> > 2007/9/25, Mario Ivankovits <[EMAIL PROTECTED]>:
> > > Hi!
> > > > I am just curious which ajax framework do you use/recommend?
> > > >
> > > It is not meant as a recommendation, I have no further experience with
> > > other ajax frameworks.
> > > I use the pprPanelGroup from tomahawk-sandbox.
> > > Compared to the other ajax frameworks the pprPanelGroup might be too
> > > limited, don't kow 
> > >
> > > Together with subForm where possible/required.
> > > Not sure if it helps you (3-4 days back - so it is brand-new), but
> I've
> > > added a preserveSubmittedValues="true|false" to the tomahawk subForm
> tag
> > > if a ppr outside of the subForm triggered the partial reload so that
> > > your model update will be reflected.
> > > On preserveSubmittedValues=false all submitted values of the embedded
> > > components will be nullified.
> > >
> > > Ciao,
> > > Mario
> > >
> > >
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>



-- 
Zied Hamdi
zatreex.sourceforge.net

Re: Page blank problem

[Alonso Isidoro Roman]

Good days, when you refer to 12 GUIs do you refer to 12 users connected to
your servant of applications dont you?


2007/9/28, Arvind Pandey <[EMAIL PROTECTED]>:
>
> Hi all,
>
>I am using myfaces 1.1.5 with ajax4jsf on JBoss 4.x .
> Everything works fine if we have one GUI connected to server. But with
> several GUIs
> (I have tested for 12 GUIs) connected to server, few GUIs go blank. May be
> due to
> Ajax call it goes blank, but I am not sure.
>   can anyone please help me regarding this issue?
>   Any suggestion will be appreciated.
>
> thanks & regards...
> Arvind Pandey
>
> Disclaimer: The information contained in this e-mail and attachments if
> any are privileged and confidential and are intended for the individual(s)
> or entity(ies) named in this e-mail. If the reader or recipient is not the
> intended recipient, or employee or agent responsible for delivering to the
> intended recipient, you are hereby notified that dissemination, distribution
> or copying of this communication or attachments thereof is strictly
> prohibited. IF YOU RECEIVE this communication in error, please immediately
> notify the sender and return the original message.
>



-- 
Alonso Isidoro Roman.

Re: Perfomance problem with JSF

[Mikael Andersson]

You should be able to use the advice given earlier and just change your code
to, especially since you already seem to have a property called userList in
the class.

public List getUserList() {

  if( userList != null ){
 return list;
  }
  // Service Locator instance
  IServiceLocator iSL = ServiceLocator.getInstance
().getIServiceLocator();

  try {
   // Search result list. Access to LDAP
   list = iSL.getAuthorizationService().searchUsers(usc);

   this.userList = list;
  } catch (TimeOutConnectorException tex) {
   tex.printStackTrace();
   this.message = "Se excedió el tiempo máximo de
respuesta.Inténtelo de nuevo.";
  } catch (Exception ex) {
   ex.printStackTrace();
}
  return userList;
 }



On 27/09/2007, Angel Miralles Arevalo <[EMAIL PROTECTED]> wrote:
>
> Well I'm using an arrayList to charge a  uicomponet. Here is
> my code, sorry about not sending it before:
>
> Here es the *managed-bean:*
>
> public List getUserList() {
>   // Service Locator instance
>   IServiceLocator iSL = ServiceLocator.getInstance
> ().getIServiceLocator();
>
>   try {
>// Search result list. Access to LDAP
>list = iSL.getAuthorizationService().searchUsers(usc);
>
>this.userList = list;
>   } catch (TimeOutConnectorException tex) {
>tex.printStackTrace();
>this.message = "Se excedió el tiempo máximo de
> respuesta.Inténtelo de
> nuevo.";
>   } catch (Exception ex) {
>ex.printStackTrace();
> }
>   return userList;
>  }
>
> The red code is where LDAP access is made.
>
> And the *JSF code* is:
>
>
> <
> t:dataTable styleClass="porcen100 left" id="users_tab_PPR"
>
> border="0" bgcolor="#AEB8D4" cellspacing="1" cellpadding="0"
>
>
> headerClass="list-header"
>
> rowClasses="datos_impar_off,datos_par_off" var="usersListPPR"
>
>
> value="#{authorizationUsersListBean.usersList}"
>
> binding="#{authorizationUsersListBean.UITable}"
>
> preserveDataModel="false"
>
> sortColumn="#{authorizationUsersListBean.column}"
>
> sortAscending="#{authorizationUsersListBean.ascending}"
>
> preserveSort="true" renderedIfEmpty="false"
>
> rowOnMouseOver="mouseOverTable(this,'#9dcbe3')"
>
> rowOnMouseOut="mouseOutTable(this)"
>
> columnClasses="hleft porcen20, hleft porcen35,hleft
> porcen35, hcenter porcen10">
> 
>
> Thank you very much!!
> - Mensaje original 
> De: Richard Yee <[EMAIL PROTECTED]>
> Para: MyFaces Discussion 
> Enviado: jueves, 27 de septiembre, 2007 14:14:07
> Asunto: Re: Perfomance problem with JSF
>
> How are you using your LDAP ArrayList? Should you be using a Map
> instead? Is the getter/setter in a ManagedBean or somewhere else? Are
> you doing more in your getter than just returning an instance variable?
>
> Angel Miralles Arevalo wrote:
> > Hi everybody, I have a perfomance problem with JSF. I have a
> > java arraList attribute. This attribute have getter and setter
> > methods. It is used to store LDAP users, so I have to access LDAP in
> > getter method.
> >
> > Because of the lifecycle the getter is invoked twice, so LDAP access
> > is twice too. The problem is my LDAP has around 15000 users. My web
> > application is getting very slow.
> >
> > How can I customize this behaviour??
> >
> > Thanks in advanced.
> >
> > 
> >
> > Sé un Mejor Amante del Cine
> > ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!
> > <
> http://us.rd.yahoo.com/mail/es/tagline/beabetter/*http://advision.webevents.yahoo.com/reto/entretenimiento.html
> >.
>
>
> --
>
> Sé un Mejor Amante del Cine
> ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!
> 
> .
>

Re: [a4j] Combine commandButton with link

[Bruno Aranda]

Use the "action" attribute of commandButtons and commandLinks to
handle navigation. It is the same for both and for all the UICommands,

Cheers,

Bruno

On 27/09/2007, Wolfgang <[EMAIL PROTECTED]> wrote:
> Hi,
>
> is there a possibility to combine the a4j:commandButton with the
> a4j:commandLink?
> So if I click on the button a new jsf site will be opened?
>
> Cheers,
> Wolfgang
>