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

[Design of JBossXB] - Re: How to force strict validation?

by alex.loubyansky＠jboss.com

I think, you should use [ code ] [ /code ] tags for XML. This is not the strictness that is supposed to be enforced by strictSchema. It's a bit confusing. This is XML validation issue. And is supposed to be the responsibility of the XML parser. Although, XB validates model groups (order of elements) to some extent. StrictSchema would affect unmarshalling if for example XbGarbageRoot didn't have name property and the name attribute was present in the XML. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132456#4132456 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132456

17 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Eclipse template wizard plugin directory structure

by mark.little＠jboss.com

A little bit late to this discussion, but I'm never a fan of flat hierarchies. Structure is better. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132455#4132455 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132455

17 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JBM 2.0 Standalone

by ataylor

How do we want to ship a standalone JBM 2 deployment. If we want to use the MC as the bootstrap, as the current JBMBootstrapServer server class does, the makes the MC a dependancy. Alternatively we could just write our own , Server.main(), but this wouldn't be pluggable. Also If its a full JMS Server then the user needs a naming server running, do we ship the JBOSS one as a default? i.e. jnpserver.jar. do we ship using the NullAuthenticationManager, would this be enough for users? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132453#4132453 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132453

17 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Implementing JAXB style parsing for aop-mc-int

by kabir.khan＠jboss.com

"adrian(a)jboss.org" wrote : Question: Do you really want an aop:bean? Is that just for ease of use? No, I didn't understand properly and blindly followed your example :-) Now it makes a lot more sense wrt @XmlAnyElement. I now have | @XmlElements | ({ | @XmlElement(name="aspect", type=AspectBeanMetaDataFactory.class), | @XmlElement(name="interceptor", type=InterceptorBeanMetaDataFactory.class), | @XmlElement(name="bind", type=BindBeanMetaDataFactory.class), | @XmlElement(name="stack", type=StackBeanMetaDataFactory.class), | @XmlElement(name="typedef", type=TypeDefBeanMetaDataFactory.class), | @XmlElement(name="cflow-stack", type=CFlowStackBeanMetaDataFactory.class) | }) | @XmlAnyElement | public void setBeanFactories(List<BeanMetaDataFactory> beanFactories) | { | super.setBeanFactories(beanFactories); | } | and that works great. Thanks for your help View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132452#4132452 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132452

17 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: New package structure

by ataylor

anonymous wrote : Then we have microcontainer stuff which is specific to the bootstrapping of the MC - much of this can probably be removed now. Ok, I'll tidy this up,we still need ServiceLocator as we are still dependant on org.jboss.security.AuthenticationManager' and we need to find it via jndi when deployed under the App server. Also ive left JBMBootstrapServer which bootstraps via the MC, I'm not sure whether we need this or not, it depends on how we want to ship standalone(I'm creating another thread for this). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132450#4132450 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132450

17 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Technology Whitepaper

by Danamin

Hey, I'm currently working on an AOP reflection tool that should support jboss aop. I'm looking for an architectural overview or a document about how the weaving is done in jboss aop. Can anyone give me a clue where I can find such a document so that I don't have to dig trough all the source.... Thanks, Wouter View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132448#4132448 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132448

17 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Eclipse template wizard plugin directory structure

by Kevin.Conner＠jboss.com

Hiya Daniel. What I was trying to say with my last posting was the following :) If you feel that you can change this structure, and make the quickstarts consistent, then please make it happen. I agree that the quickstart structure is not ideal, and that we should change it, but it is important that these changes are consistent. Kev View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132445#4132445 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132445

17 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Implementing JAXB style parsing for aop-mc-int

by adrian＠jboss.org

Also, you changed the .classpath of aop-mc-int to use AOP CR4, but the build/pom.xml still says AOP CR3, so I reverted this change. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132439#4132439 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132439

17 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Implementing JAXB style parsing for aop-mc-int

by adrian＠jboss.org

Question: Do you really want an aop:bean? Is that just for ease of use? It doesn't actually make much difference, except you'll have to reproduce all the MC schema in your schema using your namespace (and maintain it every time it changes ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132438#4132438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132438

17 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Implementing JAXB style parsing for aop-mc-int

by adrian＠jboss.org

"kabir.khan(a)jboss.com" wrote : | My AOPDeployment class | | | @XmlElement(name="bean", namespace="urn:jboss:bean-deployer:2.0", | | | You took me too literally. :-) The example above was only intended to show how the annotations work (you were using them wrong), it wasn't intended to be copied. That's why I said anonymous wrote : | Illustrative example (trying to show how it works): | I've removed the elements that are in the MC namespace which should be handled by the wildcard (@XmlAnyElement) not explicitly listed. What you've defined is a {urn:jboss:aop-beans:1.0}bean and a {urn:jboss:bean-deployer:2.0}bean in your namespace that are children of deployment. But that doesn't override the child elements which will still be in your namespace. i.e. both with have {urn:jboss:aop-beans:1.0}constructor You should let the MC schema define the {urn:jboss:bean-deployer:2.0}bean and use it as a "wildcard". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132437#4132437 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132437

17 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2008