witchcraft-developers

[J S. <sin...@gm...>]

Joaquin,

This will be an excellent solution - I have to admit my Seam knowledge
is shallow at best and your proposal (with nested conversations )
should do it.  Just test it out and commit your changes - I am very
excited to see sort restore on cancel.

Next big thing will be for you to come up with a design for
integrating EntityQuery pattern back into oaw template and then
implement it - this should push us close to releasing alpha version of
Witchcraft's seam + richfaces archetype as we will have basic crud
with searching, sorting, editing, deleting pagination, association
support etc.  We will announce it on the server side (TSS) , and
hopefully will see people take it for a test drive.

Also, I have assigned you role author on Witchcraftmda.com so now you
can create a page on the site with richfaces archetype documentation.

On Sun, Nov 15, 2009 at 2:49 PM, Joaquín Robles <eco...@gm...> wrote:
> Hi Jess,
>
> I'm working with the newShopper project, to generate war file I've had to
> change scope of javax.servlet dependency from runtime to provided.
>
> I've seen the /admin/entities/domain/customer/listCustomer.seam page, and
> I've found a problem, the CustomerList.java component did not have the
> @Scope annotation,then CustomerList was EVENT scope, this caused the lost of
> sort order.
>
> If we annotated the class with Conversation Scope there's no problem (sort
> is not lost) with the cancel button, but there's another problem (If you
> want to preserve the sort order in actions) with the action's button
> (save,edit,..).
>
> Conversation begin in listCustomer page, because there's a
> propagation="begin" in s:link actions, but conversation ends when the user
> select a save,edit,.. action,because there's many <end-conversation/> in
> rules section of pages.xml. I think if the conversation begins in
> listCustomer, the conversation must be ends in listCustomer, we can do it,
> if we add in pages.xml
>
>     <page view-id="/admin/entities/domain/customer/listCustomer.xhtml">
>         <end-conversation/>
>         ...
>         ...
>     <page>
>
> Note: This end-converstaion is processed in render-response phase.
>
> If we change these two things (I have to review the remaining pages to avoid
> conversation errors, I think we can use nested conversation in some actions)
> whe can navigate between pages without loss sort order.
>
> What do you think?
>