April 2010 - jboss-user - Jboss List Archives

Re: [jboss-user] [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/536622#536622 -------------------------------------------------------------- Better reply in other thread: http://community.jboss.org/thread/150500 ejb3_1 and its relation with ejb3 bom S, ALR -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536622#536622] Start a new discussion in EJB 3.0 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [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...]

16 years

1
0
0 / 0

Re: [jboss-user] [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...]

16 years

1
0
0 / 0

Re: [jboss-user] [jBPM] - How to configure 4.3 the right way?

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "How to configure 4.3 the right way?" To view the discussion, visit: http://community.jboss.org/message/536619#536619 -------------------------------------------------------------- Hi Christian, my cache settings are very basic so it could be not fully optimized. As far as I could see Marcel has done more work for that. He added cache as well for collections and child entities. In my case it was only top level entities without any relationship caching. Will try to extend my configuration with those as well. Cheers, Maciej -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536619#536619] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [jBPM] - How to configure 4.3 the right way?

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "How to configure 4.3 the right way?" To view the discussion, visit: http://community.jboss.org/message/536618#536618 -------------------------------------------------------------- Hi Marcel, class attribute is missing due to forum editor - that's why I placed \ in front of it in my post ;) What changes did you do to your hbm.xml files? Is it only cache settings? Would be interesting to see some figures of your tests - could you please post some results with and without cache for your test case? Cheers, Maciej -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536618#536618] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [JBoss Microcontainer] - How to avoid canonical conversion of AbstractInjectionValueMetaData's value?

by jaikiran pai

jaikiran pai [http://community.jboss.org/people/jaikiran] replied to the discussion "How to avoid canonical conversion of AbstractInjectionValueMetaData's value?" To view the discussion, visit: http://community.jboss.org/message/536611#536611 -------------------------------------------------------------- > Ales Justin wrote: > > > I was just wondering how you were able to register non-canonicalized named bean. > Asked too soon. :-) > The name is un-touched, but we do add an alias if it looks like ObjectName. > ... > So, your injection should be able to match it no matter which form (canonical or not) you use, > since it should always be able to hit canonicalized, either from actual name or its alias. I see. So in reality, looks like the other deployer isn't deploying the "jboss.domain:m=xyz,c=pqr" MC bean resulting in that deployment error. But what confused me (and took me on a wrong path :) ) was the error reported this canonical name instead of the original MC bean on which I had added that dependency. That gave me an impression that the dependency was being set on the wrong MC bean. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536611#536611] Start a new discussion in JBoss Microcontainer at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [JBoss Microcontainer] - How to avoid canonical conversion of AbstractInjectionValueMetaData's value?

by Ales Justin

Ales Justin [http://community.jboss.org/people/alesj] replied to the discussion "How to avoid canonical conversion of AbstractInjectionValueMetaData's value?" To view the discussion, visit: http://community.jboss.org/message/536607#536607 -------------------------------------------------------------- > I was just wondering how you were able to register non-canonicalized named bean. Asked too soon. :-) The name is un-touched, but we do add an alias if it looks like ObjectName. /** * Set the aliases<p> * * Aliases in this list only take effect if they are set before installation on the controller * * @param aliases the aliases */ public void setAliases(Set<Object> aliases) { // WARNING: This code is hack for backwards compatiblity // Here we fixup the aliases to map JMX like ObjectNames to their canonical form // I've made it a protected method needsAnAlias so others can subclass and // change the rules (including not doing this at all) // NOTE: This method should be invoked from all constructors if (aliases == null) { // There are no explicit aliases so just see whether the name is an ObjectName. Object alias = needsAnAlias(name); // No alias required if (alias == null) this.aliases = null; else // Add a single alias with canonical name this.aliases = Collections.singleton(alias); } else { // Always clone the aliases passed it this.aliases = new HashSet<Object>(); // Check the main name Object alias = needsAnAlias(name); if (alias != null) this.aliases.add(alias); // Check the aliases for (Object passedAlias : aliases) { this.aliases.add(passedAlias); alias = needsAnAlias(passedAlias); if (alias != null) this.aliases.add(alias); } } } So, your injection should be able to match it no matter which form (canonical or not) you use, since it should always be able to hit canonicalized, either from actual name or its alias. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536607#536607] Start a new discussion in JBoss Microcontainer at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [JBoss Microcontainer] - How to avoid canonical conversion of AbstractInjectionValueMetaData's value?

by Ales Justin

Ales Justin [http://community.jboss.org/people/alesj] replied to the discussion "How to avoid canonical conversion of AbstractInjectionValueMetaData's value?" To view the discussion, visit: http://community.jboss.org/message/536602#536602 -------------------------------------------------------------- To be back compatible - JMX legacy - we check every name against ObjectName and canonicalize it. I was just wondering how you were able to register non-canonicalized named bean. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536602#536602] Start a new discussion in JBoss Microcontainer at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [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...]

16 years

1
0
0 / 0

Re: [jboss-user] [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...]

16 years

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-user April 2010