Hey guys, I've implemented this. It's no longer static, so you can have
multiple configurations in the same VM with different
ObjectWrapperFactories.
It will be in Beta 8.
Clinton
On Thu, Jan 7, 2010 at 3:42 PM, Chris Reeves wrote:
> I did: http://issues.apache.org/jira/browse/IBATIS-725
>
>
I did: http://issues.apache.org/jira/browse/IBATIS-725
Yeah, I noticed the indentation issues later and there are a few bugs
in the code for scala objects. The patch for the core seems to work
well, excepting configuration, which isn't in the dtd. This was my
first time using textmate and I though
Hi, Chris,
Did you create a JIRA ticket for this?
I was hoping to get a proper chance to look over this, but haven't
managed as yet.
One thing I did notice on a superficial glance is the indentation in
the files isn't consistent (I said it was superficial!). I guess you
have different tab width
Cool. Thanks Chris. You might do well to create a Jira ticket (New
Feature) and attach the zip file there.
Clinton
On Sat, Jan 2, 2010 at 7:42 PM, Chris Reeves wrote:
> For those who may be interested, here is my implementation of a scala
> object wrapper. It includes an abstract base class t
Thanks Clinton; for an excellent mapper that's well designed and for
the pointers.
Here is what I came up with for an object wrapper factory. I don't
really like keeping it in static field on MetaObject, but I couldn't
come up with anything better. I'm not entirely certain the xml
configuration pa
For both cases, I believe all necessary changes would be in the wrappers.
However, there are places where Map is treated like a special case. But as
long as you stick to making a peer to the bean wrapper, then you should be
fine.
While there's no factory class, the MetaObject framework uses a fac
> Sounds interesting.
> I assume you're referring to the need to call foo_= instead of setFoo.
Yes, though I believe it ends up being foo_$eq.
> Not sure I follow. Is there any benefit in casting to ScalaObject? I
> wonder whether it's possible to reference the ScalaObject interface by
> name on
2009/12/31 Chris Reeves :
> I would like to add support for scala objects to iBATIS 3 for a
> project I'm working on, and I have a few questions before I dive in
> too deep.
Sounds interesting.
I assume you're referring to the need to call foo_= instead of setFoo.
> This would allow the scala sup
Hello,
I would like to add support for scala objects to iBATIS 3 for a
project I'm working on, and I have a few questions before I dive in
too deep.
>From what I can tell, this basically entails adding a new wrapper in
org.apache.ibatis.reflection.wrapper that can handle scala's slightly
differen
