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

[Design the new POJO MicroContainer] - Re: Moving parsing to JBossXB.Builder/JAXB

by kabir.khan＠jboss.com

Despite having a few things left I now have enough functionality in the JAXB variety to support what the AOPBeansSchemaInitializer does in AS 5. The -beans.xml files using this will probably need to be modified a bit, the main thing is that aspects with properties | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | <aop:aspect xmlns:aop="urn:jboss:aop-beans:1.0" class="org.jboss.test.microcontainer.beans.TestAspectWithDependency"> | <property name="dependency"><inject bean="Dependency"/></property> | </aop:aspect> | </deployment> | will need to be rewritten to | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | <aop:aspect xmlns:aop="urn:jboss:aop-beans:1.0" class="org.jboss.test.microcontainer.beans.TestAspectWithDependency"> | <aop:property name="dependency"><aop:inject bean="Dependency"/></aop:property> | </aop:aspect> | </deployment> | or | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | <aspect xmlns="urn:jboss:aop-beans:1.0" class="org.jboss.test.microcontainer.beans.TestAspectWithDependency"> | <property name="dependency"><aop:inject bean="Dependency"/></aop:property> | </aspect> | </deployment> | I created a new branch so that I would not interfere with the release last week http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132206 If you want me to do a merge to aop-mc-int trunk then let me know. Before this will work I need releases of common-core, and jbossxb (you probably already knew the last one :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138960#4138960 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138960

18 years

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3Deployer and EJB3ClientDeployer order

by wolfc

Ah yes, I was looking at an old setup. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138950#4138950 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138950

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Moving parsing to JBossXB.Builder/JAXB

by alesj

I would like to finish with moving MC parsing to the new JBossXB.Builder. In order to do that, lets first do a status check. :-) Kabir, what's the status of AOP-MC-int and JAXB usage? Since I've seen it moving in and out. :-) Is the SchemaBindingResolver I've modified to use this new stuff in place? Jumping in IDE to SingletonSchemaResolverFactory shows that we already use is: | private SingletonSchemaResolverFactory() | { | // old initializer | addSchema("urn:jboss:aop-beans:1.0", "org.jboss.aop.microcontainer.beans.xml.AOPBeansSchemaInitializer", Boolean.FALSE); | addSchema("urn:jboss:spring-beans:2.0", "org.jboss.spring.deployment.xml.SpringSchemaInitializer", Boolean.FALSE); | addSchema("urn:jboss:osgi-beans:1.0", "org.jboss.osgi.deployment.xml.OSGiSchemaInitializer", Boolean.FALSE); | addSchema("urn:jboss:seam-components:1.0", "org.jboss.seam.ioc.microcontainer.xml.SeamSchemaInitializer", Boolean.FALSE); | // new jaxb | //addJaxbSchema("urn:jboss:aop-beans:1.0", "org.jboss.aop.microcontainer.beans.metadata.AOPDeployment"); | addJaxbSchema("urn:jboss:bean-deployer", "org.jboss.kernel.plugins.deployment.AbstractKernelDeployment10"); | addJaxbSchema("urn:jboss:bean-deployer:2.0", "org.jboss.kernel.plugins.deployment.AbstractKernelDeployment"); | addJaxbSchema("urn:jboss:javabean:1.0", "org.jboss.javabean.plugins.jaxb.JavaBean10"); | 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"); | } | Except for AOP. We've already got people wandering: - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132413 I've put David on hold until I validate that this is all working. Probably the best test will be when I (re)move the old SchemaInitializer. :-) I'll move the initializer code to spring-int. Although predicted by Adrian that I'll eventually complain over this, I'll take my chances. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138944#4138944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138944

18 years

1
0
0 / 0

[Design of Security on JBoss] - Re: Security Injection in AS5

by anil.saldhana＠jboss.com

Thanks Alex for checking it. I think Stefan is trying to install the beans in security-policies-beans.xml (and remove the -service.xml all together). Stefan will provide the details in a little bit. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138937#4138937 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138937

18 years

1
0
0 / 0

[Design of Security on JBoss] - Re: Security Injection in AS5

by alex.loubyansky＠jboss.com

I have just updated my working copy of the AS trunk and replaced the content of the security-policies-service.xml with the xml above. I don't see any error in the log. Am I missing something? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138933#4138933 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138933

18 years

1
0
0 / 0

[Design of JMX on JBoss (JBoss/JMX)] - Re: XMBean NotSerializationExceptions issue

by dimitris＠jboss.org

What exactly you don't understand? Have you looked here? http://jira.jboss.com/jira/browse/JBAS-1955 AFAIK, the change is in 4.2.2.GA and let's you read MBeanInfo remotely. If you try accessing non-serializable fields, it'll throw an exception, which is the "correct" behaviour, anyway. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138931#4138931 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138931

18 years

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-5259, JMS Destination Names is showing as QueueServ

by alesj

This is the same issue as here: - http://www.seamframework.org/Community/SeamExamplesOnJBoss5beta4 And afaik it's not been established yet on what is the real cause. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138929#4138929 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138929

18 years

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3Deployer and EJB3ClientDeployer order

by alex.loubyansky＠jboss.com

The jboss.xml files attached to the case are what Schelly tried manually. Actually those didn't work for me. They failed to deploy due to parsing errors, i.e. home-jndi-name is not allowed as child of ejb-ref. The generated jboss.xml's don't have them. But the circularity issue is still there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138925#4138925 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138925

18 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM-3.2.2 in Tomcat-5.5 and MySQL

by kukeltje

there is a space in the url.... isn't that the cause? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138922#4138922 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138922

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JarEntry as VFS root does not return empty vfspath

by adrian＠jboss.org

"mstruk" wrote : | Ok, I'm trying another thing first - 'set parent to null' approach, that won't require any additional fields. I see two ways of doing it. One is to propagate some extra info based on which each handler can determine - as it's being created - if it is a root handler or not. That approach is processor intensive and requires small changes in many places. Another approach is to introduce setParent(VirtualFileHandler) or setAsContextRoot() method and call it on only one handler as it's assigned to be context root. That approach requires one extra method and one extra call - very elegant. But ... makes handler creation a two-phase process for handlers that become root and makes these handlers mutable. Looking at AbstractVirtualFileHandler I find no reliance on immutability so I don't expect problems. | | | I'm testing a fix made using this approach, and so far everything is working nicely. | | | In the end I'll remove more code cleaning out the current quick fix than add new code for a proper solution :) | | | - marko | Sounds overly complicated. The problem with complicated things is that they generally need workarounds when they don't work as expected leading to workarounds for workarounds (like the state you are in now :-) Why can't a JarEntryHandler just be a root in its own right with JarContext knowing how to properly construct a root handler for a jar entry? Looks to me like "laziness" in that all the code to do the entry handling requires a top level JarHandler where it does the initJarFile() and once that is done, it just does findChild(). i.e. you don't really have a VFS Context for the entry, its for the jar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138899#4138899 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138899

18 years

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 March 2008