A few quick questions:
* why are the method names changing from register to start
* why don't we support the registerAtInit option in the deployTool anymore
--
David Sean Taylor
Bluesunrise Software
[EMAIL PROTECTED]
[office] +01 707 773-4646
[mobile] +01 707 529 9194
--
[ http://issues.apache.org/jira/browse/JS2-210?page=comments#action_60016 ]
Ate Douma commented on JS2-210:
---
I've created a new CVS branch, deployment-refactoring, in which I've committed
my changes as of now.
The current version is tested with deployment
ate 2005/03/01 18:52:12
Modified:installer/src Tag: deployment-refactoring build.xml
.Tag: deployment-refactoring project.properties
portal/src/webapp/WEB-INF Tag: deployment-refactoring
web.xml
portal/src/w
ate 2005/03/01 18:51:03
Modified:portal/src/webapp/WEB-INF/assembly Tag:
deployment-refactoring pluto-factories.xml
jetspeed-spring.xml
Log:
New deployment and portlet container invokation configurations.
Revision ChangesP
ate 2005/03/01 18:50:27
Modified:portal/src/webapp/WEB-INF/pages/Administrative Tag:
deployment-refactoring role-group.psml
profiler.psml site.psml sso-admin.psml
role-mgt.psml pam.psml user-mgt.psml
ate 2005/03/01 18:49:25
Modified:portal/src/test/org/apache/jetspeed/userinfo Tag:
deployment-refactoring TestUserInfoManager.java
portal/src/test/org/apache/jetspeed/tools/pamanager Tag:
deployment-refactoring
ate 2005/03/01 18:46:28
Modified:portal/src/java/org/apache/jetspeed/engine Tag:
deployment-refactoring AbstractEngine.java
Log:
Fix issue with log4j when doing dynamic (re)configuration. First reset the
configuration to prevent append errors on closed ap
ate 2005/03/01 18:43:55
Modified:components/portlet-factory/src/java/org/apache/jetspeed/factory
Tag: deployment-refactoring
JetspeedPortletFactory.java
Added: components/portlet-factory/src/java/org/apache/jetspeed/factory
ate 2005/03/01 18:42:57
Modified:etc/project-dependencies Tag: deployment-refactoring
myfaces-deps.xml
Log:
Don't include jsp-api jar in web-inf/lib as that leads to:
org.apache.jasper.JasperException: Failed to load or instantiate
TagLibraryValidator
ate 2005/03/01 18:40:44
Modified:applications/rss Tag: deployment-refactoring project.xml
applications/pam Tag: deployment-refactoring project.xml
Log:
Fixes for rss and pam apps which didn't include commons-collections, leading
to failures on Tomcat 5.5
Revi
ate 2005/03/01 18:39:13
Modified:components/deploy-tool Tag: deployment-refactoring
README.txt
Log:
Deploy tool changes. Note: now it only supports/accepts two arguments:
inputName outputName.
Revision ChangesPath
No revision
ate 2005/03/01 18:38:54
Modified:content-server Tag: deployment-refactoring project.xml
Log:
Fixes on content-server needed to allow running on Tomcat 5.5:
- handle writing to response.getWriter and response.getOutputStream properly
- translate absolute file path on Windows i
ate 2005/03/01 18:38:00
Modified:content-server/src/java/org/apache/jetspeed/contentserver
Tag: deployment-refactoring
AbstractContentLocator.java
ContentLocatingResponseWrapper.java
Log:
Fixes on content-ser
ate 2005/03/01 18:35:43
Modified:
components/registry/src/test/org/apache/jetspeed/components/portletregistry/direct
Tag: deployment-refactoring
TestRegistryDirectPart2a.java
TestRegistryDirectPart1a.java
Log:
ate 2005/03/01 18:35:16
Modified:components/registry/src/java/org/apache/jetspeed/om/portlet/impl
Tag: deployment-refactoring
PortletDefinitionImpl.java
Log:
Registry changes (Portlet Classloader is now only maintained in the
Portl
[ http://issues.apache.org/jira/browse/JS2-187?page=comments#action_60014 ]
Peter Johnson commented on JS2-187:
---
JS2-189 is a DB related bug. This is more likely to be due to the use of JDK
1.5.
> Jetspeed-2 Issues on Tomcat 5.5
> ---
ate 2005/03/01 18:34:15
Modified:components/deploy-tool/src/java/org/apache/jetspeed/tools/deploy
Tag: deployment-refactoring
JetspeedDeployFactory.java JetspeedDeploy.java
JetspeedWebApplicationRewriter.java
L
ate 2005/03/01 18:33:18
Modified:commons/src/java/org/apache/jetspeed/container Tag:
deployment-refactoring JetspeedPortletContext.java
JetspeedContainerServlet.java
ContainerConstants.java JetspeedPortletConfig.
ate 2005/03/01 18:31:47
Modified:jetspeed-api/src/java/org/apache/jetspeed/tools/deploy Tag:
deployment-refactoring DeployFactory.java
jetspeed-api/src/java/org/apache/jetspeed/factory Tag:
deployment-refactoring PortletF
ate 2005/03/01 16:26:28
Removed: jetspeed-api/src/java/org/apache/jetspeed/tools/pamanager
Tag: deployment-refactoring
DeploymentRegistration.java
portal/src/java/org/apache/jetspeed/tools/pamanager Tag:
taylor 2005/03/01 15:32:16
Modified:portal/src/java/org/apache/jetspeed/velocity
JetspeedPowerTool.java
Log:
make data members protected, methods overrideable by subclasses as requested
by end user
Revision ChangesPath
1.42 +22 -22
jakar
taylor 2005/03/01 15:30:38
Modified:portal/src/java/org/apache/jetspeed/login
LoginRedirectorServlet.java LogoutServlet.java
LoginProxyServlet.java LoginErrorServlet.java
LoginServlet.java
Log:
make methods over
taylor 2005/03/01 15:28:36
Modified:components/deploy-tool/src/java/org/apache/jetspeed/tools/deploy
JetspeedDeploy.java
Log:
make methods overrideable by subclasses as requested by end user
Revision ChangesPath
1.10 +7 -6
jakarta-jetsp
Ate Douma wrote:
David Sean Taylor wrote:
Randy Watler wrote:
Ate/All,
Yes, 4.1 is certainly painful when it comes to deployment. I can
verify most of what Ate has outlined here.
+1 to drop 4.1.
+1 to drop 4.1 support
+1
+1 to fix 5.5 support before dropping 4.1
+1 too
... which I can say easil
Randy Watler (JIRA) wrote:
[
http://issues.apache.org/jira/browse/JS2-69?page=comments#action_59846
]
Randy Watler commented on JS2-69: -
Team,
After devoting some time to this issue over the week I think I have
come up with the heart of a proposal. I plan on commiti
David Sean Taylor wrote:
Randy Watler wrote:
Ate/All,
Yes, 4.1 is certainly painful when it comes to deployment. I can
verify most of what Ate has outlined here.
+1 to drop 4.1.
+1 to drop 4.1 support
+1
+1 to fix 5.5 support before dropping 4.1
+1 too
... which I can say easily now as have 5.5
Peter Meier wrote:
I noticed that the classloader that is stored in PortletDefinition under
portletClassLoader is *not* the classloader that is actually used (or
has been used) to load the portlet class itself. Instead, there is a
classloader stored that has been taken from a map that has been
shinsuke2005/03/01 14:19:54
Modified:components/web-content/src/java/org/apache/jetspeed/portlet
WebContentPortlet.java
Log:
fixed JS2-218
http://issues.apache.org/jira/browse/JS2-218
Revision ChangesPath
1.12 +6 -5
jakarta-jetspeed-2/
I noticed that the classloader that is stored in PortletDefinition under
portletClassLoader is *not* the classloader that is actually used (or
has been used) to load the portlet class itself. Instead, there is a
classloader stored that has been taken from a map that has been
previously created
Randy Watler wrote:
Ate/All,
Yes, 4.1 is certainly painful when it comes to deployment. I can verify
most of what Ate has outlined here.
+1 to drop 4.1.
+1 to drop 4.1 support
+1 to fix 5.5 support before dropping 4.1
--
David Sean Taylor
Bluesunrise Software
[EMAIL PROTECTED]
[office] +01 707 77
I am fine with tomcat 4 support discontinued.
Thanks,
Amit
Original Message Follows
From: Ate Douma <[EMAIL PROTECTED]>
Reply-To: "Jetspeed Developers List"
To: Jetspeed Developers List , Jetspeed
Users List
Subject: Jetspeed-2: Drop support for Tomcat 4...? Please comment/vote!
Date: T
I am using J2MI with Tomcat 5.5.7 and there are some
issues - the default portlets seem to give up because
of some tag lib issue?
Nested Exception is org.apache.jasper.JasperException:
Unable to read TLD "META-INF/fmt.tld" from JAR file
"file:/D:/apache/jakarta-tomcat-5.5.7/webapps/security/WEB-IN
+1 on dropping 4.1 support.
Ate Douma wrote:
Dear developer team and users,
I've been working the last two weeks (off and on) on a new and much
simplified deployment implementation
for Jetspeed-2 which builds mainly on official Servlet specification
(2.3) features.
See JIRA: http://issues.apache.
> And, if there are no big objections, I'd like to vote on dropping
Tomcat
> 4 support
+1
-Original Message-
From: Ate Douma [mailto:[EMAIL PROTECTED]
Sent: Monday, February 28, 2005 9:40 PM
To: Jetspeed Users List
Cc: Jetspeed Developers List
Subject: Re: Jetspeed-2: Drop support for To
hi !
i have a problem with the current new files of J2.
when i checked out an, build, deploy and start J2 the first time
on my tomcat 5.0.28, i get following message.
m1 works fine. i looked at the nodeset.java, but i can't find any
mistakes...
the important line of course:
org.apache.jetspeed.
WebContentPortlet displays multibyte characters as garbage
--
Key: JS2-218
URL: http://issues.apache.org/jira/browse/JS2-218
Project: Jetspeed 2
Type: Bug
Components: i18n and l10n
Versions: 2.0-dev/cvs
+1 to drop 4.1
Ate Douma wrote:
Dear developer team and users,
I've been working the last two weeks (off and on) on a new and much
simplified deployment implementation
for Jetspeed-2 which builds mainly on official Servlet specification
(2.3) features.
See JIRA: http://issues.apache.org/jira/brow
> bug in Tomcat 5 is really painful. IMO we should coordinate with
> Pluto and aim for the same platform support.
I second Raphaël on coordinating with Pluto.
IMHO, we should consider it a high(er) priority issue. or there are
any oppositions?
Remarks most welcome.
Oh! Better we spin off an inde
Randy Watler wrote:
Ate/All,
Yes, 4.1 is certainly painful when it comes to deployment. I can verify
most of what Ate has outlined here.
+1 to drop 4.1.
Ate, are you also working on getting 5.5 functional? I suppose it would
be good to do that before/while we deprecate 4.1 support.
I agree with
39 matches
Mail list logo
