|
Mike, I think this is related to a windows
pathing issue where the line length is greater than 256 chars. I don’t know
of a workaround for this. I would suggest pinging the dev list for a solution. -Jacobd From: Mike Skells
[mailto:[EMAIL PROTECTED] Hi , I get the following stack trace when using scomp, version
2.0.0-r191560 Is this a known bug? Is there a workaround? Application generate a large number of xsb files (exactly
1000), but not the one that it is looking for! Is there some limit as to the number of xsb files that can
be generated? 1000 seems a very suspicious number to fail at! Mike Exception in thread "main"
org.apache.xmlbeans.SchemaTypeLoaderException:
c:\projects\xmlbeansgenerated\classes\schemaorg_apache_xmlbeans\javaname\com\ebizzConsulting\resources\schemas\java\comEbzcUtilsEnvironmentTransactionTransactionFactory\StandardTransactionConfigurationType\Connections\RealConnection\ConnectionProvider\Custom.xsb
(The system cannot find the path specified) (schemaorg_apache_xmlbeans.system.sB257CA9B088397728E73131D0CF8D274.schemaorg_apache_xmlbeans/javaname/com/ebizzConsulting/resources/schemas/java/comEbzcUtilsEnvironmentTransactionTransactionFactory/StandardTransactionConfigurationType/Connections/RealConnection/ConnectionProvider/Custom)
- code 9 |
- Stack trace when using scomp Mike Skells
- RE: Stack trace when using scomp Jacob Danner
- RE: Stack trace when using scomp Mike Skells

