Hey genman
Thanks for your reply.
1. I know everything i need now :)
2. In this case that is not a very big problem, merge file is not big. Better
think that even when we have to write merge files, often we don't have to write
all we need ourselves, anly a part. But hmm... not in this case.
One more thing:
Standard MBean has three default attributes:
- StateString
- State
- Name
My XMBean has only attributes i created. So if i want to provide these
attributes for my XMBean what should i do? Is there any way to enable them, or
i should create attributes myself and change their
vitor_b wrote : But still i need a small clarification or confirmation:
Persistence applies only to situation when we redeploy our mbean or restart
server?
I am not sure that your question is clear. Based on the persistence policy you
select, it will do different things. MBean redeployment
vitor_b wrote : One more thing:
|
| Standard MBean has three default attributes:
| - StateString
| - State
| - Name
|
| My XMBean has only attributes i created. So if i want to provide these
attributes for my XMBean what should i do?
Don't use the code in your post. If you
Hey
Thank you for the reply.
defaltAttributes and defaultOperations work fine with xml using dtd file
version 1.2.
But unfortunately i cannot force my ant task to generate proper xml file for my
xmbean (dtd version 1.0, cannot merge etc.). But that is a completely different
story.
And once
1. You should be exposing start/stop/destroy etc. methods from ServiceMBean. If
your XMBean .xml file does not have them, JBoss cannot call them.
2. I'm not an XDoclet expert, but I do know that merging files is an annoyance.
3. The point of persistence is when you change the attributes of an
