Hi,
I think if your using ECS to build a large table in memory, thats your
problem. I dont know for sure, but I read an article before about using
HTML packages that since you generally create NEW objects for each tag, if
you do a large number of tags, you'll run out of memory. If your looping
through a set of tags and for a large table, I would bet that all those
objects being created is the reason your running out. We got away from ECS
and now use JSP and JavaBeans and our site has improved in speed and the
memory usage is way down. ECS is great if you want to use an html library
in your code, but separating the HTML out of the code is the only way to go
in my opinion. Its far easier to maintain and make changes. The reason we
got away from it..well there are many, but because web sites often need
changes, it was kind of a pain in the kazoo when we needed some big changes
on existing forms and had to do it in code. With JSP, I can make all the
changes right on the page and upload it to the site immediately. The JSP is
compiled into a servlet on the next hit, and voila! Using ECS and other
HTML packages in code generally mean you have to restart your server or the
servlet engine, which cant be done while you have live transactions going on.
For whats its worth, while ECS is great for its purpose, I would opt to
moving away from HTML in the code and use JSP, JavaBeans and your core code
for the database access, or use JavaBeans directly to hit the database.
Kevin Duffey
Software Engineer
[EMAIL PROTECTED]
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
