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

[Deployers on JBoss (Deployers/JBoss)] - Re: Ear deployment ordering broken in trunk

by wolfc

It's not about stages. Both ejb deployers and client deployers should have the same stage configuration. It's about the client container (/ component) being dependent on stuff from a sister deployment unit. But the client container doesn't know which sister, or even if there is one. The only thing I can state for certain is that it wants to be last in line (sort of). It's the EAR deployment rules that are not being followed. Note that there is no EAR metadata, so we have to come up with the EAR deployment order. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062827#4062827 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062827

18 years, 9 months

1
0
0 / 0

[Design of JBoss Wiki] - Re: Portal 2.6 support...

by mimra

Well - that's not the only thing that has changed. The org.jboss.portal.identity.User has also been changed. The org.jboss.wiki.JBossPortalCredentials used to call user.getRealEmail() which is no longer available... Any idea on how to get the email address? /Michael View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062823#4062823 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062823

18 years, 9 months

1
0
0 / 0

[Design of POJO Server] - Re: Bean metadata views

by adrian＠jboss.org

There's nothing in what I committed for "flattening" object models which is probably what you're interested in for the datasource. So at least we are not totally duplicating work. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062803#4062803 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062803

18 years, 9 months

1
0
0 / 0

[Design of POJO Server] - Re: Bean metadata views

by adrian＠jboss.org

To avoid you duplicating work, I've committed the stuff I'd got working on the managed object annotations (its very simplistic) and the surrounding infrastructure that lets you override things by registering what I called ManagedObjectBuilder/Populator(s) Now you know why I changed the name in the deployers to ManagedObjectCreator to avoid the confusion. :-) I also committed the metatype updates which includes all the infrastructure for "serializing/deserializing" class trees to and from metatypes and object trees to and from metavalues. This is much more complete, although it is not fully tested. :-( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062802#4062802 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062802

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MAVEN: activation-1.0.2.jar not being fetched

by adrian＠jboss.org

"scott.stark(a)jboss.org" wrote : | Your checkin included a number of invalid references to C:/Java/jdk/jdk1.5.0_10/lib/tools.jar. Why is this needed? I removed its use so that the eclipse projects would build for me. It's coming from a dependency in the javassist pom. God knows why? Javassist has its compiler. It shouldn't need tools.jar? :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062793#4062793 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062793

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MAVEN: activation-1.0.2.jar not being fetched

by adrian＠jboss.org

As far as I can tell from the pom, there are no sun-jaf jars http://repository.jboss.com/maven2/sun-jaf/activation/1.0.2/activation-1.... Although the jars do exist in the repository, nothing I do will download them. There's only sun-jaf that directly references javax.activation if you update deployers-vfs-spi to use sun-jaxb instead of javax.xml.bind View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062787#4062787 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062787

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MAVEN: activation-1.0.2.jar not being fetched

by alesj

I think you need to start using IDEA. Since I don't have that kind of problems ... yet. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062782#4062782 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062782

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MAVEN: activation-1.0.2.jar not being fetched

by adrian＠jboss.org

NPE AGAIN!!!!! :-( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062779#4062779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062779

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MAVEN: activation-1.0.2.jar not being fetched

by adrian＠jboss.org

THIS BUILD IS JUST GETTING STUPID!!!!! I did an svn update and I get NPEs again when trying to do an incremental compile. Another clean and rebuild for me. :-( But then I can't refresh in eclipse because it hasn't downloaded "sun-jaf" I have "javax/activaition". Exactly the opposite of Kabir's problem. How are we going to reproduce a build 6 months to 5 years down the line when two people can't reproduce the same build on the same day? Let's see if blowing away my whole maven repository(again) is going to fix it? Cross your fingers and go make some coffee. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062778#4062778 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062778

18 years, 9 months

1
0
0 / 0

[Design of POJO Server] - Bean metadata views

by scott.stark＠jboss.org

One thing I'm starting to work on in the context of the profile service managed objects/properties are annotations for describing which properties in an aggregate metadata bean structure (org.jboss.resource.metadata.mcf.ManagedConnectionFactoryDeploymentGroup) should be exposed as managed properties. Its possible that the object tree of exposed as the management interface has a different structure (generally flatter). I can see this being used by jmx, jsr77 aspects as well. For example, the security-domain managed property for the nth datasource deployment comes from the ManagedConnectionFactoryDeploymentGroup/deployments[n]/securityMetaData/domain property: | @ManagedObject(...) | class ManagedConnectionFactoryDeploymentGroup | { | List<ManagedConnectionFactoryDeploymentMetaData> deployments = | class ManagedConnectionFactoryDeploymentMetaData | { | @XmlElement(name="jndi-name") | @ManagedProperty(name="jndi-name", required=true, description="...", ...) | private String jndiName; | | @XmlElement(name="min-pool-size") | @ManagedProperty(name="min-pool-size", required=false, ...) | private int minSize = 0; | | private SecurityMetaData securityMetaData = new SecurityMetaData() = | class SecurityMetaData | { | @ManagedProperty(name="security-domain") | private String domain; | | protected SecurityDeploymentType type; | } | } | | } | There is an xpath like aspect for the metadata property being referenced, plus the managed property info. An xpath type syntax for a java bean object structure is a rather general feature that could be part of an object binding library. Did anything like this come out of the jbossxb/jaxb work? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062761#4062761 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062761

18 years, 9 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 July 2007