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 Shah Amit <am...@hotmail.com> on 2005/04/12 15:58:18 UTC
User Prefernces
Hi all,
How do I add user Preferences directly in the database? I know that we can
add it from the administrative portlets, but it is not feasible for me
because I have an existing system with hudreds of users, and I cannot
manually do that.
I tried to enter records into PREFS_PROPERTY_KEY, and PREFS_PROPERTY_VALUE,
and I used the node of /usr/admin/userinfo from the PREFS_NODE table when
inserting in the PREFS_PROPERTY_VALUE table. Then I tried to login as
admin/admin, but I only see user.name.given and user.name.family. I tried to
change the values of tasteDudely to "somethingElse" and that something else
does show up on the webpage. So it reads the DB, but doesn't show up the
preference that I wrote in the DB. I think I am missing something else, but
not sure what ...
Thanks,
Amit
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2 PAM Problem
Posted by jo...@hawkinsweb.co.uk.
Sorted, I changed
<portlet-app id="CedAr" version="1.0">
to
<portlet-app id="cedar" version="1.0">
and it worked.
> I have the following portlet.xml
>
> <?xml version="1.0" encoding="UTF-8"?>
> <portlet-app id="CedAr" version="1.0">
> <portlet id="CedAr">
> <portlet-name>CedAr</portlet-name>
> <display-name>CedAr</display-name>
> <portlet-class>cedar.CedAr</portlet-class>
> <expiration-cache>0</expiration-cache>
> <supports>
> <mime-type>text/html</mime-type>
> <portlet-mode>EDIT</portlet-mode>
> <portlet-mode>VIEW</portlet-mode>
> <portlet-mode>HELP</portlet-mode>
> </supports>
> <supported-locale>en</supported-locale>
> <portlet-info>
> <title>CedAr</title>
> <short-title>CedAr</short-title>
> <keywords>CedAr</keywords>
> </portlet-info>
> <portlet-preferences>
> <preference>
> <name>displaytext</name>
> <value>Hello, from your preferences</value>
> </preference>
> </portlet-preferences>
> </portlet>
> <portlet id="CedArIFrame">
> <portlet-name>CedArIFrame</portlet-name>
> <display-name>CedArIFrame</display-name>
> <portlet-class>cedar.CedArIFrame</portlet-class>
> <expiration-cache>0</expiration-cache>
> <init-param>
> <description>View Source</description>
> <name>viewSource</name>
> <value>http://bflow-2/efinancials/cedarblue.htm</value>
> </init-param>
> <supports>
> <mime-type>text/html</mime-type>
> <portlet-mode>EDIT</portlet-mode>
> <portlet-mode>VIEW</portlet-mode>
> <portlet-mode>HELP</portlet-mode>
> </supports>
> <supported-locale>en</supported-locale>
> <portlet-info>
> <title>CedAr IFrame</title>
> <short-title>CedArIFrame</short-title>
> <keywords>CedAr</keywords>
> </portlet-info>
> <portlet-preferences>
> <preference>
> <name>SRC</name>
> <value>http://bflow-2/efinancials/cedarblue.htm</value>
> </preference>
> <preference>
> <name>HEIGHT</name>
> <value>100%</value>
> </preference>
> <preference>
> <name>WIDTH</name>
> <value>100%</value>
> </preference>
> <preference>
> <name>MAX-HEIGHT</name>
> <value>800</value>
> </preference>
> <preference>
> <name>MAX-WIDTH</name>
> <value>100%</value>
> </preference>
> </portlet-preferences>
> </portlet>
> </portlet-app>
>
> and web.xml
>
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
> Application 2.3//EN"
> "http://java.sun.com/dtd/web-app_2_3.dtd">
>
> <web-app>
> <display-name>CedAr</display-name>
> <description>CedAr Portlet</description>
> <servlet>
> <servlet-name>CedAr</servlet-name>
> <display-name>CedAr Servlet</display-name>
> <description>Servlet for CedAr</description>
> <servlet-class>cedar.CedAr</servlet-class>
> <load-on-startup>0</load-on-startup>
> </servlet>
> <servlet>
> <servlet-name>CedArIFrame</servlet-name>
> <display-name>CedAr IFrame Servlet</display-name>
> <description>Servlet for CedAr IFrame</description>
> <servlet-class>cedar.CedArIFrame</servlet-class>
> <load-on-startup>1</load-on-startup>
> </servlet>
> <security-role>
> <role-name>user</role-name>
> </security-role>
> </web-app>
>
>
> The portlets deploy ok and I can see them having added them to
> default-page.psml.
>
> However, when I go into the PAM portlet I can see them listed, but if I
> click on them I do not get the portlet detail show up in the right hand
> side.
>
> Any Ideas ??
>
> Thanks
>
> Jon Hawkins
>
>
>
> ---------------------------------------------------------------------
> 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
J2 PAM Problem
Posted by jo...@hawkinsweb.co.uk.
I have the following portlet.xml
<?xml version="1.0" encoding="UTF-8"?>
<portlet-app id="CedAr" version="1.0">
<portlet id="CedAr">
<portlet-name>CedAr</portlet-name>
<display-name>CedAr</display-name>
<portlet-class>cedar.CedAr</portlet-class>
<expiration-cache>0</expiration-cache>
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>EDIT</portlet-mode>
<portlet-mode>VIEW</portlet-mode>
<portlet-mode>HELP</portlet-mode>
</supports>
<supported-locale>en</supported-locale>
<portlet-info>
<title>CedAr</title>
<short-title>CedAr</short-title>
<keywords>CedAr</keywords>
</portlet-info>
<portlet-preferences>
<preference>
<name>displaytext</name>
<value>Hello, from your preferences</value>
</preference>
</portlet-preferences>
</portlet>
<portlet id="CedArIFrame">
<portlet-name>CedArIFrame</portlet-name>
<display-name>CedArIFrame</display-name>
<portlet-class>cedar.CedArIFrame</portlet-class>
<expiration-cache>0</expiration-cache>
<init-param>
<description>View Source</description>
<name>viewSource</name>
<value>http://bflow-2/efinancials/cedarblue.htm</value>
</init-param>
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>EDIT</portlet-mode>
<portlet-mode>VIEW</portlet-mode>
<portlet-mode>HELP</portlet-mode>
</supports>
<supported-locale>en</supported-locale>
<portlet-info>
<title>CedAr IFrame</title>
<short-title>CedArIFrame</short-title>
<keywords>CedAr</keywords>
</portlet-info>
<portlet-preferences>
<preference>
<name>SRC</name>
<value>http://bflow-2/efinancials/cedarblue.htm</value>
</preference>
<preference>
<name>HEIGHT</name>
<value>100%</value>
</preference>
<preference>
<name>WIDTH</name>
<value>100%</value>
</preference>
<preference>
<name>MAX-HEIGHT</name>
<value>800</value>
</preference>
<preference>
<name>MAX-WIDTH</name>
<value>100%</value>
</preference>
</portlet-preferences>
</portlet>
</portlet-app>
and web.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<display-name>CedAr</display-name>
<description>CedAr Portlet</description>
<servlet>
<servlet-name>CedAr</servlet-name>
<display-name>CedAr Servlet</display-name>
<description>Servlet for CedAr</description>
<servlet-class>cedar.CedAr</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet>
<servlet-name>CedArIFrame</servlet-name>
<display-name>CedAr IFrame Servlet</display-name>
<description>Servlet for CedAr IFrame</description>
<servlet-class>cedar.CedArIFrame</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<security-role>
<role-name>user</role-name>
</security-role>
</web-app>
The portlets deploy ok and I can see them having added them to
default-page.psml.
However, when I go into the PAM portlet I can see them listed, but if I
click on them I do not get the portlet detail show up in the right hand side.
Any Ideas ??
Thanks
Jon Hawkins
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: AW: Struts-Bridge TL: "form" tag renders always ActionURLs
Posted by Th...@nepatec.de.
hi !
you are right !
my mistake.
the form tag will generate only actionURL's.
perhaps u can modify the method
getFormTagRenderFormStartElement
in this you get the actionURL as String.
now u can call the getURL MEthod in the same class with context, actionurl
and null
instead of StrutsPortletURL.createActionURL(...).
in the getURL he looks für the struts-portlet-config.xml configuration...
perhaps...
thomas
> hi !
>
> you could use the struts-portlet-config.xml
>
> like this
> <?xml version="1.0" encoding="UTF-8"?>
> <config>
> <portlet-url-type default="action">
> <action path="/login"/>
> <render path="/start"/>
> </portlet-url-type>
> </config>
This is not a bad idea, but I don't think it works. I did a test to be
completely sure and it failed. A review of the source code of the <form>
tag
(class FormTag.java --> TagsSupport.java -->
getFormTagRenderFormStartElement()) showed, that it will always create an
ActionURL.
The 'struts-portlet-config.xml' is probably only of use when rendering
URLs
with 'html:link'.
Thank you for your reply,
Sven.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
AW: Struts-Bridge TL: "form" tag renders always ActionURLs
Posted by Sven Thiergen <s....@itcampus.de>.
> hi !
>
> you could use the struts-portlet-config.xml
>
> like this
> <?xml version="1.0" encoding="UTF-8"?>
> <config>
> <portlet-url-type default="action">
> <action path="/login"/>
> <render path="/start"/>
> </portlet-url-type>
> </config>
This is not a bad idea, but I don't think it works. I did a test to be
completely sure and it failed. A review of the source code of the <form> tag
(class FormTag.java --> TagsSupport.java -->
getFormTagRenderFormStartElement()) showed, that it will always create an
ActionURL.
The 'struts-portlet-config.xml' is probably only of use when rendering URLs
with 'html:link'.
Thank you for your reply,
Sven.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Struts-Bridge TL: "form" tag renders always ActionURLs
Posted by Th...@nepatec.de.
hi !
you could use the struts-portlet-config.xml
like this
<?xml version="1.0" encoding="UTF-8"?>
<config>
<portlet-url-type default="action">
<action path="/login"/>
<render path="/start"/>
</portlet-url-type>
</config>
path="/start"/; startis a struts-action.
if you have a html:form tag where the login-action is used, the bridge
find the configuration
in the struts-portlet-config.xml and generate a renderURL. ( <render
path="/start"/>)
thomas
Hi,
right now if I use the <form> tag of the Struts-Bridge TagLibrary it
always
renders ActionURLs, never RenderURLs. Is there an option about this at
all;
e.g. I know that Forms - when they get submit - usually send content: So
it
has to be an ActionURL.
But maybe I want to use a form that simple points to a RenderURL; would I
have to use the <link> tag instead, or can we discuss about adding an
attribute to the <form> tag, that explicitely states to create a RenderURL
(like the way it is available for the <link> tag)?
Thank you,
Sven.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Struts-Bridge TL: "form" tag renders always ActionURLs
Posted by Sven Thiergen <s....@itcampus.de>.
Hi,
right now if I use the <form> tag of the Struts-Bridge TagLibrary it always
renders ActionURLs, never RenderURLs. Is there an option about this at all;
e.g. I know that Forms - when they get submit - usually send content: So it
has to be an ActionURL.
But maybe I want to use a form that simple points to a RenderURL; would I
have to use the <link> tag instead, or can we discuss about adding an
attribute to the <form> tag, that explicitely states to create a RenderURL
(like the way it is available for the <link> tag)?
Thank you,
Sven.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Serving different content than HTML
Posted by David Sean Taylor <da...@bluesunrise.com>.
Geoff Hollingworth wrote:
> thank you. brilliant news. I have a package that i pass the
> httpservlet request object in and it fetches the device capability using
> uaprof profiles and returns an object with the device cabilities.
> If i was to integrate this into jetspeed2 where in the source code
> should i look to put it.
Do you mean W3C's CC/PP?
That would be very nice indeed!
You should review the Capabilities component and either:
a) enhance it
b) write a second spring component with your implementation
> The package is open source called DELI. I would extend it some. See
> here: http://sourceforge.net/projects/delicon/
> Open to suggestions
> thanks
> geoff
>
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Serving different content than HTML
Posted by Geoff Hollingworth <eu...@hotmail.com>.
thank you. brilliant news. I have a package that i pass the httpservlet
request object in and it fetches the device capability using uaprof profiles
and returns an object with the device cabilities.
If i was to integrate this into jetspeed2 where in the source code should i
look to put it.
The package is open source called DELI. I would extend it some. See here:
http://sourceforge.net/projects/delicon/
Open to suggestions
thanks
geoff
>From: David Sean Taylor <da...@bluesunrise.com>
>Reply-To: "Jetspeed Users List" <je...@portals.apache.org>
>To: Jetspeed Users List <je...@portals.apache.org>
>Subject: Re: Serving different content than HTML
>Date: Wed, 27 Apr 2005 11:32:17 -0700
>
>Geoff Hollingworth wrote:
>>Hi
>>I asked this question before but did not get an answer so I will ask again
>>in the hope that somebody can help me.
>>I was using Jetspeed-1 which supported detecting the browser type and
>>returning different content types - either HTML if it detected a
>>IE/Mozilla or WML if it is a microbrowser.
>>
>>I need to have this support as I migrate to Jetspeed2,
>>Can anyone tell me if this is supported/implemented in Jetspeed2?
>>If it is not then can anyone give me any pointers on what would we the
>>best way to add the support? I will then implement it.
>>
>>My basic needs are to understand if I need to return WML or HTML and if
>>WML, I would like to have access to the UAPROF so I can work out
>>dimensions of screens and different content support.
>>
>It works just like in Jetspeed-1.
>All the capability mappings for agents -> media types are basically the
>same, although its much more configurable with Jetspeed-2.
>
>Simply place your PSML pages for WML under the user's directory such as
>
>_user/geoff/_mediatype/wml
>
>And make sure you are using the default profiling rule and it will locate
>it. Its actually much more flexible in that we can locate on any profiling
>criteria. For example Im locating specific PSML by user agent (client
>device), as Mac IE 5 has been a real problem with CSS 2.0 for me.
>
>So I made a subdir called "_user.agent", which is the profiling critirion
>name minus the underscore.
>
>This will become much easier to work with once the Site Manager portlet is
>in place
>
>--
>David Sean Taylor
>Bluesunrise Software
>david@bluesunrise.com
>[office] +01 707 773-4646
>[mobile] +01 707 529 9194
>
>---------------------------------------------------------------------
>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: Serving different content than HTML
Posted by David Sean Taylor <da...@bluesunrise.com>.
Geoff Hollingworth wrote:
> Hi
> I asked this question before but did not get an answer so I will ask
> again in the hope that somebody can help me.
> I was using Jetspeed-1 which supported detecting the browser type and
> returning different content types - either HTML if it detected a
> IE/Mozilla or WML if it is a microbrowser.
>
> I need to have this support as I migrate to Jetspeed2,
> Can anyone tell me if this is supported/implemented in Jetspeed2?
> If it is not then can anyone give me any pointers on what would we the
> best way to add the support? I will then implement it.
>
> My basic needs are to understand if I need to return WML or HTML and if
> WML, I would like to have access to the UAPROF so I can work out
> dimensions of screens and different content support.
>
It works just like in Jetspeed-1.
All the capability mappings for agents -> media types are basically the
same, although its much more configurable with Jetspeed-2.
Simply place your PSML pages for WML under the user's directory such as
_user/geoff/_mediatype/wml
And make sure you are using the default profiling rule and it will
locate it. Its actually much more flexible in that we can locate on any
profiling criteria. For example Im locating specific PSML by user agent
(client device), as Mac IE 5 has been a real problem with CSS 2.0 for me.
So I made a subdir called "_user.agent", which is the profiling
critirion name minus the underscore.
This will become much easier to work with once the Site Manager portlet
is in place
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Serving different content than HTML
Posted by Geoff Hollingworth <eu...@hotmail.com>.
Hi
I asked this question before but did not get an answer so I will ask again
in the hope that somebody can help me.
I was using Jetspeed-1 which supported detecting the browser type and
returning different content types - either HTML if it detected a IE/Mozilla
or WML if it is a microbrowser.
I need to have this support as I migrate to Jetspeed2,
Can anyone tell me if this is supported/implemented in Jetspeed2?
If it is not then can anyone give me any pointers on what would we the best
way to add the support? I will then implement it.
My basic needs are to understand if I need to return WML or HTML and if WML,
I would like to have access to the UAPROF so I can work out dimensions of
screens and different content support.
thanks
/geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org