September 2007 - jboss-dev-forums

[Design of JBossXB] - Re: jbossxb mvn test failures

by scott.stark＠jboss.org

Ok, then the tests merge needs to be fixed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086959#4086959 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086959

18 years, 6 months

1
0
0 / 0

[Design of JBossXB] - Re: jbossxb mvn test failures

by alex.loubyansky＠jboss.com

tests: 636 errors: 319 failures: 7 The tests in the jbossxb-builder override jbossxb's default handlers that are static fields. See org.jboss.xb.binding.sunday.unmarshalling.DefaultHandlers. That's probably the reason for the error you posted. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086956#4086956 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086956

18 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Status of EJB3-785 and EJB3-786

by pete.muir＠jboss.org

Just wonder what the status is on http://jira.jboss.org/jira/browse/EJBTHREE-786 and http://jira.jboss.org/jira/browse/EJBTHREE-785 - they are stopping people using EJB3 with Seam's CRUD framework (which is the way we recommend people build their applications). Thanks :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086953#4086953 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086953

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by scott.stark＠jboss.org

A bigger problem is lack of support for dom Elements as is needed for the standardjboss.xml proxy-factory-config elements. The content of these depends on the invoker type: | <proxy-factory-config> | <client-interceptors> | <home> | <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor> | <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> | <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> | <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor> | <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor> | </home> | <bean> | <interceptor>org.jboss.proxy.ejb.EntityInterceptor</interceptor> | <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> | <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> | <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor> | <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor> | </bean> | <list-entity> | <interceptor>org.jboss.proxy.ejb.ListEntityInterceptor</interceptor> | <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> | <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> | <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor> | <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor> | </list-entity> | </client-interceptors> | </proxy-factory-config> | | ... | | <proxy-factory-config> | <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI> | <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> | <CreateJBossMQDestination>false</CreateJBossMQDestination> |  | <MinimumSize>1</MinimumSize> | <MaximumSize>15</MaximumSize> | <KeepAliveMillis>30000</KeepAliveMillis> | <MaxMessages>1</MaxMessages> | <MDBConfig> | <ReconnectIntervalSec>10</ReconnectIntervalSec> | <DLQConfig> | <DestinationQueue>queue/DLQ</DestinationQueue> | <MaxTimesRedelivered>10</MaxTimesRedelivered> | <TimeToLive>0</TimeToLive> | </DLQConfig> | </MDBConfig> | </proxy-factory-config> | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086951#4086951 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086951

18 years, 6 months

1
0
0 / 0

[Design of JBossXB] - Re: jbossxb mvn test failures

by scott.stark＠jboss.org

What about the current jbossxb trunk after the jbossxb-builder merge? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086945#4086945 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086945

18 years, 6 months

1
0
0 / 0

[Design of JBossXB] - Re: jbossxb mvn test failures

by alex.loubyansky＠jboss.com

tests: 289 errors: 3 failures: 3 AnnotatedPojoServerUnitTestCase: 1 error, 3 failures JbxbPojoServerUnitTestCase: 1 error RepeatedElementsUnitTestCase: 1 error View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086944#4086944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086944

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by scott.stark＠jboss.org

"alesj" wrote : | I guess this is related: | - http://jira.jboss.com/jira/browse/JBMICROCONT-184 | | I can look at this first thing in the morning, and we can discuss it during the MC call? | Not quite as the problem is really one of ejb-jar.xml/standardjboss.xml/jboss.xml. The current unified metadata already handles the ejb-jar.xml/jboss.xml case, but not merging multiple jboss.xml documents into the same JBoss50MetaData instance. I don't see how this can be added to the org.jboss.xb.builder.runtime.BeanHandler that creates the metadata instance. The root org.jboss.ejb.metadata.jboss.JBossMetaData would have to add a mergeOverridenMetaData method that took the existing override and merged the second override into it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086893#4086893 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086893

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by alesj

"scott.stark(a)jboss.org" wrote : Another issue is the need to parse multiple documents into one object instance. This shows up in the org.jboss.test.xml.metadata.JBossEjbObjectFactoryUnitTestCase test where both the standardjboss.xml and jboss.xml need to go into the JBoss50MetaData override. | | I'm looking into how that can be handled. | I guess this is related: - http://jira.jboss.com/jira/browse/JBMICROCONT-184 I can look at this first thing in the morning, and we can discuss it during the MC call? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086882#4086882 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086882

18 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: aspect library config for jbossas

by kabir.khan＠jboss.com

The upgrade to the ServiceControllerLifecycleCallback breaks these tests: org.jboss.test.aop.test.MicrocontainerDefaultAnnotationUnitTestCase org.jboss.test.aop.test.MicrocontainerJMXUnitTestCase They run fine with the old JMXLifecycleCallback. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086871#4086871 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086871

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by scott.stark＠jboss.org

Another issue is the need to parse multiple documents into one object instance. This shows up in the org.jboss.test.xml.metadata.JBossEjbObjectFactoryUnitTestCase test where both the standardjboss.xml and jboss.xml need to go into the JBoss50MetaData override. I'm looking into how that can be handled. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086861#4086861 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086861

18 years, 6 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 September 2007