Re: Portlet support status

2015-08-07 Thread Tobias Soloschenko
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 
normal Form Submit Example and changed the bridge to get those examples working 
within the portlet container.

If you encounter problems we may help you.

kind regards

Tobias

 Am 05.08.2015 um 03:28 schrieb gmparker2000 greg.par...@brovada.com:
 
 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 stuff
 source.  Just wondering if   this is actively being used by the community? 
 Is there any documentation or sample portlets available?
 
 thanks
 
 --
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/Portlet-support-status-tp4671745.html
 Sent from the Users forum mailing list archive at Nabble.com.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Portlet support status

2015-08-04 Thread gmparker2000
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 stuff
source.  Just wondering if   this is actively being used by the community? 
Is there any documentation or sample portlets available?

thanks

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Portlet-support-status-tp4671745.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



portlet support in 1.5 1.6?

2012-06-04 Thread nino martinez wael
So is there any?

-- 
Best regards / Med venlig hilsen
Nino Martinez


Re: portlet support in 1.5 1.6?

2012-06-04 Thread Michal Margiel
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 clients and goes into Liferay or something like
that.
It  would be just nice to use wicket in in, but it is not required  - I
agree that maintaining/developing it might  cost more than it is worth.

2012/6/4 Martin Grigorov mgrigo...@apache.org

 Michal,

 Do you have experience with Portlets ?
 Can you explain me what it is good for ? What pure Servlet cannot do
 and Portlet can do or at least can do much simpler ?
 I guess you will say that a Portal can consume Porlets from many
 providers. But I can do the same with plain Servlet, and I personally
 don't know many providers of Portlet services.
 I've looked once or twice at it and I found just limitations.
 The specs always lag 2-3 years after Servlet/JSF specs releases...
 There are some bridges which fill some gaps with the other
 technologies ...

 On Mon, Jun 4, 2012 at 8:01 PM, Michal Margiel michal.marg...@gmail.com
 wrote:
  Hello,
  I know at least 2 projects that really wanted to use Wicket but had to
 drop
  it because of lack of official support for Portals (both of them runs
 on
  Liferay).
  Maybe it would be good to rethink this decision ?
 
  2012/6/4 Dan Retzlaff dretzl...@gmail.com
 
  Nino, this came up last month:
  http://bit.ly/M5Zc2j
 
 http://mail-archives.apache.org/mod_mbox/wicket-users/201205.mbox/%3CCAMomwMoDASEG22Hnb4tWOruZkhfykSRBXS3X3WKDMJFxw+9=z...@mail.gmail.com%3E
  
 
  On Mon, Jun 4, 2012 at 9:07 AM, nino martinez wael 
  nino.martinez.w...@gmail.com wrote:
 
   So is there any?
  
   --
   Best regards / Med venlig hilsen
   Nino Martinez
  
 
 
 
 
  --
  Pozdrawiam/Best regards
  Michał Margiel
 
  http://www.confitura.pl (dawniej Javarsovia)
  http://www.linkedin.com/in/MichalMargiel
  http://www.margiel.eu



 --
 Martin Grigorov
 jWeekend
 Training, Consulting, Development
 http://jWeekend.com

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Pozdrawiam/Best regards
Michał Margiel

http://www.confitura.pl (dawniej Javarsovia)
http://www.linkedin.com/in/MichalMargiel
http://www.margiel.eu


Re: Portlet Support

2012-05-06 Thread Martin Grigorov
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 greg.par...@brovada.com wrote:
 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 archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Portlet Support

2012-05-04 Thread 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 archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Patch for Portlet support in Wicket 1.5

2011-09-15 Thread Martin Grigorov
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.

Before merging it back in Wicket distro (as wicket-portlet submodule?)
I prefer to re-incubate it as WicketStuff project for a while.
It would be nice if the code is tested with more Portlet containers
and if some kind of integration tests can be added.

If you need any kind of support just contact us at d...@wicket.apache.org.

-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Portlet support

2008-10-31 Thread Janne Kario
Hi.

I've been browsing through the portlet stuff in trunk and don't really
know what to make of it. What can I expect from the upcoming 1.4-m4 in
terms of portlet support? The current portlet stuff in trunk is
stricly JSR-168 stuff, right? The JSR-286 stuff exists only as a patch
set, right? No support for other portlet containers than jetspeed2,
right?

j

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Portlet Support

2007-09-24 Thread Dipu Seminlal
Hi Ate,

Today i got some time to look at the wicket portlet demo (
jetspeed-2.1.3-dev-wicket-demo-installer.jar ), it looks very promising,
thanks very much for the great work.

I would like to see the portlet support integrated to the current trunk as
soon as possible.

Many thanks to the wicket team for the great work.

Cheers
Dipu



On 8/30/07, Ate Douma [EMAIL PROTECTED] wrote:

 Martijn Dashorst wrote:
  I think it is in a branch in our apache repo:
 
 
 http://svn.apache.org/repos/asf/wicket/branches/wicket-1.3-portlet-support/
 Yes, and there is a corresponding JIRA issue with several subtasks which I
 use for tracking the current state (and some minimal documentation):

   https://issues.apache.org/jira/browse/WICKET-647

 If you are interested in testing that out, I've provided a downloadable
 Jetspeed-2 installer which the wicket-examples application deployed as
 portlet
 application here:

http://people.apache.org/~ate/wicket/

 Note though the above branch was created on July 14 from the trunk at that
 time (r547242), and the portlet-support (as currently checked in) isn't
 perfect or
 without some serious bugs yet.

 But, I've started working on a updated version of the portlet-support this
 week which is based on the latest 1.3.0-beta3 release and it is
 progressing rather well.
 I hope to commit this update tomorrow or else early next week the latest.
 For that, I plan to create a new branch,
 wicket-1.3.0-beta3-portlet-support, as merging back in all the trunk
 changes since the branch (reliably) turned out to
 be far too much work.

 So, I started from scratch again, applying my original changes by hand,
 bit by bit (man, being on a branch of a project which moves as quickly as
 Wicket is
 painful...).
 Which turned out to be not a bad idea after all: I cleaned up and improved
 several changes along the lines as well as refactored several new classes
 and methods
 names to better reflect their purpose. Luckily, as the new portlet-support
 (in contrast to the one from 1.2.x) is now using transparent bridging
 wicket to the
 portlet environment, those internal changes didn't have any effect on the
 usage.

 Anyway, you will all soon see that the portlet-support has progressed
 nicely, to the point I think it covers many to most standard use-cases
 (albeit there still
 are and always will be a few area's where portlet support is difficult or
 even formally impossible to provide).

 The nicest part I think is that it turned out to require very little
 changes to the wicket core, and AFAIK all of those are transparent, meaning
 these changes
 have zero effect for existing plain servlet based applications!

 In my opinion, it should be ready for trunk integration soon now (after
 proper review of course), we just need to find and agree upon the right time
 frame.

 Right now I'm working on getting popup/modal windows also working
 properly, and once that's finished I'll check the stuff in under the new
 branch.

 One last important fact I need to mention is that I've build some of the
 portlet-support features upon the anticipated new Portlet 2.0 API
 (JSR-286, of which
 I'm also an EG member). As JSR-286 isn't released yet (but very soon
 now...), and no (formal) implementations exists or are even allowed, I have
 defined some
 supporting interfaces,  specifically for header contributions and Portlet
 ResourceURLs.
 To be able to actually run wicket with the new portlet-support within a
 portal, you'll need portal specific implementations for these interfaces.
 As soon as JSR-286 is available as well as supporting portals, those
 interfaces can be retrofitted back upon JSR-286 APIs and you won't need such
 proprietary
 implementations anymore.

 For my own testing, and because I'm also a Jetspeed committer, I've
 already provided Jetspeed-2 specific support implementations.
 Since the latest Jetspeed-2.1.2 release, these are provided out-of-the-box
 with the portal itself.
 For more information about this, see:
 http://issues.apache.org/jira/browse/PB-65

 So, for now, you might be required to test and experiment using
 Jetspeed-2, although I think I already saw someone report it running on
 Liferay as well.

 Regards,

 Ate

 
  Martijn
 
  On 8/30/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
  it has moved to wicket-stuff because none of the core committers have
 time
  to keep it up to date. i believe Ate was reworking it into something
 better,
  his work in progress is in wicket-stuff
 
  -igor
 
  On 8/30/07, Dipu Seminlal [EMAIL PROTECTED] wrote:
  Hi All,
 
  I checked out the wicket trunk and found that the Portlet package has
  disappeared from where it was.
  Has it been moved to somewhere else or did the Portlet support got
 removed
  totally ?
  What is the future plans for the Portlet support in wicket.
 
  Thanks
  Dipu
 
 
 


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail

Re: Portlet Support

2007-08-31 Thread Dipu Seminlal
Hi All,

many thanks for pointing me to the right direction.

Regards
Dipu

On 8/30/07, Matej Knopp [EMAIL PROTECTED] wrote:

 Hi Ate,

 thanks for the examples. The progress is tremendous. Awesome.

 -Matej

 On 8/30/07, Ate Douma [EMAIL PROTECTED] wrote:
 
  Martijn Dashorst wrote:
   I think it is in a branch in our apache repo:
  
  
 
 http://svn.apache.org/repos/asf/wicket/branches/wicket-1.3-portlet-support/
  Yes, and there is a corresponding JIRA issue with several subtasks which
 I
  use for tracking the current state (and some minimal documentation):
 
https://issues.apache.org/jira/browse/WICKET-647
 
  If you are interested in testing that out, I've provided a downloadable
  Jetspeed-2 installer which the wicket-examples application deployed as
  portlet
  application here:
 
 http://people.apache.org/~ate/wicket/
 
  Note though the above branch was created on July 14 from the trunk at
 that
  time (r547242), and the portlet-support (as currently checked in) isn't
  perfect or
  without some serious bugs yet.
 
  But, I've started working on a updated version of the portlet-support
 this
  week which is based on the latest 1.3.0-beta3 release and it is
  progressing rather well.
  I hope to commit this update tomorrow or else early next week the
 latest.
  For that, I plan to create a new branch,
  wicket-1.3.0-beta3-portlet-support, as merging back in all the trunk
  changes since the branch (reliably) turned out to
  be far too much work.
 
  So, I started from scratch again, applying my original changes by
 hand,
  bit by bit (man, being on a branch of a project which moves as quickly
 as
  Wicket is
  painful...).
  Which turned out to be not a bad idea after all: I cleaned up and
 improved
  several changes along the lines as well as refactored several new
 classes
  and methods
  names to better reflect their purpose. Luckily, as the new
 portlet-support
  (in contrast to the one from 1.2.x) is now using transparent bridging
  wicket to the
  portlet environment, those internal changes didn't have any effect on
 the
  usage.
 
  Anyway, you will all soon see that the portlet-support has progressed
  nicely, to the point I think it covers many to most standard use-cases
  (albeit there still
  are and always will be a few area's where portlet support is difficult
 or
  even formally impossible to provide).
 
  The nicest part I think is that it turned out to require very little
  changes to the wicket core, and AFAIK all of those are transparent,
 meaning
  these changes
  have zero effect for existing plain servlet based applications!
 
  In my opinion, it should be ready for trunk integration soon now (after
  proper review of course), we just need to find and agree upon the right
 time
  frame.
 
  Right now I'm working on getting popup/modal windows also working
  properly, and once that's finished I'll check the stuff in under the new
  branch.
 
  One last important fact I need to mention is that I've build some of the
  portlet-support features upon the anticipated new Portlet 2.0 API
  (JSR-286, of which
  I'm also an EG member). As JSR-286 isn't released yet (but very soon
  now...), and no (formal) implementations exists or are even allowed, I
 have
  defined some
  supporting interfaces,  specifically for header contributions and
 Portlet
  ResourceURLs.
  To be able to actually run wicket with the new portlet-support within a
  portal, you'll need portal specific implementations for these
 interfaces.
  As soon as JSR-286 is available as well as supporting portals, those
  interfaces can be retrofitted back upon JSR-286 APIs and you won't need
 such
  proprietary
  implementations anymore.
 
  For my own testing, and because I'm also a Jetspeed committer, I've
  already provided Jetspeed-2 specific support implementations.
  Since the latest Jetspeed-2.1.2 release, these are provided
 out-of-the-box
  with the portal itself.
  For more information about this, see:
  http://issues.apache.org/jira/browse/PB-65
 
  So, for now, you might be required to test and experiment using
  Jetspeed-2, although I think I already saw someone report it running on
  Liferay as well.
 
  Regards,
 
  Ate
 
  
   Martijn
  
   On 8/30/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
   it has moved to wicket-stuff because none of the core committers have
  time
   to keep it up to date. i believe Ate was reworking it into something
  better,
   his work in progress is in wicket-stuff
  
   -igor
  
   On 8/30/07, Dipu Seminlal [EMAIL PROTECTED] wrote:
   Hi All,
  
   I checked out the wicket trunk and found that the Portlet package
 has
   disappeared from where it was.
   Has it been moved to somewhere else or did the Portlet support got
  removed
   totally ?
   What is the future plans for the Portlet support in wicket.
  
   Thanks
   Dipu
  
  
  
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional