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

[Design of Messaging on JBoss (Messaging/JBoss)] - Integration on JBoss5: Clustered tests

by clebert.suconic＠jboss.com

The way I'm setting this is the following: I'm creating two JBAS configs on my clustered test target: joss-jbmcluster1 and jboss-jbmcluster2 jbm-cluster1 will have a HSQLDB set, and jbm-cluster2 is connecting to jbm-cluster1 through regular IP. I have tried to use what Brian had in place for Clustered tests, but I prefered this way, as it will be easier to migrate these tests into jboss-4.2. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095433#4095433 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095433

18 years, 5 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: profiler is not picking process id.

by clebert.suconic＠jboss.com

What parameters you are passing on the java arguments? And what files do you see on that directory? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095431#4095431 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095431

18 years, 5 months

1
0
0 / 0

[QA of JBoss Portal] - Re: Unit test framework

by julien＠jboss.com

The current status is that today I have locally the test suite for web and portlet container module migrated, there are a couple of things to finish before I can commit. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095410#4095410 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095410

18 years, 5 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ClassLoading Module usage

by kabir.khan＠jboss.com

So my take on this is currently: 1) Implement org.jboss.virtual.plugins.context.memory. MemoryContextFactory MemoryContext MemoryContextHandler 2) Plug the context factory for vfsmemory into VFSContextFactoryLocator 3) VFSTopLevelClassLoaderSystemDeployer a) When creating the top level classloader pass in a memory virtual file as one of the roots b) Attach the memory virtual file to the deployment? 4) AspectDeployer a) Get the memory virtual file from the deployment and output the generated classes to there (possibly using the AssembledXXX stuff?) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095406#4095406 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095406

18 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Compatability of jBPM with weblogic portal

by kukeltje

1: for WLS 8.1, just some lib issues unless you put it all in an ear and give that preference. Oh yeah, also the login is an 'issue' if you want to use the jbpm console (search the forum) 2: Cannot give you a definitive answer, totally depends on what you want. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095399#4095399 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095399

18 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: So what does unification mean for the ejb containers

by scott.stark＠jboss.org

The jboss_5_0.xsd also does not accept the standardjboss.xml elements like invoker-proxy-bindings and container-configurations. These should really exists in some form. For ejb3 they would be referring to aop stacks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095385#4095385 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095385

18 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: So what does unification mean for the ejb containers

by scott.stark＠jboss.org

With the schema validation turned on, parsing jboss5.xml docs is failing because of the attribute use restriction: anonymous wrote : | org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/JBoss5xEverything_testStandard.xml@9,22 | ... | Caused by: org.xml.sax.SAXException: cvc-complex-type.3.1: Value '5.0' of attribute 'version' of element 'jboss' is not valid with respect to the corresponding attribute use. Attribute 'version' has a fixed value of '3.0'. @ file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/JBoss5xEverything_testStandard.xml[9,22] | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427) | at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) | ... | Both the online and jboss-metadata jboss_5_0.xsd have a fixed value for the version: | <xsd:attribute name="version" type="javaee:dewey-versionType" fixed="3.0" use="required"> | <xsd:annotation> | <xsd:documentation> The version specifies the version of the EJB specification that the | instance document must comply with. This information enables deployment tools to validate | a particular EJB Deployment Descriptor with respect to a specific version of the EJB | schema. </xsd:documentation> | </xsd:annotation> | </xsd:attribute> | I don't see the reason for restricting this? A jboss5 jboss.xml doc should be applicable to anything from jbossas5.0 - jbossas3.0. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095381#4095381 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095381

18 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Integration on JBoss5: NullPointerException deploying jm

by clebert.suconic＠jboss.com

Looking at the source code, this NPE is because of the lacking of a primary key: | for(String key : primary.keySet()) <<-- here | { | A primary key wouldn't mean anything here. Or we change the behavior of nulls on empty tags, or we change the metadata to test for nulls on those things. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095372#4095372 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095372

18 years, 5 months

1
0
0 / 0

[Design of JBossXB] - Re: XsdBinder status

by scott.stark＠jboss.org

If you comment out the ejb-jar_2_1.xsd config line in JBoss50UnitTestCase.initResolver: | public static SchemaBindingResolver initResolver() | { | DefaultSchemaResolver resolver = new DefaultSchemaResolver(); | //resolver.addClassBindingForLocation("ejb-jar_2_1.xsd", EjbJar21MetaData.class); | ... | The EjbJar21Everything_testEverything.xml fails to parse with: anonymous wrote : | org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/EjbJar21Everything_testEverything.xml@1258,56 | ... | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to start {http://java.sun.com/xml/ns/j2ee}ejb-relationship-role: the element is not repeatable, repeatable parent expected to be a model group but got element {http://java.sun.com/xml/ns/j2ee}ejb-relation | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endRepeatableParent(SundayContentHandler.java:695) | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:334) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402) | at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) | at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) | at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) | at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) | at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:180) | ... 21 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095369#4095369 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095369

18 years, 5 months

1
0
0 / 0

[Design of JBossXB] - Re: Too much resolution?

by scott.stark＠jboss.org

Its more than just the logging that is taking the time. If I reduce the logging to INFO level, parsing a standardjboss.xml descriptor is still taking > 60 seconds: 11:33:28,038 INFO [JBoss50UnitTestCase] EjbJar21Everything_testEverything.xml parse time = 1227 11:34:34,711 INFO [JBoss50UnitTestCase] JBoss5xEverything_testStandard.xml parse time = 66673 11:34:44,040 INFO [JBoss50UnitTestCase] JBoss5xEverything_testEverything.xml parse time = 9329 Seems like we need to cache the fact that a given element is a unknown wildcard to avoid the resolution thrashing going on. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095368#4095368 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095368

18 years, 5 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 October 2007