[alrubinger]

"jaikiran" wrote:
Actually, i can give that a try myself.

This job will have the results:

http://jboss.hudson.alrubinger.com/job/jboss-embedded/13/

S,
ALR

[alrubinger]

Looks still outta-sync.

/home/deployer/.hudson/jobs/jboss-embedded/workspace/jbossas/ejb3/src/main/org/jboss/as/jpa/builder/JPA2CEMFBuilder.java:[30,23] package javax.validation does not exist

/home/deployer/.hudson/jobs/jboss-embedded/workspace/jbossas/ejb3/src/main/org/jboss/as/jpa/builder/JPA2CEMFBuilder.java:[31,23] package javax.validation does not exist

/home/deployer/.hudson/jobs/jboss-embedded/workspace/jbossas/ejb3/src/main/org/jboss/as/jpa/builder/JPA2CEMFBuilder.java:[54,9] cannot find symbol
symbol : class ValidatorFactory
location: class org.jboss.as.jpa.builder.JPA2CEMFBuilder

/home/deployer/.hudson/jobs/jboss-embedded/workspace/jbossas/ejb3/src/main/org/jboss/as/jpa/builder/JPA2CEMFBuilder.java:[54,50] cannot find symbol
symbol : variable Validation
location: class org.jboss.as.jpa.builder.JPA2CEMFBuilder

S,
ALR

[alrubinger]

"ALRubinger" wrote:
Looks still outta-sync.

Though the main build succeeds, this is the AS Maven build. Probably a missing new dependency; I'm looking into it.

S,
ALR

[alrubinger]

"ALRubinger" wrote:
Probably a missing new dependency; I'm looking into it.

[alr@localhost ejb3]$ svn di
Index: pom.xml
===================================================================
--- pom.xml (revision 96181)
+++ pom.xml (working copy)
@@ -198,6 +198,11 @@
 <groupId>org.jboss.integration</groupId>
 <artifactId>jboss-corba-ots-spi</artifactId>
 </dependency>
+
+ <dependency>
+ <groupId>javax.validation</groupId>
+ <artifactId>validation-api</artifactId>
+ </dependency>

 </dependencies>

S,
ALR

[alrubinger]

Tracking the WS problem in:

https://jira.jboss.org/jira/browse/EMB-61

Also I fixed the problem w/ Branch_5_x Maven2 build in r96188.

S,
ALR

[manuel.chinea]

"ALRubinger" wrote:
Tracking the WS problem in:

https://jira.jboss.org/jira/browse/EMB-61

Hi,

I did this test in the following way:

1. -First, I created a web project (under eclipse) and created the ws and ws client classes.
2.- Ran it under Jboss 5.1 GA, and later, on Branch5x build (no embedded mode) sucessfully
3.- Took the classes and placed them under the embedded-project and created the @Test testWs method.
4.- Ran it in embedded mode...
5.- ERROR!

I googled the problem and found this: http://www.thebeautifulcode.com/?p=35
I tested it in my setup and didn't work. Perhaps a classloading issue/missing setup in embedded?.
I'll repeat the whole process again with an updated Branch5x build just in case.

[manuel.chinea]

Hi,

i applied the patch in the jira ticket https://jira.jboss.org/jira/browse/EMB-61. I checked the code for the system property java.endorsed.libs. I changed the line in ServerTestCase.java
final File lib = new File(jbossHome,"endorsed");
to
final File lib = new File(jbossHome,"lib");
so the path were something like this: ...lib/endorsed.

Then i ran the test with no luck.

I was curious about the java.endorsed.dirs property and what jboss does with it. I put an iteration over the jboss config properties after the server.start() and saw the property jboss.bootstrap.url is set to server/default/conf/bootstrap.xml, aren't we running in the "all" config?

The code i put in the ServerTestCase.startEmbedddedASAndSetNamingContext() method, after server.start() is:

Map<String, String> props = server.getConfiguration().getProperties();
for (Iterator iterator = props.keySet().iterator(); iterator.hasNext();)
{
String key = (String) iterator.next();
log.info("key[" + key + "],value[" + props.get(key) + "]");

}

Also saw the java.endorsed.libs is not modified in jboss, according to the logs in my run.

[alrubinger]

"manuel.chinea" wrote:
i applied the patch in the jira ticket https://jira.jboss.org/jira/browse/EMB-61. I checked the code for the system property java.endorsed.libs. I changed the line in ServerTestCase.java
final File lib = new File(jbossHome,"endorsed");
to
final File lib = new File(jbossHome,"lib");
so the path were something like this: ...lib/endorsed.

You can actually ditch all that code, it was left over. The important piece that was in place for my runs was in build/pom.xml, where I manually set the sysprop when the JVM is launched.

"manuel.chinea" wrote:
I was curious about the java.endorsed.dirs property and what jboss does with it.

It's the runtime which handles this. Endorsed libraries are those that are allowed to replace those in the JRE. @see http://java.sun.com/j2se/1.5.0/docs/guide/standards/.

"manuel.chinea" wrote:
I put an iteration over the jboss config properties after the server.start() and saw the property jboss.bootstrap.url is set to server/default/conf/bootstrap.xml, aren't we running in the "all" config?

Nice catch, I'll check that.

S,
ALR

[manuel.chinea]

Hi there,

i attached a path (EMB-61v2) in the jira https://jira.jboss.org/jira/browse/EMB-61 that fixes the problem.