To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project incubator-geronimo *no longer* has an issue.
The current state of this project
The djencks/jetty-deployer1/trunk branch is basically working perfectly
so I plan to merge it back to trunk shortly.
missing features:
1. default locale configs. These can be specified in web.xml but there
aren't any defaults like jetty has in default-web.xml yet. Are these
actually useful?
Last night I committed the changes to the Kernel to remove the
dependencies on JMX. The Kernel still uses ObjectName and
MalformedObjectNameException, and those will go when we add GBeanName.
My change notes follow:
Kernel is not totally decoupled from JMX. By default the kernel will
no
The reason that we have JettyWebAppJACCContext and JettyWebAppContext is that I
thought that there might be people who want to use jetty in geronimo w/out
JACC. If this is not the case, then it makes sense to merge the two.
Regards,
Alan
-Original Message-
From:
Hi,
I'm ignant so in lay terms what is it that we have here? A generic
server side platform? An IoC container?
Could someone elaborate a lil bit more on the evolution that is taking
place or point me to any documentation. It's very interesting and I'm
curious about the big picture.
Alex
Unsurprisingly, the new deployer breaks the axis tests that attempt to
set up a web application in code. On the other hand, the new deployer
should make it possible to directly deploy axis servlet(s) for pojo web
services.
should I:
1. merge to trunk now and disable axis tests
2. rewrite the
On Dec 7, 2004, at 7:50 AM, David Jencks wrote:
Unsurprisingly, the new deployer breaks the axis tests that attempt to
set up a web application in code. On the other hand, the new deployer
should make it possible to directly deploy axis servlet(s) for pojo
web services.
should I:
1. merge to
fixed. the problem should stop now
On Dec 7, 2004, at 9:00 AM, David Jencks wrote:
I'm getting these for every message I send. Can we spam them equally
or at least unsubscribe them?
thanks
david jencks
Begin forwarded message:
From: [EMAIL PROTECTED]
Date: December 7, 2004 7:55:00 AM PST
To:
Thanks! (also testing the fix :-)
david jencks
On Dec 7, 2004, at 12:20 PM, Geir Magnusson Jr wrote:
fixed. the problem should stop now
On Dec 7, 2004, at 9:00 AM, David Jencks wrote:
I'm getting these for every message I send. Can we spam them equally
or at least unsubscribe them?
thanks
On Tue, 7 Dec 2004, Jacek Laskowski wrote:
And the tomcat gbean will never go live unless assembly is modified.
You're right, I'll modify assembly and comment out the tomcat module's
stuff. Having a switch to turn on and off the tomcat module's additions
would be great, wouldn't it?
Dain Sundstrom wrote:
Currently there is only one deployer slot available for each module
type of an EAR. The following snippit from the shows the EAR deployer
configuration
gbean name=geronimo.deployer:role=Builder,type=EAR,config=org/apache/
geronimo/J2EEDeployer
On Dec 7, 2004, at 1:05 PM, Jacek Laskowski wrote:
Dain Sundstrom wrote:
Currently there is only one deployer slot available for each module
type of an EAR. The following snippit from the shows the EAR
deployer configuration
gbean
Getting this when bootstrapping the deployer during assembly.
AIUI this moved package/module recently - any ideas why the old version
is still being used?
I have wiped out the maven repo and cache and built online from clean.
--
Jeremy
java.lang.NoClassDefFoundError:
As the build is consistently failing for me, can someone apply this and
see if Geronimo builds for them?
--
Jeremy
Index: modules/assembly/project.xml
===
--- modules/assembly/project.xml(revision 110123)
+++
Is attaching the *.patch file to the issue in JIRA
sufficient?
Who applies the patch and when?
Chandresh
From your patch:
if(password == null) {
-out.print(Password: );
-out.flush();
-password = in.readLine();
+PasswordField passWd = new PasswordField(out, in,
Password: );
+password = new
While I agree that we should turn off the tests that break, should we also file
a jira issue to make sure that they get turned back on again?
Regards,
Alan
-Original Message-
From: Dain Sundstrom [mailto:[EMAIL PROTECTED]
Sent: Tue 12/7/2004 11:08 AM
Alan D. Cabrera wrote:
While I agree that we should turn off the tests that break, should we also file a jira issue to make sure that they get turned back on again?
+1
1. merge to trunk now and disable axis tests
+1 (as I'm awaiting your changes to merge them to the tomcat builder)
Jacek
18 matches
Mail list logo
