On Tue, Nov 18, 2008 at 6:31 PM, Raymond McDermott <[EMAIL PROTECTED]> wrote:
>
> Chalk up one more disappointed user.
Hey, I'm not a disappointed user:) Just thought it might be cool to
allow the functionality.
Sorry Rick I misunderstood. You are right that is clearly limiting.
I expected nested classes to have the same automatic reflection style
processing.
Chalk up one more disappointed user.
2008/11/18 Rick <[EMAIL PROTECTED]>
> On Tue, Nov 18, 2008 at 3:43 PM, Raymond McDermott <[EMAIL PROTECTED
Hi Jeff,
Many thanks for the suggestion. I will try using a Parameter Map instead of
inline parameters. Is there any specific thing that you do when specifying
the Parameter Maps so that the NULLs are transferred correctly?
In the meantime, I have only found one way to propagate the JDBC NULL val
On Tue, Nov 18, 2008 at 3:43 PM, Raymond McDermott <[EMAIL PROTECTED]> wrote:
> iBatis supports automatically mapping in beans where the property names
> match the getters/setters so you are in luck ;-)
I understand that but that ONLY works for when you are mapping one
statement to a class.
Look
iBatis supports automatically mapping in beans where the property names
match the getters/setters so you are in luck ;-)
See page 33 of the manual for 'implicit result maps'
2008/11/18 Rick <[EMAIL PROTECTED]>
> I sent this tot he wrong list before, so I'm resending it. I think it
> would be a hu
We've actually found in the FEMA project I designed and built that using
a parameter map for this (instead of inline parameters) helps a lot.
Couldn't think of a way to manage nulls using the inline stuff.
Jeff Stahl
raulvk.soa wrote:
Hi guys,
We are invoking a Stored Procedure on an Oracle
Hi guys,
We are invoking a Stored Procedure on an Oracle Database which takes in a
lot of IN parameters. However, many of them can be NULL (and in our use case
scenario MUST be null).
We are using the following in our SqlMap.xml (reduced version of our actual
code):
My application using iBatis is working and logging well until I change a
third party jar file.
Any idea of what can cause this error?
java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:216)
at
com.ibatis.sqlmap.engine.build
On Tue, Nov 18, 2008 at 12:44 PM, Kai Grabfelder <[EMAIL PROTECTED]> wrote:
> I don't think that this is currently possible. I don't really mind writing
> result maps, as I'm generating most
> of them with abator.
Yea, I'm currently doing the same (using ibator to create my
mappings), but I still
I don't think that this is currently possible. I don't really mind writing
result maps, as I'm generating most
of them with abator.
If you really need this feature feel free to create a jire issue and attach a
patch against the current iBATIS
trunk to it.
Regards
Kai
--- Original Nachricht -
Sure thing.
Jason
Kai Grabfelder wrote:
could you please open a jira issue for this?
Regards
Kai
--- Original Nachricht ---
Absender: Jason Kratz
Datum: 18.11.2008 15:37
Is there a plan to regenerate the javadoc for the user/developer doc
pages on the website? I'm looking at the develo
could you please open a jira issue for this?
Regards
Kai
--- Original Nachricht ---
Absender: Jason Kratz
Datum: 18.11.2008 15:37
> Is there a plan to regenerate the javadoc for the user/developer doc
> pages on the website? I'm looking at the developer docs for engine.type
> and the enum typ
I sent this tot he wrong list before, so I'm resending it. I think it
would be a huge plus for ibatis. I don't mind digging into the source
code... would it be a really tough fix? To modify result maps to allow
them being based on result classes? Has this been brought up before.
Just curious.
To s
Is there a plan to regenerate the javadoc for the user/developer doc
pages on the website? I'm looking at the developer docs for engine.type
and the enum type handler doc is missing. I assume this hasn't been
done recently.
Thanks,
Jason
14 matches
Mail list logo