No, it doesn't. And it also supports JPA annotations, so you don't need
any XML at all.
Peter
On 14/07/10 22:44, Kevin Wright wrote:
hang on... does hibernate continue to read XML files after it's loaded?
If so, then that would *definitely be a bottleneck!
On 14 July 2010 13:25, jitesh dundas <jbdun...@gmail.com
<mailto:jbdun...@gmail.com>> wrote:
I am not sure if Hibernate would responsible for the slow motion..
There are many possibilities including database issues,bad
coding,ui issues.
Still, are we concluding that hibernate will give slower results
compared to other components? I would caution against that
generalisation..
In any case,xml parsing is slow so maybe one of the issues here
against hibernate...
Regards,
jd
On 7/14/10, Carl Jokl <carl.j...@gmail.com
<mailto:carl.j...@gmail.com>> wrote:
> I certainly noticed the software was slower than I though it
should be
> particularly for checking stock. I don't know if hibernate was to
> blame for that. There were some types of searches which were too
slow
> and would lock up the software for ages if not enough search
criteria
> were provided. I also thought it was a bit silly calling the
software
> Eclipse given that the name is already used for something else.
>
> The data used for the software used a local cached database for
> performance and redundancy which would synch periodically with the
> central database. I would have thought queries for an on site
database
> should have been pretty fast. The fact that a cached database
was used
> meant that checks of stock levels at other outlets could end up
being
> stale and not guaranteed to be up to date. For this reason if an
> outlet showed only one of an item in stock it was best not to trust
> that they actually had.
>
> I just worked there as a Christmas job in my final year of
University.
> It was the best paid student job I did.
>
> --
> You received this message because you are subscribed to the
Google Groups
> "The Java Posse" group.
> To post to this group, send email to javaposse@googlegroups.com
<mailto:javaposse@googlegroups.com>.
> To unsubscribe from this group, send email to
> javaposse+unsubscr...@googlegroups.com
<mailto:javaposse%2bunsubscr...@googlegroups.com>.
> For more options, visit this group at
> http://groups.google.com/group/javaposse?hl=en.
>
>
--
You received this message because you are subscribed to the Google
Groups "The Java Posse" group.
To post to this group, send email to javaposse@googlegroups.com
<mailto:javaposse@googlegroups.com>.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.com
<mailto:javaposse%2bunsubscr...@googlegroups.com>.
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
--
Kevin Wright
mail/google talk: kev.lee.wri...@gmail.com
<mailto:kev.lee.wri...@gmail.com>
wave: kev.lee.wri...@googlewave.com <mailto:kev.lee.wri...@googlewave.com>
skype: kev.lee.wright
twitter: @thecoda
--
You received this message because you are subscribed to the Google
Groups "The Java Posse" group.
To post to this group, send email to javapo...@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to javapo...@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
