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

[Design of POJO Server] - Re: migrating TransactionManager and Invokers to POJO

by adrian＠jboss.org

Obviously deployers are before deploy otherwise you couldn't deploy anything ;-) The jbossweb deployer should not depend on the TM. That dependency should be moved to the jboss.web:service=WebServer mbean like Brian did for the CCM. See the JIRA issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139644#4139644 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139644

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: PropertyReplaceTC failing in maven

by adrian＠jboss.org

Classloading was already updated to use the latest MC. Is this using an (old) snapshot? What does mvn dependency:tree say is getting used? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139642#4139642 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139642

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: VFS::visit on a leaf

by adrian＠jboss.org

I thought you'd already done this as part of the findChild() change? Yes. Visiting a leaf should just be a no-op not an exception. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139641#4139641 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139641

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Parsing more than one file

by adrian＠jboss.org

Again these are implementation details i.e. not requirements for CR1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139640#4139640 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139640

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Parsing more than one file

by adrian＠jboss.org

The parsing multiple files has two parts: 1) Being able to parse n files into one piece of metatdata from one parsing deployer This is so you can deploy something programmatically properly. e.g. You pass EjbJarMetaData. The current parsing deployers will say, ok I'm not going to reparse ejb-jar.xml but I will reparse jboss.xml which is wrong 2) Being able to parse multiple files with the same suffix from META-INF. e.g. META-INF/a-beans.xml META-INF/b-beans.xml should create two KernelDeployment attachments (with the attachment names as the metadata url). But this requires the deployers further down the chain to understand it. i.e. not use getAttachments(KernelDeployment.class) but use getAllAttachments(KernelDeployment.class) and handle the multiple pieces of configuration correctly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139639#4139639 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139639

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Deployers schema

by adrian＠jboss.org

e.g. all this could be made to look a lot nicer and easier to understand with use case xml |  | <bean name="MainDeployer" class="org.jboss.deployers.plugins.main.MainDeployerImpl"> | <property name="structuralDeployers"><inject bean="StructuralDeployers"/></property> | <property name="deployers"><inject bean="Deployers"/></property> | <property name="mgtDeploymentCreator"><inject bean="ManagedDeploymentCreator"/></property> | </bean> | |  | <bean name="ManagedDeploymentCreator" class="org.jboss.deployers.plugins.managed.DefaultManagedDeploymentCreator" /> | |  | <bean name="StructuralDeployers" class="org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl"> | <property name="structureBuilder"> |  | <bean name="StructureBuilder" class="org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder"/> | </property> |  | <incallback method="addDeployer"/> | <uncallback method="removeDeployer"/> | </bean> | |  | <bean name="Deployers" class="org.jboss.deployers.plugins.deployers.DeployersImpl"> | <constructor><parameter><inject bean="jboss.kernel:service=KernelController"/></parameter></constructor> |  | <incallback method="addDeployer"/> | <uncallback method="removeDeployer"/> | </bean> | |  | <bean name="DeclaredStructure" class="org.jboss.deployers.vfs.plugins.structure.explicit.DeclaredStructure"></bean> | |  | <bean name="WARStructure" class="org.jboss.deployers.vfs.plugins.structure.war.WARStructure"> | <property name="webInfLibFilter"> |  | <bean name="WebInfLibFilter" class="org.jboss.virtual.plugins.vfs.helpers.SuffixMatchFilter"> | <constructor><parameter class="java.lang.String">.jar</parameter></constructor> | </bean> | </property> | </bean> | |  | <bean name="JARStructure" class="org.jboss.deployers.vfs.plugins.structure.jar.JARStructure"> |  | <constructor> | <parameter> | <set elementClass="java.lang.String"> | <value>.zip</value> | <value>.ear</value> | <value>.jar</value> | <value>.rar</value> | <value>.war</value> | <value>.sar</value> | <value>.har</value> | <value>.aop</value> | <value>.deployer</value> | <value>.beans</value> | </set> | </parameter> | </constructor> | <property name="candidateStructureVisitorFactory"> |  | <bean name="JARStructureCandidates" class="org.jboss.deployers.vfs.spi.structure.helpers.DefaultCandidateStructureVisitorFactory"> |  | <property name="filter"> | <bean name="JARFilter" class="org.jboss.virtual.plugins.vfs.helpers.SuffixesExcludeFilter"> | <constructor><parameter> | <list elementClass="java.lang.String"> |  | <value>.class</value> | </list> | </parameter></constructor> | </bean> | </property> | </bean> | </property> | </bean> | |  | <bean name="FileStructure" class="org.jboss.deployers.vfs.plugins.structure.file.FileStructure"> |  | <constructor> | <parameter> | <set elementClass="java.lang.String"> | <value>-service.xml</value> | <value>-beans.xml</value> | <value>-ds.xml</value> | <value>-aop.xml</value> | </set> | </parameter> | </constructor> | </bean> | P.S. I'm not saying you should do that now. Concentrate on getting CR1 features done. These are implementation details that can be done after that. If you're not changing a SPI or fixing an important bug then its not a priority for CR1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139635#4139635 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139635

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Deployers schema

by adrian＠jboss.org

What is this rubbish? | Modified: | jbossxb/trunk/src/main/java/org/jboss/xb/binding/sunday/unmarshalling/SingletonSchemaResolverFactory.java | Log: | fix my unintentional commit | | Modified: jbossxb/trunk/src/main/java/org/jboss/xb/binding/sunday/unmarshalling/SingletonSchemaResolverFactory.java | =================================================================== | --- jbossxb/trunk/src/main/java/org/jboss/xb/binding/sunday/unmarshalling/SingletonSchemaResolverFactory.java 2008-03-27 19:59:14 UTC (rev 2761) | +++ jbossxb/trunk/src/main/java/org/jboss/xb/binding/sunday/unmarshalling/SingletonSchemaResolverFactory.java 2008-03-27 23:43:00 UTC (rev 2762) | @@ -69,7 +69,8 @@ | addJaxbSchema("urn:jboss:javabean:2.0", "org.jboss.javabean.plugins.jaxb.JavaBean20"); | addJaxbSchema("urn:jboss:policy:1.0", "org.jboss.beans.metadata.plugins.policy.AbstractPolicyMetaData"); | addJaxbSchema("urn:jboss:classloading:1.0", "org.jboss.classloading.spi.metadata.ClassLoadingMetaData10"); | - addJaxbSchema("urn:jboss:classloader:1.0", " org.jboss.classloading.spi.vfs.metadata.VFSClassLoaderFactory10"); | + addJaxbSchema("urn:jboss:classloader:1.0", "org.jboss.classloading.spi.vfs.metadata.VFSClassLoaderFactory10"); | + addJaxbSchema("urn:jboss:deployers:2.0", "org.jboss.deployers.vfs.plugins.xb.SchemaResolverDeployerMetaData"); | } | Don't you think there's likely to be other top level elements in the deployer's schema? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139631#4139631 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139631

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Is JBVFS-2 resolved

by wolfc

It's still failing at rev 71370: junit.framework.ComparisonFailure: VFS found the wrong manifest expected:<...2> but was:<...1> | at junit.framework.Assert.assertEquals(Assert.java:81) | at org.jboss.test.virtual.test.JARCacheUnitTestCase.test1(JARCacheUnitTestCase.java:106) and so is the ZLIB problem if I don't delete the file: java.io.EOFException: Unexpected end of ZLIB input stream | at java.util.zip.ZipFile$2.fill(ZipFile.java:335) | at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:134) | at java.util.jar.Manifest$FastInputStream.fill(Manifest.java:407) | at java.util.jar.Manifest$FastInputStream.readLine(Manifest.java:343) | at java.util.jar.Manifest$FastInputStream.readLine(Manifest.java:375) | at java.util.jar.Attributes.read(Attributes.java:359) | at java.util.jar.Manifest.read(Manifest.java:167) | at java.util.jar.Manifest.<init>(Manifest.java:52) | at org.jboss.test.virtual.test.JARCacheUnitTestCase.test1(JARCacheUnitTestCase.java:104) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139630#4139630 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139630

16 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: migrating TransactionManager and Invokers to POJO

by jhalliday

OK that helps, thanks Brian. I'm now hitting an issue with the war deployer (from deployers/jbossweb.deployer/) depending on the transaction manager, which I've moved from conf/jboss-service.xml to deploy/transaction-service.xml It seems the startup order is not what I expected. I thought it went: bootstrap, jboss-service.xml; deploy/*, deployers/* but that's not what I'm seeing here. Can any AS gurus shed some light on this? Documentation for the expected behaviour seems to be a bit thin on the ground right now... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139627#4139627 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139627

16 years, 2 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: jee module's alt-dd

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | Remember a deployment can be both an EJB and a Web Deployment, | e.g. webservices where the web metadata is constructed programmatically | by the ws deployers Although I think in this case, the ws deployers run after the parsing so it wouldn't actually conflict in this case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139624#4139624 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139624

16 years, 2 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 March 2008