RE: [JBoss-dev] JAR Urls and URLClassLoader

2005-07-21 Thread Dimitris Andreadis

Not sure if that helps, but in SubDeployerSupport we extract the nested
jar in order to further process it:

   // Obtain a jar url for the nested jar
   URL nestedURL = JarUtils.extractNestedJar(di.localUrl,
this.tempDeployDir); 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Bill Burke
> Sent: Thursday, July 21, 2005 8:26 PM
> To: Jboss-Dev
> Subject: [JBoss-dev] JAR Urls and URLClassLoader
> 
> I'm trying to create a URLClassLoader with the following URL:
> 
> jar:file:/home/wburke/fragments/foo.jar!/jboss-ejb3x.jar
> 
> It doesn't seem to be able to load classes from this URL.
> 
> --
> Bill Burke
> Chief Architect
> JBoss Inc.
> 
> 
> ---
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> ___
> JBoss-Development mailing list
> JBoss-Development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 


---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] jboss-head-jdk-matrix Build Failed

2005-07-21 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050721134805
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:65: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:39: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 07/21/2005 13:48:05Time to build: 6 minutes 22 secondsLast changed: 07/21/2005 13:26:04Last log entry: default to anoncvs




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last builds: (first 50 of 10)1.2modifiedrloehrjbossas/local.propertiesdefault to anoncvs1.7modifiedtdieslercommon/src/main/org/jboss/xb/binding/MappingObjectModelProvider.javaThe key to fieldMappings not sufficiently unique1.6modifiedtdieslercommon/src/main/org/jboss/xb/binding/MappingObjectModelProvider.javaMore debugging.Be strict on marshalling failures.1.1addedtdieslerwebservice/test/etc/tst.policyAdd security manager1.56modifiedtdieslerwebservice/test/build.xmlAdd security manager1.47modifiedrloehrjbossas/jbossbuild.xmlchanged cvs property to be parameterized1.1addedrloehrjbossas/local.propertiesno message1.33modifiedstarksmconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xslFix for (JBAS-2033) ConnectionFactoryTemplate.xsl contains invalid markup.1.83modifiedbillejb3/build-test.xmlchange test class directory1.33modifiedbillejb3/build.xmlchange test class directory



[JBoss-dev] jboss-head-jdk-matrix Build Failed

2005-07-21 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050721132512
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:65: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:39: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 07/21/2005 13:25:12Time to build: 6 minutes 15 secondsLast changed: 07/21/2005 13:09:59Last log entry: The key to fieldMappings not sufficiently unique




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last builds: (first 50 of 9)1.7modifiedtdieslercommon/src/main/org/jboss/xb/binding/MappingObjectModelProvider.javaThe key to fieldMappings not sufficiently unique1.6modifiedtdieslercommon/src/main/org/jboss/xb/binding/MappingObjectModelProvider.javaMore debugging.Be strict on marshalling failures.1.1addedtdieslerwebservice/test/etc/tst.policyAdd security manager1.56modifiedtdieslerwebservice/test/build.xmlAdd security manager1.47modifiedrloehrjbossas/jbossbuild.xmlchanged cvs property to be parameterized1.1addedrloehrjbossas/local.propertiesno message1.33modifiedstarksmconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xslFix for (JBAS-2033) ConnectionFactoryTemplate.xsl contains invalid markup.1.83modifiedbillejb3/build-test.xmlchange test class directory1.33modifiedbillejb3/build.xmlchange test class directory



[JBoss-dev] RE: jboss-head-jdk-matrix Build Failed

2005-07-21 Thread Ryan Campbell






The change to MappingObjectModelProvider was incompatible with j2se 1.4 [execmodules] /scratch/cruisecontrol/checkout/jboss-head/common/src/main/org/jboss/xb/binding/MappingObjectModelProvider.java:182: cannot resolve symbol[execmodules] symbol  : constructor IllegalStateException (java.lang.String,java.lang.Exception)[execmodules] location: class java.lang.IllegalStateException[execmodules]  throw new IllegalStateException("Failed to provide value for " + localName + " from " + o, e);[execmodules]    ^[execmodules] /scratch/cruisecontrol/checkout/jboss-head/common/src/main/org/jboss/xb/binding/MappingObjectModelProvider.java:195: cannot resolve symbol[execmodules] symbol  : constructor IllegalStateException (java.lang.String,java.lang.Exception)[execmodules] location: class java.lang.IllegalStateException[execmodules]  throw new IllegalStateException("Failed to provide value for " + localName + " from " + o, e);

 

 











From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]

Sent: Thursday, July 21, 2005
12:09 PM
To: jboss-development@lists.sourceforge.net;
QA
Subject: jboss-head-jdk-matrix
Build Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050721125938




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:65:
  The following error occurred while executing this line:
  /home/cruisecontrol/work/scripts/build-jboss-head.xml:39: Exit code: 1 See
  compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/
  
 
 
  
  Date
  of build: 07/21/2005 12:59:38
  
 
 
  
  Time
  to build: 6 minutes 42 seconds
  
 
 
  
  Last
  changed: 07/21/2005 12:38:56
  
 
 
  
  Last
  log entry: More debugging.Be
  strict on marshalling failures.
  
 




 




 
  
  
  
   

 Unit Tests:
(0)  Total Errors and Failures: (0) 

   
   



 
  
   
  
 





 


 


 

   
   

 


 


 


 

   
   

 


 


 

   
  
  
   
  
  
   

 Modifications
since last builds:  (first 50 of 8) 

   
   

1.6


modified


tdiesler


common/src/main/org/jboss/xb/binding/MappingObjectModelProvider.java


More debugging.Be
strict on marshalling failures.

   
   

1.1


added


tdiesler


webservice/test/etc/tst.policy


Add security manager

   
   

1.56


modified


tdiesler


webservice/test/build.xml


Add security manager

   
   

1.47


modified


rloehr


jbossas/jbossbuild.xml


changed cvs property
to be parameterized

   
   

1.1


added


rloehr


jbossas/local.properties


no message

   
   

1.33


modified


starksm


connector/src/resources/stylesheets/ConnectionFactoryTemplate.xsl


Fix for (JBAS-2033)
ConnectionFactoryTemplate.xsl contains invalid markup.

   
   

1.83


modified


bill


ejb3/build-test.xml


change test class
directory

   
   

1.33


modified


bill


ejb3/build.xml


change test class
directory

   
  
  
   
  
  
   

 

   
  
  
  
  
 




 










[JBoss-dev] JAR Urls and URLClassLoader

2005-07-21 Thread Bill Burke

I'm trying to create a URLClassLoader with the following URL:

jar:file:/home/wburke/fragments/foo.jar!/jboss-ejb3x.jar

It doesn't seem to be able to load classes from this URL.

--
Bill Burke
Chief Architect
JBoss Inc.


---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] jboss-head-jdk-matrix Build Failed

2005-07-21 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050721125938
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:65: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:39: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 07/21/2005 12:59:38Time to build: 6 minutes 42 secondsLast changed: 07/21/2005 12:38:56Last log entry: More debugging.Be strict on marshalling failures.




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last builds: (first 50 of 8)1.6modifiedtdieslercommon/src/main/org/jboss/xb/binding/MappingObjectModelProvider.javaMore debugging.Be strict on marshalling failures.1.1addedtdieslerwebservice/test/etc/tst.policyAdd security manager1.56modifiedtdieslerwebservice/test/build.xmlAdd security manager1.47modifiedrloehrjbossas/jbossbuild.xmlchanged cvs property to be parameterized1.1addedrloehrjbossas/local.propertiesno message1.33modifiedstarksmconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xslFix for (JBAS-2033) ConnectionFactoryTemplate.xsl contains invalid markup.1.83modifiedbillejb3/build-test.xmlchange test class directory1.33modifiedbillejb3/build.xmlchange test class directory



Re: [JBoss-dev] Add a jbxb:schemaBindings/ jbxb:IgnoreUnresolvedFieldOrClass

2005-07-21 Thread Alexey Loubyansky

Scott M Stark wrote:

I want to add a jbxb:schemaBindings/jbxb:IgnoreUnresolvedFieldOrClass
boolean element flag that mirrors the
SchemaBinding.setIgnoreUnresolvedFieldOrClass(boolean) method so this
can be set from the schema.


Ok


Does it also make sense for the value of
IgnoreUnresolvedFieldOrClass to be false rather than the current true? I
have run into problems in my schema not being reported due to the
default behavior of ignoring elements that don't map to a class and I'm
not clear on why ignoring is the correct default behavior.


I don't mind. The current behaviour was easier for me in debugging and 
writting examples and tests.
Maybe it even makes sense to have three values: ignore silently, ignore 
with a warning (current behaviour) and don't ignore.


alex

 


Scott Stark
Chief Technology Officer
JBoss Inc.
 
 



---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development




---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development