Here is source code that shows all of the above: a persistent XMBean, accessing
it within a web application, creating it as a Seam component, and wrapping the
MBean proxy for safety: http://chiralsoftware.com/master-sauce/. This is still
a work in progress, and in fact it always will be in prog
The issue, in my mind, is that using mbeans doesn't lend itself to the
scenarios I had in mind, with environment (dev, test, stage, etc...) and server
(app01, app02, etc...) specific configs.
However, I'm glad it worked for your situation! Can you put up an example of
how you're using the SA
Actually using MBeans is better than just having it read a config file
somewhere. With the bean, I get to store properties, and yes, that is more
cumbersome than putting them in a config file. But I get to do more: I can
have the bean not only store the path to the file storage directory, but
I just got my SAR working and it is persistent. Now I have to get access to
the SAR's mbean from within the EAR. That seems like that should be easy. And
the persistent SAR itself was pretty easy, and this is a nice way to do all
this, so config parameters can be used from the jmx-console. I
It may be the best option currently, however, this is an issue that is near and
dear to me.
My day job has me working on a pretty nice commercial Java web application
framework, which includes a really well thought out (in my opinion)
configuration mechanism involving a config path (like a clas
>From reading a bunch of pages on the Wiki it looks like what I need to do is
>set up a SAR with a simple persistent xmbean in it. Then I need to have my
>application EJBs find and connect to the mbean that's in the SAR. A bit
>cumbersome but a workable solution. Is this the right way to go?
I could do that, but isn't the app classpath all within the EAR? I want to be
able to ship out an EAR file on a CD and have the sysadmin (who knows nothing
about any of this stuff) be able to copy it into a directory and say, "I'm
done".
My idea right now is to try to do this the JBoss Way. N
How about a properties file. It's loadable from your app anywhere on the apps
claspath.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075130#4075130
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075130
_
Why don't you use a database to save that config file?
Or save the parameters to a table.
Just saying that because if an EAR archive "represents" an application there's
no way to set some config file to that application directly... but I'm just a
noob in JBoss...blahbhlah.
View the original pos
No ideas on this? It sure would be nice to have a properties file somewhere in
JBoss that is external to the EAR that lets me define parameters that are
visible to Seam. Like the location of an uploads directory, etc.
View the original post :
http://www.jboss.com/index.html?module=bb&op=view
10 matches
Mail list logo
