Hi Michele,
Hmm... you're really making you life more difficult than you need to with this approach. Out of curiosity, why do you have an non-service builder implementation?
Having said that, one idea that comes to mind might be to use a struts action hook. You can create this hook such that a particular URL will invoke your action, and provided you don't make it part of the auth.public.paths accessing the url will require credentials. You can pass credentials as part of accessing this URL of course (I've done this before using curl for example). You hook then could access your JAR that contains the service that you use with your external JDBC implementation. You portlet would, I assume, access the same jar. It does mean, if you haven't already, splitting out the classes that do the actual JDBC work into a separate library (something SB does for you automatically).
That might be something to try -- though I am always curious to know why people opt out of SB, so please share if you have time
Hmm... you're really making you life more difficult than you need to with this approach. Out of curiosity, why do you have an non-service builder implementation?
Having said that, one idea that comes to mind might be to use a struts action hook. You can create this hook such that a particular URL will invoke your action, and provided you don't make it part of the auth.public.paths accessing the url will require credentials. You can pass credentials as part of accessing this URL of course (I've done this before using curl for example). You hook then could access your JAR that contains the service that you use with your external JDBC implementation. You portlet would, I assume, access the same jar. It does mean, if you haven't already, splitting out the classes that do the actual JDBC work into a separate library (something SB does for you automatically).
That might be something to try -- though I am always curious to know why people opt out of SB, so please share if you have time
Andrew Jardine:
Hi Michele,
Hmm... you're really making you life more difficult than you need to with this approach. Out of curiosity, why do you have an non-service builder implementation?
:-) Only because it was a old portlet. The "backend" of the portlet is a mantis outside, then does not use the service of Liferay to access the data (because they are on another D
but jdbc standard.