Doug Schnelzer wrote:
I just tried to do a build using the deployment-refactoring branch in
JBoss 4.0.1sp1 and JDK 1.4.2_03-b02. I had to add the jboss-web.xml
file to the demo.war application. I am now running into a problem.
It may have nothing to do with the branch version of the code, but
I just tried to do a build using the deployment-refactoring branch in
JBoss 4.0.1sp1 and JDK 1.4.2_03-b02. I had to add the jboss-web.xml
file to the demo.war application. I am now running into a problem.
It may have nothing to do with the branch version of the code, but I
thought I would put
Chris Custine wrote:
I just made a build with the the deployment-refactoring branch today
and I should get a lot more time with it in the next few days if you
are interested to hear from a non-J2 comitter. I have an application
(several portlets, custom portlet and layout decorators) built around
Ate Douma a écrit :
I fully agree. That's the reason I wrote that comment above.
But, I also still hope we can release a M2 before the end of this
month and I really would like to see the new deployment implementation
be part of it.
Hopefully others are already testing it too without telling so
it
Hi Ate...
Ate Douma wrote:
But, I also still hope we can release a M2 before the end of this
month and I really would like to see the new deployment implementation
be part of it.
Hopefully others are already testing it too without telling so ;-)
Is the deployment-refactoring branch supposed to
Luc Fouin wrote:
Ate Douma a écrit :
I fully agree. That's the reason I wrote that comment above.
But, I also still hope we can release a M2 before the end of this
month and I really would like to see the new deployment implementation
be part of it.
Hopefully others are already testing it too
Ate,
We are currently testing the deployment-refactoring branch in Tomcat
5.5.8 and JBoss 4.0.1sp1. I read through JS2-210 and couldn't see how
we should undeploy a Portlet given the changes in the branch. Is
there a way to do this yet or do we need to wait for enhancements to
the PAM?
Thanks,
Doug Schnelzer wrote:
Ate,
We are currently testing the deployment-refactoring branch in Tomcat
5.5.8 and JBoss 4.0.1sp1. I read through JS2-210 and couldn't see how
we should undeploy a Portlet given the changes in the branch. Is
there a way to do this yet or do we need to wait for
successfully deployed a test install of standard J2
deployment-refactoring branch on a Linux Debian server
with JDK 1.5 and Tomcat 5.5.7.
We'll try to load some custom portlet developments and
let you know if we encounter any significant issues.
Anyway, I'd think we should hold on merging until we
some time :)
We have successfully deployed a test install of standard J2
deployment-refactoring branch on a Linux Debian server
with JDK 1.5 and Tomcat 5.5.7.
We'll try to load some custom portlet developments and
let you know if we encounter any significant issues.
Great news Raphaël! Thanks
with CVS HEAD later this week. What does worry me though is
that nobody seems
to have time or interest in testing this thing out...
You know, Ate, testing that branch takes some time :)
We have successfully deployed a test install of standard J2
deployment-refactoring branch
I can build and deploy J2 into Catalina
When I start Tomcat I get a NullPointer exception in the Auto-Deployment for
Jetspeed.
Comment out the Auto-Deployment section in the jetspeed.properties lets
Catalina start with no exception.
When I go to the jetspeed page only the jetspeed logo is
I got the latest CVS head for J2.
I can build it without any problems.
I can deploy it (j2\portal maven fullDeploy) with no errors.
When I start tomcat (4.1.29) I get the following exception:
WARN: Unable to intialize Catalina Portlet Application Manager. Auto
deployment will be disabled:
13 matches
Mail list logo
