Hi,
I think there are only a few using it, but with customizations at the portlet
bridge. Last time I made it running with WebSphere Portal Server 8 I also had
to apply some changes but finally got it working for me.
I made it the way that I implemented a simple App with an Ajax Example / a
I asked this question a couple of years ago and at the time it appeared that
portlet support wasn't much of a priority. I thought I would ask again
since I am about to start a project that could really benefit from using
JetSpeed or Liferay. I see that there is a portlet project in Wicket
gt; On Tue, Jul 8, 2014 at 1:11 PM, Martin Grigorov <
> > > mgrigo...@apache.org
> > > >> >
> > > >> > > wrote:
> > > >> > >
> > > >> > > > What about 6.11.0 ?
> > > >> > > >
> &
> >> > > >
> > >> > > > Martin Grigorov
> > >> > > > Wicket Training and Consulting
> > >> > > > https://twitter.com/mtgrigorov
> > >> > > >
> > >> > > >
> > >> &
t; >
> >> > > > Martin Grigorov
> >> > > > Wicket Training and Consulting
> >> > > > https://twitter.com/mtgrigorov
> >> > > >
> >> > > >
> >> > > > On Tue, Jul 8, 2014 at 12:55 PM, Ciocoiu Elvis
> > >
>> > > >> Seems that in 6.10.0 to 6.12.0 the url for my AjaxLink is ok
>> > > >>
>> > > >>
>> > > >>
>> > >
>> >
>> http://localhost:8080/web/guest/welcome?p_p_id=test_WAR_wicket
/issues.apache.org/jira/browse/WICKET-5521
It should be easy for you to workaround it:
call org.apache.wicket.Page#setWasCreatedBookmarkable(false) for Portlet
pages ?!
But as I said I don't know well Portlet stuff and I cannot suggest a proper
fix.
>
> Thank you.
>
>
> On Tue
uyvej&p_p_lifecycle=2&p_p_state=normal&p_p_mode=view&p_p_resource_id=/test/%3F0-1.IBehaviorListener.0-refreshTimeLink&p_p_cacheability=cacheLevelPage&p_p_col_id=column-1&p_p_col_count=1&_=1404812714838
> > > >>
> > > >> Starting fro
k&p_p_cacheability=cacheLevelPage&p_p_col_id=column-1&p_p_col_count=1&_=1404812714838
> > >>
> > >> Starting from 6.13.0 the url is
> > >>
> > >>
> > >>
> >
> http://localhost:8080/web/guest/?0-1.IBehaviorListener.
714838
> >>
> >> Starting from 6.13.0 the url is
> >>
> >>
> >>
> http://localhost:8080/web/guest/?0-1.IBehaviorListener.0-refreshTimeLink&_=1404812884161
> >>
> >> Any idea what change broke the wicket-portlet?
> >>
> &
38
>>
>> Starting from 6.13.0 the url is
>>
>>
>> http://localhost:8080/web/guest/?0-1.IBehaviorListener.0-refreshTimeLink&_=1404812884161
>>
>> Any idea what change broke the wicket-portlet?
>>
>> Thank you.
>>
>>
>>
>> On Tue
url is
>
>
> http://localhost:8080/web/guest/?0-1.IBehaviorListener.0-refreshTimeLink&_=1404812884161
>
> Any idea what change broke the wicket-portlet?
>
> Thank you.
>
>
>
> On Tue, Jul 8, 2014 at 10:55 AM, Ciocoiu Elvis >
> wrote:
>
> > I'
amp;p_p_cacheability=cacheLevelPage&p_p_col_id=column-1&p_p_col_count=1&_=1404812714838
Starting from 6.13.0 the url is
http://localhost:8080/web/guest/?0-1.IBehaviorListener.0-refreshTimeLink&_=1404812884161
Any idea what change broke the wicket-portlet?
Thank you.
On Tue, Jul 8, 20
#x27;ll post my
conclusions later.
Thank you.
On Tue, Jul 8, 2014 at 10:00 AM, Martin Grigorov
wrote:
> Hi,
>
> Portlets is grey area for me...
> When the problem started appearing ? With Wicket 6.16 or earlier ?
> There are no changes in wicketstuff-portlet since a while so I gu
Hi,
Portlets is grey area for me...
When the problem started appearing ? With Wicket 6.16 or earlier ?
There are no changes in wicketstuff-portlet since a while so I guess it is
a change in Wicket that may broke it.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
Hi,
I'm facing a problem with wicketstuff-portlet-6.16 in Liferay 6.2. I'm
using AjaxLink in a portlet and WicketAjax call failure with: Error while
parsing response: Invalid XML. I know there were some problems (starting
with wicket 1.5.9) but this problems were solved usin
Hello,
I'm trying to get a Wicket 6 app running as a Portlet in JBoss GateIn 3.6
using the wicketstuff-portlet lib (
https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/portlet-parent
).
So far I have managed to get the Wicket quickstart app running, i.e. I can
display simple t
I forgot to mention that the Wicket version is 1.4.22.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/DatePicker-doesn-t-work-in-the-WSRP-portlet-tp4659006p4659007.html
Sent from the Users forum mailing list archive at Nabble.com
Hi all,
I'm developing WicketPortlet which will be used via WSRP. I'm using GateIn
3.5 as a producer and a consumer.
DatePicker works fine when I use portlet straight from the producer portal,
but when I try to use it via WSRP something goes wrong. It try to load
foll
uff-core/master.
Regards,
Marek
On 11/28/2012 04:18 PM, Martin Grigorov wrote:
On Wed, Nov 28, 2012 at 4:10 PM, Thijs wrote:
Hi Colin,
How much I hate to tell you, but your mostly on your own.
We are currently on Wicket 1.4 for our portlets and also planning an
upgrade to Wicket 6. But portlet sup
On Wed, Nov 28, 2012 at 4:10 PM, Thijs wrote:
> Hi Colin,
>
> How much I hate to tell you, but your mostly on your own.
> We are currently on Wicket 1.4 for our portlets and also planning an
> upgrade to Wicket 6. But portlet support is at your own risk as non of the
>
Hi Colin,
How much I hate to tell you, but your mostly on your own.
We are currently on Wicket 1.4 for our portlets and also planning an
upgrade to Wicket 6. But portlet support is at your own risk as non of
the core committers is comfortable with portlets so it's no longer a
core fe
I solve it. The problem was the portlet-name must be equal with the string
used by the wicket filter. Thank you.
On Sat, Oct 6, 2012 at 1:25 AM, elvis.ciocoiu wrote:
> Hello,
>
> I'm stuck building a portlet using wicketstuff-portlet-1.5.8 and deploying
> it to liferay 6.1.1. M
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Portlet-ServetWebRequest-WICKET-4387-fix-Introduced-a-bug-tp4651153p4651159.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscri
On Sun, Aug 12, 2012 at 7:10 PM, pasto wrote:
> I think, that this has been fixed in wicket-portlet version 1.5.7.2, which
> can be downloaded from https://issues.apache.org/jira/browse/WICKET-4019
> (which seems to be currently down for maintenance). I checked github, but
> there is
I think, that this has been fixed in wicket-portlet version 1.5.7.2, which
can be downloaded from https://issues.apache.org/jira/browse/WICKET-4019
(which seems to be currently down for maintenance). I checked github, but
there is also an old version, maybe because wicketstuff 1.5.8 has not been
Hi,
You may need to introduce PortletWebRequest that borrows code from
ServletWebRequest.
Setup it with WebApplication#newWebRequest()
On Sun, Aug 12, 2012 at 4:44 PM, Doug Leeper wrote:
> Troubleshooting my issue where my portlet won't work upon a page refresh, I
> came acr
Troubleshooting my issue where my portlet won't work upon a page refresh, I
came across this in ServletWebRequest.
if (forwardAttributes != null || errorAttributes != null)
{
if (LOG.isDebugEn
aving troubles making wicket-portlet works with liferay
6.1, here's the solution...
I've many wicket 1.4 application that are just working fine in liferay 6.0.
But when I put them in liferay 6.1, I get the following message :
/20:49:12,379 ERROR [BasePortalLifecycle:45]
java.lang.IllegalAr
For those who are having troubles making wicket-portlet works with liferay
6.1, here's the solution...
I've many wicket 1.4 application that are just working fine in liferay 6.0.
But when I put them in liferay 6.1, I get the following message :
/20:49:12,379 ERROR [BasePortalLi
Hello,
I have very, very little experience with portlet (and to be honest I am not
very keen in getting more ;) ).
And I have to surprise you - because I share your opinion about portlets
sand portals. But I noticed lately that corporations like to say that whey
offer "portal for their cl
So is there any?
--
Best regards / Med venlig hilsen
Nino Martinez
Hi,
Yes. We removed it for 1.5.0 since none of us knows the technology.
There is a patch at https://issues.apache.org/jira/browse/WICKET-4019
which is also available at
https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/portlet-parent
On Sat, May 5, 2012 at 5:14 AM, gmparker2000
Has support for portlets been completely dropped from wicket? I was
interested to see if I could get a simple portlet running in Liferay
- Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Portlet-Support-tp4610364.html
Sent from the Users forum mailing list
Hi Portlet users,
At https://issues.apache.org/jira/browse/WICKET-4019 you can find an
attachment provided by Peter Pastrnak that brings back the support of
Portlets for Wicket 1.5.
If you would like to have this feature in your 1.5 applications now is
the time to test it and give feedback
Thanks.
I hope the functionality will remain available somewhere. May be as a
separate library.
Josh.
On Mon, Mar 21, 2011 at 10:52 AM, Wilhelmsen Tor Iver wrote:
> > Does wicket support development of portlets ? I cant find much
> information
> > by googling.
>
> Wicket 1.4 does (and it works
> Does wicket support development of portlets ? I cant find much information
> by googling.
Wicket 1.4 does (and it works fine at least in our context of using Liferay as
container), apparently in 1.5 they are moving that functionality out from the
main library.
- Tor Iver
---
Team;
Does wicket support development of portlets ? I cant find much information
by googling.
Josh
Here i am trying to build a small application,
I Have 3 pages View, Edit and Add for my portlet
initially i am at View Mode, when i go to the Edit mode from the view mode
it displays the Edit Page.
On Edit page i have Link, clicking on the link should forward to Add Page
and it never happens
> We are running Glassfish 3.0.1 + Liferay 5.2.3 and have some portlets
> using Wicket 1.4.9 (in deployment mode). These work fine on the
> platform when running on our local Windows developer PCs, but when
> deployed onto a Solaris server running the same software, forms stop
> working.
Turns out
Portlet
I am trying to deploy a Wicket application as a portlet in Liferay 5.2.3
bundled with Tomcat 6.0. I found this which has been very helpful:
http://mail-archives.apache.org/mod_mbox/wicket-users/201001.mbox/browse
r
<http://mail-archives.apache.org/mod_mbox/wicket-users/201001.mbox/br
I am trying to deploy a Wicket application as a portlet in Liferay 5.2.3
bundled with Tomcat 6.0. I found this which has been very helpful:
http://mail-archives.apache.org/mod_mbox/wicket-users/201001.mbox/browse
r
<http://mail-archives.apache.org/mod_mbox/wicket-users/201001.mbox/brows
We are running Glassfish 3.0.1 + Liferay 5.2.3 and have some portlets using
Wicket 1.4.9 (in deployment mode). These work fine on the platform when running
on our local Windows developer PCs, but when deployed onto a Solaris server
running the same software, forms stop working. Debugging indicat
Hi all,
Using Wicket 1.4.2 at the moment and have played around with Portal
functionality (displaying Wicket inside a Portlet) . However, my client now
has a requirement to embed a portlet inside the current Wicket application.
So, example being... Wicket Page containing several Panels... one
resource.onResourceRequested();
}
onClick();
}
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Error-Message-from-ResourceLink-within-a-portlet-tp2335133p2335177.html
Sent from the Wicket -
> Thanks Igor for your response. I thought I had read that wicket 1.4.x
> was JSR
> 286 complaint but not sure how that is possible since JSR 286 does call
> out
> inter-portlet communications. Did i mis-read the documentation.
One of our developers had to subclass WicketPor
patches and
tests then I'll be happy to support them.
On Wed, Aug 11, 2010 at 10:26 AM, Wilhelmsen Tor Iver wrote:
> > currently 1.5 has no support for portlets
>
> Well the portlet-related classes from 1.4 seem to still be there in
> trun
> currently 1.5 has no support for portlets
Well the portlet-related classes from 1.4 seem to still be there in trunk...?
- Tor Iver
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-m
not sure. i dont work with portlets so have no idea.
-igor
On Tue, Aug 10, 2010 at 1:07 PM, dgh1 wrote:
>
> Thanks Igor for your response. I thought I had read that wicket 1.4.x was JSR
> 286 complaint but not sure how that is possible since JSR 286 does call out
> inter-portlet co
Thanks Igor for your response. I thought I had read that wicket 1.4.x was JSR
286 complaint but not sure how that is possible since JSR 286 does call out
inter-portlet communications. Did i mis-read the documentation.
Thanks again for your response
--
View this message in context:
http
currently 1.5 has no support for portlets. and it probably wont until
someone from the core team starts using portlets on the daily basis.
-igor
On Tue, Aug 10, 2010 at 7:28 AM, dgh1 wrote:
>
>
> I read in the PortletsInAction manning book that for wicket that
> inter-portlet co
I think I read something in brix framework about this. I think is already
offered.
On Tue, Aug 10, 2010 at 11:28 AM, dgh1 wrote:
>
>
> I read in the PortletsInAction manning book that for wicket that
> inter-portlet communications is not in 1.4.x but will be in 1.5. Can
>
I read in the PortletsInAction manning book that for wicket that
inter-portlet communications is not in 1.4.x but will be in 1.5. Can
somebody please verify that the jsr 286 nter-portlet communications will be
in 1.5 and if not when might it be.
Thanks
--
View this message in context:
http
> We are trying to create parametrized portlet URLs to a maximized
> "stand-alone" portlet, and run into an issue where the constructor to
> the Page is invoked twice. But the second time, the query parameters
> are gone. Why does it create the view page twice? Or is it Life
We are trying to create parametrized portlet URLs to a maximized "stand-alone"
portlet, and run into an issue where the constructor to the Page is invoked
twice. But the second time, the query parameters are gone. Why does it create
the view page twice? Or is it Liferay "magic&
For Servlet 2.4/2.5 I have found (depending on container) that you need to add
the dispatchers involved, like so:
>
> wicket.report
> /report/*
REQUEST
INCLUDE
FORWARD
ERROR
>
- Tor Iver
--
t; Thank you Tor:
> >>>>>>
> >>>>>> Here's what I have. this is copied from the web.xml from the wicket
> >>>>>> maven project :
> >>>>>>
> >>>>>> http://java.sun.com/xml/ns/j2ee";
t;>
>>>>> On Mon, Jan 4, 2010 at 12:27 AM, Mansour Al Akeel
>>>>> wrote:
>>>>>> Thank you Tor:
>>>>>>
>>>>>> Here's what I have. this is copied from the web.xml from the wicket
>>>>>> maven project :
>>>>>>
>>>>>> http://java.sun.com/xml/
;>> http://java.sun.com/xml/ns/j2ee";
> >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> >>>>xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> >>>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";
> >>>>ve
www.w3.org/2001/XMLSchema-instance";
>>>>xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>>>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";
>>>>version="2.4">
>>>>Reports
>>>>
>>>> wicket.report
>>>>
t;>> version="2.4">
>>> Reports
>>>
>>> wicket.report
>>>
>>> org.apache.wicket.protocol.http.WicketFilter
>>>
>>> applicationClassName
>>>
>>applicationClassName
>>
>> com.example.automotive.Application
>>
>>
>> detectPortletContext
>>true
>>
applicationClassName
>
> com.example.automotive.Application
>
>
> detectPortletContext
> true
>
>
>
> wicket.report
> /report/*
>
com.example.automotive.Application
detectPortletContext
true
wicket.report
/report/*
Here's my portlet.xml :
http://java.sun.com/xml/ns/portlet/portlet-app
> What I find unclear, is the way it functions. It extends a wicker
> portlet, but the application is ran from WebApplication instance that
> mounts EditPage, HeaderPage, and doesn't seem to have any direct link
> to the WicketPortlet.
The link is via the filter mapping and page
I am trying to understand portlets using wicket. I read on multiple
resources, that wicket supports JSR 286 in a transparent way. However,
I can not see any reference to a simple portlet application to adopt
as the basis for my project and build on top of it.
I have checked out the examples from
going on.
**
Martin
2009/11/27 Goran Novak :
> I'm using wicket 1.4.1 for developing portlets on liferay 5.2.5 jboss
> 4.2.3.
> In my portlet on a page I have three DataView-es each with its own page
> navigation.
> I overrided PagingNavigation, PagingNavigator,
I'm using wicket 1.4.1 for developing portlets on liferay 5.2.5 jboss
4.2.3.
In my portlet on a page I have three DataView-es each with its own page
navigation.
I overrided PagingNavigation, PagingNavigator, PagingNavigationLink and
PagingNavigationIncrementLink to be able to give p
Hi all,
I have a Wicket portlet running in uPortal, and normal things like labels
and images work, but for anything that submits data, ie a Link or Button, it
throws a ClassCastException:
org.apache.pluto.internal.impl.ActionResponseImpl cannot be cast to
javax.portlet.RenderResponse
It may be
I've got a simple Wicket based portlet working in uPortal 3.1.1 now.
However, my implementation of ServletContextProvider is just a stub so have
a feeling it's going to eventually explode again. I'm really interested in
seeing a working implementation of ServletContextProvider if
ges/
I used to find once a ServletContextProvider implementation here.
And regarding Wicket 1.4, I think that it only supports portlet 2.0,
althought I can't remember where I heard that. But Wicket 1.4 support for
portlet is indeed far more advanced than in 1.3 (it doesn't need
Thanks Pierre.
Ok so a basic uPortal portlet doesn't need anything in web.xml. When you
deploy, as part of the spec it must be run through the Pluto Assembly which
writes the necessary config (also available as a Maven plugin which is what I
use). So you can just leave it empty and then
eXo is currently portlet 2.0 so I know nothing regarding portlet 1.0 Wicket
integration. You'll find working portlets for eXo in the standard eXo
distribution. Just copy their filters & listeners into your own
Wicket-portlet.
What I mean regarding this copy: depending upon your por
Yep I've seen that page. uPortal is Portlet 1.0 based (Pluto).
Do you mean add the same filters/listeners as a Wicket based application would
normally use to the normal uPortal descriptors? Because a uPortal portlet can
have an empty web.xml (it gets re-written by the Pluto assembly)
eXo, so I can't
help without knowing the specificities of uPortal.
Are you using portlet 1.0 or 2.0?
HTH,
Pierre
On Tue, Nov 24, 2009 at 6:16 AM, Steve Swinsburg
wrote:
> Hi all,
>
> I'm trying to get a portlet happening for uPortal 3.1.1 which is based on
> the Por
Hi all,
I'm trying to get a portlet happening for uPortal 3.1.1 which is based on
the Portlet API 1.0 spec (Pluto). Does anyone have any sample code they can
point me at?
thanks,
Steve
OSS-Tomcat-4.2.3
JDK 1.5.0_09
Liferay 5.2.3
This [1] is what I get when portlet is deployed, and bellow that [2] when I
click on
DropDownChoice and onSelectionChanged method is activated.
Thanks,
Goran
1.>>>>>>>>
09:50:33,088 INFO [STDOUT] 09:50:33,088 INFO [Portl
Hi again!
I'm really lost on this toppic. It seems to not work.
First of all. Can someone post a complete configuration of a wicket
portlet + spring, please?
I found several ways to do it but none seems to be correct.
Thank you.
El mar, 18-08-2009 a las 09:53 +0200, nino martinez
Hi again!
I'm really lost on this toppic. It seems to not work.
First of all. Can someone post a complete configuration of a wicket
portlet + spring, please?
I found several ways to do it but none seems to be correct.
Thank you.
El mar, 18-08-2009 a las 09:53 +0200, nino martinez
I renamed the plugin from server-utest-portlet to serverUtest-portlet to
remove any other '-' characters. Still the issue is present.
By the way, is it a Wicket limitation that the Liferay portlet plugin names
should not contain '-' characters other than the one in the
The '-' is a reserved character in the name of a liferay portlet
a portlets name should end with -portlet and not contain any other '-'
On 19-8-2009 9:32, glr wrote:
Having investigated the issue further, I noticed that the same code is
working in some portlets and doe
e());
>
> But that's up to you :)
>
> Rob
>
> On 8/14/09 1:50 AM, Gonzalo Aguilar Delgado wrote:
> > Hi all!
> >
> > I managed to do it with wicket 1.4. This is how:
> >
> > Define it in portlet.xml
> >
> >
> > ...
> &g
Having investigated the issue further, I noticed that the same code is
working in some portlets and does not work in others. Therefore I created 2
portlets with exactly the same content except for the plugin name and the
portlet-name:
* in the first case the plugin name is wexample-portlet and
entered the first time. Having debugged
the portlet, I found that the callback URL generated for the buttons
"onclick" handler contains some parameters, which takesthe form of
.
Specifically the callback url contains also
_wexample_WAR_wexampleportlet_requiredBorder:myText=qq
you willl never use hibernate on /myapp/ but always put
in /myapp/pages/dynamic/* for pages that use db lookup..
>
> Thank you very much for your answers...
>
>
>
>>
>> 2009/8/17 Gonzalo Aguilar Delgado :
>> > Ok. Maybe I don't understand...
>> >
aybe I don't understand...
> >
> > Let me show the situation. I have Spring + portlet + hibernate config
> > with transactions working with the current configuration:
> >
> > I have my DAO objects under package
> > com.level2crm.
17 Gonzalo Aguilar Delgado :
> Ok. Maybe I don't understand...
>
> Let me show the situation. I have Spring + portlet + hibernate config
> with transactions working with the current configuration:
>
> I have my DAO objects under package
> com.level2crm.hibernate.ente
Ok. Maybe I don't understand...
Let me show the situation. I have Spring + portlet + hibernate config
with transactions working with the current configuration:
I have my DAO objects under package
com.level2crm.hibernate.enterprise.dao.contact
And model under com.level2crm.model
I configure
n view or more preferred
>> AFAIK detachable models.
>>
>> 2009/8/14 Russell Simpkins :
>> >
>> > Errors like those are caused when the hibernate session is closed too soon.
>> > https://www.hibernate.org/43.html
>> > Russ
>> >
>
; > Errors like those are caused when the hibernate session is closed too soon.
> > https://www.hibernate.org/43.html
> > Russ
> >
> >> Subject: Re: CORRECT portlet+spring+hibernate configuration (Two options,
> >> what's right?)
> >> From: g...@
Yup so you should either use open session in view or more preferred
AFAIK detachable models.
2009/8/14 Russell Simpkins :
>
> Errors like those are caused when the hibernate session is closed too soon.
> https://www.hibernate.org/43.html
> Russ
>
>> Subject: Re: CORRECT por
Errors like those are caused when the hibernate session is closed too soon.
https://www.hibernate.org/43.html
Russ
> Subject: Re: CORRECT portlet+spring+hibernate configuration (Two options,
> what's right?)
> From: g...@aguilardelgado.com
> To: users@wicket.apache.org
> Da
>
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; version="2.4"
> xsi:schemaLocation="http://java.sun.com
--
web.xml
-
http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; version="2.4"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-a
ou :)
Rob
On 8/14/09 1:50 AM, Gonzalo Aguilar Delgado wrote:
Hi all!
I managed to do it with wicket 1.4. This is how:
Define it in portlet.xml
...
crmportal:userId
http://www.level2crm.com/params";>x:userId
Every portlet that will use it must also
Hi all!
I managed to do it with wicket 1.4. This is how:
Define it in portlet.xml
...
crmportal:userId
http://www.level2crm.com/params";>x:userId
Every portlet that will use it must also be configured with:
...
crmportal:userId
After doing this the portlet m
El jue, 13-08-2009 a las 14:46 +0200, Wilhelmsen Tor Iver escribió:
> > But it will be the portlet class the responsible for handling
> > processing. So the only way to pass information from the onClick
> > function to the
> > portlet application for rendering (for examp
Hi Rob,
I want to do it because my application is composed of several portlets.
If you click on one customer, for ex. you will want
other portlets to show information relative to the customer you have
just clicked.
This is why you will need shared-parameters. That is inside portlet 2.0
spec
Could you maybe explain why you need it? Do you want to pass data inside
your portlet or to another portlet?
Rob
On 8/13/09 1:43 PM, Gonzalo Aguilar Delgado wrote:
Hi all!,
I have some questions about parameter passing in portal environment. I
saw that WebPage class can have access to the
> But it will be the portlet class the responsible for handling
> processing. So the only way to pass information from the onClick
> function to the
> portlet application for rendering (for example) is using the portlet
> session.
But why would you want to go via the A
1 - 100 of 231 matches
Mail list logo
