Problems with validation and flow

Question

Hi
My JSF experience is limited, so please bear with me. Apologies in advance for any incorrect terminology, etc.
Outset:
We have a simple app that creates and updates fields mapped to a request scoped managed bean.
The same .jsp is used for both create and update use-cases. We distinguish between a create and update action by using an inputHidden tag with value="#{entity.id}". The inputHidden tag also has a rendered="#{entity.id ne null}" property defined. The page submits via the use of a commandButton:
<h:commandButton action="#{entity.createEntity}" value="Save"/>We determine weather or not to create or update the entity within the createEntity() method, depending on weather or not the inputHidden tag was rendered:
        final boolean isAltEditMode = getRequestParameterMap().containsKey("formName:id");
        if(isAltEditMode) {
            entity.setId(Long.parseLong(getRequestParameterMap().get("formName:id")));
The catch:
We are using JSF validation. If a blank field is entered on a required field during an "update", JSF interrupts the flow by forwarding back to the create page, and displaying the relevant error message. However, it loses the formName:id value (i.e. no value is bound to the requestParameterMap), and the app loses it's handle to the entity being updated.
Tested workarounds
We have successfully split the site model into separate create and edit screens. Validation errors using this model do pass on the entity id, but we would prefer to stick to the one-page-per-entity model described above.
We have also tried removing the rendered="#{entity.id ne null}" constraint on the hidden field. This fails on an entity create, as a blank hidden field always translates to a 0 (zero) id value, and the same entity id thus always gets created.
Question
We believe our understanding here is letting us down. There must be a better way to persist entity data for updates. Can anyone shed more light on the issue?
We'd be appreciative of any help.
Thanks,
SV

Answer 1

> Why does dreamweaver use "embed" when it shouldn't be
used with xhtml?
Because that's the only way to make Flash work on all
browsers reliably.
> How do I fix this?
http://blog.deconcept.com/2005/12/15/internet-explorer-eolas-changes-and-the-flash-plugin/
Background:
http://en.wikipedia.org/wiki/Eolas
See also
http://www.adobe.com/devnet/activecontent/
If you're running Dreamweaver 8.0.2, the fix is already built
into DW's
interface.
If not, try
http://blog.deconcept.com/swfobject/
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"PatrikI" <[email protected]> wrote in
message
news:f5dsr3$5r0$[email protected]..
>I don't understand...
>
> I've built the page using fireworks and dreamweaver cs3.
> I've inserted a flashmedia by using insert-media-flash
and on some pages
> flashbuttons. It works fine in a browser (checked with
IE7 and NS9). But
> when I
> use validate in dreamweaver I get errors that says
something like the tag
> with
> the name "embed" can't be found in (something)
versions.[XHTML 1.0
> transitional].
>
> Why does dreamweaver use "embed" when it shouldn't be
used with xhtml? How
> do
> I fix this?
>
> Please help?
>
>
> Site address:
http://www.forsakringscenter.se
>