Discussion:
Cocoon 2.2 - XSP - ESQL - Pool
kompromiss
2013-03-12 08:56:45 UTC
Permalink
Hello, I have strange problem in Cocoon 2.2, with block cocoon-xsp.

There is rather old application, which was written in Cocoon 2.1 with XSP.
I'm trying to migrate this application from C 2.1 to C 2.2
XSP-pages working fine, except for ESQL-component. The thing is I cannot use
esql:pool to use datasource from datasources configuration
(META-INF/cocoon/spring/datasources.xml)

If I specify parameters esql:driver, esql:dburl, esql:username,
esql:password with correct values - everything works. But when I'm trying to
use esql:pool - application just hangs. No errors in logs, nothing.

I was trying to investigate this problem on my own - by putting this code
into XSP-page:

String res = "";
try {
ServiceSelector selector = (ServiceSelector)
manager.lookup(org.apache.avalon.excalibur.datasource.DataSourceComponent.ROLE
+ "Selector");
DataSourceComponent datasource = (DataSourceComponent)
selector.select("web24");
if (datasource == null)
res = Boolean.toString(selector.isSelectable("web24"));
}
catch(Exception e)
{
System.out.println("error: " + e.getMessage());
res = res + " error" + e.getMessage();
}

And I've found out that the datasource component is null - selector selects
nothing. At this point I'm completely stuck. Obviously, I can specify
datasource (through esql:driver, esql:dburl, esql:username, esql:password)
in every XSP-page, but it's not exactly right, I think.

Is cocoon-xsp incompatible with spring beans or I just don't understand
something?



--
View this message in context: http://cocoon.10839.n7.nabble.com/Cocoon-2-2-XSP-ESQL-Pool-tp57831.html
Sent from the Cocoon - Dev mailing list archive at Nabble.com.

Loading...