Here here.
I know the biggest issue I always run into is stored procedure invocation.
Something really easy to implement would be binding stored procedures (not
ones that return results, just do work) to interface methods
public interface SomePackageNameOrDboOrSchemaName{
@StoredProcedure("someProcedureName(?,?,?)")
public void someProcedureName(String s, int i, Long l);
}
And do automatic binding of the method args to the procedure invocation.
For result sets, I always find it easier to just bind it as a JPA query.
On Fri, Nov 25, 2011 at 3:07 PM, José Rodolfo Freitas <
[email protected]> wrote:
> Yeah, a JBDC module would be very useful. Eventually I cross with
> requirements that asks for JDBC connections. Essentially for perfomance
> with gigantic queries and reports.
>
>
> On Fri, Nov 25, 2011 at 3:39 PM, John D. Ament <[email protected]>wrote:
>
>> Maybe we need a Seam JDBC module.
>>
>>
>> On Fri, Nov 25, 2011 at 12:32 PM, Jason Porter
>> <[email protected]>wrote:
>>
>>> No it does not, JPA only.
>>>
>>> Sent from my iPhone
>>>
>>> On Nov 25, 2011, at 8:21, José Rodolfo Freitas <
>>> [email protected]> wrote:
>>>
>>> afaik, it doesn't, but maybe a feature or two escaped from my eyes.
>>>
>>> On Fri, Nov 25, 2011 at 1:20 PM, José Rodolfo Freitas <
>>> [email protected]> wrote:
>>>
>>>> Hey guys, quick question:
>>>> Does seam-persistence provide any mechanism that handles jdbc
>>>> connections and sql native queries?
>>>>
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> seam-dev mailing list
>>> [email protected]
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>> _______________________________________________
>>> seam-dev mailing list
>>> [email protected]
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>
>
_______________________________________________
seam-dev mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-dev
