Thanks a lot everybody. I'm going to see if it works with Jeff Solution.
I'll post when i get conclusive results.
Thanks again, you saved me a few days of googling
--- In flexcoders@yahoogroups.com, Jeff Vroom jvr...@... wrote:
You can use the flex.messaging.io.PropertyProxy features. The
If it were me, I would leave the java and as objects as they were and create a
new class extending the java object. Now you can add all the properties that
hibernate wants and send it.
--- In flexcoders@yahoogroups.com, ouaqa a...@... wrote:
I am developping a J2EE/Flex Application and we
--- In flexcoders@yahoogroups.com, ouaqa a...@... wrote:
This is an option but i was wondering if you couldn't use some special
ninja keyword telling lcds not to map the field to lcds.
Transient?
Yep, here's an example:
private var _myProperty:String;
[Transient]
[Bindable( event=myPropertyChange )]
/**
* myProperty.
* @private
*/
public function get myProperty():String
{
return _myProperty;
}
/** @private */
public function set myProperty( value:String ):void
{
That still requires adding the fields to the Flex object. Marking the field
@Transient in Java will affect Hibernate, unless Blaze / LCDS have their own
@Transient I'm not aware of. There's also this blazeds annotations add-on:
http://is.gd/sETx
SmartyPants-J will do this, but it's nowhere near
You can use the flex.messaging.io.PropertyProxy features. The BeanProxy class
has a way to exclude properties from AMF serialization. You can either
register these statically or wrap an instance. These should be in the docs.
We really should have @FlexTransient or something so that can be
This is just the flex vo side. No change to the java transfer object is
necessary; for transient fields that live only in the flex app.
-TH
--- In flexcoders@yahoogroups.com, Josh McDonald j...@... wrote:
That still requires adding the fields to the Flex object. Marking the
field
@Transient
7 matches
Mail list logo
