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

Re: [jboss-dev-forums] [EJB 3.0 Development] - ejb3_1 and its relation with ejb3 bom

by Andrew Rubinger

Andrew Rubinger [http://community.jboss.org/people/ALRubinger] replied to the discussion "ejb3_1 and its relation with ejb3 bom" To view the discussion, visit: http://community.jboss.org/message/536621#536621 -------------------------------------------------------------- > jaikiran pai wrote: > As such, I think that the ejb3 bom as-6 should be the parent for the ejb3_1 module. That way, the ejb3_1 module pom will just declare the dependencies and let the parent bom declare the dependency versions. I think this is good, though there's something worthy of noting here. If the BOM is the parent of the ejb3_1 module, then the ejb3_1 module will have the correct exported dependencies. Now something else, project X, makes a depedendency upon ejb3_1. Any "exclusion"s defined by the BOM will be *ignored*. This is because Project X doesn't have the BOM in its hierarchy. The way around this is to declare in Project X a dependency twice upon ejb3_1; once in "dependencies", once in "dependencyManagement" (with scope import). S, ALR -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536621#536621] Start a new discussion in EJB 3.0 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 3.0 Development] - BOMs Away - Composing Dependency Management

by Andrew Rubinger

Andrew Rubinger [http://community.jboss.org/people/ALRubinger] replied to the discussion "BOMs Away - Composing Dependency Management" To view the discussion, visit: http://community.jboss.org/message/536620#536620 -------------------------------------------------------------- So I'd reused the existing chain (ejb3_1) and put BOM on top. So that the end user is for example AS or the Plugin. Where does the ejb3_1 profile fit in now, or does it at all? S, ALR -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536620#536620] Start a new discussion in EJB 3.0 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/536616#536616 -------------------------------------------------------------- > Emanuel Muckenhuber wrote: > > One thing which would be interesting to look at is how much configuration can actually be shared between a DataGrid and JEE server-group. Probably not a lot; just the info (e.g. URLs or some info needed for discovery) needed for the JEE servers to contact the data grid. For that particular example, it is just aggregation. I like your way of thinking about this for when we discuss in Westford. We need a use case for why heterogeneous servers need to be in the same domain as opposed to in an aggregate view. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536616#536616] 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 Emanuel Muckenhuber

Emanuel Muckenhuber [http://community.jboss.org/people/emuckenhuber] replied to the discussion "To scope or not to scope (domain.xml)" To view the discussion, visit: http://community.jboss.org/message/536614#536614 -------------------------------------------------------------- One thing which would be interesting to look at is how much configuration can actually be shared between a DataGrid and JEE server-group. I mean if it's just the domain name, then it's rather a grouping feature which is most probably easier to do on a aggregation level (JON) than in the domain model itself. Where you would also be able to share a domain across multiple groups. Also based on this we could also see if multi-tier should be done in one domain, where you cannot really share a server-group between different domains. Or if a hierarchical domain would be a better approach trying to solve this common configuration. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536614#536614] 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/536610#536610 -------------------------------------------------------------- > Emanuel Muckenhuber wrote: > In the end - I think if you configure clustering it would make sense to also deploy the needed service. Where you definitely should not care about which deployments are needed for this. Since we are going to have a domain specific model - each fragment could export a requirement on a module. The tricky part about this is the "not care about which deployments are needed for this" bit. Well, thinking about it maybe not all that tricky. :) The clustering services come in 4 general "categories" 1. Core capabilites (jgroups integration, infinispan integration) 2. Remote access stuff (HAPartition for cluster-aware proxies, HA-JNDI). You don't know if this is needed as the requirement comes from * an annotation on an unknown EJB in deploy/ * a completely unknown remote client that wants to use HA-JNDI 3. HASingleton (which is just a different use case for HAPartition), no added services 4. Misc odds and ends So, a <cluster/> element itself implies a need for 1. A couple attributes on <cluster/>, default = true, could control 2 and 3. I'd have to look more closely at the 4 stuff, but I suspect it's either so lightweight we just include it if 2 or 3 are needed, or we can detect the need for it from what other capabilities are required. So, yeah, using <cluster/> as a trigger to add some extra capabilities sounds good. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536610#536610] 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/536606#536606 -------------------------------------------------------------- Good input. While I see multiple groups in a homogeneous domain as a "must-have" to support rolling updates, a heterogeneous domain is just a "nice-to-have". I think this is a topic to clarify with PM input the week of the 19th. We need to be careful though about declaring stuff out of scope that's just going to end up back in scope later. E.g. saying a domain is homogeneous and anything heterogeneous is a JON concern. And then there is a business requirement for JON to support a more expansive view of a domain, a la the multi-tier example I posted above. And then to make that work it ends up having to be shoved back into the domain model with duct tape and baling wire. I'm not saying that will happen, just saying we should be aware of it. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536606#536606] 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] [JBoss Web Services Development] - CXF jms integration

by Alessio Soldano

Alessio Soldano [http://community.jboss.org/people/alessio.soldano%40jboss.com] replied to the discussion "CXF jms integration" To view the discussion, visit: http://community.jboss.org/message/536601#536601 -------------------------------------------------------------- A possible additional issue I can see is that the when the BusDeploymentAspect kicks in, the Bus creation process requires the jms destinations to be already available (did not look at the CXF internals here yet), so the deployers ordering might need additional reasoning changes. It's probably worth checking this early. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536601#536601] Start a new discussion in JBoss Web Services 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] [JBoss Web Services Development] - CXF jms integration

by Alessio Soldano

Alessio Soldano [http://community.jboss.org/people/alessio.soldano%40jboss.com] replied to the discussion "CXF jms integration" To view the discussion, visit: http://community.jboss.org/message/536597#536597 -------------------------------------------------------------- Right, we need proper integration through SPI here. The point is that we need to trigger destination (queue) creation during deployment. That is done using the API a given AS container provides; for instance on AS trunk, right now we'd probably end up creating a configuration for HornetQ to be used by HornetQ deployers (HornetQCoreConfigRealDeployer ?). As Richard's correctly saying, we should not use those AS API directly in JBWS CXF in order to maintain proper abstraction, so we need to enrich the JBossWS SPI (few additions in org.jboss.wsf.spi.deployment might be enough) for having those info (it's probably just the name of the destinations) available in a container independent way. That part of the SPI could be populated by CXF specific deployment aspect that parses the provided or generated jboss-cxf.xml. Later in the chain, we'd have another deployment aspect (coming from the container integration) that uses the new SPI info to create the JMS medatadata (HornetQ conf, for isntance) and provides the requirements for the JMS deployers to run. All this assumes we review the current WSDeploymentAspectDeployer that forces every deployment aspect to be bound to the web deployers, given the JBossWebMetaData input/ouput. I imagine some minor changes might also be required a bit earlier in the deployer chain. Jim, I'd encourage you to create branches like a did when working on cxf/jaxrpc issue and start doing changes there. Either Richard or me can help you step by step there, till we have something working that can be merged to trunk. This way you can also start now that 3.3.0 is not released yet (this work is targeted for 4.x) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536597#536597] Start a new discussion in JBoss Web Services 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 Alexey Loubyansky

Alexey Loubyansky [http://community.jboss.org/people/alex.loubyansky%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/536585#536585 -------------------------------------------------------------- It's true that the best place to put this in is the same xml file where the factories are defined, i.e. (standard)jboss.xml. So, jboss_6_0.dtd makes sense. I don't like the idea of a seperate DTD for EAP though. Putting it in some other xml file and getting it later from some managed bean (which would serve just this purpose) is not nicer. IMO, a system property would be better than that. I can't suggest anything better. So, I guess I'm gonna do the DTDs. I won't be able to complete this earlier than Monday though. Is that ok? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536585#536585] 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] [JCA Development] - JcaXAResourceRecovery

by Jesper Pedersen

Jesper Pedersen [http://community.jboss.org/people/jesper.pedersen] replied to the discussion "JcaXAResourceRecovery" To view the discussion, visit: http://community.jboss.org/message/536584#536584 -------------------------------------------------------------- After some digging around I managed to get the TransactionManagerService into the JMX component using the system-jmx module in AS. So no need to extend the current TMS MBean interface with the recovery methods. Jonathan, I'll keep you in the loop on my progress. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536584#536584] Start a new discussion in JCA 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