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

Re: [jboss-dev-forums] [JBoss Web Services Development] - Recent changes on CXF integration

by Richard Opalka

Richard Opalka [http://community.jboss.org/people/richard.opalka%40jboss.com] replied to the discussion "Recent changes on CXF integration" To view the discussion, visit: http://community.jboss.org/message/535998#535998 -------------------------------------------------------------- Good job Alessio. This was real CXF integration improvement we've been missing. The performance bottleneck during deployment time isn't so significant and it can be always solved with using separate worker thread to read the CXF configuration file asynchronously when it will became an real issue. I'd say we should remove CxfServletExt lazy load of the bus because this is broken by design. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/535998#535998] 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-dev-forums] [JBoss Web Services Development] - Recent changes on CXF integration

by Alessio Soldano

Alessio Soldano [http://community.jboss.org/people/alessio.soldano%40jboss.com] replied to the discussion "Recent changes on CXF integration" To view the discussion, visit: http://community.jboss.org/message/535993#535993 -------------------------------------------------------------- > Alessio Soldano wrote: > > > An interesting question now is whether we want this to be the default behaviour or not. Currently there's a system property for choosing when to load the bus, the default is lazy behaviour (load in servlet). > I changed the default behaviour, which is now eager load, during deployment. The point now is whether we want to support the lazy one, which might be useful on user development environment for speeding up boot with many ws endpooints having http binding. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/535993#535993] 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-dev-forums] [JBoss Tools Development] - How to Make Your JUnit Tests Run Faster in Eclipse

by Alexey Kazakov

Alexey Kazakov [http://community.jboss.org/people/akazakov] commented on the document "How to Make Your JUnit Tests Run Faster in Eclipse" To view all comments on this document, visit: http://community.jboss.org/docs/DOC-15108#comment-3089 -------------------------------------------------- Thanks! --------------------------------------------------

16 years

1
0
0 / 0

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

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] replied to the discussion "Domain model work in AS 6.0.0" To view the discussion, visit: http://community.jboss.org/message/535967#535967 -------------------------------------------------------------- IMO we need to at least flesh out the core domain model content/structure, including how multiple servers should be represented, so that we don't end up redoing all of this again. However, we certainly don't have to implement all of it in one stroke. We could for example define a full domain schema, but not implement the clustering portion (require that people manually copy the file around). Once we have done this, we can start looking at timelines. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/535967#535967] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - domain.xml work

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] replied to the discussion "domain.xml work" To view the discussion, visit: http://community.jboss.org/message/535965#535965 -------------------------------------------------------------- > Scott Stark wrote: > > I'm thinking that the profileservice ManagedComponent api is no longer relevant for our discussion. The fact that we introduced an indirection layer to allow for a stable metadata is only one part of what is needed. We need a well defined domain model that describes what the supported administration capabilities are for a given release. Now I'm thinking that the domain.xml is all that matters. Until a feature of the server has a representation in the domain.xml model, its not properly managable. I totally agree. We should focus on the requirements, use-cases and the model/configuration itself. I also agree that something has to be in domain.xml for it to be truly managable. I kind of saw runtime management of components not in domain.xml as more of a stop-gap. However, it probably is easier to just focus on the domain model, and look at the non-classified runtime stuff later, if it is even relevant anymore. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/535965#535965] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - domain.xml work

by Scott Stark

Scott Stark [http://community.jboss.org/people/scott.stark%40jboss.org] replied to the discussion "domain.xml work" To view the discussion, visit: http://community.jboss.org/message/535963#535963 -------------------------------------------------------------- Having IOC type of configuration in the domain.xml really defeats the purpose of IOC as I see it. The endpoint of most injection references should be resolvable via the type/component naming conventions of the spec. The only domain.xml elements that should exist are those that correspond to the non-spec defined container information that would be found in jboss.xml server specific settings. Only for cases where the resolution is ambiguous or one is attempting non-standard behaviors like resolving an endpoint to an bean in another deployment would one need to administer IOC information. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/535963#535963] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - domain.xml work

by Scott Stark

Scott Stark [http://community.jboss.org/people/scott.stark%40jboss.org] replied to the discussion "domain.xml work" To view the discussion, visit: http://community.jboss.org/message/535962#535962 -------------------------------------------------------------- Right. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/535962#535962] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - domain.xml work

by Scott Stark

Scott Stark [http://community.jboss.org/people/scott.stark%40jboss.org] replied to the discussion "domain.xml work" To view the discussion, visit: http://community.jboss.org/message/535960#535960 -------------------------------------------------------------- Each part of the component namespace would include a wildcard properties bag to allow for configuration outside of the domain model to at least exist in the domain model. To have some safety there could be a notion of whether or not a property needed to be understood by the ManagedComponent that maps from the domain model onto deployment metadata. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/535960#535960] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-dev-forums] [Management Development] - domain.xml work

by Scott Stark

Scott Stark [http://community.jboss.org/people/scott.stark%40jboss.org] replied to the discussion "domain.xml work" To view the discussion, visit: http://community.jboss.org/message/535949#535949 -------------------------------------------------------------- I'm thinking that the profileservice ManagedComponent api is no longer relevant for our discussion. The fact that we introduced an indirection layer to allow for a stable metadata is only one part of what is needed. We need a well defined domain model that describes what the supported administration capabilities are for a given release. Now I'm thinking that the domain.xml is all that matters. Until a feature of the server has a representation in the domain.xml model, its not properly managable. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/535949#535949] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

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/535946#535946 -------------------------------------------------------------- I'm doubtful we will have a domain.xml implementation that covers the most common configuration elements we would want in a reasonably full implementation. However, I think the discussion needs to focus on the fact that until we do have a domain.xml implementation, our server is not really managable in a way we can compatibly evolve. The first step in deciding if the 6.0 GA is possible is what the minimal schema that makes the effort worthwhile. The reason I'm doubtful we can have a fully complete implementation is that I envision a fair amount of work to get a mapping implemented that goes from the domain metadata to the corresponding deployment metadata, along with proper handling of persistence, your issue 2. I don't believe we can have the domain.xml be anything other than a centralized configuration file in AS6.0 for sure. 3 is an issue we will have to solve even if the domain.xml is just a centralized configuration file because we still have to write back any changes made via the profileservice that intersect with the domain.xml. I'm of the opinion that until we do define a domain.xml we really do not have a manageable server. The fact that we introduced an indirection layer that allows for JON to create an rhq-plugin.xml type of mapping is still incomplete because short of JON providing the UI to view the supported "domain model", we don't know what components are managable. 4 is not important in terms of implementation version. What matters is that we have a consistent mechanism to administer servers that the AS exposes and maintains the responsibility of compabitily as it evolves. We are taking over the problem that JON has been trying to hack in, and we have been rightly criticized as a weakness. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/535946#535946] Start a new discussion in Management 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-dev-forums April 2010