Last time I did this I had some text as resources and I created the
templating mechanism using String.replaceAll.
It was something like 10-20 lines of Java code.
Spring uses velocity and thus is something like a 1-2 mb dependency
and the resulting code:
http://static.springframework.org/spring/
You guys are starting with the wrong problem.
Development tools, language, frameworks doesn't really matter.
It is whether it works at the end-user.
How fast it loads, whether there are obscure security dialogs, whether
graphics flashes and flickers ...
Solve that and you will have users and d
gle.com/p/persist/
> > - EoD SQL athttps://eodsql.dev.java.net/
> > - Ebean athttp://www.avaje.org/
>
> > On Feb 22, 6:21 am, Christian Hvid wrote:
> >> Hi Java people.
>
> >> I have been toying with simplier ways of doing embedded SQL in Java.
>
> &
ich uses similar
> syntax to convert resultsets into beans using a the BeanProcessor class.
>
> Hope this helps,
>
> Mark
>
> On Sun, Feb 22, 2009 at 6:21 AM, Christian Hvid
> wrote:
>
>
>
>
>
> > Hi Java people.
>
> > I have been toying with s
e.simple.
>
> http://static.springframework.org/spring/docs/2.5.x/api/org/springfra...
>
> Keith
>
> On Feb 22, 1:11 pm, Christian Hvid wrote:
>
> > I have worked with Hibernate but I think that is different approach
> > altogether.
>
> > I haven't look
keep working on it. Perhaps
> suggest to your direct friends they could give it a go.
>
> If it has an edge over the alternatives, then it should (could /
> might) take off.
>
> On Feb 23, 12:21 am, Christian Hvid wrote:
>
> > But since it is incredibly hard for a new
y been prepared
> on.
>
> I'm simply suggesting that you might be able to get away with hiding
> the connection management.
>
> I'm not trying to discourage your work. I have written a persistence
> layer which takes a completely different approach again.
>
> Nice
courage your work. I have written a persistence
> layer which takes a completely different approach again.
>
> Nice name by the way. :)
>
> On Feb 23, 5:58 am, Christian Hvid wrote:
>
> > :-D
>
> > Great, exactly.
>
> > This is the point - it removes a
nts. So I've got
> some wacky opinions
> relative to Java norms.)
>
> ~~ Robert.
>
>
>
> Christian Hvid wrote:
> > But you can leave it up to the caller to open the connection - meaning
> > you just don't open or close any connections.
>
> > public int
since you have to
> think about preparing
> statements and managing connections and data sets and the like.
>
> ~~ Robert.
>
>
>
> Christian Hvid wrote:
> > I don't understand - why would that be a problem? (That you have
> > explictly open and close your da
> Ibatis is quite common - not used it so can't say for sure.
>
> > Spring JDBC though is very nice and have used it extensively.
>
> > Rakesh
>
> > On Sun, Feb 22, 2009 at 2:21 PM, Christian Hvid
> > wrote:
> >> Hi Java people.
>
> >>
; have you looked at Spring JDBC? It has a similar interface and manages
> the connections for you.
>
> I think if you go down a non-orm route and want to have lots of sql,
> Ibatis is quite common - not used it so can't say for sure.
>
> Spring JDBC though is very nice and
Hi Java people.
I have been toying with simplier ways of doing embedded SQL in Java.
And would like your comments on this one?
http://code.google.com/p/chalkmine/
It allows you to write code like this:
openConnection();
try {
int count = queryScalar(Integer.class, "select count(*) from
pe
13 matches
Mail list logo
