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

[Design the new POJO MicroContainer] - Re: Scoped Kernels

by bkeh12

Hi,kabir pls,see previously posts for Ales. | <beanfactory name="InterceptedAdvice" class="org.jboss.test.kernel.deployment.test.CalledInterceptor"/> | | <bean name="appScopeObject" class="org.jboss.test.kernel.deployment.support.SimpleObjectWithBean"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> |  | </bean> | | <bean name="AspectManager" class="org.jboss.aop.AspectManager"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment2")</annotation> | <constructor factoryClass="org.jboss.aop.AspectManager" factoryMethod="instance"/> | </bean> | | <bean name="InterceptedAspect" class="org.jboss.aop.microcontainer.beans.Aspect"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment2")</annotation> | <property name="advice"><inject bean="InterceptedAdvice"/></property> | <property name="manager"><inject bean="AspectManager"/></property> | </bean> | | <bean name="InterceptedBinding" class="org.jboss.aop.microcontainer.beans.AspectBinding"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment2")</annotation> | <property name="pointcut"> | execution(* $instanceof{org.jboss.test.kernel.deployment.support.SimpleObjectWithBean}->*(..)) | </property> | <property name="aspect"><inject bean="InterceptedAspect" property="definition"/></property> | <property name="manager"><inject bean="AspectManager"/></property> | </bean> .... result this .. anonymous wrote : | [ScopedKernelController] Error installing to Start: name=InterceptedBinding state=Create | org.jboss.aop.pointcut.ast.TokenMgrError: Lexical error at line 1, column 1. Encountered: "\n" (10), after : "" thank View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021998#4021998 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021998

18 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped Kernels

by bkeh12

Hi,Ales I try this for MC's "ScopingTestCase". | <?xml version="1.0" encoding="UTF-8"?> | | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | |  | | | <beanfactory name="InterceptedAdvice" class="org.jboss.test.kernel.deployment.test.CalledInterceptor"/> | | <bean name="appScopeObject" class="org.jboss.test.kernel.deployment.support.SimpleObjectWithBean"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> |  | </bean> | | <bean name="AspectManager" class="org.jboss.aop.AspectManager"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment2")</annotation> | <constructor factoryClass="org.jboss.aop.AspectManager" factoryMethod="instance"/> | </bean> | | <bean name="InterceptedAspect" class="org.jboss.aop.microcontainer.beans.Aspect"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment2")</annotation> | <property name="advice"><inject bean="InterceptedAdvice"/></property> | <property name="manager"><inject bean="AspectManager"/></property> | </bean> | | <bean name="InterceptedBinding" class="org.jboss.aop.microcontainer.beans.AspectBinding"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment2")</annotation> | <property name="pointcut">execution(* $instanceof{org.jboss.test.kernel.deployment.support.SimpleObjectWithBean}->*(..))</property> | <property name="aspect"><inject bean="InterceptedAspect" property="definition"/></property> | <property name="manager"><inject bean="AspectManager"/></property> | </bean> | | <bean name="deploy1" class="org.jboss.test.kernel.deployment.support.SimpleObjectWithBean"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment1")</annotation> | <property name="simpleBean"><inject bean="simple"/></property> | </bean> | | <bean name="deploy2" class="org.jboss.test.kernel.deployment.support.SimpleObjectWithBean"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment2")</annotation> | <property name="simpleBean"><inject bean="simple"/></property> | </bean> | | <bean name="deploy3" class="org.jboss.test.kernel.deployment.support.SimpleObjectWithBean"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment3")</annotation> | <property name="simpleBean"><inject bean="simpleFromBoot"/></property> | </bean> | | <bean name="deploy4" class="org.jboss.test.kernel.deployment.support.SimpleObjectWithBean"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment4")</annotation> | <property name="simpleBean"><inject bean="simpleFromApp"/></property> | </bean> | | <bean name="simple" class="org.jboss.test.kernel.deployment.support.SimpleBeanImpl"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment1")</annotation> | <constructor> | <parameter>deployment1</parameter> | </constructor> | </bean> | | <bean name="simple" class="org.jboss.test.kernel.deployment.support.SimpleBeanImpl"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment2")</annotation> | <constructor> | <parameter>deployment2</parameter> | </constructor> | </bean> | | <bean name="simpleFromBoot" class="org.jboss.test.kernel.deployment.support.SimpleBeanImpl"> | <constructor> | <parameter>fromBoot</parameter> | </constructor> | </bean> | | <bean name="simpleFromApp" class="org.jboss.test.kernel.deployment.support.SimpleBeanImpl"> | <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation> | <constructor> | <parameter>fromApp</parameter> | </constructor> | </bean> | | </deployment> | But result for this.. anonymous wrote : | [ScopedKernelController] Still unresolved Instantiated:..{name=deploy1..idependOn=..name=deploy1 dependsOn=InterceptedAspect... | [ScopedKernelController] Still unresolved Instantiated:..{name=deploy3..idependOn=..name=deploy3 dependsOn=InterceptedAspect... | [ScopedKernelController] Still unresolved Instantiated:..{name=deploy4..idependOn=..name=deploy4 dependsOn=InterceptedAspect... | deploy2 work for InterceptedAspect is right. why deploy1,3,4 dependsOn=InterceptedAspect ? thank View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021986#4021986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021986

18 years, 10 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by weston.price＠jboss.com

Thinking about this a bit more, I wonder if it makes sense to 'aspectize' the parsing of the *-ds.xml file. Ideally we want the ability to be able to plug-n-play various pieces of the parsing and to be able to easily extend the parsing when new elements/changes to the *-ds.xml format come along. Also, we may want to replace the *-ds.xml file format all together at some point. Effectively this would be just taking what's in the JAXP based parser now and breaking it up into a parsing chain. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021974#4021974 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021974

18 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Why failoverValve has the ThreadLocal routine

by timfox

I've just woken up and this is off the top of my head, untried, but how about something like this: | lass Valve | { | private int count; | private boolean locked; | | public synchronized void enter() | { | while (locked) | { | wait(); | } | count++; | } | | public synchronized void exit() | { | count--; | | notifyAll(); | } | | public synchronized void lock() | { | if (locked) return; | | locked = true; | | do | { | while (count > 0) | { | wait(); | } | } | } | | public synchronized void unlock() | { | if (!locked) return; | | locked = false; | | notifyAll(); | } | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021915#4021915 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021915

18 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Why failoverValve has the ThreadLocal routine

by clebert.suconic＠jboss.com

Basically this is the scenario... You have several threads trying to acquire the writeLock simultaneously... Different from a Tomcat Valve where from what I remember when I read the code, then don't have such requirement. You have several threads... each one with a readLock... then all of these threads will try to acquire a writeLock... Any thread will be able to assume the writeLock... as there are other threads with readLocks. so... before acquiring the writeLock, I would need to release the readLock... But... as the Valve is Reentrant.. I needed to store the number of reentrances before releasing readLocks executed before. The only solution to avoid the ThreadLocal would be to avoid reentrance on the Valve and aways release one readlock.. but I don't think that's completely possible. But if anyone can find a way to have this following test work (without releasing a readLock), we can apply the fix to the Valve: public void testOnReadlocks() throws Exception | { | int THREAD_COUNT = 10; | final ReadWriteLock readWriteLock = new WriterPreferenceReadWriteLock(); | final Object sync = new Object(); | | Thread threads[] = new Thread[THREAD_COUNT]; | | for (int i = 0; i < THREAD_COUNT; i++) | { | threads = new Thread() | { | public void run() | { | try | { | synchronized (sync) | { | sync.wait(); | } | readWriteLock.readLock().acquire(); | readWriteLock.writeLock().acquire(); | } | catch (Exception e) | { | e.printStackTrace(); | } | } | }; | threads.start(); | } | | Thread.sleep(2000); | | synchronized (sync) | { | sync.notify(); | } | | for (int i=0;i<threads.length;i++) | { | threads.join(); | } | } | This test would hang forever View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021809#4021809 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021809

18 years, 10 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Admin content editor plugin

by julien＠jboss.com

I worked a bit on it today, the cool thing is that I have added a facelet tag handler which allows to create a notion of nested context, very similar to ui:include but for nested content. For example | <h:outputText value="#{a.b.c}"/> | <h:outputText value="#{a.b.d}"/> | can be rewritten | <pfc:context> | <ui:param name="e" value="#{a.b}"/> | <h:outputText value="#{e.c}"/> | <h:outputText value="#{e.d}"/> | </pfc:context> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021805#4021805 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021805

18 years, 10 months

1
0
0 / 0

[Design of JBoss Wiki] - Word to Wiki Converter

by b_boyle18

Hey! I was just wondering if there is any tool available to convert MS Word docs to Jboss wiki? THanks Chris View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021802#4021802 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021802

18 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Save and Close button in the web console

by kukeltje

I have to admit, it is somewhere in the dungeons. Your searchterms do not give a response, but other, closely related ones didn't either. I only found it through my personal links... hmmm The webconsole in 3.2beta does not take the assignments fully into account. This should be fixed in 3.2 final (I even think there is a jira issue for this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021778#4021778 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021778

18 years, 10 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Virtual hosts and multiple portal server instances

by erich_lol

Hi, is it already planned to integrate support for supporting multiple virtual hosts with one portal container? For which release? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021705#4021705 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021705

18 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: JBAOP-368, Need to correct the ProtectionDomain for toCl

by scott.stark＠jboss.org

I have committed a change to trunk to require a ProtectionDomain to be passed into the TransformerCommon.toClass calls and updated the callers. This gets past the problems of null CodeSources in the ProtectionDomain check. In general we should not be creating classes without a ProtectionDomain as it will not meaningful CodeSource location. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021674#4021674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021674

18 years, 10 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