April 2010 - jboss-dev-forums - Jboss List Archives

Re: [jboss-dev-forums] [Management Development] - ProfileService SPI impacts of domain.xml

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] replied to the discussion "ProfileService SPI impacts of domain.xml" To view the discussion, visit: http://community.jboss.org/message/536689#536689 -------------------------------------------------------------- So as an example, an alternative design could involve a singular thread pool management service, which simply reads the domain metadata and creates pools. It would also have some management capability to drain pools, resize them etc. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536689#536689] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - ProfileService SPI impacts of domain.xml

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] replied to the discussion "ProfileService SPI impacts of domain.xml" To view the discussion, visit: http://community.jboss.org/message/536688#536688 -------------------------------------------------------------- One thing to consider is that maybe it doesn't make sense for things like thread pools and connections to be individually deployable, especially if the whole goal is to configure them in one place. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536688#536688] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - Domain model work in AS 6.0.0

by Scott Stark

Scott Stark [http://community.jboss.org/people/scott.stark%40jboss.org] replied to the discussion "Domain model work in AS 6.0.0" To view the discussion, visit: http://community.jboss.org/message/536686#536686 -------------------------------------------------------------- > Brian Stansberry wrote: > > > Yep. This will probably mean some other stuff (iiop, snmp) get pulled in, at least the socket configurations. > > The SBM does provide two other nice benefits: > > 1. The easy-to-specify "for this server offset base port numbers by XX". Which can be a server-level property in a domain model. > 2. A central view to all the port configurations. Which is just a view on the domain model; doesn't mean they all need to be configured in the same place. > I agree that both of these are something we should support. For cross configuration views the domain metadata should have the properties annotated with the view type as an example. > Leave other server.xml stuff (e.g. valves) out of scope? > > It is so common that people do configure valves, so we may have to support them in some manner. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536686#536686] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - ProfileService SPI impacts of domain.xml

by Scott Stark

Scott Stark [http://community.jboss.org/people/scott.stark%40jboss.org] replied to the discussion "ProfileService SPI impacts of domain.xml" To view the discussion, visit: http://community.jboss.org/message/536684#536684 -------------------------------------------------------------- The deployment DSL should have a more admin oriented DSL. Ideally the project provides this and there is a mapping via a ManagedComponent from the admin DSL onto the deployment DSL metadata. I'm not sure how much simpler the integration of the admin configuration vs deployment features can be. Is there something you have in mind? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536684#536684] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [EJB Development] - Allow for configuring default resource adaptor name for the EJB2 MDBs

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] replied to the discussion "Allow for configuring default resource adaptor name for the EJB2 MDBs" To view the discussion, visit: http://community.jboss.org/message/536681#536681 -------------------------------------------------------------- > Alexey Loubyansky wrote: > > IMO, a separate DTD for EAP is even uglier. > > DTDs to be created are jboss_6_0.dtd, jboss_5_x_eap.dtd. And in case we want to support this in 5.x non-EAP versions then also jboss_5_x.dtd. > > Yeah the forking can create a slight mess. One thing that does help though is that once an EAP line starts, we don't do community releases on that branch. So there should only be two descriptors. We could also call EAP 5.0, jboss 5.2, and EAP 5.1 jboss 5.3 etc if we want to keep them incremental. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536681#536681] Start a new discussion in EJB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - Domain model work in AS 6.0.0

by Brian Stansberry

Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] replied to the discussion "Domain model work in AS 6.0.0" To view the discussion, visit: http://community.jboss.org/message/536672#536672 -------------------------------------------------------------- > Scott Stark wrote: > > For the YES, this is my quick overview. Again my concern is having suffucient structure to be able to evolve the domain model, but a sufficiently limited scope in terms of content to be able to have an implementation. > > bindingservice.beans - All of the containers/services intersected by this need associated entries in the domain model such that this configuration can be dropped. Yep. This will probably mean some other stuff (iiop, snmp) get pulled in, at least the socket configurations. The SBM does provide two other nice benefits: 1. The easy-to-specify "for this server offset base port numbers by XX". Which can be a server-level property in a domain model. 2. A central view to all the port configurations. Which is just a view on the domain model; doesn't mean they all need to be configured in the same place. > mod_cluster.sar, > jboss-cache-manager.sar, > jgroups-channel-factory.sar, > deploy-hasingleton-jboss-beans.xml, > farm-deployment-j-b.xml, > hajndi-j-b.xml, > hapartition-jboss-beans.xml, - Need a cluster domain metadata model mod_cluster is a bit of an outlier, as it doesn't require any sort of intra-cluster communication; can be applied to a server-group. > jbossweb.sar/server.xml, > ejb3-connectors-j-b.xml, > remoting3-j-b.xml, > remoting-j-b.xml, > xnio-provider.jar - Need a connector/transport domain metadata model Leave other server.xml stuff (e.g. valves) out of scope? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536672#536672] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - ProfileService SPI impacts of domain.xml

by David Lloyd

David Lloyd [http://community.jboss.org/people/david.lloyd%40jboss.com] replied to the discussion "ProfileService SPI impacts of domain.xml" To view the discussion, visit: http://community.jboss.org/message/536668#536668 -------------------------------------------------------------- Also from the sound of it, it sounded to me like what goes into the domain.xml file should be a layer separate from any deployment DSLs we have (jboss-threads.xml, jboss-logging.xml, jboss-xnio.xml, jboss-remoting.xml are mine so far). If we constrain what goes into the deployment DSLs (which are natural extensions of how the service is installed, not managed) by what goes into the management-oriented domain.xml, we're going to have a hard time carrying that off in a way that doesn't suck. Instead it would be better to have a parallel management-oriented schema (or schemas) which act purely as an override set for what's been installed - though it's going to be really ugly trying to just slap that on top of what we have today. I'd rather do the work of reimplementing all these deployers with a nice, well-thought-out API than be faced with the prospect of hacking anything more on top of them (I think this paradigm is already at its complexity limit before it becomes untenable). -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536668#536668] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - ProfileService SPI impacts of domain.xml

by David Lloyd

David Lloyd [http://community.jboss.org/people/david.lloyd%40jboss.com] replied to the discussion "ProfileService SPI impacts of domain.xml" To view the discussion, visit: http://community.jboss.org/message/536667#536667 -------------------------------------------------------------- > Scott Stark wrote: > > Based on the thread-pool prototyping, BeanMetaDataFactories are going to have their own domain level DSL describing their configuration. What we need to provide in terms of spi/plugin support in jboss-managed is an easy way to map from the configuration metadata to the BeanMetaData the factory produces. > > The jboss-threads project is certainly one we should try to work with to make this connection as easy as possible. The means by which the threads DSL is mapped from XML to a BMDF is purely an implementation detail. We probably don't have a lot of alternatives, but the whole process of going from XML to object model via XB, and then to BeanMetaData via BMDF is pretty clunky. I'd like to at least keep the door open to alternatives, so hopefully we won't be locked too tightly into this model... -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536667#536667] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - To scope or not to scope (domain.xml)

by Brian Stansberry

Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] replied to the discussion "To scope or not to scope (domain.xml)" To view the discussion, visit: http://community.jboss.org/message/536664#536664 -------------------------------------------------------------- Getting to what you describe shouldn't be a huge hurdle; things already largely work this way in AS 5, it's just that the core JGroups and JBC related services, like everything else, are in their own config files. People don't configure a JGroups stack in container configuration files or annotations; at most they indicate what named cache config to use from a centralized set managed by the CacheManager service; that cache config specifies the name of the JGroups stack to use, which again comes from a centralized set from the ChannelFactory service. Those centralized sets are logically under the control of an admin. The stuff I was talking about when I said "the details of what needs to be configured are often disparate between different services, so I'm not sure those configs can profitably be externalized into some common configuration element" was things like load balance policies for remote EJBs, eviction configurations for entity caches, etc. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536664#536664] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - ProfileService SPI impacts of domain.xml

by Scott Stark

Scott Stark [http://community.jboss.org/people/scott.stark%40jboss.org] replied to the discussion "ProfileService SPI impacts of domain.xml" To view the discussion, visit: http://community.jboss.org/message/536655#536655 -------------------------------------------------------------- Based on the thread-pool prototyping, BeanMetaDataFactories are going to have their own domain level DSL describing their configuration. What we need to provide in terms of spi/plugin support in jboss-managed is an easy way to map from the configuration metadata to the BeanMetaData the factory produces. The jboss-threads project is certainly one we should try to work with to make this connection as easy as possible. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536655#536655] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2010