You are right of course. It is a solution and I have no idea on how else to do
it either.
But as you said having the url as part of the identifier is ugly. and if it is
the only thing that differs to items from different modules it is even uglier,
because the url itself does not have a meaning.
A vendor is free to add his own extensions to the jsr77 base stuff, and while I
look more to it, I understand that knowing the actual deployment url is
something useful.
The ugly part is to have this url in the objectname, although my guess is that
most management tools will not show this.
On
It would solve the problem. Although it would expose information that should
not be avialable via J2EE management, right?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939856#3939856
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
I'm looking into ways of solving this. The idea for a parent module won't solve
all problems, I think.
For example consider:
deploy/test-service.xml
deploy/management/test-service.xml
You get the same problem, but there is certainly no notion of an enclosing
parent module here.
For the way jb
No, definitly not. That bug was reported by me. The problem there is that the
cleanup for ResourceAdapters is not doing all it should.
This is an initialization problem.
Scott, if you have no objections I will enter a bug report
View the original post :
http://www.jboss.org/index.html?module=
Yes, add a bug, and no it has nothing to do with JBAS-1281
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862703#3862703
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862703
--
Or is it the same problem as this unresolved bug :
http://jira.jboss.com/jira/browse/JBAS-1281 ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862702#3862702
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862702
---
Exactly!
+1
Shall I add a bug entry?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862697#3862697
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862697
---
The SF
There should be a parent module name in the same way an ejb-jar in an ear has a
parent name to define the scope.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862696#3862696
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=repl
oh the forum drop something:
[jar-file]/[path]/fti-service.xml
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862549#3862549
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862549
-
Thanks, I found it.
I have two service files in two different jar files that have the same name.
thus:
2005-01-18 10:58:17,447 INFO [org.jboss.management.j2ee.ServiceModule]
Registration is not done -> stop
2005-01-18 10:58:17,460 DEBUG [org.jboss.management.j2ee.ServiceModule] Could
not crea
This is the JSR77 implementation that monitors deployment notifications of
.ear, .war, .sar, .etc, and maintains its own "standard" view of MBeans.
The message is not something to worry about, it's coming from
ServiceMBeanSupport baseclass. as if it tries to create on of those management
mbeans
12 matches
Mail list logo
