February 2008 - jboss-dev-forums - Jboss List Archives

[Design of OSGi Integration] - Re: Facade Questions

by johnbailey

Assuming the DeploymentControllerContext is always available to the Bundle, can we also assume the DeploymentControllerContext has also been installed into the Controller? Looking through the DeployersImpl the DeploymentControllerContext is created, installed into the controller, attached to the DeploymentContext, and moved through all known states for the DeployersImpl. So if the Bundle.start method delegates to the DeploymentControllerContext.changeState(...), would it look something like this: | public void start() throws BundleException | { | DeploymentControllerContext deploymentControllerContext = getControllerContext(); | DeploymentContext deploymentContext = deploymentControllerContext.getDeploymentContext(); | | // Go through the states in order | List<ControllerState> states = getControllerContext().getController().getStates(); | for (ControllerState state : states) | { | if (DeploymentState.ERROR.equals(deploymentContext.getState()) == false) | { | try | { | deploymentControllerContext.getController().change(getControllerContext(), state); | } | catch (Throwable t) | { | deploymentContext.setState(DeploymentState.ERROR); | deploymentContext.setProblem(t); | } | } | } | | } | Also, I have completed some other work on the Facade, should I document it on the existing 'OSGI Facade' JIRA http://jira.jboss.com/jira/browse/JBOSGI-8, or create a more detailed task? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131726#4131726 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131726

18 years, 1 month

1
0
0 / 0

[Design of JBoss Portal] - JBoss MC usage in various modules

by julien＠jboss.com

I think it would make sense to have the usage of MC pom (version) driven by the common/mc module. I mean that our modules should not declare the MC version but should rely on the one defined by common/mc if it is possible. To investigate... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131692#4131692 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131692

18 years, 1 month

1
0
0 / 0

[QA of JBoss Portal] - Update to poms

by julien＠jboss.com

I am trying to trim down a bit the pom dependencies we are using to keep only what is necessary. For instance the web module poms declares lot of stuff it does not have to declares: - jbossxb : is not used directly and is already declared by its consumers (microcontainer) - jboss vfs : same - javassist : same However those jars are needed to build test cases, but maven antrun extended plugin is able to resolve the dependencies transitively so it works. The only dependency I am not able to remove is the concurrent oswego jar. For some reason it is used by something but I cannot determine what. I have removed first the dependency of the common module over that concurrent jar (by using java.util.concurrent)... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131691#4131691 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131691

18 years, 1 month

1
0
0 / 0

[Design of JBoss Portal] - Re: future directions (Repost)

by PMN

It sounds excellent to me, thanks sohil. Now I like to get an answer from Julien or Thomas as they both say I can change layout for a page and region for a portlet. It needs to be in the PortalNodeEventListener and for the page being displaid. The classes I get there are PortalNode, PortalRuntimeContext and NavigationalStateContext. PortlaNode has a map of properties and I suppose I could change properties in there, what properties and will it be sufficient? Changing layout needs a full redraw, changing region may not need a full redraw (as opposed as partial refresh), that's why I have doubts about their answer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131645#4131645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131645

18 years, 1 month

1
0
0 / 0

[Design of JBoss Serialization] - Re: JBOSS Serialization & other JBOSS projects

by fredworks

Another question is that whether the JBoss Serialization is used in JBoss AS 4.0.5 (or above) to serialize JNDI binding objects? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131659#4131659 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131659

18 years, 1 month

1
0
0 / 0

[Design of JBoss Portal] - Re: future directions

by PMN

It sounds excellent to me, thanks sohil. Now I like to get an answer from Julien or Thomas as they both say I can change layout for a page and region for a portlet. It needs to be in the PortalNodeEventListener and for the page being displaid. The classes I get there are PortalNode, PortalRuntimeContext and NavigationalStateContext. PortlaNode has a map of properties and I suppose I could change properties in there, what properties and will it be sufficient? Changing layout needs a full redraw, changing region may not need a full redraw (as opposed as partial refresh), that's why I have doubts about their answer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131645#4131645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131645

18 years, 1 month

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: Remoting issue

by ron.sigal＠jboss.com

I went ahead and added the delayed destruction feature to the Remoting 2.4 branch. I a pure Remoting in-jvm test, I got a speed up of about 2 by using delayed client invoker destruction. For more information, see the thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=126382&postdays=.... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131604#4131604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131604

18 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: Moving jbossas to a maven repo for thirdparty

by pgier

Just wanted to give an update on progress of trying to reproduce the thirdparty directory. I decided to work on a new plugin instead of trying to use the standard assembly plugin to do this for two reasons. 1. assembly plugin has no idea how to create libraries.ent 2. the assembly plugin's existing features don't give much advantage over the standard maven stuff available to all maven plugins (downloading dependencies, reading the pom, etc). So far I don't see any technical issues. The only issue is that it will be a bit tedious and time consuming to configure a mapping between the maven names of artifacts and the names that the build scripts expect in the thirdparty folder. But so far, I don't see any reason why I can't have this working by next Friday. I'll give another update probably Tuesday with progress on this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131586#4131586 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131586

18 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: JBossAS CR1 build plan

by scott.stark＠jboss.org

So based on this morning's call there are two possible plans: a. Paul works on reproducing the current local jbossas trunk thirdparty structure from maven artifacts. This requires that the existing jbossas project artifacts are the same as the current jbossbuild artifacts. The steps to build and test the server would be: a1. Build the jbossas projects that ejb3 depends on using maven to make them available via the maven repo. a2. Build ejb3 to make its artifacts available via the maven repo. a3. Build the remaining jbossas projects using maven to make them available via the maven repo. a4. Run an assembly step equivalent to the current build-thirdparty.xml to produce a local thirdparty repository from the maven repository rather than the jbossbuild repository. This allows the existing build/build-distr.xml, testsuite and eclipse project/classpath settings, config files, etc. to remain unchanged. a5. Run the build/build-distr.xml to create the jboss-5.0.0.CR1 distribution structure. a6. Run the testsuite as ususal to validate the artifacts. Note that this either requires that the target directory for the maven builds use the jbossbuild output/lib convention, or the testsuite module classpaths need to be updated to refer to the target/* locations of the maven build. The B plan would be to simply: b1. Build the jbossas projects that ejb3 depends on using maven to make them available via the maven repo. b2. Build ejb3 to make its artifacts available via the maven repo. b3. Upload the ejb3 artifacts to the jbossbuild repository b4. Run the jbossbuild as ususual. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131570#4131570 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131570

18 years, 1 month

1
0
0 / 0

[Design of Management Features on JBoss] - JBAS-5246, Open console support

by scott.stark＠jboss.org

I created a new umbrella issue for open console support issues needing to be resolved for jbossas-5.0.0.CR1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131566#4131566 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131566

18 years, 1 month

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 February 2008