Seam Application Framework (EntityHome, QueryHome)

[slominskir]

Does Seam 3 have the Seam Application Framework components EntityHome and EntityQuery?  Does the Seam Application Framework within Seam 2 (labeled as a framework within a framework in the book Seam in Action) apply anymore when working with CDI and JSF 2?

[gus888]

Anybody knows about this issue? I am also wondering whether Seam 3 have the Seam 2's framework :EntityHome and EntityQuery. Thanks.

[mimik789]

It looks like it doesn't. But I'm also interested in this (are there feautres planned?)

If you want pagination helpers you could try:
DataValve
http://www.andygibson.net/blog/projects/datavalve/

[lightguard]

The stuff that Andy has done is a possibility for for Seam 3.  We're still looking at what we want to do WRT Seam Application Framework.  Please list ideas / changes / suggestions etc you may have.

[gonzalad]

One great force of Seam Application Framework from Seam 2 is its simplicity (Query / Home).

I would like it to be :

1. less tied to Jpa or Hibernate (i.e. use whatever data access technology I want - i.e. Jdbc, mainframe access APIs, etc..).

[rogermorituesta.rogermori.yahoo.com]

The EntityHome is a very powerful  component that has been unfairly criticized. We fall in love with this component because of not being able to build a better one.

My suggestions are as follows:

1. Add a string parameter to the getPersistenceContextName method in order to pick a runtime entityManager different than the embedded one .  As a result, the Home component will work with one or more entityManagers simultaneously if desired.


2. An empty protected postFind method,  called by the find method when the entity is found, would be very useful.  Actually it will replace the wire method that is tied to the seam-gen edit view.


3. Capability to turn off the messages especially when there exists several Home components working together in a chain.


4. Add a Logger component.


5. Add an empty wire method to interface with seam-gen views.


6. The golden coin would be a method getComponentName to know what is the component name when it has more than a Role.


7. To add a parameter to the isManaged method in order to check not only the current instance but also its related entities.

[allenc]

I would be happy with a Seam 3 based EntityHome and EntityQuery that matched the current functionality. I feel this would help Seam-Forge to offer the capabilites of seam-gen sooner. Once that has been accomplished look at enhancing it.

[serkan.s.eskici.online.nl]

The same functionality as in Seam 2 plus I'd like to be able to do this kind of stuff:

components.xml (or beans.xml I assume ?)

  <!-- Name to use for the selected row/entity from the query -->
  <fwk:entityQuery sql="..." dataModelSelection="selectedEntity" .../>        NEW-1

And now we can do this:

<h:dataTable value="#{entityQuery.resultList}" var="entity">
   <h:column>
      <s:link action="#{entityHome.delete(selectedEntity)}"/>                 NEW-2
      
       <!-- And this should also work -->                                     NEW-3
      <s:link action="#{entityHome.delete(entityQuery.dataModelSelection)}"/> 

      <s:link value="Edit">
         <a:support reRender="editDiv" />
      <s:link/>
   </h:column
</h:dataTable>

<s:div id="editDiv" rendered="#{not empty selectedEntity}">
   Prop1: #{selectedEntity.prop1}
   ...
</s:div>

[ratking]

Andy Gibson have done some good work.
JpaQueryProvider is equals QueryHome. But IMO JpaEntityHome is not perfect.

https://github.com/andygibson/datavalve/blob/fa1e3d23dda69074fdc791a9a33e93501afd1490/datavalve-jpa/src/main/java/org/fluttercode/datavalve/provider/jpa/JpaQueryProvider.java

http://www.andygibson.net/blog/projects/datavalve/
https://github.com/andygibson/datavalve