You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by Mike Skells <mi...@ebizz-consulting.com> on 2005/09/02 11:18:16 UTC

Stack trace when using scomp, with a deep directory structure [reposed from user@xmlbeans.apache.org]

Hi,
 
ARe there any workarounds for this?
it seem to be caused by the mkdirs() failing to report that the directory
cannot be created 
on FilerImpl:91 (in the current source for 2.0.0).
 
the underlying error is java.io.FileNotFoundException:
c:\projects\xmlbeansgenerated\classes\schemaorg_apache_xmlbeans\javaname\com
\ebizzConsulting\resources\schemas\java\comEbzcUtilsEnvironmentTransactionTr
ansactionFactory\StandardTransactionConfigurationType\Connections\RealConnec
tion\ConnectionProvider\Custom.xsb (The system cannot find the path
specified)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
        at
org.apache.xmlbeans.impl.util.FilerImpl.createBinaryFile(FilerImpl.java:93)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.getSaverStrea
m(SchemaTypeSystemImpl.java:2209)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHead
er(SchemaTypeSystemImpl.java:1588)
...
 
Mike

  _____  

From: Jacob Danner [mailto:jacobd@bea.com] 
Sent: 01 September 2005 18:59
To: user@xmlbeans.apache.org
Subject: RE: Stack trace when using scomp



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:mike.skells@ebizz-consulting.com] 
Sent: Thursday, September 01, 2005 2:52 AM
To: user@xmlbeans.apache.org
Subject: Stack trace when using scomp

 

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\comEbzcUtilsEnvironmentTransactionTr
ansactionFactory\StandardTransactionConfigurationType\Connections\RealConnec
tion\ConnectionProvider\Custom.xsb (The system cannot find the path
specified)
(schemaorg_apache_xmlbeans.system.sB257CA9B088397728E73131D0CF8D274.schemaor
g_apache_xmlbeans/javaname/com/ebizzConsulting/resources/schemas/java/comEbz
cUtilsEnvironmentTransactionTransactionFactory/StandardTransactionConfigurat
ionType/Connections/RealConnection/ConnectionProvider/Custom) - code 9
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.getSaverStrea
m(SchemaTypeSystemImpl.java:2213)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHead
er(SchemaTypeSystemImpl.java:1588)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.savePointerFile(SchemaT
ypeSystemImpl.java:372)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.savePointersForClassnam
es(SchemaTypeSystemImpl.java:355)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.savePointers(SchemaType
SystemImpl.java:336)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.save(SchemaTypeSystemIm
pl.java:1304)
        at
org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:109
3)
        at
org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:367)

WSDL Schema parser

Posted by Shrinivas Alageri <al...@india.hp.com>.
Hi 
I would like to parse the WSDL file for getting into <complexType>.I would
like to get the value of element name,maxOccurs,maxOccurs within the
<sequence> tag.How do I proceed .I am attaching the WSDL file.
With Best Regards
Shrinivas


  _____  

From: Mike Skells [mailto:mike.skells@ebizz-consulting.com] 
Sent: Tuesday, September 06, 2005 4:46 PM
To: dev@xmlbeans.apache.org
Subject: RE: Stack trace when using scomp, with a deep directory structure
[reposed from user@xmlbeans.apache.org]


I fixed this with an xsdconfig file to adjust the namespaces, so as to
reduce the depth 

Mike


  _____  

From: Mike Skells [mailto:mike.skells@ebizz-consulting.com] 
Sent: 02 September 2005 10:18
To: dev@xmlbeans.apache.org
Subject: Stack trace when using scomp, with a deep directory structure
[reposed from user@xmlbeans.apache.org]


Hi,
 
ARe there any workarounds for this?
it seem to be caused by the mkdirs() failing to report that the directory
cannot be created 
on FilerImpl:91 (in the current source for 2.0.0).
 
the underlying error is java.io.FileNotFoundException:
c:\projects\xmlbeansgenerated\classes\schemaorg_apache_xmlbeans\javaname\com
\ebizzConsulting\resources\schemas\java\comEbzcUtilsEnvironmentTransactionTr
ansactionFactory\StandardTransactionConfigurationType\Connections\RealConnec
tion\ConnectionProvider\Custom.xsb (The system cannot find the path
specified)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
        at
org.apache.xmlbeans.impl.util.FilerImpl.createBinaryFile(FilerImpl.java:93)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.getSaverStrea
m(SchemaTypeSystemImpl.java:2209)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHead
er(SchemaTypeSystemImpl.java:1588)
...
 
Mike

  _____  

From: Jacob Danner [mailto:jacobd@bea.com] 
Sent: 01 September 2005 18:59
To: user@xmlbeans.apache.org
Subject: RE: Stack trace when using scomp



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:mike.skells@ebizz-consulting.com] 
Sent: Thursday, September 01, 2005 2:52 AM
To: user@xmlbeans.apache.org
Subject: Stack trace when using scomp

 

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\comEbzcUtilsEnvironmentTransactionTr
ansactionFactory\StandardTransactionConfigurationType\Connections\RealConnec
tion\ConnectionProvider\Custom.xsb (The system cannot find the path
specified)
(schemaorg_apache_xmlbeans.system.sB257CA9B088397728E73131D0CF8D274.schemaor
g_apache_xmlbeans/javaname/com/ebizzConsulting/resources/schemas/java/comEbz
cUtilsEnvironmentTransactionTransactionFactory/StandardTransactionConfigurat
ionType/Connections/RealConnection/ConnectionProvider/Custom) - code 9
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.getSaverStrea
m(SchemaTypeSystemImpl.java:2213)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHead
er(SchemaTypeSystemImpl.java:1588)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.savePointerFile(SchemaT
ypeSystemImpl.java:372)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.savePointersForClassnam
es(SchemaTypeSystemImpl.java:355)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.savePointers(SchemaType
SystemImpl.java:336)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.save(SchemaTypeSystemIm
pl.java:1304)
        at
org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:109
3)
        at
org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:367)

RE: Stack trace when using scomp, with a deep directory structure [reposed from user@xmlbeans.apache.org]

Posted by Mike Skells <mi...@ebizz-consulting.com>.
I fixed this with an xsdconfig file to adjust the namespaces, so as to
reduce the depth 

Mike


  _____  

From: Mike Skells [mailto:mike.skells@ebizz-consulting.com] 
Sent: 02 September 2005 10:18
To: dev@xmlbeans.apache.org
Subject: Stack trace when using scomp, with a deep directory structure
[reposed from user@xmlbeans.apache.org]


Hi,
 
ARe there any workarounds for this?
it seem to be caused by the mkdirs() failing to report that the directory
cannot be created 
on FilerImpl:91 (in the current source for 2.0.0).
 
the underlying error is java.io.FileNotFoundException:
c:\projects\xmlbeansgenerated\classes\schemaorg_apache_xmlbeans\javaname\com
\ebizzConsulting\resources\schemas\java\comEbzcUtilsEnvironmentTransactionTr
ansactionFactory\StandardTransactionConfigurationType\Connections\RealConnec
tion\ConnectionProvider\Custom.xsb (The system cannot find the path
specified)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
        at
org.apache.xmlbeans.impl.util.FilerImpl.createBinaryFile(FilerImpl.java:93)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.getSaverStrea
m(SchemaTypeSystemImpl.java:2209)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHead
er(SchemaTypeSystemImpl.java:1588)
...
 
Mike

  _____  

From: Jacob Danner [mailto:jacobd@bea.com] 
Sent: 01 September 2005 18:59
To: user@xmlbeans.apache.org
Subject: RE: Stack trace when using scomp



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:mike.skells@ebizz-consulting.com] 
Sent: Thursday, September 01, 2005 2:52 AM
To: user@xmlbeans.apache.org
Subject: Stack trace when using scomp

 

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\comEbzcUtilsEnvironmentTransactionTr
ansactionFactory\StandardTransactionConfigurationType\Connections\RealConnec
tion\ConnectionProvider\Custom.xsb (The system cannot find the path
specified)
(schemaorg_apache_xmlbeans.system.sB257CA9B088397728E73131D0CF8D274.schemaor
g_apache_xmlbeans/javaname/com/ebizzConsulting/resources/schemas/java/comEbz
cUtilsEnvironmentTransactionTransactionFactory/StandardTransactionConfigurat
ionType/Connections/RealConnection/ConnectionProvider/Custom) - code 9
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.getSaverStrea
m(SchemaTypeSystemImpl.java:2213)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHead
er(SchemaTypeSystemImpl.java:1588)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.savePointerFile(SchemaT
ypeSystemImpl.java:372)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.savePointersForClassnam
es(SchemaTypeSystemImpl.java:355)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.savePointers(SchemaType
SystemImpl.java:336)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.save(SchemaTypeSystemIm
pl.java:1304)
        at
org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:109
3)
        at
org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:367)