Mach-II for CFML Google Group

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T21:53:33Z

Some other discourse on this is how to a value on a bean back to NULL --
like I suggested:

.pjf

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T21:49:27Z

FYI, You could set a null by using the return void exploit from a
cffunction. Adobe CF is the only engine that works like this -- Railo
and Open BD work differently.

[link]

.pjf

Sumit Verma said the following on 11/22/2009 03:00 PM:

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T21:27:29Z

It's interesting they phrased it that way--I'd say the results are entirely
expected. Not what *should* happen in my opinion, but the results are
consistent and therefore aren't unexpected.

Thank you for helping us think through this issue. Chances are we'll come up
with a solution for 1.9, and we'll definitely want everyone's feedback as we

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T21:00:05Z

PK won't always be id, but I agree, exception to the normal rule is fine.

Well, no null in Adobe CF :o) From javacast documentation:

Note: Do not assign the results of JavaCast("null","") to a ColdFusion
variable. Unexpected results will occur.

Thanks a lot you guys for being so responsive. Makes the learning curve much

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T20:25:38Z

Sumit Verma said the following on 11/22/2009 02:07 PM:
Well, over time your beans will be more than table definitions -- or
you'll have a pretty anemic domain model. I wouldn't worry about having
to define an occasional setter/getter/other method. No bean is going to
always be the same so an exception to the normal rules is fine. If your

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T20:07:13Z

Yes, overriding the setter in the bean is an option. I was trying to not add
any method in the bean itself and keep only table definition, but I think
the setter for ID is needed. It will allow me to remove the check from the
constructor in base entity.

From what I have tested so far, I don't think we can reset the ID in save

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T19:48:39Z

I think the easiest workaround is to just define a concrete setter in
your bean to override the generated setter. You would just not set a
value if the incoming argument is equal "" (basically ignoring the
setter call).

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T19:02:03Z

Hi Kurt,

If we use the ignore option then we will have to put if/else logic in
listner to set the PK in case of "edit" forms. I will be happy to help test
and find the best solution. Let me know what you want me to do. Here is what
I ended up doing currently:

I extend all my entity with base entity and perform the init in base entity.

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T18:53:56Z

Hi Matt,

Yes, not the answer I wanted to hear, even though I knew that's what I will
get :o) I fully understand the reasoning as well.

Few things for you guys to ponder:

They way Hibernate works, you can't even default your primary key in
constructor. Any time you set the primary key after object creation,

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T17:48:19Z

I haven't gotten a change to try out the new event-bean command with a
CF 9 ORM CFC yet, however, I think it will work just fine. Maybe today
I think throw a quick example together using AppBooster.

There are a couple of ways that the primary key can be handled. The
first idea would be use the ability to ignore certain event args when

Re: [Mach-II] Re: Event-Beans and the Form tag

2009-11-22T17:29:38Z

Unless I'm misunderstanding, you're going to have this problem whether
you're using Mach-II or not because of the way CF handles nulls. Your safest
and easiest bet is to provide default values for all your bean properties so
things don't "disappear" if they're null. You could also not use event bean.

Re: Event-Beans and the Form tag

2009-11-22T05:09:54Z

Hi Peter,

So how will this work with ORM? I'm using the same flow as yours but I
don't think it will work with ORM on the "Add New" forms. Since the
event-bean calls setter on primary key as well, which is of type
"generator", entitySave() will always perform update instead of
insert.

Ideally, I would like to keep it as simple as this:

Blog Post on OpenBD on GAE - Aaron Lynch

2009-11-21T17:52:45Z

Apologize for the cross-posting if you're on the OpenBD mailing list as
well, but this is of interest to Mach-II users as well.

Aaron Lynch has a nice blog post on running OpenBD on Google App Engine:
[link]

Re: [Mach-II] Broken Docs?

2009-11-20T22:19:29Z

Awesome, thanks! Now to look up that question I had :-)
~~ Summer

Re: [Mach-II] Broken Docs?

2009-11-19T22:58:48Z

FYI, this issue has been resolved.

Peter J. Farrell said the following on 11/19/2009 01:35 PM: