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

[Design the new POJO MicroContainer] - Re: MC + JAXB (JBossXB Builder)

by adrian＠jboss.org

I also spoke to Alex about getting two new features related to schema config. 1) Lazy initialization of schema bindings. Currently when you configure a class in the bootstrap, it has to exist at startup to be included. e.g. the aop and spring schemas aren't included in JBossAS because they aren't in the bootstrap classes. So you have to configure them manually. It would be better if this was done "on-demand". 2) Allow specification of config in the top level element (similar to the way schema locations are handled) which doesn't require the "2 phase" configuration that is currently done. | <deployment xmlns:jbxb="urn:jbossxb:2.0" jbxb:schemabinding="urn:jbossjms:5.0 org.jboss.jms.Whatever"/> | It would be good if Alex can include these, so they are available for our RC1 release and JBoss5 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133179#4133179 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133179

16 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: New Reflection Project

by scott.stark＠jboss.org

Moving mc up to a peer of jbossas would require creating a new svn repository, with a need for migration from the jbossas repository. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133176#4133176 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133176

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MC + JAXB (JBossXB Builder)

by alesj

"adrian(a)jboss.org" wrote : | We need to double check with Kabir that he isn't forced to ues the classes | from metadata.plugins directly. This may require adding new features to | the BeanMetaDataBuilder. He already did add some new stuff. And I forced him to write the tests for it. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133175#4133175 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133175

16 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: ManagedProject and Dependencies - AOP

by scott.stark＠jboss.org

Ok to all for me. I think the testing can be in the profileservice for now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133174#4133174 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133174

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MC + JAXB (JBossXB Builder)

by adrian＠jboss.org

I also moved the GenericBeanFactoryMetaData2 into the spi and called it GenericBeanFactoryMetaData. Kabir wants to reuse it for AOP. We need to double check with Kabir that he isn't forced to ues the classes from metadata.plugins directly. This may require adding new features to the BeanMetaDataBuilder. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133173#4133173 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133173

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MC + JAXB (JBossXB Builder)

by adrian＠jboss.org

You obviously missed my point about the generated SchemaBInding not matching the xsd. I've fixed all this. I've also made it so there are top level schemas for javabean 1.0, 2.0 and the MC 1.0 and 2.0 the 2.0 and 1.0 were completely missing. For the javabean 1.0 i've disabled the constructor element as per schema. It would be too much effort to retrofit the classes such that we can generate a proper 1.0 schema that matches the xsd (although I did do it for the top level deploymen element). For 3.0 we need to properly control how these metadata classes evolve. Anyway, I re-opened the issue. This work isn't complete until we use it (rather than just testing :-). Work still to do: 0) Do the same thing to the PolicyMetaData/parsing 1) Get a jbossxb release that includes these schemas in the factory settings (see the singleton schema resolver bootstrap code) 2) Remove the old SchemaBindingInitializer 3) Co-ordinate with Kabir for the aop parsing and update the Spring parsing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133172#4133172 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133172

16 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: New Reflection Project

by alesj

"adrian(a)jboss.org" wrote : What I propose to do is to leave the "container" project in the MC | but rename it to "javabean", to include this xml parsing code. Sounds reasonable. A bit off this direct topic or a bit higher in the project hierarchy. I think we should move MC svn directory a bit higher. At the same level as jbossas. And all the new spin-off projects should still be gathered under that directory. But as separate projects - with branches, tags, trunk, ... Microcontainer as a name, should still be understood as the 'cradle' of those (sub)projects. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133171#4133171 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133171

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Changing dependencies in poms

by dimitris＠jboss.org

I believe the issue type "Release" was created some time ago by QA for a different purpose, to track project releases, e.g. http://jira.jboss.com/jira/browse/JBQA-802 I've made a new issue type called "Component Upgrade" for the purpose of tracking updates. Initially, I've marked this new type to be a "subtask" type, because there are usually more than one library upgrades, so it's convenient to group them under a parent task, however, if that seems too restrictive I can change the type to a standard one, so it can appear standalone. What do you think? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133166#4133166 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133166

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Changing dependencies in poms

by alesj

"adrian(a)jboss.org" wrote : | (2) is optional, but it would be friendly, otherwise we end up with different | subprojects referencing different versions (e.g. because only one uses a new feature) | and Eclipse gets confused when running tests or showing source. | Friendly or not :-), you should always be able to create those files from some maven plugin. Like all IntelliJ users have to do it. ;-) And with projects getting mavenized, what's the reason to still keep these .classpath files? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133164#4133164 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133164

16 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Bold Transitions in Workflow-Designer

by kukeltje

I had a quick look out of curiosity and changing the getText() method in org.jbpm.gd.jpdl.part.TransitionOutlineEditPart to protected String getText() { | | String defaultTransitionName = null; | String transitionName = getTransition().getName(); | | transitionName = transitionName == null ? "transition" : transitionName; | | if (getTransition().getFrom().getLeavingTransitionsList().size() > 1) { | defaultTransitionName = getTransition().getFrom().getDefaultLeavingTransition().getName(); | defaultTransitionName = defaultTransitionName == null ? "transition" : defaultTransitionName; | } | | if (defaultTransitionName.equals(getTransition().getName())) { | return transitionName + "\n<default>"; | } else { | return transitionName; | } | } Might already do something. (not tested, not even to java correctness) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133147#4133147 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133147

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