¡¶ÐÂÈ«¹úÍøÂçϵͳ¼¯³É·½°¸´óÈ«¡· + Ô´ÂëϵÁйâÅÌ
Bugs item #635899, was opened at 2002-11-09 13:34
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=635899group_id=22866
Category: None
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 7
Submitted By: Michael Lipp (mlipp)
Assigned to:
Bugs item #635899, was opened at 2002-11-09 13:34
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=635899group_id=22866
Category: None
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Lipp (mlipp)
Assigned to:
lördagen den 9 november 2002 kl 10.03 skrev Chris Kimpton:
It varies - usually none - but sometimes the cvs command spits out
some lock messages - but then carries on...
um ... I am nor as clear as I need to be in my written english ...
When I do a clean co, then build will fail, becouse of
Bugs item #630665, was opened at 2002-10-29 21:32
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=630665group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Leon Doud (ldoud)
Assigned to:
David,
I'm thinking of a minimal that is perhaps smaller than that. I think
that
the MBean API + proxies should be sufficient for many clients.
Currently setting up the sar deployer is done in the jboss startup code,
and the minimal jboss-service.xml is then read in. Without this, how do
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.3.1_06
Java(TM) 2 Runtime Environment, Standard
Title: Nachricht
Fellow
Web-Service-Geeks,
as always
beforetaking 3 weeks off, I tried to break thebuild
;-)
no, just kidding. I
just managed to integrate into head (finally!) the 1.0 release of
Axisincluding some jboss.net extensions wrt e-mail transport of soap
messages as
Matt Munz wrote:
What's wrong with mbeanServer().registerMBean(mmb, name) ?
Thank you matt. That is exactly what I am thinking.
The first time you lookup an EJB or JMS connection, we we lazily force
the client side to have an MBeanServer. Then we register only the
mbeans required to
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.4.1_01
Java(TM) 2 Runtime Environment, Standard
Bugs item #621664, was opened at 2002-10-10 21:18
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=621664group_id=22866
Category: JBossServer
Group: None
Status: Open
Resolution: None
Priority: 9
Submitted By: Joe Simone (jsimone)
Assigned to:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.3.1_06
Java(TM) 2 Runtime Environment, Standard
On 2002.11.09 12:10:20 -0500 Dain Sundstrom wrote:
Matt Munz wrote:
What's wrong with mbeanServer().registerMBean(mmb, name) ?
Thank you matt. That is exactly what I am thinking.
The first time you lookup an EJB or JMS connection, we we lazily force
the client side to have an
Bugs item #621664, was opened at 2002-10-10 18:18
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=621664group_id=22866
Category: JBossServer
Group: None
Status: Open
Resolution: None
Priority: 9
Submitted By: Joe Simone (jsimone)
Assigned to:
A JMX microkernel on the client is an avenue to explore. The focus should
be extending the current dynamic proxy and detached invokers to a kernel
for peer-peer type of computing: agents, grid computing, JMS, RMI callbacks,
distributed caches, and whatever P2P is going by these days.
To me the
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.4.1_01
Java(TM) 2 Runtime Environment, Standard
The build failure is caused by jboss.net which uses /thirdparty/apache-commons that is
missing in a checkout of jboss-head.
After a manual checkout of this module with
cvs co -d apache-commons thirdparty/apache/commons
in the thirdparty directory, the build succeeds. (verified on linux and
Scott,
Interesting.. Do you have this scoped in your mind yet? I mean, Jboss (I
hate how outlook fixes the b in jboss) currently uses JavaGroups,
which assumes a multicast-enabled network. When you get to true
peer-to-peer, you may have a double firewall situation where multicast
doesn't work
Thanks, Adrian fixed it by updating the CVSROOT defs and a clean checkout
has been scheduled.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Harald Gliebe [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
Bugs item #636010, was opened at 2002-11-09 15:34
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=636010group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Archimedes Trajano (trajano)
Number of tests run: 991
Successful tests: 986
Errors:5
Failures: 0
[time of test: 9 November 2002 12:44 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
David Jencks wrote:
Agreed. All I am talking about is an MBean server. If someone wants
more JBoss services on the client side they can do that, but it
shouldn't be required.
Conceptually I like this, but...
Are you thinking that these mbeans won't have any attributes? Or do you
plan to
22 matches
Mail list logo
