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

[Design of POJO Server] - refactoring visitor in VFS

by bill.burke＠jboss.com

The VisitorAttributes usage seems very unclean, why not just change the Visitor interface to be: public interface VFSVisitor { public boolean visitTreeBranch(VirtualFile vf); public void visitLeaf(VirtualFile vf); } visitTreeBranch() returns true if you want to recurse into it. Gives the developer more control over how to recurse. So, if you want to remove isArchive() the Visitor can still find out if the VF is an "archive" or not by querying the deployment context. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976331#3976331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976331

19 years, 6 months

1
0
0 / 0

[Design of POJO Server] - removing isArchive()

by bill.burke＠jboss.com

Are you sure that is really wise? With JAR DeploymentUnits, you still have the issue of nest jars being in the classpath and you will want a way to be able to visit resources in the classpath without recursing the nested jar (or directoy that is a deployment unit). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976325#3976325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976325

19 years, 6 months

1
0
0 / 0

[Design of JBoss Portal] - Re: JBOSS Portal, JSF, XHTML and AJAX !!!finally!!! :-)

by tzimmer

Hi Danijel, when will there be an downloadable version of your code? I´m really interessted in that. Regards, TZ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976324#3976324 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976324

19 years, 6 months

1
0
0 / 0

[Design of JBossCache] - Re: PojoCache physical POJO field mapping and region

by bstansberry＠jboss.com

It would be good if when I call getChildrenNames() the resulting set doesn't include _JBossInternal_. Having that exposed to user code as a child is the only downside I see to what you propose. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976316#3976316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976316

19 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Allowing multiple AbstractParsingDeployer to work with t

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : "scott.stark(a)jboss.org" wrote : | | Where is the metadata model going and how is it relating to the current org.jboss.metadata? | | | | Not sure what you are asking. Let me answer both questions :-) | ... | Just whether the current org.jboss.metadata classes will continue to exist so that I can finish up an initial pass of the web-app 2.4 runtime deployer prototype. I have the metadata part done and now just need to complete the real web app deployer. "adrian(a)jboss.org" wrote : | EJB3 has their own factory(ies) as well. | Right, I have merged the ejb3 web tier factories with the legacy XmlLoadable stuff to have a unified org.jboss.metadata based model with the org.jboss.metadata.WebMetaData as the root web app model. I have not updated the ejb3 layers that rely on the duplicate org.jboss.metamodel to use the merged org.jboss.metadata objects. This will need to be done in the context of stuff you are currently working on. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976314#3976314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976314

19 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: .sar showing up multiple times

by bill.burke＠jboss.com

Ok, makes a lot of sense now...THis component notion. Makes rollbacks a lot easier and you depend on the deployment architecture to manage what needs to be rolledback... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976313#3976313 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976313

19 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: all files that make up a deployment unit

by bill.burke＠jboss.com

"adrian(a)jboss.org" wrote : Do what you want, I'll fix it later. | This needs to work on the classpath notion. | | A visitor on the classpath (a concept that doesn't exist | but I suggested you write on an earlier thread) | should not be recursing into nested deployments. I'm fine with using DeploymentUnit.getDeploymentContext().getClassPath() as long as this classpath is equivalent to the notion of a resource loader in the old container. So for instance, a jar within a WAR would be its own DeploymentUnit with a context with a classpath of only that jar (and its manifest references). Bill View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976312#3976312 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976312

19 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Allowing multiple AbstractParsingDeployer to work with t

by adrian＠jboss.org

"scott.stark(a)jboss.org" wrote : | Where is the metadata model going and how is it relating to the current org.jboss.metadata? | Not sure what you are asking. Let me answer both questions :-) 1) I'm creating a JavaEE deployer project that does all the standard/comon stuff then there will be EJBDeployer/WebDeployer projects, etc. This is to seperate the deployer from the container so it can a) do "on demand", b) the metadata model is shared where appropriate, c) the container doesn't need to know anything about how the model is created. 2) The metadata model will be a shared sanitised and refactored model, e.g. I'm splitting BeanMetaData into security, persistence, transactions, methods, etc The org.jboss.metadata will still exist for read only by old container plugins (e.g. user written interceptors). But it will just be a wrapper/mapper to the real metadata model. e.g. | org.jboss.metadata.BeanMetaData | | /** The delegate */ | private EJBeanMetaData delegate; | | /** | * Create a new BeanMetaData. | * | * @param delegate the delegate | * @throws IllegalArgumentException for a null delegate | */ | public BeanMetaData(EJBeanMetaData delegate) | { | if (delegate == null) | throw new IllegalArgumentException("Null delegate"); | this.delegate = delegate; | } | | <snip/> | | /** | * Get the container managed transactions | * | * @return the container managed transactions | */ | public boolean isContainerManagedTx() | { | EJBTransactionMetaData result = delegate.getTransactionConfig(); | if (result == null) | return EJBTransactionMetaData.DEFAULT_CONTAINER_MANAGED_TX; | return result.isContainerManagedTx(); | } | Of course EJBTransactionMetaData should be an annotation with it really coming from the metadata repository so it can be overridden at different levels, e.g. deployment level transaction defaults. anonymous wrote : | I have merged the web tier parsing into population of the root org.jboss.metadata.WebMetaData instance by writing ObjectModelFactory. | I'm using annotations to bind to the schema. See the link I posted to a JBossXB forum post in a comment by itself above. EJB3 has their own factory(ies) as well. anonymous wrote : | It should be schema based however. | Correct. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976303#3976303 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976303

19 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Allowing multiple AbstractParsingDeployer to work with t

by scott.stark＠jboss.org

"weston.price(a)jboss.com" wrote : If you get a chance could you or Stark have Stephen Hawking call and explain the new deployment stuff to me? I am having a hard time understanding anything your saying at this point (actually for about 8 months now) and I thought he could clear things up for me. | Start here: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976301#3976301 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976301

19 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Allowing multiple AbstractParsingDeployer to work with t

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : Ok, FYI I'm currently working on reworking the JavaEE parsing. | | ... | | I'm working on a schema based deployer for JavaEE5 where | EJB2,3, RAR, WAR, CAR, EAR can share the same metamodel. | Where is the metadata model going and how is it relating to the current org.jboss.metadata? I have merged the web tier parsing into population of the root org.jboss.metadata.WebMetaData instance by writing ObjectModelFactory. It should be schema based however. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976299#3976299 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976299

19 years, 6 months

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 October 2006