November 2009 - jboss-dev-forums - Jboss List Archives

[JBoss AS Development] - Re: JBAS-7469, move bootstrap class loading into profile

by scott.stark＠jboss.org

Ultimately there should just be a repository that serves all artifact contents, be it library jars, server deployments, etc. Right now the problem is that the server install structure is a reflection of the repository. There should be a disconnect between the repository store, and what actually is getting pulled into the bootstrap classpath. The deployments should just have references to the package dependencies which are then resolved from the repository. In terms of the messiness of the directories, its mostly just an issue of needing to have client facing variations so that they know where to put libraries and deployments without worrying about how it affects the server class isolation as well as knowing what customization they have made. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266821#4266821 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266821

16 years, 4 months

1
0
0 / 0

[JBoss Tools Development] - Re: [Struts Flow Editor Bug] any solution or advise for debu

by keibun

Thanks scabanovich! I'm surprised at your quick response and clear explanation. my team heavily use struts flow editor. I owe you very much, thank you! I want to contribute to development as much as posible, I'm very new to jboss community, so would you tell me some manner at the community? 1. When finding problem which is better ? a. reporting to "develper forum" b. creating issue on JIRA. 2. Is there any good develor tutorial for develper who want to send patch or participating develpment process. I'm also interested where most core jboss developer gathers, e.g mailing list or forums. 3. Should I do something agains bug which I reported? Will this bug be fixed by someone and when? I'm not sure I can fix this bug quickly so I want to know how reported bug are treated in general. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266815#4266815 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266815

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: Supporting qualifiers in MC

by kabir.khan＠jboss.com

It seems the metadata for the context is created after the context is described. From some breakpoints | QualifierMetaData.describeVisit(MetaDataVisitor) line: 59 | DescribedMetaDataVisitor(AbstractMetaDataVisitor).internalDescribeVisit(MetaDataVisitorNode) line: 137 | DescribedMetaDataVisitor(AbstractMetaDataVisitor).describeVisit(MetaDataVisitorNode) line: 87 | AbstractBeanMetaData(AbstractFeatureMetaData).describeVisit(MetaDataVisitor) line: 106 | DescribedMetaDataVisitor.run() line: 53 | AccessController.doPrivileged(PrivilegedAction<T>) line: not available [native method] | AbstractKernelControllerContext.infoprocessMetaData() line: 249 | AbstractKernelControllerContext.setBeanInfo(BeanInfo) line: 180 | PreInstallAction.installActionInternal(KernelControllerContext) line: 89 <<< | PreInstallAction(InstallsAwareAction).installAction(KernelControllerContext) line: 54 | | BasicMetaDataRepository.addMetaDataRetrieval(MetaDataRetrieval) line: 109 | KernelScopeInfo(AbstractScopeInfo).addMetaData(MutableMetaDataRepository, ControllerContext) line: 126 | BasicKernelMetaDataRepository.addMetaData(ControllerContext) line: 70 | PreInstallAction.installActionInternal(KernelControllerContext) line: 95 <<< | PreInstallAction(InstallsAwareAction).installAction(KernelControllerContext) line: 54 | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266811#4266811 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266811

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: MemoryMetaDataLoader not threadsafe?

by kabir.khan＠jboss.com

Or rather if putIfAbsent() was there, it would be a user error if not used when contention could occur. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266809#4266809 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266809

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: MemoryMetaDataLoader not threadsafe?

by kabir.khan＠jboss.com

So how are you going to fix it? :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266808#4266808 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266808

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: Supporting qualifiers in MC

by kabir.khan＠jboss.com

Forgot to mention, the above method is from a MetaDataVisitorNode class View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266806#4266806 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266806

16 years, 4 months

1
0
0 / 0

[JBoss Portal Development] - Re: setting up portlet user attributes for hosted portlets i

by chenwang

Thanks for the reply Andy. Yes jboss portal and other popular portals should support a way of supplying/customising user attributes but my question is about jboss portlet container which, out of box, doesn't seem to have clear instruction of how to do it. We're basically implementing a portal using the portlet container plus our own code for identity, group and layout management because of the migration need from our previous portal. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266805#4266805 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266805

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: Supporting qualifiers in MC

by kabir.khan＠jboss.com

The requirements for the usage of MDR are clearer after our team call. For the record, supplied qualifiers should be read from the MDR so that qualifiers can be applied on for example deployment level. I've stumbled upon this though when trying to populate the MDR with qualifers, that the mutable scope has not been created yet: | public void describeVisit(MetaDataVisitor vistor) | { | super.describeVisit(vistor); | KernelControllerContext context = vistor.getControllerContext(); | | MetaDataRetrieval retrieval = context.getKernel().getMetaDataRepository().getMetaDataRepository().getMetaDataRetrieval(context.getScopeInfo().getMutableScope()); | if (retrieval instanceof MutableMetaData) | { | /At this stage retrieval is null | } | I'm still a bit wooly on the MDR stuff, so I might be doing something wrong View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266804#4266804 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266804

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: MemoryMetaDataLoader not threadsafe?

by alesj

Even putIfAbsent doesn't completely solve your problem. e.g. what if something just adds something while you're doing the merge? Or is that what you meant by "For simple values this will probably be fine"? But then the first one wins. :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266803#4266803 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266803

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - MemoryMetaDataLoader not threadsafe?

by kabir.khan＠jboss.com

Although it will not happen when describing this metadata class, the following does not look very thread safe to me. | @Override | public void describeVisit(MetaDataVisitor vistor) | { | super.describeVisit(vistor); | KernelControllerContext context = vistor.getControllerContext(); | MetaDataRetrieval retrieval = context.getKernel().getMetaDataRepository().getMetaDataRepository().getMetaDataRetrieval(context.getScopeInfo().getMutableScope()); | if (retrieval instanceof MutableMetaData) | { | MetaDataItem<?> item = retrieval.retrieveMetaData(QUALIFIER_KEY); | //TODO - The following is not threadsafe | List<Object> list = null; | if (item == null) | { | list = new CopyOnWriteArrayList<Object>(); | ((MutableMetaData)retrieval).addMetaData(QUALIFIER_KEY, list, List.class); | } | else | { | list = (List<Object>)item.getValue(); | } | list.addAll(getEnabled()); | } | } | Since MDR is considered for general usage, it might be an issue if two different threads need to do something similar. i.e. check for existance of metadata then add metadata. addMetaData() seems to overwrite what is there so a check is needed, unless ConcurrentMap.putIfAbsent () semantics are added. For simple values this will probably be fine, last one wins and overwrites, but for things like collections we should have the possiblity to merge the new collection and the exisiting collection, if that is what is intended. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266800#4266800 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266800

16 years, 4 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 November 2009