This thread was started by hchafi to discuss using theHibernateAdapter
to reach the goal of using Hibernate Annotations.I introduced a
different approach to achieve the same goal byAVOIDING the
HibernateAdapter (becuase it only supports CRUDmethods and requires 100%
of your business logic to be written inactionscript on the
client).bjk0002, I am not sure which method you are truly interestedin.
For my approach, the documentation is out there. I wouldsuggest your
starting point be reading the Jav...
We have the JBoss implementation of EJB 3.0 working withFlex. The JBoss
implementation of EJB 3.0 is really hibernateannotations... In this
configuration, Flex does not need to talkdirectly to Hibernate, and we
have the full power of the new EJB3.0 Annotations (beyond the support
and features provided in theHibernateAdapter). Our Assemblers use JNDI
to access session beanswhich work with the entity beans.One huge problem
with Flex however is that due to therelationships between objects in the
When the JavaAdapter calls an updateItem Assembler method,
anArrays.ArrayList passed in as the changes parameter. This is
animmutable object list. This means I can not change more
objectproperties on the server side, add the property names to the
list,and get the client in sync. I can do this effectively if I use a
sync method and theChangeObject system, which maintains a String for
the list ofchanged properties. Please bring the JavaAdapter up to date
withthis functionality. It is very import...
It appears that DataService is not handling theUpdateCollectionMessage
correctly when updateMode = server_update,and the DataService autoCommit
= false. Our application first calls DataService.createItem, then
ourAssembler returns APPEND_TO_FILL on the refreshFill method call.
Wesee the UpdateCollectionMessage being dispatched, but nothinghappens
to the collection on the client.NOTE: If we change nothing in our
application exceptautoCommit = true, then everything works correctly.
(We do not want...
We are writing a framework around the AbstractAssemblerinterface.
However, we need to throw different database exceptionsso the client can
get a decent error message about what went wrong.This was not a problem
when writing sync functions because theywere not tied to a specific
interface. When we extendAbstractAssembler, the compiler does not let us
implement methodswhich throw any exceptions. There should be a mechanism
for sendingan intelligent error message from the server back to
We use a common base class to handle most Assembler functionswithout
writing a separate DAO class for each destination. The onlytrouble we
have in this design is using the API functions inAbstractAssembler which
give no reference whatsoever to the Classof object to act on. One such
function is getItem(Map). The Maponly contains id information, with no
reference to what kind ofobject to retreive. If the destination string
was included, or aClass object, we could get any record in the system by
I thought that the AsyncToken was always supposed to beavailable in the
ResultEvent?After a call to createItem (on a DataService), the token
dataI set is not in the token property of the event when theResultEvent
function executes. The result is an AcknowledgeMessage.But in the debug
environment, I do see a dynamic objectcalled __token_chain__ below the
outermost token. Beneath it is aUID, and below that is the token I'm
looking for - the one whichcontains the true result of my original call,