[ http://nagoya.apache.org/jira/browse/GERONIMO-281?page=history ]
Gianny DAMOUR closed GERONIMO-281:
--
Resolution: Fixed
Fix Version: 1.0-M3
This has been fixed by Dain when he has rewritten the deployment code.
> Optional packages support
>
[ http://nagoya.apache.org/jira/browse/GERONIMO-281?page=history ]
Gianny DAMOUR updated GERONIMO-281:
---
Version: 1.0-M2
Add 1.0-M2 to the list of affected versions.
> Optional packages support
> -
>
> Key: GERONIMO-281
[ http://nagoya.apache.org/jira/browse/GERONIMO-261?page=history ]
Gianny DAMOUR closed GERONIMO-261:
--
Resolution: Fixed
Fix Version: 1.0-M3
There were three problems:
1. If you specify a resource-env-ref or resource-ref in a web.xml file, an
[ http://nagoya.apache.org/jira/browse/GERONIMO-347?page=history ]
David Jencks updated GERONIMO-347:
--
Component: transaction manager
(was: general)
> TransactionContext usage is confused and confusing
> --
[ http://nagoya.apache.org/jira/browse/GERONIMO-258?page=history ]
David Jencks closed GERONIMO-258:
-
Assign To: David Jencks (was: Jeremy Boynes)
Resolution: Cannot Reproduce
Fix Version: 1.0-M3
A lot has changed in jetty and xml mungin
[ http://nagoya.apache.org/jira/browse/GERONIMO-382?page=history ]
David Jencks closed GERONIMO-382:
-
Assign To: David Jencks
Resolution: Cannot Reproduce
Fix Version: 1.0-M3
I removed the extra copies of j2ee-schema from the project.xml
[ http://nagoya.apache.org/jira/browse/GERONIMO-389?page=history ]
Alan Cabrera closed GERONIMO-389:
-
Resolution: Won't Fix
jetty issue
> Download org.mortbay.jetty-5.1-SNAPSHOT.jar / warning: last-modified not
> specified
> --
[ http://nagoya.apache.org/jira/browse/GERONIMO-260?page=history ]
Gianny DAMOUR closed GERONIMO-260:
--
Resolution: Fixed
Fix Version: 1.0-M3
This issue has been fixed when the deployment code has been rewritten by Dain.
Now, when application.
[ http://nagoya.apache.org/jira/browse/GERONIMO-389?page=history ]
Ralf Barkow updated GERONIMO-389:
-
Version: 1.0-M3
(was: 1.0-M2)
Jacek's post to [EMAIL PROTECTED] on 2004-11-05 (subject: Jetty jars corrupted
- warning: last-modified
David Jencks wrote:
Well, not a lot, since I haven't figured out how servlets are deployed
in jetty. What I imagine is parsing web.xml, constructing a gbean for
each servlet, and registering it somehow with the webapp gbean or the
jetty container. Unfortunately on my last venture into jetty co
[ http://nagoya.apache.org/jira/browse/GERONIMO-403?page=history ]
David Jencks closed GERONIMO-403:
-
Assign To: David Jencks
Resolution: Fixed
Fix Version: 1.0-M3
implemented
> Split j2ee module into j2ee and j2ee-builder
>
[ http://nagoya.apache.org/jira/browse/GERONIMO-418?page=history ]
David Jencks closed GERONIMO-418:
-
Assign To: David Jencks
Resolution: Fixed
Fix Version: 1.0-M3
implemented
> Split naming module into naming and naming-builder
> --
[ http://nagoya.apache.org/jira/browse/GERONIMO-405?page=history ]
David Jencks closed GERONIMO-405:
-
Assign To: David Jencks
Resolution: Fixed
Fix Version: 1.0-M3
implemented
> jetty module should be split into jetty and jetty-builder
>
+1 from me.
On Sat, 6 Nov 2004 12:35:01 -0500 (EST), Aaron Mulder
<[EMAIL PROTECTED]> wrote:
> I'd like to remove the current "deployer.jar" tool, remove the
> command-line processing logic from the Deployer class, rename
> "new-deployer.jar" to "deployer.jar" and change the bootstrapper
I'd like to remove the current "deployer.jar" tool, remove the
command-line processing logic from the Deployer class, rename
"new-deployer.jar" to "deployer.jar" and change the bootstrapper to build
the new one instead of the old one. Currently there are two so we'd have
some sort of trans
New CLI deployer should accept foreign JAR file not impl class
--
Key: GERONIMO-449
URL: http://nagoya.apache.org/jira/browse/GERONIMO-449
Project: Apache Geronimo
Type: Improvement
Components: deployment
[
http://nagoya.apache.org/jira/browse/GERONIMO-272?page=comments#action_55142 ]
Srinath Perera commented on GERONIMO-272:
-
To handle the Web Service referances creating the Axis stubs for the Web
Services and binding them (XXLocater) in the JN
I've added all the M3 issues to the M3 release notes. There were
about 60 of them.
There are 120 open issues currently. I don't think I want to add
them all to the "known issues" or "still missing" list, since they'll
drown out the positive changes and many of them are build o
[ http://nagoya.apache.org/jira/browse/GERONIMO-360?page=history ]
Aaron Mulder closed GERONIMO-360:
-
Assign To: Dain Sundstrom
Resolution: Fixed
Fix Version: 1.0-M3
Fixed according to Dain
> wrong tx policy for at least StatefulSession
[ http://nagoya.apache.org/jira/browse/GERONIMO-447?page=history ]
Aaron Mulder closed GERONIMO-447:
-
Assign To: Aaron Mulder
Resolution: Fixed
Fix Version: 1.0-M3
> Schema dir missing openejb-jar.xsd
> --
[ http://nagoya.apache.org/jira/browse/GERONIMO-448?page=history ]
Aaron Mulder updated GERONIMO-448:
--
Summary: OpenEJB ITests Fail under Sun JDK 1.5.0 (RMIoverIIOP failure)
(was: OpenEJB ITests Fail under Sun JSK 1.5.0 (RMIoverIIOP failure))
> OpenEJ
OpenEJB ITests Fail under Sun JSK 1.5.0 (RMIoverIIOP failure)
-
Key: GERONIMO-448
URL: http://nagoya.apache.org/jira/browse/GERONIMO-448
Project: Apache Geronimo
Type: Bug
Components: OpenEJB
Reporte
Schema dir missing openejb-jar.xsd
--
Key: GERONIMO-447
URL: http://nagoya.apache.org/jira/browse/GERONIMO-447
Project: Apache Geronimo
Type: Bug
Components: buildsystem
Reporter: Aaron Mulder
In the main Geronimo assembly, t
23 matches
Mail list logo
