You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Brad Gardner <bg...@gmail.com> on 2009/10/01 19:18:08 UTC
Possible portal site manager bug
I'm working with Jetspeed 2 using a custom portal built using the maven
tutorial on the jetspeed 2 site. Everything seems to be functioning
perfectly until I start creating pages for roles. After creating a role
page, navigating to it from a user that gets the page results in a blank
page with the text "Failed to create rendering job". No errors in the log
files are reported, but I was able to find the problem by looking at the
PSML file that is generated. In the generated PSML, I found this line:
<fragment id="P-124110d78e4-10007" type="layout" ></fragment>
I noticed that this did not name a layout to use, so I changed it to read:
<fragment id="P-124110d78e4-10007" type="layout"
name="jetspeed-layouts::VelocityTwoColumns"></fragment>
and the page works.
Has anyone had a similar experience? I'm trying to do a bit more research
before reporting it as a bug, because it could be something I've done.
Right now, I have the same symptoms on a deployed portal on our win2k3
server, and a seperate portal build on my local system.
*Brad Gardner*
Mailto: bgardner87@gmail.com
Re: Possible portal site manager bug
Posted by Randy Watler <wa...@wispertel.net>.
Brad,
Just the overridden beans should work AFAIK.
Randy
Brad Gardner wrote:
> Thanks,
> I was able to pull down the latest code for everything and bump my portal
> up to 2.2.1 and everything looks and works great!
>
> One last question,
>
> For my portal, I need to override a setting in the pipelines.xml file. To
> do this, do I need to put an entire copy of the pipelines.xml file under
> WEB-INF/assembly/override, or a pipelines.xml file that contains just my
> override parameters?
>
> *Brad Gardner*
> Mailto: bgardner87@gmail.com
>
>
>
> On Fri, Oct 2, 2009 at 4:21 AM, Vivek Kumar <vi...@gmail.com> wrote:
>
>
>> Hi
>>
>> There was a bug in portal site manager. I had created jira issue and fixed
>> it (https://issues.apache.org/jira/browse/JS2-1054).
>> Issue is fixed in j2-admin trunk.
>>
>> Vivek
>>
>>
>> David Sean Taylor wrote:
>>
>>
>>> On Oct 1, 2009, at 3:34 PM, Brad Gardner wrote:
>>>
>>> Jetspeed 2.2.0 is the version I am using. Here is what I did:
>>>
>>>> Navigate to "jetspeed administrative portlets"
>>>> Navigate to "Portal Site Manager"
>>>> Click on "_role" folder
>>>> Click on "add subfolder" and entered name="test" title and short title
>>>> both
>>>> = "test page"
>>>> Click on the newly created "test" folder
>>>> Click "add page" and entered name="mypage" title and short title both =
>>>> "my
>>>> page"
>>>>
>>>> If i specify the page name as "test.psml" the resulting page becomes
>>>> "test.psml.psml" so I omitted this in my tests. Creating the file this
>>>> way
>>>> yields the same results as well. Is there somewhere that the default
>>>> layout
>>>> is specified? Maybe I'm missing a default setting.
>>>>
>>>>
>>> Shouldn't matter. We use the jetspeed.properties (or override.properties)
>>> to retrieve the layout.page.default. But if it is not configured, then it
>>> uses VelocityOneColumn as the default:
>>>
>>>
>>> page.getRootFragment().setName(getServiceLocator().getPortalConfiguration().getString("layout.page.default",
>>> "jetspeed-layouts::VelocityOneColumn"));
>>>
>>> Check your override and jetspeed properties and ensure that
>>> layout.page.default is set
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>>> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Possible portal site manager bug
Posted by Brad Gardner <bg...@gmail.com>.
Thanks,
I was able to pull down the latest code for everything and bump my portal
up to 2.2.1 and everything looks and works great!
One last question,
For my portal, I need to override a setting in the pipelines.xml file. To
do this, do I need to put an entire copy of the pipelines.xml file under
WEB-INF/assembly/override, or a pipelines.xml file that contains just my
override parameters?
*Brad Gardner*
Mailto: bgardner87@gmail.com
On Fri, Oct 2, 2009 at 4:21 AM, Vivek Kumar <vi...@gmail.com> wrote:
> Hi
>
> There was a bug in portal site manager. I had created jira issue and fixed
> it (https://issues.apache.org/jira/browse/JS2-1054).
> Issue is fixed in j2-admin trunk.
>
> Vivek
>
>
> David Sean Taylor wrote:
>
>>
>> On Oct 1, 2009, at 3:34 PM, Brad Gardner wrote:
>>
>> Jetspeed 2.2.0 is the version I am using. Here is what I did:
>>>
>>> Navigate to "jetspeed administrative portlets"
>>> Navigate to "Portal Site Manager"
>>> Click on "_role" folder
>>> Click on "add subfolder" and entered name="test" title and short title
>>> both
>>> = "test page"
>>> Click on the newly created "test" folder
>>> Click "add page" and entered name="mypage" title and short title both =
>>> "my
>>> page"
>>>
>>> If i specify the page name as "test.psml" the resulting page becomes
>>> "test.psml.psml" so I omitted this in my tests. Creating the file this
>>> way
>>> yields the same results as well. Is there somewhere that the default
>>> layout
>>> is specified? Maybe I'm missing a default setting.
>>>
>>
>> Shouldn't matter. We use the jetspeed.properties (or override.properties)
>> to retrieve the layout.page.default. But if it is not configured, then it
>> uses VelocityOneColumn as the default:
>>
>>
>> page.getRootFragment().setName(getServiceLocator().getPortalConfiguration().getString("layout.page.default",
>> "jetspeed-layouts::VelocityOneColumn"));
>>
>> Check your override and jetspeed properties and ensure that
>> layout.page.default is set
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
Re: Possible portal site manager bug
Posted by Vivek Kumar <vi...@gmail.com>.
Hi
There was a bug in portal site manager. I had created jira issue and
fixed it (https://issues.apache.org/jira/browse/JS2-1054).
Issue is fixed in j2-admin trunk.
Vivek
David Sean Taylor wrote:
>
> On Oct 1, 2009, at 3:34 PM, Brad Gardner wrote:
>
>> Jetspeed 2.2.0 is the version I am using. Here is what I did:
>>
>> Navigate to "jetspeed administrative portlets"
>> Navigate to "Portal Site Manager"
>> Click on "_role" folder
>> Click on "add subfolder" and entered name="test" title and short
>> title both
>> = "test page"
>> Click on the newly created "test" folder
>> Click "add page" and entered name="mypage" title and short title both
>> = "my
>> page"
>>
>> If i specify the page name as "test.psml" the resulting page becomes
>> "test.psml.psml" so I omitted this in my tests. Creating the file
>> this way
>> yields the same results as well. Is there somewhere that the default
>> layout
>> is specified? Maybe I'm missing a default setting.
>
> Shouldn't matter. We use the jetspeed.properties (or
> override.properties) to retrieve the layout.page.default. But if it is
> not configured, then it uses VelocityOneColumn as the default:
>
>
> page.getRootFragment().setName(getServiceLocator().getPortalConfiguration().getString("layout.page.default",
> "jetspeed-layouts::VelocityOneColumn"));
>
> Check your override and jetspeed properties and ensure that
> layout.page.default is set
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Possible portal site manager bug
Posted by David Sean Taylor <d....@onehippo.com>.
On Oct 1, 2009, at 3:34 PM, Brad Gardner wrote:
> Jetspeed 2.2.0 is the version I am using. Here is what I did:
>
> Navigate to "jetspeed administrative portlets"
> Navigate to "Portal Site Manager"
> Click on "_role" folder
> Click on "add subfolder" and entered name="test" title and short
> title both
> = "test page"
> Click on the newly created "test" folder
> Click "add page" and entered name="mypage" title and short title
> both = "my
> page"
>
> If i specify the page name as "test.psml" the resulting page becomes
> "test.psml.psml" so I omitted this in my tests. Creating the file
> this way
> yields the same results as well. Is there somewhere that the
> default layout
> is specified? Maybe I'm missing a default setting.
Shouldn't matter. We use the jetspeed.properties (or
override.properties) to retrieve the layout.page.default. But if it is
not configured, then it uses VelocityOneColumn as the default:
page
.getRootFragment
().setName
(getServiceLocator
().getPortalConfiguration().getString("layout.page.default", "jetspeed-
layouts::VelocityOneColumn"));
Check your override and jetspeed properties and ensure that
layout.page.default is set
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Possible portal site manager bug
Posted by Brad Gardner <bg...@gmail.com>.
Jetspeed 2.2.0 is the version I am using. Here is what I did:
Navigate to "jetspeed administrative portlets"
Navigate to "Portal Site Manager"
Click on "_role" folder
Click on "add subfolder" and entered name="test" title and short title both
= "test page"
Click on the newly created "test" folder
Click "add page" and entered name="mypage" title and short title both = "my
page"
If i specify the page name as "test.psml" the resulting page becomes
"test.psml.psml" so I omitted this in my tests. Creating the file this way
yields the same results as well. Is there somewhere that the default layout
is specified? Maybe I'm missing a default setting.
*Brad Gardner*
Mailto: bgardner87@gmail.com
On Thu, Oct 1, 2009 at 4:58 PM, David Sean Taylor <d....@onehippo.com>wrote:
>
> On Oct 1, 2009, at 10:18 AM, Brad Gardner wrote:
>
> I'm working with Jetspeed 2 using a custom portal built using the maven
>> tutorial on the jetspeed 2 site. Everything seems to be functioning
>> perfectly until I start creating pages for roles. After creating a role
>> page, navigating to it from a user that gets the page results in a blank
>> page with the text "Failed to create rendering job". No errors in the log
>> files are reported, but I was able to find the problem by looking at the
>> PSML file that is generated. In the generated PSML, I found this line:
>>
>> <fragment id="P-124110d78e4-10007" type="layout" ></fragment>
>>
>> I noticed that this did not name a layout to use, so I changed it to read:
>>
>> <fragment id="P-124110d78e4-10007" type="layout"
>> name="jetspeed-layouts::VelocityTwoColumns"></fragment>
>>
>> and the page works.
>>
>> Has anyone had a similar experience? I'm trying to do a bit more research
>> before reporting it as a bug, because it could be something I've done.
>> Right now, I have the same symptoms on a deployed portal on our win2k3
>> server, and a seperate portal build on my local system.
>>
>>
> How did you create the page for a role? I used the Site Manager and created
> a page named dev1.psml, and it created this:
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <page id="/_role/dev/dev1.psml" hidden="false">
> <title>DevOne</title>
> <short-title>DevOne</short-title>
> <defaults></defaults>
> <fragment id="P-12411e1b12f-10000" type="layout"
> name="jetspeed-layouts::VelocityTwoColumns"></fragment>
> </page>
>
>
> What version?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
Re: Possible portal site manager bug
Posted by David Sean Taylor <d....@onehippo.com>.
On Oct 1, 2009, at 10:18 AM, Brad Gardner wrote:
> I'm working with Jetspeed 2 using a custom portal built using the
> maven
> tutorial on the jetspeed 2 site. Everything seems to be functioning
> perfectly until I start creating pages for roles. After creating a
> role
> page, navigating to it from a user that gets the page results in a
> blank
> page with the text "Failed to create rendering job". No errors in
> the log
> files are reported, but I was able to find the problem by looking at
> the
> PSML file that is generated. In the generated PSML, I found this
> line:
>
> <fragment id="P-124110d78e4-10007" type="layout" ></fragment>
>
> I noticed that this did not name a layout to use, so I changed it to
> read:
>
> <fragment id="P-124110d78e4-10007" type="layout"
> name="jetspeed-layouts::VelocityTwoColumns"></fragment>
>
> and the page works.
>
> Has anyone had a similar experience? I'm trying to do a bit more
> research
> before reporting it as a bug, because it could be something I've done.
> Right now, I have the same symptoms on a deployed portal on our win2k3
> server, and a seperate portal build on my local system.
>
How did you create the page for a role? I used the Site Manager and
created a page named dev1.psml, and it created this:
<?xml version="1.0" encoding="UTF-8"?>
<page id="/_role/dev/dev1.psml" hidden="false">
<title>DevOne</title>
<short-title>DevOne</short-title>
<defaults></defaults>
<fragment id="P-12411e1b12f-10000" type="layout" name="jetspeed-
layouts::VelocityTwoColumns"></fragment>
</page>
What version?
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org