The procedure tag has never accepted a parameterClass as the schema shows
it.
I will modify the code to remove it.


On 11/16/06, Bob Hanson <[EMAIL PROTECTED]> wrote:

Today I (think I) grabbed the latest version from SVN. The schema no
longer requires a paramterMap.

While looking through the source it appears that the Procedure class has
also been modified to accept a parameterClass. However SqlMap.xsd has not
been updated to allow parameterClass. Am I correct or did I not get the
latest file?

On 11/16/06, Gilles Bayon < [EMAIL PROTECTED]> wrote:
>
> It's in SVN
>
> On 11/15/06, Bob Hanson <[EMAIL PROTECTED]> wrote:
> >
> > Are there any plans to change the schema so that a parameter map is not 
required for a stored procedure?
> >
> >
> > ------------------
> > From: Oddur Snær Magnússon [mailto:[EMAIL <%5BEMAIL>
> >  PROTECTED]
> > Sent: Mon 7/24/2006 10:11 PM
> > To: [email protected]
> > Subject: RE: Problem calling stored procedure having no parameter
> >
> >
> >
> >
> > I got around it by having an empty parametermap
> >
> >         <parameterMaps>
> >                 <parameterMap id="noparams"></parameterMap>
> >         </parameterMaps>
> >
> > And then using that in the <procedure> statement:
> >
> >
> >
> > <procedure id="GetAllSomething"  parameterMap="noparams"
> > resultMap="SomeThing">sprocName</procedure>
> >
> > I think that's the only solution since the parameterMap attribute is 
required
> >
> > on the procedure element.
> >
> > - Oddur
> >
> >
>
>
> --
> Cheers,
> Gilles
>
> <a href=" http://www.amazon.com/gp/registry/6JCP7AORB0LE ">Wish List</a>
>





--
Cheers,
Gilles

<a href="http://www.amazon.com/gp/registry/6JCP7AORB0LE";>Wish List</a>

Reply via email to