But not being the database guy around here, I'm not the one to talk
about these things so I'll be glad if somebody else wants to come
forward.
One thing is for sure: XSP is showing its age and we should move
forward... but without loosing its value.
Why not pull the ESQL stuff out and provide
Torsten Curdt wrote:
My idea is to come up with an unified syntax. Taking the
best out of the SQLTransformer and the ESQL logicsheet.
Then come up with an ESQL transformer and a logicsheet
using the same code base (as much as possible). For
an easy migration we could provide an ant task that
Le Lundi, 2 fév 2004, à 11:45 Europe/Zurich, Guido Casper a écrit :
Torsten Curdt wrote:
...I just hope it's worth the effort since everyone
seems to be going the OJB way...
It _is_ worth it IMHO since there is more to databases (like reporting
applications) than persisting Java objects
On 2 Feb 2004, at 04:37, Torsten Curdt wrote:
But not being the database guy around here, I'm not the one to talk
about these things so I'll be glad if somebody else wants to come
forward.
One thing is for sure: XSP is showing its age and we should move
forward... but without loosing its
Stefano Mazzocchi wrote:
On 1 Feb 2004, at 19:27, Steve Krulewitz wrote:
I still find the esql taglib to be a very useful and easy way to go
from SQL query to an XML document. If xsp is deprecated, the only
other way to easily do this is the SQLTransformer, but it is lacking
many of the
Stefano Mazzocchi wrote:
snip/
I think that the ESQL logicsheet is the only really valuable and
unique thing that we have in XSP, so, yeah, I totally
understand your
concern.
Ryan Hoegg wrote:
Why not pull the ESQL stuff out and provide a stripped down
ESQLTransformer?
I haven't
