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

[Design of POJO Server] - Re: ManagementView changes

by scott.stark＠jboss.org

"charles.crouch(a)jboss.com" wrote : | | 3) I see two stubbed implementations of ManagementView, they also include this method: | | | public void setView(ProfileKey key, String deploymentName, HashMap<String, PropertyInfo> view) | | throws NoSuchProfileException, IOException | | I think this should be changed to be | | public void setView(ProfileKey key, String deploymentName, ManagedObject view) | | throws NoSuchProfileException, IOException | | and put into the ManagementView interface. | Until we drill into the ManagedObject to attachment metadata property/bean propertymapping I'm not sure the current view notion is adequate. The complexity of the ManagedObject as returned from an ear vs a data source is essentially unbounded. As a collection of changes the profile service saves off its ok, but how tools edit this needs expanding. Certainly related to 4. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995703#3995703 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995703

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: ManagementView changes

by scott.stark＠jboss.org

"charles.crouch(a)jboss.com" wrote : | 2) Currently the only method on ManagementView is | | public ManagedObject getView(ProfileKey key, String deploymentName, String version) | | throws NoSuchProfileException, NoSuchDeploymentException; | | What does the version argument correspond to here? | The version of the managed object view for the deployment. There are two version levels currently, the profile version which defines what deployments are in the profile, and the managed object view which defines the admin changes that have been applied. There is not a global version notion ala svn. The profile version changes when deployments are added/removed. The deployment managed object version changes as admin edits are applied. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995700#3995700 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995700

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: ManagementView changes

by scott.stark＠jboss.org

"charles.crouch(a)jboss.com" wrote : Initial changes/questions... | | 1) Update org.jboss.deployers.spi.management.ManagementView to use | org.jboss.managed.api.ManagedObject | ... | | I guess we need a Beta2? | We have to decouple the elements of the mc as used by jbossas to allow for finer grained artifacts. There should be a jboss-managed snapshot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995699#3995699 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995699

17 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: java:comp.ejb3 versus java:comp

by bill.burke＠jboss.com

I will modify EJB2 container to work the same as EJB3. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995695#3995695 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995695

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - ManagementView changes

by charles.crouch＠jboss.com

Initial changes/questions... 1) Update org.jboss.deployers.spi.management.ManagementView to use org.jboss.managed.api.ManagedObject not org.jboss.deployers.spi.management.ManagedObject nor org.jboss.annotation.management.ManagedObject To do this we need a new release or snapshot of the Microcontainer right? So we can get the jboss-managed.jar (http://anonsvn.jboss.org/repos/jbossas/projects/microcontainer/trunk/mana...) into /thirdparty/jboss/microcontainer/lib. Since /trunk is currently using the MC Beta from November: Implementation-Version: 2.0.0.Beta (build: SVNTag=https://svn.jboss.org/repos/jbossas/projects/microcontainer/tags/J... date= 200611172149) I guess we need a Beta2? 2) Currently the only method on ManagementView is public ManagedObject getView(ProfileKey key, String deploymentName, String version) | throws NoSuchProfileException, NoSuchDeploymentException; What does the version argument correspond to here? 3) I see two stubbed implementations of ManagementView, they also include this method: | public void setView(ProfileKey key, String deploymentName, HashMap<String, PropertyInfo> view) | throws NoSuchProfileException, IOException I think this should be changed to be public void setView(ProfileKey key, String deploymentName, ManagedObject view) | throws NoSuchProfileException, IOException and put into the ManagementView interface. 4) We need the concept of a deployment type in order to support retrieving all ManagedObject's/deploymentName's of a particular type e.g. DataSource either public List<ManagedObject> getViews(ProfileKey key, DeploymentType deploy) | throws NoSuchProfileException, IOException | or | public List<String> getDeploymentNames(ProfileKey key, DeploymentType deploy) | throws NoSuchProfileException, IOException 5) If we're going to have deploymentName in the API for getView() and setView() then ManagedObject needs to be updated to support accessing the associated deploymentName, otherwise if we've got a list of ManagedObjects and we want to update one of them then we're not going to know what to pass into setView() 6) I didn't want to muddy the waters further but clearly we're going to need some concept of setView() representing new deployments, and also removeView() to undeploy/delete existing deployments. I figure we can get to those later, once we've got further on the Read/List api. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995694#3995694 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995694

17 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: java:comp.ejb3 versus java:comp

by wolfc

But what happens then if I make an EJB2 call from an EJB3 session bean? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995691#3995691 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995691

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Moving forward with the profile service mgmt api

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : | The initial construction of DeploymentContexts from the profile | is a problem for the profile service (with or without predetermined attachments). | | Of course the managed object will provide a method to | turn a managed object into its wrapped attachment (metadata object) | for serialization by the profile service. | | The piece that is missing outside the profile service | will be an extension to the deployers api where there will be two links: | | 1) You are a "parsing deployer", tell me what your managed object looks like. | i.e. construct a managed object for this attachment you created. | | 2) You want to support runtime updates (not just redeployment), | then the server side support of the managed object needs a link to the | "real deployer' for the attachment. | For 1), I am relying on a new MainDeployer.process(CLASSLOADER_DEPLOYER) to only process deployments using deployers below a given level/order. For 2), this gets back to the ManagedObject to metadata mapping. A given ManagedProperty can apply to both an attachment metadata property and a kernel bean property. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995685#3995685 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995685

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Moving forward with the profile service mgmt api

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : "charles.crouch(a)jboss.com" wrote : | | 2) Should the org.jboss.deployers.spi.management.ManagementView be updated to use the new ManagedObject api? | | | | The ManagementView looks more like a profile service api than a deployers | or a managed object api? Right, its the bridge between the deployments and ManagedObjects. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995681#3995681 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995681

17 years, 4 months

1
0
0 / 0

[Design of JBoss Internal Benchmarking] - Re: Changes required for using the pooled invoker from the e

by clebert.suconic＠jboss.com

I don't know what version of the KIT you're using, but we used to use UnifiedInvokers on the config, removing UnifiedInvokers will make it fail. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995676#3995676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995676

17 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Why no 3.0.12 version src of gpd on anonyCVS??

by kukeltje

please learn cvs..... jbpm.3 is the module and the CVS is at JBoss, so the webcvs on Sourceforge will not show that View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995636#3995636 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995636

17 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums December 2006