You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Aaron Evans <aa...@gmail.com> on 2008/06/13 03:21:16 UTC
building and deploying jetspeed-layouts
I have a jetspeed 2.1 portal installation with the default layouts
that came with it.
I built it using the maven plugin a while back.
I would like to add another layout. Basically it's another instance
of MultiColumnPortlet only with different init params (i want to use a
custom layout velocity template).
Adding a new portlet to the portlet.xml of the layouts app in place
and restarting tomcat doesn't do the trick. I guess you have to
re-deploy the app to jetspeed so it picks up the new portlet instance?
Anyhow, I am just looking for the quickest and easiest way to make
this happen. Any suggestions welcome...
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: building and deploying jetspeed-layouts
Posted by Aaron Evans <aa...@gmail.com>.
Yeah, you can just make a copy of the existing exploded
jetspeed-layouts app,. modify the portlet.xml, war it back up and drop
it in WEB-INF/deploy.
If you are on 2.1.3, try just modifying the portlet.xml as David suggests.
On Tue, Jun 24, 2008 at 2:08 AM, Serkan Camurcuoglu
<se...@telenity.com> wrote:
> Hi Aaron,
> I also need to deploy a new two column layout portlet with different widths.
> Have you found a better way of doing this? If I want to do it the way you
> told, shall I deploy it as a normal portlet application? (e.g. by copying it
> to webapps/jetspeed/WEB-INF/deploy/ )
>
> Regards,
>
> SerkanC
>
>
> Aaron Evans wrote:
>>
>> Just an update to this:
>>
>> I was able to take a copy of the exploded jetspeed-layouts from my
>> jetspeed implementation, add my changes and then war it up and
>> re-deploy it and that worked.
>>
>> However, I would really like to make this part of my build process and
>> also be able to make changes to the layouts configs and then run some
>> maven command to build and deploy just the jetspeed layouts.
>>
>> However, in my generated portal project (again, I did the binary build
>> using the plugin), I cannot find any trace of the jetspeed-layouts
>> application, so I'm not sure how I would go about doing this.
>>
>> -aaron
>>
>> On Thu, Jun 12, 2008 at 9:21 PM, Aaron Evans <aa...@gmail.com>
>> wrote:
>>
>>>
>>> I have a jetspeed 2.1 portal installation with the default layouts
>>> that came with it.
>>>
>>> I built it using the maven plugin a while back.
>>>
>>> I would like to add another layout. Basically it's another instance
>>> of MultiColumnPortlet only with different init params (i want to use a
>>> custom layout velocity template).
>>>
>>> Adding a new portlet to the portlet.xml of the layouts app in place
>>> and restarting tomcat doesn't do the trick. I guess you have to
>>> re-deploy the app to jetspeed so it picks up the new portlet instance?
>>>
>>> Anyhow, I am just looking for the quickest and easiest way to make
>>> this happen. Any suggestions welcome...
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: building and deploying jetspeed-layouts
Posted by Serkan Camurcuoglu <se...@telenity.com>.
Hi Aaron,
I also need to deploy a new two column layout portlet with different
widths. Have you found a better way of doing this? If I want to do it
the way you told, shall I deploy it as a normal portlet application?
(e.g. by copying it to webapps/jetspeed/WEB-INF/deploy/ )
Regards,
SerkanC
Aaron Evans wrote:
> Just an update to this:
>
> I was able to take a copy of the exploded jetspeed-layouts from my
> jetspeed implementation, add my changes and then war it up and
> re-deploy it and that worked.
>
> However, I would really like to make this part of my build process and
> also be able to make changes to the layouts configs and then run some
> maven command to build and deploy just the jetspeed layouts.
>
> However, in my generated portal project (again, I did the binary build
> using the plugin), I cannot find any trace of the jetspeed-layouts
> application, so I'm not sure how I would go about doing this.
>
> -aaron
>
> On Thu, Jun 12, 2008 at 9:21 PM, Aaron Evans <aa...@gmail.com> wrote:
>
>> I have a jetspeed 2.1 portal installation with the default layouts
>> that came with it.
>>
>> I built it using the maven plugin a while back.
>>
>> I would like to add another layout. Basically it's another instance
>> of MultiColumnPortlet only with different init params (i want to use a
>> custom layout velocity template).
>>
>> Adding a new portlet to the portlet.xml of the layouts app in place
>> and restarting tomcat doesn't do the trick. I guess you have to
>> re-deploy the app to jetspeed so it picks up the new portlet instance?
>>
>> Anyhow, I am just looking for the quickest and easiest way to make
>> this happen. Any suggestions welcome...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: building and deploying jetspeed-layouts
Posted by Aaron Evans <aa...@gmail.com>.
Cool, I will have to check that out!
On Tue, Jun 24, 2008 at 11:27 AM, Serkan Camurcuoglu
<se...@telenity.com> wrote:
> I haven't used maven yet but you can make XSL transformations with Ant for
> XML/DOM manipulation.. I think you could easily add nodes to a portlet.xml
> using a simple XSL stylesheet..
>
>
> Aaron Evans wrote:
>>
>> This would be with my old maven 1 build (still on JS 2.1, haven't had
>> time to upgrade).
>>
>> If in 2.1.3 modifying the existing portlet.xml in place works, that
>> will be fine.
>>
>> The only problem with that is that in order to automate that task as
>> part of our build process, we'll have to take a copy of portlet.xml
>> and apply our change, save that in our SVN repo and use maven or ant
>> to copy it out to the installed jetspeed instance post-install. This
>> is fine except we'll have to remember to re-apply our change for every
>> subsequent jetspeed upgrade.
>>
>> If only ant/maven could handle XML/DOM manipulation. :)
>>
>> One source of confusion for me though was in my generated portal
>> project (maven1 genapp goal), I can find no trace of the
>> jetspeed-layouts app. So I couldn't even modify it before I do the
>> final install.
>>
>> Does the maven build just pull down a copy of the jetspeed layouts war
>> from a maven repository as part of the installation?
>>
>> cheers,
>> aaron
>>
>> On Tue, Jun 24, 2008 at 2:32 AM, David Sean Taylor
>> <da...@bluesunrise.com> wrote:
>>
>>>
>>> On Jun 13, 2008, at 7:42 AM, Aaron Evans wrote:
>>>
>>>
>>>>
>>>> Just an update to this:
>>>>
>>>> I was able to take a copy of the exploded jetspeed-layouts from my
>>>> jetspeed implementation, add my changes and then war it up and
>>>> re-deploy it and that worked.
>>>>
>>>> However, I would really like to make this part of my build process and
>>>> also be able to make changes to the layouts configs and then run some
>>>> maven command to build and deploy just the jetspeed layouts.
>>>>
>>>> However, in my generated portal project (again, I did the binary build
>>>> using the plugin), I cannot find any trace of the jetspeed-layouts
>>>> application, so I'm not sure how I would go about doing this.
>>>>
>>>>
>>>
>>> You should be able to simply update the portlet.xml in the deployed area
>>> and
>>> it will pick it up
>>> At least that works in 2.1.3, just tested it
>>>
>>> As for automating the portlet.xml override in a Maven build, is it a
>>> Maven-1
>>> or Maven-2 build?
>>> Either way, recommend creating a modified jetspeed-layouts.war with your
>>> portlet.xm inside it
>>>
>>> With Maven-1, you can pretty easily write a goal to do that for you
>>> With Maven-2, I was hoping you could put this project into your custom
>>> project under applications
>>> Unfortunately this will not be treated as a local application, we don't
>>> have
>>> a local-application prototype
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: building and deploying jetspeed-layouts
Posted by Serkan Camurcuoglu <se...@telenity.com>.
I haven't used maven yet but you can make XSL transformations with Ant
for XML/DOM manipulation.. I think you could easily add nodes to a
portlet.xml using a simple XSL stylesheet..
Aaron Evans wrote:
> This would be with my old maven 1 build (still on JS 2.1, haven't had
> time to upgrade).
>
> If in 2.1.3 modifying the existing portlet.xml in place works, that
> will be fine.
>
> The only problem with that is that in order to automate that task as
> part of our build process, we'll have to take a copy of portlet.xml
> and apply our change, save that in our SVN repo and use maven or ant
> to copy it out to the installed jetspeed instance post-install. This
> is fine except we'll have to remember to re-apply our change for every
> subsequent jetspeed upgrade.
>
> If only ant/maven could handle XML/DOM manipulation. :)
>
> One source of confusion for me though was in my generated portal
> project (maven1 genapp goal), I can find no trace of the
> jetspeed-layouts app. So I couldn't even modify it before I do the
> final install.
>
> Does the maven build just pull down a copy of the jetspeed layouts war
> from a maven repository as part of the installation?
>
> cheers,
> aaron
>
> On Tue, Jun 24, 2008 at 2:32 AM, David Sean Taylor
> <da...@bluesunrise.com> wrote:
>
>> On Jun 13, 2008, at 7:42 AM, Aaron Evans wrote:
>>
>>
>>> Just an update to this:
>>>
>>> I was able to take a copy of the exploded jetspeed-layouts from my
>>> jetspeed implementation, add my changes and then war it up and
>>> re-deploy it and that worked.
>>>
>>> However, I would really like to make this part of my build process and
>>> also be able to make changes to the layouts configs and then run some
>>> maven command to build and deploy just the jetspeed layouts.
>>>
>>> However, in my generated portal project (again, I did the binary build
>>> using the plugin), I cannot find any trace of the jetspeed-layouts
>>> application, so I'm not sure how I would go about doing this.
>>>
>>>
>> You should be able to simply update the portlet.xml in the deployed area and
>> it will pick it up
>> At least that works in 2.1.3, just tested it
>>
>> As for automating the portlet.xml override in a Maven build, is it a Maven-1
>> or Maven-2 build?
>> Either way, recommend creating a modified jetspeed-layouts.war with your
>> portlet.xm inside it
>>
>> With Maven-1, you can pretty easily write a goal to do that for you
>> With Maven-2, I was hoping you could put this project into your custom
>> project under applications
>> Unfortunately this will not be treated as a local application, we don't have
>> a local-application prototype
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: building and deploying jetspeed-layouts
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Jun 24, 2008, at 7:47 AM, Aaron Evans wrote:
> This would be with my old maven 1 build (still on JS 2.1, haven't had
> time to upgrade).
>
> If in 2.1.3 modifying the existing portlet.xml in place works, that
> will be fine.
>
> The only problem with that is that in order to automate that task as
> part of our build process, we'll have to take a copy of portlet.xml
> and apply our change, save that in our SVN repo and use maven or ant
> to copy it out to the installed jetspeed instance post-install. This
> is fine except we'll have to remember to re-apply our change for every
> subsequent jetspeed upgrade.
>
> If only ant/maven could handle XML/DOM manipulation. :)
>
> One source of confusion for me though was in my generated portal
> project (maven1 genapp goal), I can find no trace of the
> jetspeed-layouts app. So I couldn't even modify it before I do the
> final install.
>
> Does the maven build just pull down a copy of the jetspeed layouts war
> from a maven repository as part of the installation?
>
yes, it will pull it out of your local repository first
the goals j2:pam.layoutdeploy is available to you:
<goal name="j2:pam.layoutdeploy">
<j:set var="maven.war.final.name" value="jetspeed-layouts"/>
<attainGoal name="j2:localdeploy"/>
</goal>
as is a more generic:
<goal name="j2:localdeploy">
<j:set var="j2.war.groupId" value="${plugin.groupId}"/>
<j:set var="j2.war.version" value="${jetspeed.version}"/>
<j:set var="isLocalWarDeploy" value="true"/>
<attainGoal name="j2:warDeploy"/>
</goal>
so you could write your own goal in your custom maven.xml:
<goal name="custom-localdeploy">
<j:set var="maven.war.final.name" value="jetspeed-layouts"/>
<j:set var="j2.war.groupId" value="${plugin.groupId}"/>
<j:set var="j2.war.version" value="${jetspeed.version}"/>
<j:set var="isLocalWarDeploy" value="true"/>
<attainGoal name="j2:warDeploy"/>
</goal>
Im looking at the j2:warDeploy goal, it does some useful tasks, like
infusing the jetspeed container
however it requires properties to be set
<!-- warDeploy allows you to deploy arbitrary wars to the portal
deploy folder,
optionally downloading it from remote repositories if not
available yet
Required properties to set:
- maven.war.final.name
- j2.war.groupId
- j2.war.version
-->
<goal name="j2:warDeploy">
You may want to just take the j2:warDeploy goal, copy it into your
custom maven.xml, and modify it for your needs
Re: building and deploying jetspeed-layouts
Posted by Aaron Evans <aa...@gmail.com>.
This would be with my old maven 1 build (still on JS 2.1, haven't had
time to upgrade).
If in 2.1.3 modifying the existing portlet.xml in place works, that
will be fine.
The only problem with that is that in order to automate that task as
part of our build process, we'll have to take a copy of portlet.xml
and apply our change, save that in our SVN repo and use maven or ant
to copy it out to the installed jetspeed instance post-install. This
is fine except we'll have to remember to re-apply our change for every
subsequent jetspeed upgrade.
If only ant/maven could handle XML/DOM manipulation. :)
One source of confusion for me though was in my generated portal
project (maven1 genapp goal), I can find no trace of the
jetspeed-layouts app. So I couldn't even modify it before I do the
final install.
Does the maven build just pull down a copy of the jetspeed layouts war
from a maven repository as part of the installation?
cheers,
aaron
On Tue, Jun 24, 2008 at 2:32 AM, David Sean Taylor
<da...@bluesunrise.com> wrote:
>
> On Jun 13, 2008, at 7:42 AM, Aaron Evans wrote:
>
>> Just an update to this:
>>
>> I was able to take a copy of the exploded jetspeed-layouts from my
>> jetspeed implementation, add my changes and then war it up and
>> re-deploy it and that worked.
>>
>> However, I would really like to make this part of my build process and
>> also be able to make changes to the layouts configs and then run some
>> maven command to build and deploy just the jetspeed layouts.
>>
>> However, in my generated portal project (again, I did the binary build
>> using the plugin), I cannot find any trace of the jetspeed-layouts
>> application, so I'm not sure how I would go about doing this.
>>
>
> You should be able to simply update the portlet.xml in the deployed area and
> it will pick it up
> At least that works in 2.1.3, just tested it
>
> As for automating the portlet.xml override in a Maven build, is it a Maven-1
> or Maven-2 build?
> Either way, recommend creating a modified jetspeed-layouts.war with your
> portlet.xm inside it
>
> With Maven-1, you can pretty easily write a goal to do that for you
> With Maven-2, I was hoping you could put this project into your custom
> project under applications
> Unfortunately this will not be treated as a local application, we don't have
> a local-application prototype
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
AW: Accessing rundata-/session objects in popup on jetspeed 1.x
Posted by David Psiuk <ap...@salesfactory.org>.
Hello all,
problem solved, thanks
-----Ursprüngliche Nachricht-----
Von: David Psiuk [mailto:apache@salesfactory.org]
Gesendet: Mittwoch, 25. Juni 2008 10:58
An: 'Jetspeed Users List'
Betreff: Accessing rundata-/session objects in popup on jetspeed 1.x
Hello,
I have a portlet with some thumbnails within. Once a user clicks one of the
thumbnails, I want a small popup to be opened and display additional
informations without all the jetspeed decorators like navigational items and
so on.
Someone can help me with this issue?
Thank you and best regards
David
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Accessing rundata-/session objects in popup on jetspeed 1.x
Posted by David Psiuk <ap...@salesfactory.org>.
Hello,
I have a portlet with some thumbnails within. Once a user clicks one of the
thumbnails, I want a small popup to be opened and display additional
informations without all the jetspeed decorators like navigational items and
so on.
Someone can help me with this issue?
Thank you and best regards
David
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: building and deploying jetspeed-layouts
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Jun 13, 2008, at 7:42 AM, Aaron Evans wrote:
> Just an update to this:
>
> I was able to take a copy of the exploded jetspeed-layouts from my
> jetspeed implementation, add my changes and then war it up and
> re-deploy it and that worked.
>
> However, I would really like to make this part of my build process and
> also be able to make changes to the layouts configs and then run some
> maven command to build and deploy just the jetspeed layouts.
>
> However, in my generated portal project (again, I did the binary build
> using the plugin), I cannot find any trace of the jetspeed-layouts
> application, so I'm not sure how I would go about doing this.
>
You should be able to simply update the portlet.xml in the deployed
area and it will pick it up
At least that works in 2.1.3, just tested it
As for automating the portlet.xml override in a Maven build, is it a
Maven-1 or Maven-2 build?
Either way, recommend creating a modified jetspeed-layouts.war with
your portlet.xm inside it
With Maven-1, you can pretty easily write a goal to do that for you
With Maven-2, I was hoping you could put this project into your custom
project under applications
Unfortunately this will not be treated as a local application, we
don't have a local-application prototype
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: building and deploying jetspeed-layouts
Posted by Aaron Evans <aa...@gmail.com>.
Just an update to this:
I was able to take a copy of the exploded jetspeed-layouts from my
jetspeed implementation, add my changes and then war it up and
re-deploy it and that worked.
However, I would really like to make this part of my build process and
also be able to make changes to the layouts configs and then run some
maven command to build and deploy just the jetspeed layouts.
However, in my generated portal project (again, I did the binary build
using the plugin), I cannot find any trace of the jetspeed-layouts
application, so I'm not sure how I would go about doing this.
-aaron
On Thu, Jun 12, 2008 at 9:21 PM, Aaron Evans <aa...@gmail.com> wrote:
> I have a jetspeed 2.1 portal installation with the default layouts
> that came with it.
>
> I built it using the maven plugin a while back.
>
> I would like to add another layout. Basically it's another instance
> of MultiColumnPortlet only with different init params (i want to use a
> custom layout velocity template).
>
> Adding a new portlet to the portlet.xml of the layouts app in place
> and restarting tomcat doesn't do the trick. I guess you have to
> re-deploy the app to jetspeed so it picks up the new portlet instance?
>
> Anyhow, I am just looking for the quickest and easiest way to make
> this happen. Any suggestions welcome...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org