Saxonica Developer Community

Today

• 
  Michael Kay Saxon

  19:56 · Commented on issue

  Thanks, that's useful feedback.
  The specification of result document handling in fn:transform() was a significant challenge because the WG didn't want to define some half-baked side-effect mechanism; delegating the disposal of seconda... Bug #4403: Internal error when calling saxon:transform() with stylesheet without primary output

  For the moment, we chain multiple transformations together by using the standard transform() function without any problems (see the simplified example 1 in attached zip). In order to reduce memory consumption, we like to replace this fun...

2019-12-04

• 
  Michael Kay Saxon

  16:14 · Replied in forum

  I'd be grateful if you don't cross post on this forum and on StackOverflow. It gets very confusing when people find the question in one place or another and it appears to be unanswered. You're welcome to use either forum, but please don'... Help: RE: Java - How to manage different expressions in the same way

  Hi! I have this code sample:
  ~~~ java
  package com.test.xml;
  import javax.xml.parsers.DocumentBuilder;
  import javax.xml.parsers.ParserConfigurationException;
  import javax.xml.xpath.XPath;
  import javax.xml.xpath.XPathExpression;
  ...
• 
  Michael Kay This is one of the weaknesses of the JAXP XPath API, which becomes particularly acute when you move to XPath 2.0 with its richer type system: when you execute an XPath expression, you have to say what kind of result is expected.
  I wou...

  15:55 · Replied in forum
• 
  Michael Kay Saxon

  15:48 · Commented on issue

  The fix will ensure that Saxon doesn't crash after reporting the error.
  I've no plans to change the underlying design: Saxon implements the XSD 1.1 specification by default, which makes this schema invalid, but has an XSD 1.0 mode in ... Bug #4402: Cannot be cast to net.sf.saxon.type.ComplexType

  Hi Team,
  We get below exception while loading XSD to SchemaManager object(schemaMgr.load(new StreamSource(xsd));)
  Exception which we get is:-
  net.sf.saxon.type.BuiltInAtomicType (loaded by org.apache.felix.framework.BundleWiringImpl...
• 
  Michael Kay We hope to produce the next maintenance release within the next week.
  However, the patch doesn't solve your problem, and isn't needed for you to make progress. As I explained, the underlying problem is that your schema relies on a fea...

  09:58 · Commented on issue
• 
  Michael Kay Saxon

  11:48 · Commented on issue

  saxon:transform() is pretty ancient and rather reflects the old XSLT 1.0 processing model where there is always one source document. Have you considered using the standard XSLT 3.0 fn:transform() function instead, which is much more flex... Bug #4403: Internal error when calling saxon:transform() with stylesheet without primary output

  For the moment, we chain multiple transformations together by using the standard transform() function without any problems (see the simplified example 1 in attached zip). In order to reduce memory consumption, we like to replace this fun...

2019-12-03

• 
  Michael Kay Saxon

  16:49 · Closed issue

  Preventing the crash seems to be a simple matter of checking before entering the "compile" phase for a complex type that the validation phase was successful: a simple test at the start of `UserComplexType.compile()`. I will commit this p... Bug #4402 (Resolved): Cannot be cast to net.sf.saxon.type.ComplexType

  Hi Team,
  We get below exception while loading XSD to SchemaManager object(schemaMgr.load(new StreamSource(xsd));)
  Exception which we get is:-
  net.sf.saxon.type.BuiltInAtomicType (loaded by org.apache.felix.framework.BundleWiringImpl...
• 
  Michael Kay We have a complexType with complexContent named NoteType:
  ~~~
  <xsd:complexType name="NoteType">
  <xsd:complexContent>
  <xsd:extension base="DescriptionType">
  <xsd:attribute name="author" type="xsd:string" use="optio...

  16:31 · Commented on issue
• 
  Michael Kay I get similar results with Saxon 9.8. Oddly though, oXygen seems to accept this schema, and allows validation using a number of validation engines.

  16:06 · Commented on issue
• 
  Michael Kay Thanks. The output I get on 9.9 is:
  ~~~
  Saxon-EE 9.9.1.5J from Saxonica
  Java version 1.8.0_121
  Using license serial number K007537
  Loading schema document file:/Users/mike/bugs/2019/4402-rathee/Content/XSD.xsd
  Finished loading sc...

  15:49 · Commented on issue