Hi Frank,
Thanks for your reply. This sounds quite complicated to me. There must
be an easier way. The Jetspeed Admin application uses quite some
PortalServices. I suspect that the following steps will be required
(please comment):
1.) Define the API of the service in a separate project and put it into
maven repo (for compiplation) and the tomcat/shared/lib (similar to the
jetspeed-api). Thus I can refernce the Service in every application this
api will be included.
2.) Define my service in the portlat.genapp portal container using the
'normal' spring config approach.
Question:
How can I add a component to the PortalServices (normally defined in
jetspeed-services.xml) without copy and modify the jetspeed-services.xml
from the jetspeed distribution.
3.) Define the service in the jetspeed-portlet.xml of the application.
4.) Reference the service like this:
service = (MyService)context.getAttribute(<name of service component>);
Do I have any errors in reasoning?
Thanks for any comment.
Joachim
Frank Villarreal wrote:
> Hi Joachim,
>
> I'm not sure about J2-Final, but in the previous releases, the only way I
> was able to accomplish this was by creating a Tomcat-specific-Resource (see
> the Tomcat docs on how to do this) ... which consisted of a class that
> "looked up" my Spring application context. I in turn created a Jetspeed
> service (that referenced the resource) normally and made the appropriate
> entries in the J2 assembly files. A major problem I ran into was where to
> place my spring-application files ... due to class loader issues (Tomcat
> 5.30), I had to place my jars in {TOMCAT_HOME}/common/lib instead of the
> "recommended" location of "shared/lib" ... which did not work as advertised.
> This was the only way I could share a spring-context across all of my
> portlet applications. I'm hoping to devise a better solution with a newer
> version of Tomcat and J2-Final.
>
> - Frank
>
>> -----Original Message-----
>> From: Joachim Müller [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, January 31, 2006 06:01 AM
>> To: Jetspeed Users List
>> Subject: extending jetspeed with new services
>>
>>
>> Hi all.
>>
>> I want to extend the jetspeed portal with new spring configured
>> services, similar the JetspeedPortletServices.
>>
>> Using a portal.genapp.miminal codebase and several portal applications
>> that deploy into this portal container:
>>
>> How can I define new services that are known to the portal applications
>> via the standard way of accessing the services
>>
>> service = (MyService)context.getAttribute(<name of service component>);
>>
>> without changing the jetspeed codebase (i.e. jetspeed-api)? Is there a
>> easy way that the developers already have had in mind?
>>
>> (Defining the services in the portal container is not the problem, but
>> how can I access them in the portal applications?)
>>
>>
>> Thanks for any reply.
>>
>>
>> Joachim
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
. frankfurt am main, 1°c, die gefühlte temperatur
liegt bei -3°c. zur zeit durchbrochene bewölkung in
366 m. die sichtweite reicht 8.0 km.
< joachim müller
[EMAIL PROTECTED]
t +49 69 759003 11
wemove digital solutions GmbH
www.wemove.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
