So I made our JVM implementation support the JVMStats interface
from JSR-77, and added some AJAX so the server info portlet refreshes the
memory figures. That is too cool! :) It's no graph, but hey.
Aaron
[
http://issues.apache.org/jira/browse/GERONIMO-975?page=comments#action_12322610
]
Stefan Schmidt commented on GERONIMO-975:
-
Upon further research I found in the WS-I BasicProfile-1.1
Sachin Patel wrote:
Yes, I think this is needed. Since these are eclipse plugins to begin
with I consider these to be part of the project configuration. Eclipse
users should be able to directly import these projects into Eclipse
without having to generate the .classpath.
As long as these
Hmmm now that I think about this...
Sachin, these files will likely get overwritten when someone does a
maven eclipse. Be prepared for these to get overwritten fairly often,
and will likely get rechecked in.
Jeff
Jeff Genender wrote:
Sachin Patel wrote:
Yes, I think this is needed.
Yes, the same configuration works on all platforms and it contains no
machine specific info.
Jeff Genender wrote:
Sachin Patel wrote:
Yes, I think this is needed. Since these are eclipse plugins to begin
with I consider these to be part of the project configuration.
Eclipse users should
-1 because this will modify the public API defined by the specification
classes which will cause the signature tests to fail. These constants
must be moved elsewhere.
I can't confirm this because openejb no longer builds with rebuild-all
(as it depends on the older rc4 version).
--
Jeremy
Hmm. The spec doesn't actually define a Java-level API, it's all
in UML and stuff. What signature tests can we run against it?
In any case, sorry I forgot to put in the OpenEJB change. It's in
now, though we can revert them both if it's causing tests to fail.
Aaron
On Sun, 4
Sachin Patel wrote:
Could we just prevent that by overriding the maven:eclipse goal in the
projects' maven.xml and echo out a message stating a message that no
.classpath generation is necessary since these are already eclipse
projects?
Lets get others' input on this. If the .classpath
Aaron Mulder wrote:
Hmm. The spec doesn't actually define a Java-level API, it's all
in UML and stuff. What signature tests can we run against it?
http://java.sun.com/j2ee/1.4/docs/api/javax/management/j2ee/statistics/Statistic.html
Signature tests are part of the J2EE TCK. I
On Sun, 4 Sep 2005, Jeremy Boynes wrote:
http://java.sun.com/j2ee/1.4/docs/api/javax/management/j2ee/statistics/Statistic.html
Signature tests are part of the J2EE TCK. I tweaked OpenEJB and ran
those tests and can confirm that they now fail.
OK.
Aaron
[ http://issues.apache.org/jira/browse/GERONIMO-977?page=all ]
Jeremy Boynes closed GERONIMO-977:
--
Fix Version: (was: 1.0-M5)
Resolution: Fixed
Security beans need a reference to the login service so they can initialize the
login module
One last statement before everyone else throws there two cents in :)...
I strongly believe that including this is a necessity. Unlike geronimo,
these aren't regular java projects that can be adapted to invoke within
a users context and IDE choice and that can be launched different ways.
Aaron Mulder wrote:
On Sun, 4 Sep 2005, Jeremy Boynes wrote:
http://java.sun.com/j2ee/1.4/docs/api/javax/management/j2ee/statistics/Statistic.html
Signature tests are part of the J2EE TCK. I tweaked OpenEJB and ran
those tests and can confirm that they now fail.
OK.
I reran the
Sachin Patel wrote:
One last statement before everyone else throws there two cents in :)...
I strongly believe that including this is a necessity. Unlike geronimo,
these aren't regular java projects that can be adapted to invoke within
a users context and IDE choice and that can be
So I'm still struggling with the issue of how to figure out which
network connectors go with which network containers. This is a general
problem that applies to Tomcat Jetty (web connectors to web container),
OpenEJB, ActiveMQ, etc. Obviously in typical cases you'd only have one
On Sep 4, 2005, at 4:10 PM, Aaron Mulder wrote:
So, put all this together, and anything that's stopped is
effectively invisible. One way to make it work is to put the
relationship
into the ObjectName and query based on ObjectName. For example,
On Sun, 4 Sep 2005, Dain Sundstrom wrote:
I suggest you follow JSR77 naming rules and include a fully specified
name such as:
geronimo.server:
j2eeType=WebConnector,
name=MyConnector,
WebContainer=MyJettyContainer
J2EEModule=org/apache/geronimo/Server,
On Sun, 4 Sep 2005, Aaron Mulder wrote:
That being the case, as far as I can tell there's only one
alternative. That is to use a kernel query to list all connectors of the
correct type. Then for each one, get its GBeanData, and pick out the
container reference by name, and see what
On Sep 4, 2005, at 5:30 PM, Aaron Mulder wrote:
On Sun, 4 Sep 2005, Dain Sundstrom wrote:
I suggest you follow JSR77 naming rules and include a fully specified
name such as:
geronimo.server:
j2eeType=WebConnector,
name=MyConnector,
WebContainer=MyJettyContainer
On Sun, 4 Sep 2005, Dain Sundstrom wrote:
I suggest you follow JSR77 naming rules and include a fully specified
name such as:
geronimo.server:
j2eeType=WebConnector,
name=MyConnector,
WebContainer=MyJettyContainer
J2EEModule=org/apache/geronimo/Server,
On Sep 4, 2005, at 6:52 PM, Aaron Mulder wrote:
On Sun, 4 Sep 2005, Dain Sundstrom wrote:
But what if there are two containers named MyJettyContainer, one
in Configuration JettyAdminStuff and one in Configuration
JettyUserStuff?
The J2EEModule property above is the configuration name,
21 matches
Mail list logo
