I've taken all of the points raised on board and just checked in the
second cut, which splits Spring support into runtime and deploy time
components.
I'm still having trouble getting the Builder spotted by the Deployer,
but as long as I run the DebugConsole config aswell I am OK - I'll look
Spelling mistake
Key: GERONIMO-564
URL: http://issues.apache.org/jira/browse/GERONIMO-564
Project: Apache Geronimo
Type: Bug
Components: kernel
Versions: 1.0-M3
Environment: Windows NT
Reporter: Mark DeLaFranier
Priority:
[ http://issues.apache.org/jira/browse/GERONIMO-192?page=history ]
Dain Sundstrom reassigned GERONIMO-192:
---
Assign To: Gianny DAMOUR (was: Dain Sundstrom)
ejbSelect method support
Key: GERONIMO-192
[ http://issues.apache.org/jira/browse/GERONIMO-186?page=history ]
Dain Sundstrom reassigned GERONIMO-186:
---
Assign To: Gianny DAMOUR (was: Dain Sundstrom)
EJB-QL support
--
Key: GERONIMO-186
URL:
[ http://issues.apache.org/jira/browse/GERONIMO-332?page=history ]
Dain Sundstrom reassigned GERONIMO-332:
---
Assign To: David Jencks
Support for service-ref in J2EE App Client
--
Key:
Removing an entity bean does not cancel its timers
--
Key: GERONIMO-565
URL: http://issues.apache.org/jira/browse/GERONIMO-565
Project: Apache Geronimo
Type: Bug
Components: OpenEJB
Versions: 1.0-M3
Rob Harrop wrote:
Jules,
I think it is best to keep the metadata in geronimo-spring.xml, purely
because spring.xml has no support for modifying the XML format. You
want that to be a standard Spring config with no special features.
I though you might say that :-)
We will end up with an xdoclet
Jules,
The Spring config file does not change when new modules are added, it is
generic enough to support most configuration options. For JMX metadata
we currently use interfaces or source level metadata (Commons Attributes
or Annotations). I am working on an XML-based JMX descriptor, but this
Rob Harrop wrote:
Jules,
The Spring config file does not change when new modules are added, it
is generic enough to support most configuration options. For JMX
metadata we currently use interfaces or source level metadata (Commons
Attributes or Annotations). I am working on an XML-based JMX
jsr-77 name changes for Tomcat
---
Key: GERONIMO-566
URL: http://issues.apache.org/jira/browse/GERONIMO-566
Project: Apache Geronimo
Type: Task
Components: Tomcat
Versions: 1.0-M3
Reporter: anita kulshreshtha
[ http://issues.apache.org/jira/browse/GERONIMO-566?page=history ]
anita kulshreshtha updated GERONIMO-566:
Attachment: patch.zip
jsr-77 name changes for Tomcat
---
Key: GERONIMO-566
URL:
Is anybody seeing the following:
java -jar bin\deployer.jar deploy myejbhw.jar
Username: system
Password: manager
Deployment failed
Server reports: javax.management.remote.JMXServerErrorException: Error
thrown during invocation
org.apache.geronimo.kernel.InternalKernelException:
I think you have an out of date version of openejb. You may need to
rebuild it rather than just build it, the signature of that method
changed return type which did not involve any openejb source changes
but makes previously compiled code unable to run as you are seeing.
thanks
david
(haven't discovered a tranql list...)
I'm getting a test failure in tranql on os x
[junit] Running org.tranql.sql.sql92.InjectRegisteredEmptyVisitorTest
[junit] Tests run: 3, Failures: 3, Errors: 0, Time elapsed: 0.308
sec
[junit] [ERROR] TEST
I am just in the process of updating... I was trying to avoid.
I think ibiblio is having troubles: I can access:
http://www.ibiblio.org/maven/mx4j/jars/
However, I can access http://www.ibiblio.org/maven/geronimo/jars
Mark
David Jencks wrote:
I think you have an out of date version of openejb.
Jules Gosnell wrote:
Rob Harrop wrote:
Jules,
The Spring config file does not change when new modules are added, it
is generic enough to support most configuration options. For JMX
metadata we currently use interfaces or source level metadata
(Commons Attributes or Annotations). I am working on
Sigh:
I can't access - http://www.ibiblio.org/maven/mx4j/jars/
Mark wrote:
I am just in the process of updating... I was trying to avoid.
I think ibiblio is having troubles: I can access:
http://www.ibiblio.org/maven/mx4j/jars/
However, I can access http://www.ibiblio.org/maven/geronimo/jars
On Feb 2, 2005, at 7:54 AM, Jules Gosnell wrote:
Jules Gosnell wrote:
Rob Harrop wrote:
Jules,
The Spring config file does not change when new modules are added,
it is generic enough to support most configuration options. For JMX
metadata we currently use interfaces or source level metadata
A couple of questions:
1. If I have a GBean with an attribute port, is this a required entry
in the xml? I am thinking that I can default to port X and if the user
wants to reassing it then they can add the attribute attribute
name=portY/attribute to the XML.
2. Lets say the user wants to
[ http://issues.apache.org/jira/browse/GERONIMO-565?page=history ]
David Jencks closed GERONIMO-565:
-
Resolution: Fixed
Fix Version: 1.0-M4
Added some code the the remove objects to cancel all timers for the entity.
Possibly the code that
David Jencks wrote:
On Feb 2, 2005, at 7:54 AM, Jules Gosnell wrote:
Jules Gosnell wrote:
Rob Harrop wrote:
Jules,
The Spring config file does not change when new modules are added,
it is generic enough to support most configuration options. For JMX
metadata we currently use interfaces or source
On Feb 2, 2005, at 8:12 AM, Mark wrote:
A couple of questions:
1. If I have a GBean with an attribute port, is this a required
entry in the xml? I am thinking that I can default to port X and if
the user wants to reassing it then they can add the attribute
attribute name=portY/attribute to
On Feb 2, 2005, at 8:04 AM, Mark wrote:
To all, most likely Alan,
A little confusion on my end. I was trying to use the
ReferenceCollectionListern to handle adding and removing of
EJBContainers. Originally I was thinking of uisng the ContainerIndex
like the EJBServer does. I have a GBean
Jules Gosnell wrote:
David Jencks wrote:
On Feb 2, 2005, at 7:54 AM, Jules Gosnell wrote:
Jules Gosnell wrote:
Rob Harrop wrote:
Jules,
The Spring config file does not change when new modules are added,
it is generic enough to support most configuration options. For
JMX metadata we currently use
On Feb 2, 2005, at 7:54 AM, Jules Gosnell wrote:
Jules Gosnell wrote:
Rob Harrop wrote:
Jules,
The Spring config file does not change when new modules are added,
it is generic enough to support most configuration options. For JMX
metadata we currently use interfaces or source level metadata
Jules Gosnell wrote:
I would like to change the kernel - I don't think there is much value in
Spring support if the first thing we do is to start eroding its feature
set.
Please not at this time - IMHO changes to the kernel now would pose too
much risk to the rest of the project with the
On Feb 2, 2005, at 5:40 AM, [EMAIL PROTECTED] wrote:
public class SPRConfigBuilder
implements ConfigurationBuilder
{
- protected static final Log
log=LogFactory.getLog(SPRConfigBuilder.class);
- protected static final String
defaultConfigPath=META-INF/spring.xml;
+ protected static
Dain Sundstrom wrote:
On Feb 2, 2005, at 7:54 AM, Jules Gosnell wrote:
Jules Gosnell wrote:
Rob Harrop wrote:
Jules,
The Spring config file does not change when new modules are added,
it is generic enough to support most configuration options. For JMX
metadata we currently use interfaces or
Jeremy Boynes wrote:
Jules Gosnell wrote:
I would like to change the kernel - I don't think there is much value
in Spring support if the first thing we do is to start eroding its
feature set.
Please not at this time - IMHO changes to the kernel now would pose
too much risk to the rest of the
gbean name=interop:type=Server,name=RMIIIOP
class=org.apache.geronimo.interop.rmi.iiop.server.RmiIiopServerGBean
reference
name=ContainerIndexopenejb:type=ContainerIndex/reference
reference
name=Containersopenejb.server:EJBModule=ejbhw,*/reference
Do you really mean to be
On Feb 2, 2005, at 11:50 AM, Mark wrote:
gbean name=interop:type=Server,name=RMIIIOP
class=org.apache.geronimo.interop.rmi.iiop.server.RmiIiopServerGBean
reference
name=ContainerIndexopenejb:type=ContainerIndex/reference
reference
Jules Gosnell wrote:
Jeremy Boynes wrote:
Jules Gosnell wrote:
I would like to change the kernel - I don't think there is much
value in Spring support if the first thing we do is to start eroding
its feature set.
Please not at this time - IMHO changes to the kernel now would pose
too much risk
On Feb 2, 2005, at 8:04 AM, Mark wrote:
In my plan, I have:
1. In the reference for Contains, I have a name pattern for EJBs.
However, I don't seem to be able to add a wildcard to represent
any/all containers. I have tried various settings all result in
either a Malformed exception or
Oh, I'm hanging out on IRC if you want to pop in and say hello (server:
irc.freenode.net, channel #geronimo). I'd love to give you an overview
on how to adapt a protocol for use in OpenEJB and the architecture for
network services. There is plenty of work to be done there.
-David
On Feb
Sorry for that. I was pretty sure to have done a rebuild prior to commit...
Dain, thanks for having fixed this problem.
Gianny
David Jencks [EMAIL PROTECTED] wrote:
(haven't discovered a tranql list...)
I'm getting a test failure in tranql on os x
[junit] Running
some related questions...
Currently the XML plans are not placed in the
geronimo-assembly-1.0-SNAPSHOT.jar, they are placed in
geronimo\modules\assembly\target\plan, which would only be available to
those who build from the source code.
Q1. Should we be relocating the plans so they are
36 matches
Mail list logo
