Re: [Opaltoolkit-users] Hibernate database connection

[Sriram K. <sr...@sd...>]

Hello Anthony,

Thanks for your comments. Responses inline -

> -First, I've found a bug in my "typed WSDL addon": on a freshly  
> installed opal2 with the addon, you cannot deploy any service. So I  
> attach a patched file to put in OpalSOAPRequestFilter package.  
> Briefly, the problem was that the file WEB-INF/server-config.wsdd  
> (which is used by the filter) doesn't exists when no service is  
> deployed.

Thanks. I will take a look at this once we are done with Opal release  
2.1. A release candidate should be available soon, and we are hoping  
for a 2.1 release before the end of the month.


> -I see you've included c3p0 and mysql connector packages (which is  
> great!), but their are not the latest versions available (0.9.1.1  
> instead of 0.9.1.2 for c3p0 and 5.1.0 instead of 5.1.8 for mysql). I  
> have no particular problem with these older versions but I was  
> wondering if there was a reason for that...

No particular reason. I had c3p0 version 0.9.1.1 and mysql version  
5.1.0 working for another project - so decided to use that. However, I  
upgraded to the latest versions in SVN like you suggested, and  
everything still works fine.

> -Speaking about c3p0, I've seen you haven't included the  
> "c3p0.preferredTestQuery=SELECT 1;" property. Is this intended? It  
> can be defined in $OPAL_SOURCES/etc/hibernate-opal.cfg.xml using  
> "<property name="c3p0.preferredTestQuery">SELECT 1;</property>".  
> Looking at the doc, it seems like it makes testing database  
> availability faster.

This was an oversight on my part. It is now checked into SVN, and the  
performance does seem to be slightly better on initial testing.

> -There's also a new bug in svn: our servers are not running on the  
> 8080 port, so the dashboard has some problems with it (maybe you are  
> aware of it?). From what I have seen, there's at least one hard- 
> coded 8080 port in webapps/opal2/dashboard-jsp/serviceList.jsp on  
> line 51 (there may be the same bug in other files). Making this  
> configurable would be quite useful!

I fixed this in SVN. Now the serviceList.jsp uses the OPAL_URL  
parameter in the web.xml. I will add some documentation on how to  
configure this in the very near future.

> Apart from that, Opal2 is running smoothly and the new application  
> list is great!

>
> You told me you could give me commit access to svn: if you're still  
> ok with that, do I need to create a sourceforge account?

Yes, please. Send me an email with your SourceForge account, and I can  
give you access. We should also talk about protocols, practices, etc  
for committing code.

Cheers,
Sriram