I am going to add the following for the test driver:
| public interface DriverContext
| {
| String getProperty(String name);
| }
|
and on the TestDriver interface the following methods:
| void init(DriverContext context);
| void destroy();
|
I need to have proper demarcation of the life cycle of a test driver, which is needed in various places. I also need test driver configuration which is different from parameters. A test driver configuration is something like the local directory that would contain archives to deploy, or the initial node id in a distributed test.
Those would be added to the jboss-unit.xsd as well as runtime switches.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094436#4094436
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094436
For the moment I've reinstated the hack to get to the deprecated EJB 3 deployers.
I've added EjbJarMetaData as an optional input, because we use it to specify overridden meta data.
I don't like the exception coming from the parse method, they're non-descriptive.
Shouldn't we parse standardjboss.xml on each run of the mill? If not, then we should have a line in there that says 'only parsed once, restart server if changed'.
I think the latter is better, because it won't leave deployments in a state that's no longer attainable.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094428#4094428
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094428
Hi Folks,
I've found that our 'WSDL schema section' generation process
is in method JAXBWSDLGenerator.processTypes() where we call
JAXBRI.generateSchema() method.
This JAXB based schema generation doesn't preserve the object
inheritance hierarchy in generated schema.
So my question is:
Is there a way to force JAXB schema generator
to preserve object inheritance hierarchy in
generated schema?
Richard
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094403#4094403
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094403
We need the capability to be able to set parameters on Main that will be used as global parameters (overriden naturally by the jboss-unit.xml values).
>From ant we need to be able to set them from the jboss-unit task, in order to pass an ant property to a test execution such as:
| <jboss-unit>
| <tests ...>
| <parameter name="foo" value="${foo_value}"/>
| </tests>
| </jboss-unit>
|
| <jboss-unit>
| <parameter name="foo" value="${foo_value}"/>
| </jboss-unit>
|
from the command line we would have the matching equivalent.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094321#4094321
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094321