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

[Design the new POJO MicroContainer] - Re: VFS and directory handling

by scott.stark＠jboss.org

"alesj" wrote : | So, I'm probably reading your quote wrong | ""scott.stark(a)jboss.org" wrote : | | A nested jar should simply be seen as a JarInputStream. | | | If by that you mean that URL of nested jar should return JIS, then we're almost there - we return ZIS. | Yes, we should be there is a JarInputStream is returned. "alesj" wrote : | Off topic: | I remember having problems finding MANIFEST.MF file if the IS impl in nested jar handling was JIS, instead of ZIS. Having accessors for the Manifest is basically all JarInputStream adds to the ZipInputStream. Really, from "URL from which an InputStream in jar format can be obtained. ", I don't think a JarInputStream is required as ZipInputStream is in the jar format. Can you validate with the hibernate team that this works for them? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154716#4154716 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154716

16 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation Tests in deployers-vfs

by alesj

OK, I think I now see what you mean. But this still leaves we wondering how we do merging. Since currently we don't care about the duplicates. e.g. I have a BeanMetaData_mybean in unit X. And I also have KernelDeployment in unit X which also contains BeanMetaData_mybean. And I don't see how you can handle this properly and undeply w/o any additional information, e.g. who was there first --> should do the component removal, ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154713#4154713 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154713

16 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation Tests in deployers-vfs

by alesj

"adrian(a)jboss.org" wrote : Ok, but if you do use the class, then you need to make sure it is removed | at undeploy in the scanning deployer otherwise you'll cause a classloader leak. I have a SoftRef on it. | public class DefaultElement<A extends Annotation, M extends AccessibleObject> extends WeakClassLoaderHolder implements Element<A, M> | { | protected String className; | protected Signature signature; | protected Class<A> annClass; | protected Class<M> aoClass; | | private SoftReference<Class<?>> classRef; | And WeakRef on the ClassLoader. | abstract class WeakClassLoaderHolder | { | private WeakReference<ClassLoader> clRef; | | ... | | public class DefaultAnnotationEnvironment extends WeakClassLoaderHolder implements AnnotationEnvironment | Is that OK? Or should I explicitly go and nullify it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154712#4154712 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154712

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by scott.stark＠jboss.org

So Thomas, to be clear, this annotated client and jboss-client.xml override should be producing a metadata ServiceReferenceMetaData with an getAnnotatedElement() pointing to te client field? | public class WSAppclient extends VehicleClient | { | @WebServiceRef(name="service/wsjwsdefaultwebservice") | static com.sun.ts.tests.jws.webservice.webservice1.client.DefaultWebServiceService service = null; | | [532][valkyrie: jar]$ cat META-INF/jboss-client.xml | <?xml version="1.0" encoding="UTF-8"?> | | <jboss-client version="5.0"> | <jndi-name>WSDefaultWebServiceApp_wsappclient_vehicle_client</jndi-name> | <service-ref> | <service-ref-name>service/wsjwsdefaultwebservice</service-ref-name> | <wsdl-override>http://localhost:8080/WSDefaultWebServiceApp/jws/defaultWebService?WSDL&l...> | </service-ref> | </jboss-client> | I don't know where this would have been populated previously. Its only populated for @Resource so I'm not sure has change here either. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154703#4154703 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154703

16 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portal with sticky session enabled in mod_jk

by ankiewsky

Apologize me , I did a question into the wrong place, sorry for any inconvinience. Edgar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154701#4154701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154701

16 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation Tests in deployers-vfs

by adrian＠jboss.org

Ok, but if you do use the class, then you need to make sure it is removed at undeploy in the scanning deployer otherwise you'll cause a classloader leak. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154699#4154699 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154699

16 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - Portal with sticky session enabled in mod_jk

by ankiewsky

Hi Everyone, We have a loadbalancer enabled using mod_jk with just 2 JBoss Servers, when we configure stitcky_session="true", the portal login does not works and a Hibernate Cache problem happens with no clear message about this problem, have some of you guys already tried promote this kind of balancer with this similar scenario? Are there some best practices to do or some tips to configure Portal properly in order to make it works with no errors? Thanks Edgar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154698#4154698 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154698

16 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation Tests in deployers-vfs

by alesj

"adrian(a)jboss.org" wrote : The attachment doesn't actually have to be the annotation if you need other | information from the class that is annotated. e.g. It could be a collection of classes. Yup, exactly what I wanted to point out. Since in my @Bean case, I need the actual class that is annoatted. Otherwise there is no point in having @Bean if you could define the class there. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154696#4154696 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154696

16 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation Tests in deployers-vfs

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | I wanted you to seperate the annotation scanning from the component creation. | i.e the annotation @Bean or a "collection" of them @Beans? | becomes an attachment in its own right. | The attachment doesn't actually have to be the annotation if you need other information from the class that is annotated. e.g. It could be a collection of classes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154694#4154694 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154694

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by scott.stark＠jboss.org

Ok, were not populating this field. We still need some minimal processing of the ws annotations to pass annotated element through. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154691#4154691 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154691

16 years, 7 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 May 2008