December 2006 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: How does SErviceDeployer register with MC

by bill.burke＠jboss.com

More importantly I need to know how to create a AbstractDemandMetaData to create the dependency. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992079#3992079 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992079

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JACC: Policy Configuration needs to be linked with child

by anil.saldhana＠jboss.com

One JaccPolicy bean per deployment or for all the deployments? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992076#3992076 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992076

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - How does SErviceDeployer register with MC

by bill.burke＠jboss.com

Hoping that somebody will answer before I spend the next hour or so figuring it out myself... But... I need to be able to set up a dependency between an EJBContainer and a datasource deployed. Currently ds.xml creates a set of MBeans (the old shit), just wondering how these MBeans are registered with the MC so that I can create a dependency on them. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992075#3992075 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992075

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: vfs* based URLs

by bill.burke＠jboss.com

almost done with this... I'm running into other non-related problems that prevent me from doing adequet testing View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992070#3992070 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992070

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JACC: Policy Configuration needs to be linked with child

by scott.stark＠jboss.org

I don't really follow the bean example. There are examples of deployers "creating" service beans by setting up the ServiceMetaData for the bean for the ServiceDeployer to pickup. This is just an expression of the bean in terms of its metadata, and includes things like dependencies: | protected void deployWebModule(DeploymentUnit unit, WebMetaData metaData, | AbstractWarDeployment deployment) | throws Exception | { | log.debug("deployWebModule"); | try | { | ServiceMetaData webModule = new ServiceMetaData(); | String name = getObjectName(metaData); | ObjectName objectName = new ObjectName(name); | webModule.setObjectName(objectName); | webModule.setCode(WebModule.class.getName()); | // WebModule(DeploymentUnit, AbstractWarDeployer, AbstractWarDeployment) | ServiceConstructorMetaData constructor = new ServiceConstructorMetaData(); | constructor.setSignature(new String[] { DeploymentUnit.class.getName(), | AbstractWarDeployer.class.getName(), AbstractWarDeployment.class.getName()}); | constructor.setParameters(new Object[] {unit, this, deployment}); | webModule.setConstructor(constructor); | | // Dependencies...Still have old jmx names here | Collection<String> depends = metaData.getDependencies(); | List<ServiceDependencyMetaData> dependencies = new ArrayList<ServiceDependencyMetaData>(); | for(String iDependOn : depends) | { | ServiceDependencyMetaData sdmd = new ServiceDependencyMetaData(); | sdmd.setIDependOn(iDependOn); | } | webModule.setDependencies(dependencies); | | // TODO could create multiple components for the deployment | unit.addAttachment(ServiceMetaData.class, webModule); | } | catch (Exception e) | { | throw DeploymentException.rethrowAsDeploymentException("Error creating rar deployment " + unit.getName(), e); | } | | } | The jacc policy for the deployment could be a kernel bean or service bean. I think what we need is a JaccPolicy instance that manages the lifecycle of all the policy configurations, and a security deployer manages the metadata for this. The first security metadata in a deployment triggers the security deployer to create the JaccPolicy service/kernel bean metadata, and then the jacc policy configuration metadata for components is associated with the JaccPolicy by injection for example. The component deployers need to have a dependency on the JaccPolicy so that the policy lifecycle is triggered before the components are fully started. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992055#3992055 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992055

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JACC: Policy Configuration needs to be linked with child

by anil.saldhana＠jboss.com

Some information from Scott on this: | ***I don't believe the jacc policy linking is being handled correctly currently. In the discussions we had around this in the forums I believed we needed to separate out linking into a separate aspect that had component deployers registering their local policies on whatever the root policy was in the deployment graph. The lifecycle of the aspect is what should be triggering the policy refresh and commit behaviors. This should not be done by deployers. | | ***but we are overusing deployers. Deployers should not be manipulating the runtime state of components. Deployers should only be manipulating metadata that is consumed by the kernel deployer at which point, the lifecycle of the components triggers the correct transition to running objects based on dependencies and aspects associated with the component. | | *** | maybe its just that we are not comfortable with the new model. A large part of it is that what the legacy deployers do is wrong under the mc model, and moving to the correct way of doing this is not a trivial port of code. As the profile service is brought into the picture, we will have to be even more clear about deployer operation as an assembly line that takes metadata in and outputs its transformation without doing too much in terms of assumptions regarding runtime behavior of components. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992037#3992037 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992037

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JACC: Policy Configuration needs to be linked with child

by anil.saldhana＠jboss.com

Scott, I placed a new EARInitializingDeployer that can do jacc policy configuration initialization for the EAR. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992015#3992015 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992015

18 years, 1 month

1
0
0 / 0

[Design of Kosmos] - Re: Performance with many projects

by aron.gombas

anonymous wrote : I would like to see Kosmos appear more quickly and do the data gathering in the background. Is there anything I can configure which would speed this initial startup? Unfortunately, the SVN traversal can be very expensive. There is no way to save this time, otherwise the commit- or file information would not available. After each traversal, the result is cached and redisplayed until the next traversal completes. anonymous wrote : Also, is there a way to disable the informational logging? Kosmos is using log4j for logging, so you can easily configure the logging output as you wish. (You can disable the whole Kosmos logging by disabling it for the hu.midori.kosmos package.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992007#3992007 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992007

18 years, 1 month

1
0
0 / 0

[Design of Kosmos] - Re: Kosmos refresh button

by aron.gombas

Glad that it helped. Yes, you have to. It's updated on the serverside, but you have to reload it in your browser to see the actual changes. (Otherwise we would need to server to force the browser refresh itself, which is hard, but not impossible [with AJAX]). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992002#3992002 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992002

18 years, 1 month

1
0
0 / 0

[Design of Kosmos] - Performance with many projects

by bjoy

I have experimented by configuring Kosmos to monitor many small projects (27 projects each with 13 folders and 8 files) all in the same repository. I have a Liferay portal page with only the Kosmos portlet on it. When I select it, nothing shows for 5 minutes and the Tomcat log grows by 180K. Once the page shows everything works as expected. The Tomcat log shows the timings on executing many Subversion commands. The timestamps agree with the timings and there does not seem to be any gaps. So I think that 5 minutes is mostly spent gathering data. I would like to see Kosmos appear more quickly and do the data gathering in the background. Is there anything I can configure which would speed this initial startup? Also, is there a way to disable the informational logging? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992001#3992001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992001

18 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums December 2006