Menu
▾
▴
springframework-developer
|
From: <jue...@we...> - 2004-11-17 16:41:37
|
Rob, =20 That's fine. What's already there looks good to me! I'll give it a final = review when you're done.=20 =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Colin Sampaleanu Gesendet: Mi 17.11.2004 16:35 An: spr...@li... Betreff: Re: [Springframework-developer] JasperReports Support in 1.1.3 +1 Rob Harrop wrote: > If everyone is in agreement I would like to move the JasperReports > stuff into the main branch ready for 1.1.3. I spent some time > yesterday polishing the JavaDocs for this module which I plan to > finish off over the next few days, plus I'll add a couple of pages of > documentation for this as well. > > Rob > > > ------------------------------------------------------- > This SF.Net email is sponsored by: InterSystems CACHE > FREE OODBMS DOWNLOAD - A multidimensional database that combines > robust object and relational technologies, making it a perfect match > for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <jue...@we...> - 2004-11-19 15:31:10
|
Thanks for moving the JasperReports support over to the main sources, = Rob! I'm currently about to revise it a bit, for example regarding = exception handling on initialization (implementing afterPropertiesSet = instead of overriding initApplicationContext, to allow for throwing any = exception and avoid the need to use unchecked wrapper exceptions). =20 There's one further thing I'd like to improve: JRDataSource lookup. It = would be good if controller code would not have to add a = JasperReports-specific class to the model. Instead, we could pass in a = bean collection or bean array, to be implicitly wrapped with a = JRBeanCollectionDataSource or a JRBeanArrayDataSource, respectively. =20 It looks to me that the JasperReports parameter map does not support = collections or arrays anyway, so we could in principle auto-detect a = collection or array in the model and wrap it accordingly as = JRDataSource. Else, we could define a specific model name for the = JRDataSource (as bean property on the view): if specified, the given = model object will be used (wrapped if necessary), rather than searching = the model map for matching values. =20 I've also updated JasperReports to the recently released 0.6.2. I'll = commit my current state tonight or tomorrow morning. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Rob Harrop Gesendet: Mi 17.11.2004 10:34 An: spr...@li... Betreff: [Springframework-developer] JasperReports Support in 1.1.3 If everyone is in agreement I would like to move the JasperReports stuff into the main branch ready for 1.1.3. I spent some time yesterday polishing the JavaDocs for this module which I plan to finish off over the next few days, plus I'll add a couple of pages of documentation for this as well. Rob ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Rob H. <ro...@ca...> - 2004-11-19 16:04:13
|
Jurgen, Fire away with any modfications - I'll be sure to pay attention to what you do so I can get the same pattern in the rest of may code. As for adding auto-lookup of collections to wrap with JRBeanCollectionDataSource - I did that this morning along with appropriate tests. It uses a specific parameter name, reportData, which should be an instance of Collection. The reason I didn't opt for just taking the first collection it sees is because I don't know if JR will support passing a collection as parameter at some point in the future or whether some other reporting engine already has this support. Rob jürgen höller [werk3AT] wrote: >Thanks for moving the JasperReports support over to the main sources, Rob! I'm currently about to revise it a bit, for example regarding exception handling on initialization (implementing afterPropertiesSet instead of overriding initApplicationContext, to allow for throwing any exception and avoid the need to use unchecked wrapper exceptions). > >There's one further thing I'd like to improve: JRDataSource lookup. It would be good if controller code would not have to add a JasperReports-specific class to the model. Instead, we could pass in a bean collection or bean array, to be implicitly wrapped with a JRBeanCollectionDataSource or a JRBeanArrayDataSource, respectively. > >It looks to me that the JasperReports parameter map does not support collections or arrays anyway, so we could in principle auto-detect a collection or array in the model and wrap it accordingly as JRDataSource. Else, we could define a specific model name for the JRDataSource (as bean property on the view): if specified, the given model object will be used (wrapped if necessary), rather than searching the model map for matching values. > >I've also updated JasperReports to the recently released 0.6.2. I'll commit my current state tonight or tomorrow morning. > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag von Rob Harrop >Gesendet: Mi 17.11.2004 10:34 >An: spr...@li... >Betreff: [Springframework-developer] JasperReports Support in 1.1.3 > > > >If everyone is in agreement I would like to move the JasperReports stuff >into the main branch ready for 1.1.3. I spent some time yesterday >polishing the JavaDocs for this module which I plan to finish off over >the next few days, plus I'll add a couple of pages of documentation for >this as well. > >Rob > > >------------------------------------------------------- >This SF.Net email is sponsored by: InterSystems CACHE >FREE OODBMS DOWNLOAD - A multidimensional database that combines >robust object and relational technologies, making it a perfect match >for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: InterSystems CACHE >FREE OODBMS DOWNLOAD - A multidimensional database that combines >robust object and relational technologies, making it a perfect match >for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > |
|
From: <jue...@we...> - 2004-11-20 19:49:10
|
I've just committed a bunch of changes.
=20
The JasperReports web view support does not define specific exceptions =
for startup failures now but uses standard exceptions instead (similar =
to VelocityView and co). Additionally, I've reworked the implementation =
hierarchy to avoid Writer/OutputStream-specific subclasses: =
AbstractJasperReportsView does not only define a "createExporter" =
template method but also a "useWriter" method that subclasses can use to =
indicate whether they want text or binary content written.
=20
Furthermore, I've reduced the scope of JasperReportsUtils: It has just =
render methods left, as the rest is covered in a simple enough fashion =
by the JasperReports API itself now (in particular as of version 0.6.2). =
For rendering, there's always a new instance of JRXxxExporter getting =
created: Those exporter instances are not meant to be reused and are not =
thread-safe, judging from the implementation. (JasperReports API doc =
does generally leaves something to be desired.)
=20
Report data can be any object now, to be converted to a JRDataSource: =
either a JRDataSource itself, a Collection or an object array. In the =
web view, by default a corresponding object in the given model gets =
located (first looking for a JRDataSource, then for a Collection, then =
for an array). A specific model attribute gets used if the =
"reportDataKey" property is specified on AbstractJasperReportsView, =
which can in turn refer to any of those types. The difference is that it =
doesn't matter if there are other collections or arrays in the model =
then.
=20
I wanted to avoid a default model key ("reportData" or the like) being =
used if no JRDataSource is found in the model. A Controller should be =
able to pass any model in, choosing any key for report data, or also any =
parameter under the key "reportData" (with report data under a different =
name). It seems to me that auto-detection by type, with the option to =
specify a specific model key instead (on the view definition), is the =
better strategy. If other parameters are collections or arrays, a =
"reportDataKey" *must* be specified.
=20
Rob, I hope you don't object to these changes, in particular not to the =
reduced scope of JasperReportsUtils. My main intent there was to avoid =
1-to-1 duplication of methods in JasperReports API, which isn't =
desirable in multiple respects (for example, maintenance and =
compatibility with the recommended style in future JasperReports =
versions). Convenience methods to render a specific format (for use =
outside web views) add value in any case, as they replace a couple of =
lines of JasperReports API calls.
=20
Juergen
=20
=20
________________________________
Von: spr...@li... im Auftrag =
von Rob Harrop
Gesendet: Fr 19.11.2004 17:06
An: spr...@li...
Betreff: Re: [Springframework-developer] JasperReports Support in 1.1.3
Jurgen,
Fire away with any modfications - I'll be sure to pay attention to what
you do so I can get the same pattern in the rest of may code. As for
adding auto-lookup of collections to wrap with
JRBeanCollectionDataSource - I did that this morning along with
appropriate tests. It uses a specific parameter name, reportData, which
should be an instance of Collection. The reason I didn't opt for just
taking the first collection it sees is because I don't know if JR will
support passing a collection as parameter at some point in the future or
whether some other reporting engine already has this support.
Rob
j=FCrgen h=F6ller [werk3AT] wrote:
>Thanks for moving the JasperReports support over to the main sources, =
Rob! I'm currently about to revise it a bit, for example regarding =
exception handling on initialization (implementing afterPropertiesSet =
instead of overriding initApplicationContext, to allow for throwing any =
exception and avoid the need to use unchecked wrapper exceptions).
>
>There's one further thing I'd like to improve: JRDataSource lookup. It =
would be good if controller code would not have to add a =
JasperReports-specific class to the model. Instead, we could pass in a =
bean collection or bean array, to be implicitly wrapped with a =
JRBeanCollectionDataSource or a JRBeanArrayDataSource, respectively.
>
>It looks to me that the JasperReports parameter map does not support =
collections or arrays anyway, so we could in principle auto-detect a =
collection or array in the model and wrap it accordingly as =
JRDataSource. Else, we could define a specific model name for the =
JRDataSource (as bean property on the view): if specified, the given =
model object will be used (wrapped if necessary), rather than searching =
the model map for matching values.
>
>I've also updated JasperReports to the recently released 0.6.2. I'll =
commit my current state tonight or tomorrow morning.
>
>Juergen
>
>
>________________________________
>
>Von: spr...@li... im Auftrag =
von Rob Harrop
>Gesendet: Mi 17.11.2004 10:34
>An: spr...@li...
>Betreff: [Springframework-developer] JasperReports Support in 1.1.3
>
>
>
>If everyone is in agreement I would like to move the JasperReports =
stuff
>into the main branch ready for 1.1.3. I spent some time yesterday
>polishing the JavaDocs for this module which I plan to finish off over
>the next few days, plus I'll add a couple of pages of documentation for
>this as well.
>
>Rob
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: InterSystems CACHE
>FREE OODBMS DOWNLOAD - A multidimensional database that combines
>robust object and relational technologies, making it a perfect match
>for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: InterSystems CACHE
>FREE OODBMS DOWNLOAD - A multidimensional database that combines
>robust object and relational technologies, making it a perfect match
>for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>=20
>
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: Rob H. <ro...@ca...> - 2004-11-21 12:26:07
|
Jurgen,
I just took a look at what you did - looks cool! This is definitely
ready for inclusion now.
Rob
jürgen höller [werk3AT] wrote:
>I've just committed a bunch of changes.
>
>The JasperReports web view support does not define specific exceptions for startup failures now but uses standard exceptions instead (similar to VelocityView and co). Additionally, I've reworked the implementation hierarchy to avoid Writer/OutputStream-specific subclasses: AbstractJasperReportsView does not only define a "createExporter" template method but also a "useWriter" method that subclasses can use to indicate whether they want text or binary content written.
>
>Furthermore, I've reduced the scope of JasperReportsUtils: It has just render methods left, as the rest is covered in a simple enough fashion by the JasperReports API itself now (in particular as of version 0.6.2). For rendering, there's always a new instance of JRXxxExporter getting created: Those exporter instances are not meant to be reused and are not thread-safe, judging from the implementation. (JasperReports API doc does generally leaves something to be desired.)
>
>Report data can be any object now, to be converted to a JRDataSource: either a JRDataSource itself, a Collection or an object array. In the web view, by default a corresponding object in the given model gets located (first looking for a JRDataSource, then for a Collection, then for an array). A specific model attribute gets used if the "reportDataKey" property is specified on AbstractJasperReportsView, which can in turn refer to any of those types. The difference is that it doesn't matter if there are other collections or arrays in the model then.
>
>I wanted to avoid a default model key ("reportData" or the like) being used if no JRDataSource is found in the model. A Controller should be able to pass any model in, choosing any key for report data, or also any parameter under the key "reportData" (with report data under a different name). It seems to me that auto-detection by type, with the option to specify a specific model key instead (on the view definition), is the better strategy. If other parameters are collections or arrays, a "reportDataKey" *must* be specified.
>
>Rob, I hope you don't object to these changes, in particular not to the reduced scope of JasperReportsUtils. My main intent there was to avoid 1-to-1 duplication of methods in JasperReports API, which isn't desirable in multiple respects (for example, maintenance and compatibility with the recommended style in future JasperReports versions). Convenience methods to render a specific format (for use outside web views) add value in any case, as they replace a couple of lines of JasperReports API calls.
>
>Juergen
>
>
>
>________________________________
>
>Von: spr...@li... im Auftrag von Rob Harrop
>Gesendet: Fr 19.11.2004 17:06
>An: spr...@li...
>Betreff: Re: [Springframework-developer] JasperReports Support in 1.1.3
>
>
>
>Jurgen,
>
>Fire away with any modfications - I'll be sure to pay attention to what
>you do so I can get the same pattern in the rest of may code. As for
>adding auto-lookup of collections to wrap with
>JRBeanCollectionDataSource - I did that this morning along with
>appropriate tests. It uses a specific parameter name, reportData, which
>should be an instance of Collection. The reason I didn't opt for just
>taking the first collection it sees is because I don't know if JR will
>support passing a collection as parameter at some point in the future or
>whether some other reporting engine already has this support.
>
>Rob
>
>jürgen höller [werk3AT] wrote:
>
>
>
>>Thanks for moving the JasperReports support over to the main sources, Rob! I'm currently about to revise it a bit, for example regarding exception handling on initialization (implementing afterPropertiesSet instead of overriding initApplicationContext, to allow for throwing any exception and avoid the need to use unchecked wrapper exceptions).
>>
>>There's one further thing I'd like to improve: JRDataSource lookup. It would be good if controller code would not have to add a JasperReports-specific class to the model. Instead, we could pass in a bean collection or bean array, to be implicitly wrapped with a JRBeanCollectionDataSource or a JRBeanArrayDataSource, respectively.
>>
>>It looks to me that the JasperReports parameter map does not support collections or arrays anyway, so we could in principle auto-detect a collection or array in the model and wrap it accordingly as JRDataSource. Else, we could define a specific model name for the JRDataSource (as bean property on the view): if specified, the given model object will be used (wrapped if necessary), rather than searching the model map for matching values.
>>
>>I've also updated JasperReports to the recently released 0.6.2. I'll commit my current state tonight or tomorrow morning.
>>
>>Juergen
>>
>>
>>________________________________
>>
>>Von: spr...@li... im Auftrag von Rob Harrop
>>Gesendet: Mi 17.11.2004 10:34
>>An: spr...@li...
>>Betreff: [Springframework-developer] JasperReports Support in 1.1.3
>>
>>
>>
>>If everyone is in agreement I would like to move the JasperReports stuff
>>into the main branch ready for 1.1.3. I spent some time yesterday
>>polishing the JavaDocs for this module which I plan to finish off over
>>the next few days, plus I'll add a couple of pages of documentation for
>>this as well.
>>
>>Rob
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by: InterSystems CACHE
>>FREE OODBMS DOWNLOAD - A multidimensional database that combines
>>robust object and relational technologies, making it a perfect match
>>for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by: InterSystems CACHE
>>FREE OODBMS DOWNLOAD - A multidimensional database that combines
>>robust object and relational technologies, making it a perfect match
>>for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>>
>>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: InterSystems CACHE
>FREE OODBMS DOWNLOAD - A multidimensional database that combines
>robust object and relational technologies, making it a perfect match
>for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: InterSystems CACHE
>FREE OODBMS DOWNLOAD - A multidimensional database that combines
>robust object and relational technologies, making it a perfect match
>for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
|
|
From: Thomas R. <tho...@tr...> - 2004-11-21 16:46:08
|
Just noticed that the tests fail -maybe CVS mangled the report file - is
DataSourceReport.jasper a binary file?
Thomas
Rob Harrop wrote:
> Jurgen,
>
> I just took a look at what you did - looks cool! This is definitely
> ready for inclusion now.
>
> Rob
>
> jürgen höller [werk3AT] wrote:
>
>> I've just committed a bunch of changes.
>>
>> The JasperReports web view support does not define specific
>> exceptions for startup failures now but uses standard exceptions
>> instead (similar to VelocityView and co). Additionally, I've reworked
>> the implementation hierarchy to avoid Writer/OutputStream-specific
>> subclasses: AbstractJasperReportsView does not only define a
>> "createExporter" template method but also a "useWriter" method that
>> subclasses can use to indicate whether they want text or binary
>> content written.
>>
>> Furthermore, I've reduced the scope of JasperReportsUtils: It has
>> just render methods left, as the rest is covered in a simple enough
>> fashion by the JasperReports API itself now (in particular as of
>> version 0.6.2). For rendering, there's always a new instance of
>> JRXxxExporter getting created: Those exporter instances are not meant
>> to be reused and are not thread-safe, judging from the
>> implementation. (JasperReports API doc does generally leaves
>> something to be desired.)
>>
>> Report data can be any object now, to be converted to a JRDataSource:
>> either a JRDataSource itself, a Collection or an object array. In the
>> web view, by default a corresponding object in the given model gets
>> located (first looking for a JRDataSource, then for a Collection,
>> then for an array). A specific model attribute gets used if the
>> "reportDataKey" property is specified on AbstractJasperReportsView,
>> which can in turn refer to any of those types. The difference is that
>> it doesn't matter if there are other collections or arrays in the
>> model then.
>>
>> I wanted to avoid a default model key ("reportData" or the like)
>> being used if no JRDataSource is found in the model. A Controller
>> should be able to pass any model in, choosing any key for report
>> data, or also any parameter under the key "reportData" (with report
>> data under a different name). It seems to me that auto-detection by
>> type, with the option to specify a specific model key instead (on the
>> view definition), is the better strategy. If other parameters are
>> collections or arrays, a "reportDataKey" *must* be specified.
>>
>> Rob, I hope you don't object to these changes, in particular not to
>> the reduced scope of JasperReportsUtils. My main intent there was to
>> avoid 1-to-1 duplication of methods in JasperReports API, which isn't
>> desirable in multiple respects (for example, maintenance and
>> compatibility with the recommended style in future JasperReports
>> versions). Convenience methods to render a specific format (for use
>> outside web views) add value in any case, as they replace a couple of
>> lines of JasperReports API calls.
>>
>> Juergen
>>
>>
>>
>> ________________________________
>>
>> Von: spr...@li... im Auftrag
>> von Rob Harrop
>> Gesendet: Fr 19.11.2004 17:06
>> An: spr...@li...
>> Betreff: Re: [Springframework-developer] JasperReports Support in 1.1.3
>>
>>
>>
>> Jurgen,
>>
>> Fire away with any modfications - I'll be sure to pay attention to what
>> you do so I can get the same pattern in the rest of may code. As for
>> adding auto-lookup of collections to wrap with
>> JRBeanCollectionDataSource - I did that this morning along with
>> appropriate tests. It uses a specific parameter name, reportData, which
>> should be an instance of Collection. The reason I didn't opt for just
>> taking the first collection it sees is because I don't know if JR will
>> support passing a collection as parameter at some point in the future or
>> whether some other reporting engine already has this support.
>>
>> Rob
>>
>> jürgen höller [werk3AT] wrote:
>>
>>
>>
>>> Thanks for moving the JasperReports support over to the main
>>> sources, Rob! I'm currently about to revise it a bit, for example
>>> regarding exception handling on initialization (implementing
>>> afterPropertiesSet instead of overriding initApplicationContext, to
>>> allow for throwing any exception and avoid the need to use unchecked
>>> wrapper exceptions).
>>>
>>> There's one further thing I'd like to improve: JRDataSource lookup.
>>> It would be good if controller code would not have to add a
>>> JasperReports-specific class to the model. Instead, we could pass in
>>> a bean collection or bean array, to be implicitly wrapped with a
>>> JRBeanCollectionDataSource or a JRBeanArrayDataSource, respectively.
>>>
>>> It looks to me that the JasperReports parameter map does not support
>>> collections or arrays anyway, so we could in principle auto-detect a
>>> collection or array in the model and wrap it accordingly as
>>> JRDataSource. Else, we could define a specific model name for the
>>> JRDataSource (as bean property on the view): if specified, the given
>>> model object will be used (wrapped if necessary), rather than
>>> searching the model map for matching values.
>>>
>>> I've also updated JasperReports to the recently released 0.6.2. I'll
>>> commit my current state tonight or tomorrow morning.
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im
>>> Auftrag von Rob Harrop
>>> Gesendet: Mi 17.11.2004 10:34
>>> An: spr...@li...
>>> Betreff: [Springframework-developer] JasperReports Support in 1.1.3
>>>
>>>
>>>
>>> If everyone is in agreement I would like to move the JasperReports
>>> stuff
>>> into the main branch ready for 1.1.3. I spent some time yesterday
>>> polishing the JavaDocs for this module which I plan to finish off over
>>> the next few days, plus I'll add a couple of pages of documentation for
>>> this as well.
>>>
>>> Rob
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by: InterSystems CACHE
>>> FREE OODBMS DOWNLOAD - A multidimensional database that combines
>>> robust object and relational technologies, making it a perfect match
>>> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by: InterSystems CACHE
>>> FREE OODBMS DOWNLOAD - A multidimensional database that combines
>>> robust object and relational technologies, making it a perfect match
>>> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: InterSystems CACHE
>> FREE OODBMS DOWNLOAD - A multidimensional database that combines
>> robust object and relational technologies, making it a perfect match
>> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: InterSystems CACHE
>> FREE OODBMS DOWNLOAD - A multidimensional database that combines
>> robust object and relational technologies, making it a perfect match
>> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
|
|
From: snpe <sn...@sn...> - 2004-11-21 14:59:11
|
Juergen, Rob
Is it possible use jasper out of spring MVC (for instance, in spring rcp) =
and is there any documentation, please ?
Thanks
On Saturday 20 November 2004 07:52 pm, j=FCrgen h=F6ller [werk3AT] wrote:
> I've just committed a bunch of changes.
> =20
> The JasperReports web view support does not define specific exceptions fo=
r startup failures now but uses standard exceptions instead (similar to Vel=
ocityView and co). Additionally, I've reworked the implementation hierarchy=
to avoid Writer/OutputStream-specific subclasses: AbstractJasperReportsVie=
w does not only define a "createExporter" template method but also a "useWr=
iter" method that subclasses can use to indicate whether they want text or =
binary content written.
> =20
> Furthermore, I've reduced the scope of JasperReportsUtils: It has just re=
nder methods left, as the rest is covered in a simple enough fashion by the=
JasperReports API itself now (in particular as of version 0.6.2). For rend=
ering, there's always a new instance of JRXxxExporter getting created: Thos=
e exporter instances are not meant to be reused and are not thread-safe, ju=
dging from the implementation. (JasperReports API doc does generally leaves=
something to be desired.)
> =20
> Report data can be any object now, to be converted to a JRDataSource: eit=
her a JRDataSource itself, a Collection or an object array. In the web view=
, by default a corresponding object in the given model gets located (first =
looking for a JRDataSource, then for a Collection, then for an array). A sp=
ecific model attribute gets used if the "reportDataKey" property is specifi=
ed on AbstractJasperReportsView, which can in turn refer to any of those ty=
pes. The difference is that it doesn't matter if there are other collection=
s or arrays in the model then.
> =20
> I wanted to avoid a default model key ("reportData" or the like) being us=
ed if no JRDataSource is found in the model. A Controller should be able to=
pass any model in, choosing any key for report data, or also any parameter=
under the key "reportData" (with report data under a different name). It s=
eems to me that auto-detection by type, with the option to specify a specif=
ic model key instead (on the view definition), is the better strategy. If o=
ther parameters are collections or arrays, a "reportDataKey" *must* be spec=
ified.
> =20
> Rob, I hope you don't object to these changes, in particular not to the r=
educed scope of JasperReportsUtils. My main intent there was to avoid 1-to-=
1 duplication of methods in JasperReports API, which isn't desirable in mul=
tiple respects (for example, maintenance and compatibility with the recomme=
nded style in future JasperReports versions). Convenience methods to render=
a specific format (for use outside web views) add value in any case, as th=
ey replace a couple of lines of JasperReports API calls.
> =20
> Juergen
> =20
> =20
>=20
> ________________________________
>=20
> Von: spr...@li... im Auftrag von=
Rob Harrop
> Gesendet: Fr 19.11.2004 17:06
> An: spr...@li...
> Betreff: Re: [Springframework-developer] JasperReports Support in 1.1.3
>=20
>=20
>=20
> Jurgen,
>=20
> Fire away with any modfications - I'll be sure to pay attention to what
> you do so I can get the same pattern in the rest of may code. As for
> adding auto-lookup of collections to wrap with
> JRBeanCollectionDataSource - I did that this morning along with
> appropriate tests. It uses a specific parameter name, reportData, which
> should be an instance of Collection. The reason I didn't opt for just
> taking the first collection it sees is because I don't know if JR will
> support passing a collection as parameter at some point in the future or
> whether some other reporting engine already has this support.
>=20
> Rob
>=20
> j=FCrgen h=F6ller [werk3AT] wrote:
>=20
> >Thanks for moving the JasperReports support over to the main sources, Ro=
b! I'm currently about to revise it a bit, for example regarding exception =
handling on initialization (implementing afterPropertiesSet instead of over=
riding initApplicationContext, to allow for throwing any exception and avoi=
d the need to use unchecked wrapper exceptions).
> >
> >There's one further thing I'd like to improve: JRDataSource lookup. It w=
ould be good if controller code would not have to add a JasperReports-speci=
fic class to the model. Instead, we could pass in a bean collection or bean=
array, to be implicitly wrapped with a JRBeanCollectionDataSource or a JRB=
eanArrayDataSource, respectively.
> >
> >It looks to me that the JasperReports parameter map does not support col=
lections or arrays anyway, so we could in principle auto-detect a collectio=
n or array in the model and wrap it accordingly as JRDataSource. Else, we c=
ould define a specific model name for the JRDataSource (as bean property on=
the view): if specified, the given model object will be used (wrapped if n=
ecessary), rather than searching the model map for matching values.
> >
> >I've also updated JasperReports to the recently released 0.6.2. I'll com=
mit my current state tonight or tomorrow morning.
> >
> >Juergen
> >
> >
> >________________________________
> >
> >Von: spr...@li... im Auftrag vo=
n Rob Harrop
> >Gesendet: Mi 17.11.2004 10:34
> >An: spr...@li...
> >Betreff: [Springframework-developer] JasperReports Support in 1.1.3
> >
> >
> >
> >If everyone is in agreement I would like to move the JasperReports stuff
> >into the main branch ready for 1.1.3. I spent some time yesterday
> >polishing the JavaDocs for this module which I plan to finish off over
> >the next few days, plus I'll add a couple of pages of documentation for
> >this as well.
> >
> >Rob
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by: InterSystems CACHE
> >FREE OODBMS DOWNLOAD - A multidimensional database that combines
> >robust object and relational technologies, making it a perfect match
> >for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> >_______________________________________________
> >Springframework-developer mailing list
> >Spr...@li...
> >https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >
> >
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by: InterSystems CACHE
> >FREE OODBMS DOWNLOAD - A multidimensional database that combines
> >robust object and relational technologies, making it a perfect match
> >for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> >_______________________________________________
> >Springframework-developer mailing list
> >Spr...@li...
> >https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >
> >
> >=20
> >
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
|
|
From: Andy D. <an...@ma...> - 2004-11-22 18:57:41
|
I too am interested in an answer as we will be using it with spring-rich as well. - Andy On Sunday 21 November 2004 08:58 am, snpe wrote: > Juergen, Rob > > Is it possible use jasper out of spring MVC (for instance, in spring rcp) > and is there any documentation, please ? > > Thanks |
|
From: <jue...@we...> - 2004-11-21 18:40:09
|
Indeed - just fixed it.
=20
Juergen
=20
________________________________
Von: spr...@li... im Auftrag =
von Thomas Risberg
Gesendet: So 21.11.2004 17:44
An: spr...@li...
Betreff: Re: [Springframework-developer] JasperReports Support in 1.1.3
Just noticed that the tests fail -maybe CVS mangled the report file - is
DataSourceReport.jasper a binary file?
Thomas
Rob Harrop wrote:
> Jurgen,
>
> I just took a look at what you did - looks cool! This is definitely
> ready for inclusion now.
>
> Rob
>
> j=FCrgen h=F6ller [werk3AT] wrote:
>
>> I've just committed a bunch of changes.
>>
>> The JasperReports web view support does not define specific
>> exceptions for startup failures now but uses standard exceptions
>> instead (similar to VelocityView and co). Additionally, I've reworked
>> the implementation hierarchy to avoid Writer/OutputStream-specific
>> subclasses: AbstractJasperReportsView does not only define a
>> "createExporter" template method but also a "useWriter" method that
>> subclasses can use to indicate whether they want text or binary
>> content written.
>>
>> Furthermore, I've reduced the scope of JasperReportsUtils: It has
>> just render methods left, as the rest is covered in a simple enough
>> fashion by the JasperReports API itself now (in particular as of
>> version 0.6.2). For rendering, there's always a new instance of
>> JRXxxExporter getting created: Those exporter instances are not meant
>> to be reused and are not thread-safe, judging from the
>> implementation. (JasperReports API doc does generally leaves
>> something to be desired.)
>>
>> Report data can be any object now, to be converted to a JRDataSource:
>> either a JRDataSource itself, a Collection or an object array. In the
>> web view, by default a corresponding object in the given model gets
>> located (first looking for a JRDataSource, then for a Collection,
>> then for an array). A specific model attribute gets used if the
>> "reportDataKey" property is specified on AbstractJasperReportsView,
>> which can in turn refer to any of those types. The difference is that
>> it doesn't matter if there are other collections or arrays in the
>> model then.
>>
>> I wanted to avoid a default model key ("reportData" or the like)
>> being used if no JRDataSource is found in the model. A Controller
>> should be able to pass any model in, choosing any key for report
>> data, or also any parameter under the key "reportData" (with report
>> data under a different name). It seems to me that auto-detection by
>> type, with the option to specify a specific model key instead (on the
>> view definition), is the better strategy. If other parameters are
>> collections or arrays, a "reportDataKey" *must* be specified.
>>
>> Rob, I hope you don't object to these changes, in particular not to
>> the reduced scope of JasperReportsUtils. My main intent there was to
>> avoid 1-to-1 duplication of methods in JasperReports API, which isn't
>> desirable in multiple respects (for example, maintenance and
>> compatibility with the recommended style in future JasperReports
>> versions). Convenience methods to render a specific format (for use
>> outside web views) add value in any case, as they replace a couple of
>> lines of JasperReports API calls.
>>
>> Juergen
>>
>>
>>
>> ________________________________
>>
>> Von: spr...@li... im Auftrag
>> von Rob Harrop
>> Gesendet: Fr 19.11.2004 17:06
>> An: spr...@li...
>> Betreff: Re: [Springframework-developer] JasperReports Support in =
1.1.3
>>
>>
>>
>> Jurgen,
>>
>> Fire away with any modfications - I'll be sure to pay attention to =
what
>> you do so I can get the same pattern in the rest of may code. As for
>> adding auto-lookup of collections to wrap with
>> JRBeanCollectionDataSource - I did that this morning along with
>> appropriate tests. It uses a specific parameter name, reportData, =
which
>> should be an instance of Collection. The reason I didn't opt for just
>> taking the first collection it sees is because I don't know if JR =
will
>> support passing a collection as parameter at some point in the future =
or
>> whether some other reporting engine already has this support.
>>
>> Rob
>>
>> j=FCrgen h=F6ller [werk3AT] wrote:
>>
>>=20
>>
>>> Thanks for moving the JasperReports support over to the main
>>> sources, Rob! I'm currently about to revise it a bit, for example
>>> regarding exception handling on initialization (implementing
>>> afterPropertiesSet instead of overriding initApplicationContext, to
>>> allow for throwing any exception and avoid the need to use unchecked
>>> wrapper exceptions).
>>>
>>> There's one further thing I'd like to improve: JRDataSource lookup.
>>> It would be good if controller code would not have to add a
>>> JasperReports-specific class to the model. Instead, we could pass in
>>> a bean collection or bean array, to be implicitly wrapped with a
>>> JRBeanCollectionDataSource or a JRBeanArrayDataSource, respectively.
>>>
>>> It looks to me that the JasperReports parameter map does not support
>>> collections or arrays anyway, so we could in principle auto-detect a
>>> collection or array in the model and wrap it accordingly as
>>> JRDataSource. Else, we could define a specific model name for the
>>> JRDataSource (as bean property on the view): if specified, the given
>>> model object will be used (wrapped if necessary), rather than
>>> searching the model map for matching values.
>>>
>>> I've also updated JasperReports to the recently released 0.6.2. I'll
>>> commit my current state tonight or tomorrow morning.
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im
>>> Auftrag von Rob Harrop
>>> Gesendet: Mi 17.11.2004 10:34
>>> An: spr...@li...
>>> Betreff: [Springframework-developer] JasperReports Support in 1.1.3
>>>
>>>
>>>
>>> If everyone is in agreement I would like to move the JasperReports
>>> stuff
>>> into the main branch ready for 1.1.3. I spent some time yesterday
>>> polishing the JavaDocs for this module which I plan to finish off =
over
>>> the next few days, plus I'll add a couple of pages of documentation =
for
>>> this as well.
>>>
>>> Rob
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by: InterSystems CACHE
>>> FREE OODBMS DOWNLOAD - A multidimensional database that combines
>>> robust object and relational technologies, making it a perfect match
>>> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> =
https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by: InterSystems CACHE
>>> FREE OODBMS DOWNLOAD - A multidimensional database that combines
>>> robust object and relational technologies, making it a perfect match
>>> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> =
https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>> =20
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: InterSystems CACHE
>> FREE OODBMS DOWNLOAD - A multidimensional database that combines
>> robust object and relational technologies, making it a perfect match
>> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> =
https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: InterSystems CACHE
>> FREE OODBMS DOWNLOAD - A multidimensional database that combines
>> robust object and relational technologies, making it a perfect match
>> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> =
https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>=20
>>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: <jue...@we...> - 2004-11-22 19:02:12
|
Well, all I can say beyond that JasperReports is not tied to a web = environment: check out the JasperReports docs at = http://jasperreports.sourceforge.net - standalone usage of JasperReports = does not have anything to do with Spring. The only convenience that = Spring offers is the JasperReportsUtils class, which you may or may not = choose to use for rendering a report - the plain JasperReports API is = not too hard either in that respect. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Andy Depue Gesendet: Mo 22.11.2004 19:57 An: spr...@li... Betreff: Re: [Springframework-developer] JasperReports Support in 1.1.3 I too am interested in an answer as we will be using it with spring-rich = as well. - Andy On Sunday 21 November 2004 08:58 am, snpe wrote: > Juergen, Rob > > Is it possible use jasper out of spring MVC (for instance, in spring = rcp) > and is there any documentation, please ? > > Thanks ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Darren D. <da...@da...> - 2004-11-23 01:34:47
|
should the tests for JasperReports be working at the moment? In the latest= =20 snapshot I have 46 errors from the 58 tests (JDK 1.4.2 on Linux 2.6.9) Could not parse JasperReports report for URL=20 [org/springframework/ui/jasperreports/DataSourceReport.jasper]; nested=20 exception is net.sf.jasperreports.engine.JRException: Error loading object= =20 from InputStream =20 org.springframework.context.ApplicationContextException: Could not parse=20 JasperReports report for URL=20 [org/springframework/ui/jasperreports/DataSourceReport.jasper]; nested=20 exception is net.sf.jasperreports.engine.JRException: Error loading object= =20 from InputStreamjava.io.EOFException at=20 java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:= 2165)=20 =2E. [some snipped] .. java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at=20 net.sf.jasperreports.engine.util.JRLoader.loadObject(JRLoader.java:233) at= =20 org.springframework.ui.jasperreports.JasperReportsUtilsTests.getReport(Jasp= erReportsUtilsTests.java:150)=20 at=20 org.springframework.ui.jasperreports.JasperReportsUtilsTests.testRenderAsCs= vWithDataSource(JasperReportsUtilsTests.java:51)=20 at =2D-=20 Darren Davison Public Key: #DD356B0D |
|
From: Rob H. <ro...@ca...> - 2004-11-23 10:12:58
|
I think that file got corrupted in CVS. Jurgen uploaded it again I think. Rob Darren Davison wrote: >should the tests for JasperReports be working at the moment? In the latest >snapshot I have 46 errors from the 58 tests (JDK 1.4.2 on Linux 2.6.9) > > >Could not parse JasperReports report for URL >[org/springframework/ui/jasperreports/DataSourceReport.jasper]; nested >exception is net.sf.jasperreports.engine.JRException: Error loading object >from InputStream > > org.springframework.context.ApplicationContextException: Could not parse >JasperReports report for URL >[org/springframework/ui/jasperreports/DataSourceReport.jasper]; nested >exception is net.sf.jasperreports.engine.JRException: Error loading object >from InputStreamjava.io.EOFException at >java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2165) >.. [some snipped] .. >java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at >net.sf.jasperreports.engine.util.JRLoader.loadObject(JRLoader.java:233) at >org.springframework.ui.jasperreports.JasperReportsUtilsTests.getReport(JasperReportsUtilsTests.java:150) >at >org.springframework.ui.jasperreports.JasperReportsUtilsTests.testRenderAsCsvWithDataSource(JasperReportsUtilsTests.java:51) >at > > > |
|
From: Darren D. <da...@da...> - 2004-11-23 10:48:19
|
On Tue, November 23, 2004 10:14, Rob Harrop said: > I think that file got corrupted in CVS. Jurgen uploaded it again I thi= nk. Thanks Rob, I'll give 'em another go. Was just a bit worried it may have= been a Win32/UNIX file-system issue or something.. --=20 Darren Davison Public Key: #DD356B0D |
|
From: Patrick B. <pbu...@gm...> - 2004-11-17 17:14:12
|
I don't have access to check out the sandbox, so I have a silly question.= =20 What sort of support is provided? What's the purpose of the support? Thanks, Patrick On Wed, 17 Nov 2004 17:39:20 +0100, j=FCrgen h=F6ller [ werk3AT ] <jue...@we...> wrote: > Rob, >=20 > That's fine. What's already there looks good to me! I'll give it a final = review when you're done. >=20 > Juergen >=20 > ________________________________ >=20 > Von: spr...@li... im Auftrag von= Colin Sampaleanu > Gesendet: Mi 17.11.2004 16:35 > An: spr...@li... > Betreff: Re: [Springframework-developer] JasperReports Support in 1.1.3 >=20 >=20 >=20 >=20 > +1 >=20 > Rob Harrop wrote: >=20 > > If everyone is in agreement I would like to move the JasperReports > > stuff into the main branch ready for 1.1.3. I spent some time > > yesterday polishing the JavaDocs for this module which I plan to > > finish off over the next few days, plus I'll add a couple of pages of > > documentation for this as well. > > > > Rob > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: InterSystems CACHE > > FREE OODBMS DOWNLOAD - A multidimensional database that combines > > robust object and relational technologies, making it a perfect match > > for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 > > _______________________________________________ > > Springframework-developer mailing list > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: InterSystems CACHE > FREE OODBMS DOWNLOAD - A multidimensional database that combines > robust object and relational technologies, making it a perfect match > for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: InterSystems CACHE > FREE OODBMS DOWNLOAD - A multidimensional database that combines > robust object and relational technologies, making it a perfect match > for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
