Hi!
From what I remember, there are no special descriptors for uPortal
deployment. It's a while since I worked with uPortal, so I don't
remember exactly where I found the instructions, but there are some
deployment instructions somewhere in the uPortal documentation. I
remember it involved
Hi Gurus,
In my application I'm using Struts2.0.1 framework. I have a
Request Filter, which is supposed to redirect all URLs except a few to a JSP
page(lets call it AccessDeniedPage.jsp) which is mentioned as the init-param of
the RequestFilter. But when the filter gets any
Hi Guys,
I have been working around the utilities classes of struts 1. What I
am wondering is if this API as defined by these utilities classes
supported by us? currently the TagUtils class throws sometimes NPE's.
What I would like to do is to replace these NPE with a JSP exception,
but this
The class:
org.apache.struts2.views.velocity.components.AutocompleterDirective;
appears to be missing from trunk. It is used by the VelocityManager.
David
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Mark,
This bug is related. You're welcomed to investigate it:
https://issues.apache.org/struts/browse/STR-2437
Mark Bakker wrote:
Hi Guys,
I have been working around the utilities classes of struts 1. What I
am wondering is if this API as defined by these utilities classes
supported by us?
In my experience, the only difficult part of a release is catching up
the release notes. The rest is just mechanics. I'll setup a release
notes page for Struts 1.36, and if someone wants to bring it up to
date, I'll take care of the rest.
-Ted.
On 11/26/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Ohh okee I will look into that too. Do I understand correctly that the
signatures of TagUtils methodes may change? I don't see another real
option if we want to improve the exception handeling around the tag
libraries.
currently I am working on bug
-
Right now, we're posting the api and core JARs for Struts 2
Would it be difficult to switch that to the all JAR, which includes
the plugins?
(And, now that I say it, I realize that maybe the all JAR is the one
we should J4.)
Is there a non-technical reason why we are just posting the JARs, and
It is in this patch(WW-1520_1.patch)
https://issues.apache.org/struts/browse/WW-1520
I think Ted hasn't applied it yet.
musachy
David H. DeWolf wrote:
The class:
org.apache.struts2.views.velocity.components.AutocompleterDirective;
appears to be missing from trunk. It is used by the
I applied the first patch in r479236, but left out that file. It's
committed in r479638.
On 11/27/06, Musachy Barroso [EMAIL PROTECTED] wrote:
It is in this patch(WW-1520_1.patch)
https://issues.apache.org/struts/browse/WW-1520
I think Ted hasn't applied it yet.
musachy
David H. DeWolf
Thanks, Paul. We dropped the ball on the issue tickets during the 1.1
deathmarch, and never really recovered. It's nice to see progress. Are
there really 35 open bug tickets against Struts 1, or are some of
these unreviewed and unconfirmed? At the point of a release, we
usually have zero open bug
Yay!!
On 11/23/06, Mark Bakker [EMAIL PROTECTED] wrote:
I am interested to do some work on the Struts project. I have been
investigating STR-1183
https://issues.apache.org/struts/browse/STR-1183
currently I started to create some code.
In general I am creating a ViewUtils class in the
On Nov 25, 2006, at 9:32 AM, Ted Husted wrote:
Could we also document the alternative of moving the org.apache.tiles
packages *into* the struts2-plugin?
The proposal cites three problems:
1 Can't release
2 Not visible
3 Not permanent
As part of the Struts2 Plugin, problems 1 and 2 will be
Ted,
Are there really 35 open bug tickets against Struts 1, or are some of
these unreviewed and unconfirmed?
Where are you getting the 35 number from?
At the point of a release, we
usually have zero open bug tickets.
I still have a bunch of incremental improvements for Struts 1.3, and the
Mark,
I do not know where you read that the signature of the TagUtils may
change. I wouldn't bet on it. At all costs, keep the signatures the same
:-) And wherever you see the JspException thrown, add in the root cause
to the constructor.
Mark Bakker wrote:
Ohh okee I will look into that
On 11/27/06, Paul Benedict [EMAIL PROTECTED] wrote:
Where are you getting the 35 number from?
*
https://issues.apache.org/struts/secure/IssueNavigator.jspa?mode=hiderequestId=10674
I still have a bunch of incremental improvements for Struts 1.3, and the
release of 1.3.6 is kind of
Ted Husted wrote:
*
https://issues.apache.org/struts/secure/IssueNavigator.jspa?mode=hiderequestId=10674
At least half of those are enhancement requests. I had every intention
of continuing to build these into 1.3.6 until your idea to do a release.
The others are unconfirmed bugs. If you
On 11/27/06, Greg Reddin [EMAIL PROTECTED] wrote:
To create community, a codebase needs to stand on its own or be part
of a larger umbrella project, like the Commons or the ASF itself.
I agree. I don't see this move as building community. It's just a
stepping stone on the path to
Ted,
Do you want the open tickets to hold up the release? Please respond. If
you respond in the negative, please tag. Afterwards, I will:
* Re-assign the open tickets to 1.3.7
* Write the release notes
* Update the maven projects to 1.3.7-SNAPSHOT
Paul
Ted Husted wrote:
In my experience,
On 11/27/06, Paul Benedict [EMAIL PROTECTED] wrote:
Do you want the open tickets to hold up the release? Please respond. If
you respond in the negative, please tag. Afterwards, I will:
* Re-assign the open tickets to 1.3.7
* Write the release notes
* Update the maven projects to 1.3.7-SNAPSHOT
On 11/27/06, Paul Benedict [EMAIL PROTECTED] wrote:
Ted,
Do you want the open tickets to hold up the release? Please respond. If
you respond in the negative, please tag. Afterwards, I will:
If there's a patch attached to a bug ticket, or we otherwise know how
to fix the bug, we should resolve
Sorry for the rant. I would have just sent the last two paragraphs,
but the phone rang, and I pressed the wrong button :(
On 11/27/06, Ted Husted [EMAIL PROTECTED] wrote:
Here's the thing: If all these other projects depend on Tiles, then
why are they not contributing? If other people won't
The class:
org.apache.struts2.components.Autocompleter;
appears to be missing from trunk. It is used by the AutocompleterDirective.
Mark
On 11/27/06, Ted Husted [EMAIL PROTECTED] wrote:
I applied the first patch in r479236, but left out that file. It's
committed in r479638.
On 11/27/06,
It is building ok from head.
musachy
Mark Bakker wrote:
The class:
org.apache.struts2.components.Autocompleter;
appears to be missing from trunk. It is used by the
AutocompleterDirective.
Mark
On 11/27/06, Ted Husted [EMAIL PROTECTED] wrote:
I applied the first patch in r479236, but left
according the svn it is not in there
http://svn.apache.org/viewvc/struts/struts2/trunk/core/src/main/java/org/apache/struts2/components/
a update should break your build
On 11/27/06, Musachy Barroso [EMAIL PROTECTED] wrote:
It is building ok from head.
musachy
Mark Bakker wrote:
The class:
My bad :) I created the class so I had it locally, humm... I'd swear it
was there today.
musachy
Mark Bakker wrote:
according the svn it is not in there
http://svn.apache.org/viewvc/struts/struts2/trunk/core/src/main/java/org/apache/struts2/components/
a update should break your build
hehe thanks
On 11/27/06, Musachy Barroso [EMAIL PROTECTED] wrote:
My bad :) I created the class so I had it locally, humm... I'd swear it
was there today.
musachy
Mark Bakker wrote:
according the svn it is not in there
No problem. I just haven't had time to formulate a response yet :-)
Greg
On Nov 27, 2006, at 2:02 PM, Ted Husted wrote:
Sorry for the rant. I would have just sent the last two paragraphs,
but the phone rang, and I pressed the wrong button :(
On 11/27/06, Ted Husted [EMAIL PROTECTED] wrote:
The only real disadvantage of defaulting to the struts2-all.jar is that
you lose the self-configuration aspect of the plugins. For example, by
including the Spring plugin jar, it is able to tell Struts 2 to use its
ObjectFactory automatically. However, if you included both the Spring
and
I added the file to svn.
Don
On 11/27/06, Mark Bakker [EMAIL PROTECTED] wrote:
hehe thanks
On 11/27/06, Musachy Barroso [EMAIL PROTECTED] wrote:
My bad :) I created the class so I had it locally, humm... I'd swear it
was there today.
musachy
Mark Bakker wrote:
according the svn it is
OK, with Don's fix to the blank dependencies, and with Rainer's XWork2
beta2, I'll try and tag and roll a 2.0.2 build.
-Ted.
On 11/25/06, Ted Husted [EMAIL PROTECTED] wrote:
The Action tests in the blank application are failing from a command
line build, but it works from IDEA. These same
I can successfully build the entire Struts 1.3.6 website from the parent
POM. This POM I have upgraded to the latest versions of the plug-ins (no
snapshots) and closed out most of the tickets that recommended build
enhancements. Specifically, we can now build one entire aggregated
javadoc for
On 11/27/06, Paul Benedict [EMAIL PROTECTED] wrote:
PSS: I really really miss having the previously released versions on the
left-hand bar in the 1.x website. I like to flip back to previous
releases at times to get to the documentation, when I need it. And
that's no longer available. Can we
On 11/28/06, Paul Benedict [EMAIL PROTECTED] wrote:
I can successfully build the entire Struts 1.3.6 website from the parent
POM. This POM I have upgraded to the latest versions of the plug-ins (no
snapshots) and closed out most of the tickets that recommended build
enhancements. Specifically,
Thanks Ted. If just a poor committer couldn't find them, can we safely
assume there's even a less chance the typical user will?
Ted Husted wrote:
On 11/27/06, Paul Benedict [EMAIL PROTECTED] wrote:
PSS: I really really miss having the previously released versions on the
left-hand bar in the
So, when I get to the assembly:assembly stage, the build fails,
complaining that it can't find XWork beta2.
I installed XWork beta2 manually, but still no joy.
Another bit of strangeness is that I can't get a clean build from my
usual checkout. It fails on the ActionTag tests. If I try from
On 11/27/06, Paul Benedict [EMAIL PROTECTED] wrote:
Thanks Ted. If just a poor committer couldn't find them, can we safely
assume there's even a less chance the typical user will?
Why would a typical user need to access the documentation from several
releases back?
-Ted.
On 11/27/06, Niall Pemberton [EMAIL PROTECTED] wrote:
+1 and we could make space by removing Similar Projects and having
Related Projects which just contains Shale, Jakarta Commons,
Velocity Struts and Strecks.
I would suggest that the policy be that we publish the links to the
documentation
Not everyone is using the same version of Struts. If I was still using
1.2.9, I'd hope to be able to quickly get to 1.2.9 docs whenever I was
developing with it ... or 1.1, etc.
Ted Husted wrote:
On 11/27/06, Paul Benedict [EMAIL PROTECTED] wrote:
Thanks Ted. If just a poor committer
On 11/28/06, Ted Husted [EMAIL PROTECTED] wrote:
On 11/27/06, Niall Pemberton [EMAIL PROTECTED] wrote:
+1 and we could make space by removing Similar Projects and having
Related Projects which just contains Shale, Jakarta Commons,
Velocity Struts and Strecks.
I would suggest that the policy
We have this site issue
https://issues.apache.org/struts/browse/STR-2926
The complaint is we don't have any download links for Struts-Faces. Now
with the 1.3.5 release, struts-faces is part of the library. However,
that wasn't the case with earlier releases.
Do we want to provide a link on
On 11/28/06, Paul Benedict [EMAIL PROTECTED] wrote:
We have this site issue
https://issues.apache.org/struts/browse/STR-2926
The complaint is we don't have any download links for Struts-Faces. Now
with the 1.3.5 release, struts-faces is part of the library. However,
that wasn't the case with
42 matches
Mail list logo