Re: How do I know My JSF Version?

2007-09-15 Thread Vadim Dmitriev
Hello, Michael. Your JSF version is basically defined by JSF implementation you use in your project. If you use one that ships with RAD7, i guess it would be 1.1. At least, web-facesconfig.dtd version has nothing to do with JSF impl version. If you use myfaces: 1. jar file naming should tell you

Re: deploying demo of trinidad

2007-09-15 Thread Vadim Dmitriev
Hi. What is the server/version you are trying to deploy 1.2.x demo to? Does it support JSF 1.2 (JSP2.1) ? aj1m wrote: hi; i am trying to deploy trinidad demo; so i succeed to deploy the version (trinidad-blank-1.0.2.war and trinidad-demo-1.0.2.war) but when i tried to deloy the

Re: deploying demo of trinidad

2007-09-15 Thread Vadim Dmitriev
JSF1.2 support was added in tomcat 6. If I'm not mistaken, JBoss = 4.2.0 is tomcat 6 based. So you should try upgrading to at least 4.2 if you want to use JSF 1.2. Hope it helps. aj1m wrote: i tried many server like tomcat 5 and jboss 4.0.5.GA but i always get error. and i dont know how it can

Re: deploying demo of trinidad

2007-09-15 Thread Vadim Dmitriev
I have just downloaded JBoss AS 4.2.1 and successfully ran trinidad examples 1.2.1 on it. Should you try the same - don't forget to remove myfaces JSF1.2 from war and accordingly remove startup listener from web.xml. aj1m wrote: i tried it in tomcat 6. but it didnt work.

Re: deploying demo of trinidad

2007-09-15 Thread Vadim Dmitriev
As I already wrote: Should you try the same - don't forget to remove myfaces JSF1.2 from war and accordingly remove startup listener from web.xml. JSF 1.2 spec requires JSF impl to be generally server-provided, if there are both project- and server-level JSF implementations then server's take

Passing objects between pages after redirect

2007-09-06 Thread Vadim Dmitriev
It is not clear, weather you use redirect navigation rule. If you don't use redirect/ for navigation rule, you can refer bean2 directly from bean1: FacesContext fctx = FacesContext.getCurrentContext() Bean2 b2 = fctx.getApplication().getVariableResolver().resolveVariable( fctx, bean2 );

[Trinidad] Question regarding client-side validation and tr:form defaultCommand

2007-09-06 Thread Vadim Dmitriev
Hi! It looks like client-side validation is intentionally skipped if form is submitted via tr:form defaultCommand. Can anyone explain why such a decision was taken by devs or just why it's useful for client-side to be skipped in this case? Thanks in advance. P.S. At least tr:form behaves like

Re[2]: Passing objects between pages after redirect

2007-09-06 Thread Vadim Dmitriev
No, I didn't meant that you should redirect programmatically. In both cases you use faces-config NavigationRule to handle transition. 'redirect' is merely parameter on how to handle that transition. If redirect/ is present, then navigation will be handled traditional way: server asks browser to

Re: [Trinidad] Question regarding client-side validation and tr:form defaultCommand

2007-09-06 Thread Vadim Dmitriev
Just noticed: if form is initially submitted by 'enter' and then by commandButton, then most of inline error messages are doubled. First ones are printed by server-side validation (client-side skipped by defaultCommand), second - by client-side. Hi! It looks like client-side validation is

Re: [Trinidad] how to avoid loading tr:table rows twice

2007-09-06 Thread Vadim Dmitriev
Hi, Renzo. I don't think any component would do such a thing internally. After all, component just evaluate EL and can't figure out, when it is undesired. As a solution I can recommend you to use FacesContext.getCurrentInstance().getRenderResponse() to detect, when getter is called during

[Trinidad] Warning: Illegal HTML... should be reported?

2007-09-06 Thread Vadim Dmitriev
Hi. I was making up yet another page when noticed that when i open it in the browser about 10-15 warning got printed to console: 07.09.2007 0:18:07 org.apache.myfaces.trinidadinternal.io.DebugHtmlResponseWriter _errorWithComment WARNING: Illegal HTML: cannot put a tr element in a td element. I

[Trinidad] Question regarding client-side validation and tr:form defaultCommand

2007-09-06 Thread Vadim Dmitriev
an JIRA bug and we'll get this fixed asap. Thanks, Danny On 9/6/07, *Vadim Dmitriev* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi! It looks like client-side validation is intentionally skipped if form is submitted via tr:form defaultCommand. Can anyone explain why

[Trinidad] Warning: Illegal HTML... should be reported?

2007-09-06 Thread Vadim Dmitriev
Impl - 1.0.2), skin:rast.desktop (rast)--/html Thanks. Danny Robinson wrote: If you can supply the source page snippet and the rendered output we should be able to figure out if there's a problem to report. Thx, Danny On 9/6/07, * Vadim Dmitriev* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED

Re: [Trinidad] Warning: Illegal HTML... should be reported?

2007-09-06 Thread Vadim Dmitriev
It's not each component in every subform. I stripped page code of unimportant layout for that warning source can be easily pinpointed. Originally there are 5-10 inputs per subform. It's rather complex form with about 100 input components. They all must be lined up and some blocks must have partial

[Tomahawk] validateEqual problem for second field

2007-09-04 Thread Vadim Dmitriev
You may find it useful. Today I faced similar problem with validating-two-separate-mandatory-fields. I ended up using h:hiddenText value=1 required=true validator=#{validating.function} / somewhere after these two input components. So validating function is invoked in processValidations phase even

[Trinidad] tr:messages - EL expressions in components' labels are not evaluated

2007-09-03 Thread Vadim Dmitriev
Hi. tr:messages by default outputs messages in form label - massage. In my application I actively use EL expressions in components labels. Problem is that these labels got printed by tr:messages like this EL expressions are simple strings. For example #{resourceBundle['some.label']} - value

[Trinidad] tr:messages - EL expressions in components' labels are not evaluated

2007-09-03 Thread Vadim Dmitriev
Small follow-up: seems that labels are displayed correctly while client-side validation processes errors. When server-side validation kicks in - tr:messages labels turn to EL Hi. tr:messages by default outputs messages in form label - massage. In my application I actively use EL

[Trinidad] tr:inputText - rendering.

2007-09-02 Thread Vadim Dmitriev
Hi, Darren. Correct me if I'm wrong: you want second tr:inputText not to be rendered if #{bean1.appointGprnRender} is true? Then you can simply change #{bean1.appointGprnRender} to something like #{!bean2.appointGprnRender bean1.appointGprnRender} (for second input changes are similar).

[Trinidad] Re: Desperate: Simple GUI with partial validation?

2007-08-31 Thread Vadim Dmitriev
Stephen Friedrich wrote: Thanks a lot Vadim - the layout is looking nice now. Somehow I never noticed the showRequired attribute. I additionally needed to add a message component plus some layout. Just in case: if you added tr:message to display messages of tr:selectOneChoice

Re: Desperate: Simple GUI with partial validation?

2007-08-30 Thread Vadim Dmitriev
Hi. You can try something like that (removed all EL's to test it locally): tr:form defaultCommand=saveButton tr:panelFormLayout tr:subform default=true tr:panelLabelAndMessagefor=projectLeadSelect styleClass=inputLabel_10

Re: [Trinidad] Looking for client-side partial page validation

2007-08-28 Thread Vadim Dmitriev
Adam Winer wrote: On 8/28/07, Vadim Dmitriev [EMAIL PROTECTED] wrote: Hi! As far as I know ADF had some limitation regarding client-side validation with subforms. Suppose we have following block in a page: tr:form tr:inputText required=true / tr:subform tr:inputText

Re: [Trinidad] Looking for client-side partial page validation

2007-08-28 Thread Vadim Dmitriev
tr:inputText required=true label=Sub Default:/ tr:commandButton text=Submit Default/ /tr:subform tr:commandButton text=Submit Outside/ /tr:form /tr:document On 8/28/07, *Vadim Dmitriev* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi