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

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-2520 - HASingleton stopping problem

by ScottMarlow

>From email with Brian: anonymous wrote : For failure to stop, I could see: | | 1) Undeploy service on node that failed. Undeploy could mean stop + destroy, or a true full undeploy. Or just a stop. | 2) Undeploy service across cluster. | 3) Ignore, but don't proceed to start. | 4) Ignore. | 5) Redeploy on failed node. | 6) Redeploy across cluster. | | For failure to start, it would be the same, except you could replace #3 with "Elect a new master". | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013031#4013031 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013031

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : | | We discussed it a while ago (I think some of the major discussions were on | | the jboss-dev mailing list). I called it "policy" configuration at that time. | | | How to find this? :-) | No idea. I had a quick search but I couldn't find anything (or more correctly I found too much). The problem is that "policy" is a pretty common word. ;-) anonymous wrote : | Is this http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85442&postdays=0... it? | Yes, but you'll probably need to follow the links as well. anonymous wrote : | About this issue (Microcontainer and JBossXB) that I came up with: | - http://www.jboss.org/index.html?module=bb&op=viewtopic&t=95841 | Snapshots are ok as long as tagged releases don't get tagged with references to snapshots. i.e. jboss-microcontainer-2.0.0-beta2 should not have any snapshots in the build-thirdparty.xml when it is tagged for release! If it contains snapshot references then the build will be unreproducable when somebody changes the snapshot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013028#4013028 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013028

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JAXBDeployer

by adrian＠jboss.org

Of course we can eventually push these features back into the spec, but we don't have to hold our breaths when we need something important. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013021#4013021 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013021

19 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: JAXBDeployer

by adrian＠jboss.org

Update: I've written a simple JAXB unmarshalling implementation over JBossXB so it is a sort of half-way house solution. JAXB annotations with JBossXB http://www.jboss.com/index.html?module=bb&op=viewtopic&t=101041 The advantages are: 1) We don't have to choose a JAXB implementation which gets forced on the users. 2) We can fix the bugs when there is a problem (my version doesn't have the bug reported above - although it probably has others :-) 3) We can implement new stuff/features like dtd support which is going to be pretty difficult to get into the spec/RI. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013018#4013018 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013018

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: wsimport API, SPI, command line tool, and ant task

by jason.greene＠jboss.com

My position is unchanged. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013016#4013016 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013016

19 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: Support for JAXB annotations

by adrian＠jboss.org

As a side note, I got the repeatable wildcards working. I did this by completely ignoring the RtElementHandler. I've reimplemented all the handlers including the type handlers. So whatever the problem is with the repeatable wildcards it is in the RtElementHandler? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013015#4013015 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013015

19 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Support for JAXB annotations

by adrian＠jboss.org

I've committed some stuff that adds support for JAXB annotations using JBossXB (the unmarshalling part). https://svn.jboss.org/repos/common/jbossxb-builder/trunk/ http://anonsvn.jboss.org/repos/common/jbossxb-builder/trunk/ This was pretty easy to do, since it is very simillar to some other code that I'm working on to construct ManagedObjects for the profile service. Although the code that splits and creates the model for the attributes/elements/wildcards is very ugly. I guess it really needs an intermediate infoset model to make this code nicer. :-) This has support for the most of the basics. I haven't done anything that does things with JAXBElement and theres a couple of things missing like the ValueAdapters that don't map directly to the JBossXB notion, but should be trivial to add? The api I've implemented works in a similar way to JAXB. You don't need a schema, it just creates the xml model from the object model. i.e. object model -> SchemaBinding There's a TODO to integrate this with some other work I did before Christmas where the model is validated against the schema bindings. This allows more strict checking/mapping of the object model to the schema (e.g. you can tell when you forget to map something or did it wrong) i.e. schema -> SchemaBinding <- object model There are also some additional annotations that does extra things beyond what the JAXB annotations allow. The api is not currently a JAXBContext/Unmarshaller but you can do something that is pretty similar with the JBossXB api. Example usage: | SchemaBinding schemaBinding = JBossXBBuilder.build(MyJAXBAnnotatedRoot.class); | Unmarshaller unmarshaller = UnmarshallerFactory.newInstance().newUnmarshaller(); | Object result = unmarshaller.unmarshal(urlString, schemaBinding); | If you want to allow multiple roots that don't appear in the same Object hierarchy then you can do something with a SchemaBindingResolver like this one I used to test wildcards: http://anonsvn.jboss.org/repos/common/jbossxb-builder/trunk/src/test/java... Though that is obviously not a full implementation. :-) Finally, the build is broken since there are a few dependencies in the pom.xml that don't exist in the maven2 repository. But you can add them manually to your local repository until I get this updated properly. You need the latest versions of JBossXB and jboss-container. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013014#4013014 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013014

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by alesj

"adrian(a)jboss.org" wrote : | We discussed it a while ago (I think some of the major discussions were on | the jboss-dev mailing list). I called it "policy" configuration at that time. | How to find this? :-) "adrian(a)jboss.org" wrote : | There is also work to do on how ScopeKeys get constructed | This is very environment specific. | See my comments on the metadata integration thread in the last couple of months. | | Also note that there are two notions of scope (configuration time and runtime). | This is important in the code above where the parent kernel needs to come | from the parent runtime scope, but it is added to local configuration time scope. | Again, this difference is explained in the metadata integration thread. Is this http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85442&postdays=0... it? About this issue (Microcontainer and JBossXB) that I came up with: - http://www.jboss.org/index.html?module=bb&op=viewtopic&t=95841 Is this a problem with my current updates on the common-core and jbossxb? Probably not, since our MC version is also a snapshot one? But once we do MC release, there should be no dependencies on the snapshots, right. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013009#4013009 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013009

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by alesj

"adrian(a)jboss.org" wrote : | The policy xml should be unmarshalled to an object that implements | BeanMetaDataFactory. When the deployment invokes getBeans() | that object will create some BeanMetaData for a POJO | that knows how to install/uninstall data into the MetaData repository. | Ok, this answers my question. :-) I've already written initial policy + XB code - it's in the trunk; along with tests, xsd, common-core and xb update. "adrian(a)jboss.org" wrote : | | | public class Policy implements BeanMetaDataFactory | | { | | public void setScope(ScopeMetaData); | | | | public void setMappings(Map<String, ValueMetaData>) | | | | public List<BeanMetaData> getBeanMetaData() | | { | | // IMPORTANT the Mappings needs to be converted to a MapMetaData | | // such that the injections in ValueMetaData work correctly, i.e. dependencies | | return buildMetaDataRepositoryInstallerBeanMetaData(); | | } | | } | | | Currently I have a separate binding element, which takes any MC value. This should do it for the injection / dependency, right? "adrian(a)jboss.org" wrote : | NOTE: I'm not overly impressed by the name "Policy" | perhaps <metadata> would be a better name? Uf, 'metadata'. We have 'metadata' everywhere - xb, administration, repo, ... I still like 'policy' better (and the fact that the initial code is already written). But I'm open for suggestions, refactoring makes wonders these days ;-). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012997#4012997 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012997

19 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: recursing directories on deployment

by adrian＠jboss.org

NOTE: The other way to do it is to add an empty META-INF subdirectory to the lib/ folder. The JARStructureDeployer should then recognise it as a jar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012987#4012987 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012987

19 years, 2 months

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