Added testsute reporting (ported from EAP 5)
by Ondřej Žižka
Hi all,
the testsuite test reports as you know it from EAP 5 were ported to AS
7. AS7-2011
How to run it?
It runs during testsuite's "site" phase. So, for example this
will give you reports in the AS7/testsuite/target/reports directory:
./build.sh clean install -DallTests
./integration-tests.sh site
Next to work on in this axis will be _code coverage_. AS7-2022
Regards,
Ondra
12 years, 5 months
JAVA_OPTS for Debug in starting script?
by Marek Novotny
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Could we add JAVA_OPTS for remote server debugging into standalone.sh
script at least?
This was in previous major versions of AS always there as commented line
and you just have to only uncomment it and start to debug. Does it worth
to have it there generally?
WDYT?
- --
Marek Novotny
- --
Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
Email: mnovotny(a)redhat.com
Office phone: +420 532 294 287, ext. 82-62 087
mobile: +420 608 509 230
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk631doACgkQU4HO8G8hNxXdBwCgvW7Z8+9uAlfbwteWAz5p9LIj
vIAAoKjUCSXDDoHrtSpMCBPf6Jq5BvX3
=4uGi
-----END PGP SIGNATURE-----
12 years, 5 months
Loading resources through JBWeb context API
by Thomas Diesler
Hi Remy,
I have a 3rd party servlet that uses this API
InputStream is = getServletContext().getResourceAsStream(propFile);
How is it possible to hook into this call using the dynamic context API?
Here is what I do to register the servlet
// Add the RegistryServlet
servlet = new RegistryServlet();
wrapper = context.createWrapper();
wrapper.setName("JUDDIRegistryServlet");
wrapper.setServlet(servlet);
wrapper.setServletClass(servlet.getClass().getName());
wrapper.setLoadOnStartup(1);
context.addChild(wrapper);
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
12 years, 5 months
Deploy resource adapter as subdeployment of an ear without an application.xml
by Panzer, Robert
Hi,
I am quite new to JBoss 7 and its architecture. I was using JBoss 4.0.5 and 5.1 for the last couple of years.
Now I want to switch to JBoss 7 and tried to deploy an ear file containing a resource adapter.
There is no application.xml in the ear file.
Unfortunately the server does not pay any attention to the rar during deployment and I did not know how to define the connection factories other than writing an ironjacamar.xml and placing it in the rar.
On JBoss 4/5 this worked without any problems by defining the connector-module inside the application.xml and placing a -ra.xml file in the deploy/ folder. But I do not want to write down this unnecessary stuff and try to live without an application.xml at all.
Is there anything I have missed in the documentation?
I debugged the code and was able to get the resource adapter deployed by modifying the EarStructureProcessor on the current master. (Just pulled this morning.)
It simply adds ".rar" to the list of well know subdeployment file extensions and creates a subdeployment for a resource adapter in case no ear meta data is present.
I attached the necessary patches. (I am not really firm with git yet, so please excuse any nonsense.)
What is your opinion on this?
Any comments are welcome!
Kind regards,
Robert
WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193
Diese E-Mail enthält vertrauliche Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.
This e-mail may contain confidential information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
12 years, 5 months
XSDValidationUnitTestCase - pls don't hard-code paths, and keep QA processes in mind.
by Ondřej Žižka
Please don't hardcode paths in tests.
Remember that tests may be shuffled around.
I'll introduce a new system properties, pointing to the testsuite dir,
evt. to project's root dir.
Also please remember that the testsuite will run agains productized
build -
perhaps the following tests could use XSD's from src/main/resources
instead?
(QA will run against provided EAP, let's not force them to run whole
build.)
Thanks,
Ondra
public class AbstractValidationUnitTest {
private static final Map<String, File> JBOSS_SCHEMAS = new
HashMap<String, File>();
private static Map<String, String> NAMESPACE_MAP = new
HashMap<String, String>();
static final File MOD_DIR = new
File(System.getProperty("user.dir"));
static final File TARGET_DIR = new File(MOD_DIR,
"../../build/target/");
private static File BASE_DIR = null;
static {
NAMESPACE_MAP.put("http://java.sun.com/xml/ns/javaee/javaee_6.xsd",
"schema/javaee_6.xsd");
NAMESPACE_MAP.put("http://www.w3.org/2001/xml.xsd",
"schema/xml.xsd");
final File[] children = TARGET_DIR.listFiles();
if (children != null) {
for (File child : children) {
if (child.getName().startsWith("jboss-")) {
BASE_DIR = child;
break;
}
}
if (BASE_DIR != null) {
final File schemaDir = new File(BASE_DIR,
"docs/schema");
final File[] xsds =
schemaDir.listFiles(SchemaFilter.FILTER);
for (File xsd : xsds) {
JBOSS_SCHEMAS.put(xsd.getName(), xsd);
}
}
}
}
12 years, 5 months
Which JBoss Logging version to use in AS and Hibernate Core
by Emmanuel Bernard
JBoss AS 7.1 is targeted to use JBoss Logging 3.0.1 AFAIK.
Hibernate Core 4.0 right now is using JBoss Logging 3.1.0.Beta3
// logging
logging: 'org.jboss.logging:jboss-logging:3.1.0.Beta3',
logging_generator: 'org.jboss.logging:jboss-logging-generator:1.0.0.CR3',
logging_processor: 'org.jboss.logging:jboss-logging-processor:1.0.0.CR3',
So which one we should go to? Once we have decided, I will align Search, OGM and Commons Annotations.
Emmanuel
12 years, 5 months
