Robert Van Overmeiren wrote:
What's the big deal with embedded SQL?
Mixing languages is always bad, particularly when you have to do string
concatenation to build your query. Also, you have to recompile in order
to realize changes in your SQL.
Does it expose security vulnerabilities for the dbase?
Depending upon how parameters are handled and how exception handling is
treated, it could expose vulnerabilities.
Why is there an SQL taglib then?
I don't know. A lot of people do a lot of dumb things. See EJB.
I used to play around with 'persistence' by working with cached rowsets
(CRS) and ObjectDB (JDOQL).
Isn't Hibernate like a middle layer Object-Relational Bridge?
Kinda, but it goes well beyond that allowing you to navigate complex
object relationships and pull back queries that take inheritance,
polymorphism, and encapsulation into account. It also keeps you focused
upon your business and domain logic without worrying about the
underlying persistence semantics.
I wasn't able to get that to work, and their support wasn't any help.
Maybe things are better now.
Things are much better now. But still, I prefer iBATIS. Definitely
give it a look. Better yet, combine iBATIS (or Hibernate) with Spring
--> www.thespringframework.org
-KG
Keep SQL as far away from your Java code as possible and keep it even
farther away from your JSPs. There are several good frameworks, in
particular I recommend:
- Hibernate -- www.hibernate.org
- iBATIS -- www.ibatis.com
My personal favorite is iBATIS, but both are excellent frameworks for
handling database activity without sacrificing your OO integrity. :)
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
