Is there a solution in myfaces 1.1.1 to the browser back button problem?

Re: Is there a solution in myfaces 1.1.1 to the browser back button problem?

RE: How Does JDeveloper Compare with Java Studio Creator

no value for h:message or t:message

Hello Everyone:

I have the following simple code:

I have defined an input text as required. However, I get the following for 
the validation error:

"{0}": Value is required

if I use h:message or t:message, neither the input id nor the label value is 
replaced for {0}. I even tried to deply the simple application put on the 
myfaces homepage, I get the same thing for validation. I am using RAD 6.01.1 
and WAS 6.2.7. I am following everything by the book. Can anyone be kind 
enough to point out what I doing wrong? Here is the code snippet (The first 
input is the on that is required).

I have also tried to replace <t:message ... in the following snippet with

          <h:message id="pmrError" for="form1:pmr" styleClass="red-dark"/>

but of no avail

<h:form id="form1" name="pmrSearch">
   <h:panelGrid columns="3" cellpadding="2" >
	<h:panelGroup>
	   <h:outputLabel for="form1:pmr" value="#{msg['pmrNo']}" />
	   <h:inputText id="pmr" maxlength="6" size="6" 
value="#{searchPmrBean.pmr}" required="true" >
            	<f:validateLength minimum="1" maximum="6" />
           </h:inputText>
           <t:message id="pmrError" for="form1:pmr" styleClass="red-dark" 
replaceIdWithLabel="true"/>
        </h:panelGroup>

	<h:panelGroup>
           <h:outputLabel for="form1:bno" value="#{msg['bno']}:" />
	   <h:inputText id="bno" value="#{searchPmrBean.bno}" maxlength="3" 
size="3" >
             <f:validateLength maximum="3" />
            </h:inputText>
	</h:panelGroup>

	<h:panelGroup>
            <h:outputLabel for="form1:cno" value="#{msg['cno']}:" />
			<h:inputText id="cno" value="#{searchPmrBean.cno}" maxlength="3" size="3" 
 >
               	<f:validateLength maximum="3" />
            </h:inputText>
            <h:commandButton id="searchPmr" styleClass="button-blue" 
value="#{msg['go']}" action="#{searchPmrBean.searchPmr}"/>
	</h:panelGroup>
     </h:panelGrid>
</h:form>

Problem with: inputCalender, facelets and <base href=...>

Re: Can I load another jsf page by t:popup?

So  tomahawk is not provide such function.
With tomahawk popup only static data can be loaded. I can not add any
jsf interaction in popup page. right?

--

Anthony Hong

Re: How Does JDeveloper Compare with Java Studio Creator

On 3/3/06, Craig McClanahan <craigmcc <at> apache.org> wrote:
>
>
>
> On 3/3/06, Adam Winer <awiner <at> gmail.com> wrote:
> > Why can't JSC just run the component and actually let it render
> > itself by default?  I know that's what JDeveloper does, and
> > it works well.
>
>
>  Creator does that too, and it definitely works well ... the only *required*
> additional code is a BeanInfo class (see the JavaBeans API) that lets the
> component developer describe the component to the tool (for example,
> declaring that for the "style" property, use the nice CSS Style editor
> instead of just a string editor on the property sheet).
>
>
> > As a component developer (I've never worked on JDeveloper itself
> > at all, to be explicit), I really dislike the idea of writing a bunch of
> > extra Java code for all my components.  Supporting optional Java
> > code when renderers can't render in design time (graphs, etc.) is
> > a great feature, but you shouldn't force component developers to
> > write anything for the common case.
>
>
>  Writing dynamic behavior is possible, but not required.  It's up to the
> component developer to decide if you want to make your component behave in
> interesting ways at design time or not.  Examples we have implemented in the
> Creator components include:
>
>  * When you drop a Drop Down List component onto the page,
>    also create a helper bean for the options and bind the component
>    to it.
>
>  * When you have a Label component bound to an input component
>    via the "for" property, and you change the "id" of the input component,
>    respond to a property change event and change the "for" attribute
>    on the Label component as well so that it stays in sync.
>
>  * Do not allow a parameter (<f:param>) to be dropped except
>    in a context where it is relevant (such as inside an output link).
>
>  All of this stuff is optional, but provides you a way to improve the life
> of the users of your compoinents at design time, without messing up how they
> operate at run time.
>
>  By the way, the API we provide to component developers to make this
> possible has also been submitted to the JCP process
> (http://jcp.org/en/jsr/detail?id=273), so hopefully we can
> see a future world where a component developer can write design time
> behavior like this for more than one tool, instead of having to deal with
> each tool's individual APIs.

FYI, JSR 276 (http://jcp.org/en/jsr/detail?id=276) is a complimentary
JSR that takes a metadata-driven, JSF-specific approach, instead
of the Java code, generic JavaBean approach of 273.  Both can
work together.  (I kinda like 276 more; I'm guessing Craig likes
273 more.  Just a hunch. ;) )

-- Adam

Re: How Does JDeveloper Compare with Java Studio Creator

On 3/3/06, Yee CN <yeecn <at> streamyx.com> wrote:
>
>
>
> Is there any supports for Facelets in JDeveloper or JSC? I am using
> MyEclipse – and I am seriously looking for an alternative.

Unfortunately not.  Facelets has come on strong basically at
exactly the wrong point in the development cycle for JDeveloper
(and JSC too, I'd imagine).  I'm certainly pushing Facelets
to anyone in earshot. :)

-- Adam

model update error : hide exception

RE: Portlet support - multiple instances of a portlet.