dependabot[bot] commented on PR #5:
URL: https://github.com/apache/struts-archive/pull/5#issuecomment-1107434742
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
major or minor version,
lukaszlenart closed pull request #5: Bump spring-core from 2.5.6 to 5.3.19 in
/plugins/struts2-portlet-plugin
URL: https://github.com/apache/struts-archive/pull/5
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
dependabot[bot] commented on PR #2:
URL: https://github.com/apache/struts-archive/pull/2#issuecomment-1107117717
Superseded by #5.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
dependabot[bot] closed pull request #2: Bump spring-core from 2.5.6 to 5.3.18
in /plugins/struts2-portlet-plugin
URL: https://github.com/apache/struts-archive/pull/2
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
dependabot[bot] opened a new pull request, #5:
URL: https://github.com/apache/struts-archive/pull/5
Bumps [spring-core](https://github.com/spring-projects/spring-framework)
from 2.5.6 to 5.3.19.
Release notes
Sourced from
dependabot[bot] opened a new pull request, #2:
URL: https://github.com/apache/struts-archive/pull/2
Bumps [spring-core](https://github.com/spring-projects/spring-framework)
from 2.5.6 to 5.3.18.
Release notes
Sourced from
czw., 18 kwi 2019 o 08:10 John Bush napisał(a):
>
> I think that makes sense. Anyone using the portlet-plugin in an
> enterprise setting will want to maintain their testing. I also wondered
> if Spring or the license would allow repackaging the code, especially
> since they no
I think that makes sense. Anyone using the portlet-plugin in an
enterprise setting will want to maintain their testing. I also wondered
if Spring or the license would allow repackaging the code, especially
since they no longer support it. Sorry I didn't open an issue - missed
the request. What
d from Spring
> Framework 4.x)." [1]
>
> So we at Struts may also deprecate Portlet or we may create custom
> adapter classes (possibly derived from Spring Framework 4.x) in junit or
> portlet plugin.
>
> Could you please register an issue including your test code and t
u may create
custom adapter classes in your own project (possibly derived from Spring
Framework 4.x)." [1]
So we at Struts may also deprecate Portlet or we may create custom
adapter classes (possibly derived from Spring Framework 4.x) in junit or
portlet plugin.
Could you please register an issue
spring-webmvc-portlet
test
Regards.
On 11/22/2018 8:45 PM, John Bush wrote:
I'm by no means a struts inner-workings expert so the following
statements may totally be wrong. I'm not sure a portlet guru is needed
since the problem isn't in struts2-portlet-plugin. It still
spring-webmvc-portlet
test
Regards.
On 11/22/2018 8:45 PM, John Bush wrote:
> I'm by no means a struts inner-workings expert so the following
> statements may totally be wrong. I'm not sure a portlet guru is needed
> since the problem isn't in struts2-portl
I'm by no means a struts inner-workings expert so the following
statements may totally be wrong. I'm not sure a portlet guru is needed
since the problem isn't in struts2-portlet-plugin. It still provides the
portlet request/response life-cycle emulation for the application
appropriately
śr., 14 lis 2018 o 08:48 John Bush napisał(a):
> WW-3826 solved a problem running JUnit tests on portlet actions via
> struts2-portlet-plugin and struts2-junit-plugin. The solution used
> Spring's org.springframework.mock.web.portlet package in the spring-test
> framework. Spring
WW-3826 solved a problem running JUnit tests on portlet actions via
struts2-portlet-plugin and struts2-junit-plugin. The solution used
Spring's org.springframework.mock.web.portlet package in the spring-test
framework. Spring Portlet MVC is no longer supported (SPR-14129) and the
package has
code for the portlet plugin version 2.3.4, and
have been testing a fix for this issue today.
I am just unsure on how to proceed, since I'm not a contributor to the project.
Thanks in advance,
Todd Kofford
tkoff...@ku.edu
Developers List dev@struts.apache.org
Subject: Portlet Plugin Problem w/Dynamic Actions Using the URL Tag
I have just upgraded to struts 2.3.4 for an existing application, and found a
potential issue. This issue seems to only happen when the application is run as
a portlet and does not occur when I run
2012/5/28 bphill...@ku.edu bphill...@ku.edu:
When running a unit test of a Struts portlet action using StrutsTestCase with
version of the Struts portlet plugin from 2.3.1 on a NullPointerException is
thrown. The same test passes with version 2.2.1 of the Struts portlet
plugin.
See: https
2012/5/31 Łukasz Lenart lukasz.len...@googlemail.com:
I have a question: why the example project doesn't contain
struts2-portlet-plugin as a dependency ?
It is defined in pom, needed to scroll down a bit ;-)
Regards
--
Łukasz
mobile +48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG
When running a unit test of a Struts portlet action using StrutsTestCase with
version of the Struts portlet plugin from 2.3.1 on a NullPointerException is
thrown. The same test passes with version 2.2.1 of the Struts portlet
plugin.
See: https://issues.apache.org/jira/browse/WW-3826
in context:
http://struts.1045723.n5.nabble.com/Struts-Portlet-Plugin-2-3-3-Breaks-Using-Struts-App-As-Both-Portlet-and-Standalone-Web-App-tp5686113p5697856.html
Sent from the Struts - Dev mailing list archive at Nabble.com
Could you create a new issue or reopen the old one ?
Regards
--
Łukasz http://www.lenart.org.pl/
mobile +48 606 323 122, office +27 11 0838747
Warszawa JUG conference - Confitura http://confitura.pl/
-
To unsubscribe, e-mail:
Anyway, something is messed up. Regarding this:
@StrutsTagAttribute(description = Specifies if this should be a
portlet render or action URL. Default is \render\. To create an
action URL, use \action\.)
public void setPortletUrlType(String portletUrlType) {
Ignore this
2012/5/7 Łukasz Lenart lukasz.len...@googlemail.com:
Anyway, something is messed up. Regarding this:
@StrutsTagAttribute(description = Specifies if this should be a
portlet render or action URL. Default is \render\. To create an
action URL, use \action\.)
public void
The 2.3.3 release of the Struts Portlet Plugin breaks using a Struts
application as both a portlet and as a standalone Java application. I
believe the issue is similar to
https://issues.apache.org/jira/browse/WW-3763. Thought we had fixed that
issue, but additional changes made to the Struts
See
https://builds.apache.org/job/Struts2/org.apache.struts$struts2-portlet-plugin/321/changes
Changes:
[jogep] WW-3620: Bring Portlet 2.0 (JSR286) plugin from sandbox to trunk
--
[JENKINS] Archiving
/home/hudson/hudson-slave/workspace/Struts2/struts2
See
https://builds.apache.org/job/Struts2/org.apache.struts$struts2-portlet-plugin/323/changes
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
-the-existing-Portlet-Plugin-tp4475639p4491890.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h
+1 Binding
Am 10.06.2011 um 11:18 schrieb Johannes Geppert:
After the passed Vote [1] to move the portlet plugin from sandbox to regular
code base, we need a second Vote to replace the existing portlet plugin
version with this new version.
[1]
http://struts.1045723.n5.nabble.com/VOTE
+1 to replace existing plugin with the new version
On 10.06.11 11:18, Johannes Geppert wrote:
After the passed Vote [1] to move the portlet plugin from sandbox to regular
code base, we need a second Vote to replace the existing portlet plugin
version with this new version.
[1]
http
On Mon, Jun 13, 2011 at 8:51 PM, Rene Gielen gie...@it-neering.net wrote:
+1 to replace existing plugin with the new version
On 10.06.11 11:18, Johannes Geppert wrote:
After the passed Vote [1] to move the portlet plugin from sandbox to
regular
code base, we need a second Vote to replace
After the passed Vote [1] to move the portlet plugin from sandbox to regular
code base, we need a second Vote to replace the existing portlet plugin
version with this new version.
[1]
http://struts.1045723.n5.nabble.com/VOTE-Promote-JSR286-Portlet-Plugin-from-sandbox-to-regular-code-base
+1 not binding
Johannes
-
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep
--
View this message in context:
http://struts.1045723.n5.nabble.com/VOTE-Replacing-the-existing-Portlet-Plugin-tp4475639p4475646.html
Sent from the Struts - Dev mailing list archive at Nabble.com
this message in context:
http://struts.1045723.n5.nabble.com/VOTE-Replacing-the-existing-Portlet-Plugin-tp4475639p4475646.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr
Geppert jo...@apache.org:
+1 not binding
Johannes
-
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep
--
View this message in context:
http://struts.1045723.n5.nabble.com/VOTE-Replacing-the-existing-Portlet-Plugin-tp4475639p4475646.html
Sent from the Struts - Dev mailing list
+1 not binding
-Original Message-
From: maurizio.cucchi...@gmail.com
[mailto:maurizio.cucchi...@gmail.com] On Behalf Of Maurizio Cucchiara
Sent: Friday, June 10, 2011 8:10
To: Struts Developers List; lukasz.len...@gmail.com
Subject: Re: [VOTE] Replacing the existing Portlet Plugin
:
http://struts.1045723.n5.nabble.com/VOTE-Promote-JSR286-Portlet-Plugin-from-sandbox-to-regular-code-base-tp4439671p4469645.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr
Good job guys,
+1 binding,
cheers,
Rainer
Am 30.05.2011 um 17:41 schrieb Rene Gielen:
The code in sandbox was developed for replacing the current portlet
plugin. If the vote passes, the code will be moved to the regular code
base, which is a requirement before we can think about adding
://twitter.com/jogep
--
View this message in context:
http://struts.1045723.n5.nabble.com/VOTE-Replace-the-current-Portlet-Plugin-with-Sandbox-Version-tp4438472p4438472.html
Sent from the Struts - Dev mailing list archive at Nabble.com
the choice of the right
dispatcher. That's why it would replace the existing portlet plugin
rather than being added as additional (say portlet2) plugin.
- René
On 30.05.11 08:47, Johannes Geppert wrote:
The version in the Sandbax is based on JSR286 and except the Portlet event
handling feature
, it
detects the API version on the fly / through the choice of the right
dispatcher. That's why it would replace the existing portlet plugin
rather than being added as additional (say portlet2) plugin.
+1 binding
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG
. That's why it would replace the existing portlet plugin
rather than being added as additional (say portlet2) plugin.
+1 binding
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG conference - Confitura http://confitura.pl
twitter: http://twitter.com/jogep
--
View this message in context:
http://struts.1045723.n5.nabble.com/VOTE-Replace-the-current-Portlet-Plugin-with-Sandbox-Version-tp4438472p4438472.html
Sent from the Struts - Dev mailing list archive at Nabble.com
+1
Jason Pyeron
-Original Message-
From: Johannes Geppert [mailto:jo...@apache.org]
Sent: Monday, May 30, 2011 2:48
To: dev@struts.apache.org
Subject: [VOTE] Replace the current Portlet Plugin with
Sandbox Version
The version in the Sandbax is based on JSR286 and except
this message in context:
http://struts.1045723.n5.nabble.com/VOTE-Replace-the-current-Portlet-Plugin-with-Sandbox-Version-tp4438472p4438472.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e
and may be delivered later.
https://issues.apache.org/jira/browse/WW-3620
+1
Johannes
-
--
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep
--
View this message in context:
http://struts.1045723.n5.nabble.com/VOTE-Replace-the-current-Portlet-Plugin
The code in sandbox was developed for replacing the current portlet
plugin. If the vote passes, the code will be moved to the regular code
base, which is a requirement before we can think about adding it to the
next Struts 2 release.
(Johannes, I hope you don't mind that I jumped in here to push
... and here's mine
+1
On 30.05.11 17:41, Rene Gielen wrote:
The code in sandbox was developed for replacing the current portlet
plugin. If the vote passes, the code will be moved to the regular code
base, which is a requirement before we can think about adding it to the
next Struts 2
-the-current-Portlet-Plugin-with-Sandbox-Version-tp4438472p4438472.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h
@rene thank you for catching this.
+1 not binding
Johannes
-
--
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep
--
View this message in context:
http://struts.1045723.n5.nabble.com/VOTE-Promote-JSR286-Portlet-Plugin-from-sandbox-to-regular-code-base
+1
Jason Pyeron
-Original Message-
From: Rene Gielen [mailto:rgie...@apache.org]
Sent: Monday, May 30, 2011 11:42
To: Struts Developers List
Subject: [VOTE] Promote JSR286 Portlet Plugin from sandbox to
regular code base
The code in sandbox was developed for replacing
On Mon, May 30, 2011 at 9:38 PM, Jason Pyeron jpye...@pdinc.us wrote:
+1
Jason Pyeron
-Original Message-
From: Rene Gielen [mailto:rgie...@apache.org]
Sent: Monday, May 30, 2011 11:42
To: Struts Developers List
Subject: [VOTE] Promote JSR286 Portlet Plugin from sandbox to
regular
@struts.apache.org
Subject: Re: [VOTE] Promote JSR286 Portlet Plugin from sandbox to regular code
base
On Mon, May 30, 2011 at 9:38 PM, Jason Pyeron jpye...@pdinc.us wrote:
+1
Jason Pyeron
-Original Message-
From: Rene Gielen [mailto:rgie...@apache.org]
Sent: Monday, May 30, 2011 11:42
+1 binding
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG conference - Confitura http://confitura.pl/
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail:
plugin, brings same method to handle directRender from action phase. Thus it
has same problems :). But since the source is from struts bundled portlet
plugin, I'd better discuss this issue here.
First let me clear the ACTION word. It's both used in struts and portlet
specification, referencing
:
Hi Pyerson,
I'm also using portlet2 plugin, which seems derived from struts portlet
plugin, brings same method to handle directRender from action phase. Thus it
has same problems :). But since the source is from struts bundled portlet
plugin, I'd better discuss this issue here.
First
plugin, which seems derived from struts portlet
plugin, brings same method to handle directRender from action phase. Thus it
has same problems :). But since the source is from struts bundled portlet
plugin, I'd better discuss this issue here.
First let me clear the ACTION word. It's both
Hi Pyerson,
I'm also using portlet2 plugin, which seems derived from struts
portlet plugin, brings same method to handle directRender from action
phase. Thus it has same problems :). But since the source is from struts
bundled portlet plugin, I'd better discuss this issue here.
First let me
, subject to license 20080407P00.
_
From: huang.mi...@gmail.com [mailto:huang.mi...@gmail.com]
Sent: Sunday, May 22, 2011 14:02
To: Struts Developers List
Subject: RE: Portlet plugin renderDirect location transfer via session may has
concurrent issue
Hi Pyerson,
I'm also using portlet2
Hi,
I'm using struts2 portlet plugin for a portlet project recently.
In some case, I have to use renderDirect action to render JSP result
directly from an portlet action phase request.
When I'm examining the PortletResult source code, surprisingly I found
the result location is transfer
, 2011 11:52
To: dev@struts.apache.org
Subject: Portlet plugin renderDirect location transfer via session may
has concurrent issue
Hi,
I'm using struts2 portlet plugin for a portlet project recently.
In some case, I have to use renderDirect
plugin.
That being said, you can always submit patches for it.
musachy
On Sat, Oct 10, 2009 at 9:59 AM, Leonard Broman
leonard.bro...@gmail.com wrote:
Hi!
We are using struts in portlets for custom modules in sitevision
(proprietary portal) but the portlet-plugin has some bugs it seems
this on needs to be open to ideas from others since portal
vendor,framework and DBs are always changing
Martin Gainty
__
(standard caveats apply)
Date: Thu, 15 Oct 2009 11:16:23 +0200
Subject: Re: Portlet-plugin maintainer?
From: leonard.bro...@gmail.com
2009 11:16:23 +0200
Subject: Re: Portlet-plugin maintainer?
From: leonard.bro...@gmail.com
To: dev@struts.apache.org
I've started looking at the codebase a bit, since I have found some
other issues and dislike submitting bugs unless I can reproduce and
have some tech-info on them.
About
Date: Thu, 15 Oct 2009 20:57:26 +0200
Subject: Re: Portlet-plugin maintainer?
From: leonard.bro...@gmail.com
To: dev@struts.apache.org
It worked! I always used the update project configuration in eclipse
because I thought it did the same thing, but obviously not... Now I'm
all set
mg shutdown now
On Thu, Oct 15, 2009 at 3:40 PM, Martin Gainty mgai...@hotmail.com wrote:
Date: Thu, 15 Oct 2009 20:57:26 +0200
Subject: Re: Portlet-plugin maintainer?
From: leonard.bro...@gmail.com
To: dev@struts.apache.org
It worked! I always used the update project configuration
Hi!
We are using struts in portlets for custom modules in sitevision
(proprietary portal) but the portlet-plugin has some bugs it seems,
that might be related directly to this portal. I've started looking at
the codebase for portlet-plugin to try to debug the issues, but I've
realised it's going
The portlet plugin is still using a StringBuffer in its call to UrlHelper, but
that recent patch changed it to a StringBuilder--Musachy, is that something
you're in the process of completing or am I missing something?
(I'm switching to a Vista S2 build box; haven't been able to build on the Mac
Agr...I tried not to change any StringBuffer for StringBuilder in
interfaces but messed up on that one, feel free to update the Portlet
plugin code.
musachy
On Sat, Nov 29, 2008 at 7:59 PM, Dave Newton [EMAIL PROTECTED] wrote:
The portlet plugin is still using a StringBuffer in its call
, checking stuff in again.
Dave
--- On Sat, 11/29/08, Musachy Barroso [EMAIL PROTECTED] wrote:
Agr...I tried not to change any StringBuffer for
StringBuilder in
interfaces but messed up on that one, feel free to update
the Portlet
plugin code.
musachy
On Sat, Nov 29, 2008 at 7:59 PM, Dave Newton
I have finally been able to extract the portlet code into a plugin,
but it required some shortcuts due to couplings between the
Components (URL, Form and it's super classes) and generating the URLs.
But at least all tests pass, and there are no more dependencies to the
portlet API in the core. I
Nils,
This is a great start. I had wanted to do this myself, but I never
found the time. I only took a brief look at the patch, but a few things
jumped out at me:
1. I'm not sure the UrlRendererFactory is needed. I believe the whole
purpose of guice is to not have anymore factories
Thanks for the feedback!
On 6/12/07, Tom Schneider [EMAIL PROTECTED] wrote:
1. I'm not sure the UrlRendererFactory is needed. I believe the whole
purpose of guice is to not have anymore factories anymore, so guice
should just inject the necessary UrlRenderer. (especially if they are
I have started the process of moving the portlet code to a plugin. But
any further progress requires the url building abstraction discussed
earlier. What is the status for this code?
Also, I think the code in general would benefit from a common
abstraction of the servlet- and portlet types
The trunk is the correct place (we branched for 2.0.x).
On 3/25/07, Nils-Helge Garli [EMAIL PROTECTED] wrote:
Hi!
I want to start looking into moving the portlet support to a plugin,
but need a little guidance to get started.
- What is the status of refactoring the URL-building, as discussed
75 matches
Mail list logo
