September 2007 - jboss-dev-forums

[Design the new POJO MicroContainer] - Re: docbook build error

by scott.stark＠jboss.org

Ok, that was it. The pdf is generating again and now the structure looks with the latest checkin. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083620#4083620 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083620

17 years, 1 month

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: DeployerConfig vs. WebMetaData

by anil.saldhana＠jboss.com

So, either the metadata or the deploymentunit sitting in the WebApplication are the current bridge from the Deployer to a Deployment in the web space? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083618#4083618 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083618

17 years, 1 month

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: DeployerConfig vs. WebMetaData

by scott.stark＠jboss.org

That is right. Really, the DeployerConfig is obsolete as the notion of multiple web deployers from a common core is not a reality we have supported for years now. The other point of the current separation was better class loader isolation, but with the new class loading model that will also be obsolete. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083616#4083616 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083616

17 years, 1 month

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - DeployerConfig vs. WebMetaData

by bstansberry＠jboss.com

Wanting to clean up some stuff related to clustered webapp configuration, but first want to be sure I understand how things are meant to work. Looking at DeployerConfig and WebMetaData, it seems like there's some overlap in their usage. Both contain some metadata about a web app. AFAICT, DeployerConfig should contain information that solely tells the deployer how to do the deployment, while WebMetaData would be the place to put things that the webapp itself would need to understand. Metadata that the deployer doesn't care about but the webapp does should be stored in WebMetaData. DeployerConfig has a number of clustering-related properties that based on the above should be stored in WebMetaData rather than in DeployerConfig: cacheName useJK useLocalCache snapshotMode snapshotInterval This will eliminate a bunch of code where TomcatDeployment is passing these values into the clustered session manager one at a time. Instead they all would get passed with WebMetaData. Am I wrong-headed here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083615#4083615 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083615

17 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: Modules depend on jboss-j2ee instead of jboss-javaee

by wolfc

No, they don't. Which ant files did you check? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083614#4083614 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083614

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: WebDeployer settings to a Valve

by scott.stark＠jboss.org

The valve settings can be app specific from the context.xml, so it has to be overridable from some app level settings. A default set of valves configured at the deployer level is fine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083603#4083603 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083603

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: WebDeployer settings to a Valve

by anil.saldhana＠jboss.com

The TomcatDeployment which instantiates the valves has access to the WebApplication instance (which contains the deploymentunit /attachments). This way we can inject the settings from the deployer onto the valve. Anything wrong with this approach? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083595#4083595 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083595

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JCA Deployer Related

by scott.stark＠jboss.org

Its parsed based on the jaxb annotations on the org.jboss.resource.metadata.mcf.SecurityDomainMetaData class. The org.jboss.resource.deployers.ManagedConnectionFactoryParserDeployer is the deployer that controls this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083588#4083588 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083588

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: WebDeployer settings to a Valve

by scott.stark＠jboss.org

The WebMetaData is the correct place in absence of being able to directly configure the valves in a beans.xml descriptor/metadata (which is where we need to get to in terms of jbossweb). Logically a valve should be specified as an aspect with introductions that add the required tomcat interfaces. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083586#4083586 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083586

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: WebDeployer settings to a Valve

by bstansberry＠jboss.com

[OT] Had a hacky way. Gone, as the valve no longer needs info from the deployer. Actually, it was just the old 4.x code left in place. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083585#4083585 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083585

17 years, 1 month

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 September 2007