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

[Design of JBossXB] - Re: Mixing wildcards and elements

by alex.loubyansky＠jboss.com

If you try <aspect class="org.jboss.test.microcontainer.beans.XmlLoadableAspect"> | <property name="property">Test1</property> | <somexml>hello</somexml> | <attribute name="IntAttr">12</attribute> | </aspect> It'll pass. The reason is the order of particles in the sequence. property is preceding the wildcard. So, in your case, when somexml is encountered before the property, the cursor in sequence moves to the repeated wildcard. And everything after the somexml is considered to be a wildcard content. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147817#4147817 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147817

15 years, 11 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Classloading problems with ClassProxyFactory

by kabir.khan＠jboss.com

My previous comment relates to the fact that once a ClassProxyContainer is created for an ArrayList with no bindings, the ClassProxyContainer would never be updated when new bindings which should affect it are added View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147796#4147796 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147796

15 years, 11 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Classloading problems with ClassProxyFactory

by kabir.khan＠jboss.com

Digging into this I deiscovered that if you create a proxy for something loaded up by a bootstrap classloader (e.g. java.util.ArrayList) the associated advisor is cleared due to JBoss5Integration.isValidClassLoader() returning false . http://jira.jboss.com/jira/browse/JBAS-5495 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147790#4147790 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147790

15 years, 11 months

1
0
0 / 0

[Design of JBossXB] - Re: Mixing wildcards and elements

by kabir.khan＠jboss.com

XmlLoadableAopTestCase, I get the XB error if I change XmlLoadableAopTestCase.xml from | <aspect class="org.jboss.test.microcontainer.beans.XmlLoadableAspect"> | <somexml>hello</somexml> | <attribute name="IntAttr">12</attribute> |  | </aspect> | to | <aspect class="org.jboss.test.microcontainer.beans.XmlLoadableAspect"> | <somexml>hello</somexml> | <attribute name="IntAttr">12</attribute> | <property name="property">Test1</property> </aspect> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147775#4147775 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147775

15 years, 11 months

1
0
0 / 0

[Design of JBoss Profiler] - jboss-profiler-1.0.CR4 - Help regarding Browser

by JKV

I am using Windows XP : JBoss 4.2.2. I downloaded jboss-profiler-1.0.CR4; I installed the profiler and I didnot get any exceptions in my console. I activated the profiler in my JMX-Console and I started my application. I found ContendedEnter ThreadId 316519480 -1634149983 ContendedEnter ThreadId 316480320 -1634149983 ..... in my console. I then stopped my profiler Mbean. I went to the web browser and selected Runtime Profiler, after selecting my directory Stack on Objects and Stack on methods I got Processed 10000 registers (72%) Processed 20000 registers (99%) Process Finished.... click here after clicking the hyperlink I am not able to see any thing except the headers I am using EJB3 in my application and there are lots of inter ejb calls. I am not able to see the Method Names and usages. Can any one help me View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147772#4147772 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147772

15 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: WS EJB invocation

by heiko.braun＠jboss.com

Looking closer makes me think that the best place would be JBossEnterpriseBeanMetaData. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147763#4147763 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147763

15 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: WS EJB invocation

by heiko.braun＠jboss.com

Please forget my last comment ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147761#4147761 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147761

15 years, 11 months

1
0
0 / 0

[Design of JBossXB] - Re: Mixing wildcards and elements

by alex.loubyansky＠jboss.com

Once again, which test are you running? I just refreshed my microcontainer. The XmlLoadableAopTestCase passed. And the XmlLoadableTest has one error "java.lang.IllegalStateException: Bean not found Bean at state ControllerState@87a5cc{Installed}" and junit.framework.AssertionFailedError: expected:<1> but was:<0> | at junit.framework.Assert.fail(Assert.java:47) | at junit.framework.Assert.failNotEquals(Assert.java:277) | at junit.framework.Assert.assertEquals(Assert.java:64) | at junit.framework.Assert.assertEquals(Assert.java:195) | at junit.framework.Assert.assertEquals(Assert.java:201) | at org.jboss.test.microcontainer.beans.test.XmlLoadableTest.testClassMetaDataLoader(XmlLoadableTest.java:56) But I don't see the XB error. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147760#4147760 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147760

15 years, 11 months

1
0
0 / 0

[Design of JBossXB] - Re: Mixing wildcards and elements

by kabir.khan＠jboss.com

I do not see this when running from within Eclipse. All I see in the console is: | 0 DEBUG [XmlLoadableTest] ==== setUp org.jboss.test.microcontainer.beans.test.XmlLoadableTest ==== | 453 DEBUG [KernelFactory] Starting JBoss Kernel construction... | 2766 DEBUG [KernelFactory] Completed JBoss Kernel construction. Duration: 2313 milliseconds | 3312 DEBUG [XmlLoadableTest] No test specific deployment org/jboss/test/microcontainer/beans/test/XmlLoadableTest-aop.xml | 3312 DEBUG [XmlLoadableTest] Deploying file:/C:/cygwin/home/Kabir/sourcecontrol/microcontainer/aop-mc-int/target/tests-classes/org/jboss/tes | t/microcontainer/beans/test/XmlLoadableTest.xml | 3672 DEBUG [SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@d3db51, isNamespaceAware: true, isValidating: true, isXIn | cludeAware: true | 3672 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/validation set to: true | 3672 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true | 3672 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true | 3703 DEBUG [SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@d3db51, isNamespaceAware: true, isValidating: true, isXIn | cludeAware: true | 11719 DEBUG [XmlLoadableTest] ==== tornDown org.jboss.test.microcontainer.beans.test.XmlLoadableTest ==== | 11797 DEBUG [XmlLoadableTest] ==== Starting testAspectInterceptorAndDynamicCFlow ==== | 11812 DEBUG [XmlLoadableTest] testAspectInterceptorAndDynamicCFlow took 15ms | 11812 DEBUG [XmlLoadableTest] ==== Stopping testAspectInterceptorAndDynamicCFlow ==== | And for the test | java.lang.ClassCastException: org.apache.xerces.dom.ElementNSImpl | at org.jboss.beans.metadata.spi.factory.GenericBeanFactoryMetaData.getBeans(GenericBeanFactoryMetaData.java:609) | at org.jboss.aop.microcontainer.beans.metadata.AspectBeanMetaDataFactory.getBeans(AspectBeanMetaDataFactory.java:134) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:229) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:304) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130) | at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:76) | at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:88) | at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:158) | at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.deploy(MicrocontainerTestDelegate.java:294) | at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.deploy(MicrocontainerTestDelegate.java:438) | at org.jboss.test.aop.junit.AOPMicrocontainerTestDelegate.deploy(AOPMicrocontainerTestDelegate.java:74) | at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.setUp(MicrocontainerTestDelegate.java:83) | at org.jboss.test.aop.junit.AOPMicrocontainerTestDelegate.setUp(AOPMicrocontainerTestDelegate.java:58) | at org.jboss.test.AbstractTestSetup.setUp(AbstractTestSetup.java:63) | at org.jboss.test.AbstractTestCaseWithSetup.setUp(AbstractTestCaseWithSetup.java:103) | at org.jboss.test.kernel.junit.MicrocontainerTest.setUp(MicrocontainerTest.java:82) | at junit.framework.TestCase.runBare(TestCase.java:132) | at junit.framework.TestResult$1.protect(TestResult.java:110) | at junit.framework.TestResult.runProtected(TestResult.java:128) | at junit.framework.TestResult.run(TestResult.java:113) | at junit.framework.TestCase.run(TestCase.java:124) | at junit.framework.TestSuite.runTest(TestSuite.java:232) | at junit.framework.TestSuite.run(TestSuite.java:227) | at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81) | at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) | at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147750#4147750 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147750

15 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: WS EJB invocation

by heiko.braun＠jboss.com

For the easiest would be to publish the ObjectName with DeploymentUnit attachments using a fixed property name that's part of the WS SPI. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147747#4147747 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147747

15 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2008