[
http://nagoya.apache.org/jira/browse/GERONIMO-511?page=comments#action_56201 ]
Aaron Mulder commented on GERONIMO-511:
---
See also GERONIMO-510 and GERONIMO-345
Remote EJB invocation should use Geronimo thread pools
[
http://nagoya.apache.org/jira/browse/GERONIMO-345?page=comments#action_56202 ]
Aaron Mulder commented on GERONIMO-345:
---
See also GERONIMO-511 and GERONIMO-510
Integrate Geronimo and Derby ThreadPools
non-reference gbean dependencies
Key: GERONIMO-512
URL: http://nagoya.apache.org/jira/browse/GERONIMO-512
Project: Apache Geronimo
Type: New Feature
Components: kernel
Versions: 1.0-M3
Reporter: David Jencks
Assigned
jndi refs should result in dependencies, optionally
---
Key: GERONIMO-513
URL: http://nagoya.apache.org/jira/browse/GERONIMO-513
Project: Apache Geronimo
Type: New Feature
Components: naming
Versions: 1.0-M3
[
http://nagoya.apache.org/jira/browse/GERONIMO-513?page=comments#action_56203 ]
Aaron Mulder commented on GERONIMO-513:
---
In the case of optional references, I would prefer to turn this into an
optional dependency instead of not creating a
[
http://nagoya.apache.org/jira/browse/GERONIMO-513?page=comments#action_56205 ]
David Jencks commented on GERONIMO-513:
---
I don't understand how your proposal would work. I can understand that you
could have needs to be started and needs to
Hi
I do not build OpenEJB etc. from the source. Is it
possible that I am getting a different version of
OpenEJB in which
org.openejb.deployment.OpenEJBMOduleBuilder still
references
org.apache.geronimo.security.GeronimoSecurityException?
Any help will be appreciated.
Thanks
Anita
--- anita
That is what is happening. I think it's possible that the outdated
build of openejb is being refreshed by someone or some process, since a
couple of days ago when I was so incautious as to build geronimo
without -o maven pulled down a copy of openejb with the incorrect class
references. I
I think part of the problem is that I haven't been publishing
builds often enough. I had hoped that the automated process would publish
fairly frequently, but I guess that isn't happening. We need to have the
JARs published when we make packaging changes (like moving exceptions or
moving
If you try a maven -o m:rebuild-all then you'll get the
following error in the Tomcat module:
[echo] Deploying Apache Tomcat configuration
[java] Unable to access jarfile
/data/cvs/geronimo/modules/assembly/target/geronimo-1.0-SNAPSHOT/bin/deployer.jar
This is because
Incorrect Deployment Error
--
Key: GERONIMO-514
URL: http://nagoya.apache.org/jira/browse/GERONIMO-514
Project: Apache Geronimo
Type: Bug
Components: web, deployment, connector
Reporter: Aaron Mulder
Attempted a web application with
GeronimoPolicyConfigurationFactory does not always return same instance
---
Key: GERONIMO-515
URL: http://nagoya.apache.org/jira/browse/GERONIMO-515
Project: Apache Geronimo
Type: Bug
Components:
GeronimoPolicy tries to use guaranteed open PolicyConfigurations as if they are
in service
--
Key: GERONIMO-516
URL: http://nagoya.apache.org/jira/browse/GERONIMO-516
Project: Apache
[ http://nagoya.apache.org/jira/browse/GERONIMO-515?page=history ]
David Jencks resolved GERONIMO-515:
---
Assign To: Alan Cabrera
Resolution: Fixed
Fixed in jetty-deployer branch. needs review.
GeronimoPolicyConfigurationFactory does not
14 matches
Mail list logo