Hi Eric
for what purposes do you use the shipped derby-db internally? Only for
Statistics and Registry?
Yes
What if your users change the
webapp\WEB-INF\classes\conf\wso2esb.hibernate.cfg.xml to use an
Oracle-DB, because they don't want to use and start a derby db?
This is possible
Since your integration of the WSO2 Registry the derby db will not only
be used for the registry meta data but also for all the registry
content, right?
Yes
If I remeber correctly this can't be changed to Oracle right now. Is
this correct?
As I am aware not right out of the box.. yet.. but I maybe wrong.. but
you can run with Oracle as long as you create the schema..
If a users don't uses the new WSO2 Registry but the old file-based
approach, will the derby-db be used for other purposes?
Nope
While looking at the code in class ServiceBusManger it seems as if the
derby server will always be started.
Yes..
If the database won't be used for other purposes would it be possible
to don't start it at all.
Yes, I can make this enhancement to switch it off..
Otherwise it's only a waste of resources, blocks a port and is confusing.
asankha
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
