This is a known issue with the registry in Synapse 1.2. See SYNAPSE-406, SYNAPSE-428 and SYNAPSE-440 for more information.
Andreas On Thu, Dec 4, 2008 at 13:01, Java Programmer <[EMAIL PROTECTED]> wrote: > Hello, > I have problem with an XSLT transfromation - a solution which I found > on web: http://wso2.org/forum/thread/4163 do not work. > XSLT file is well formed with MapForce, and all transformations worked > well with Saxon. With Xalan problem appears when we use: > <xsl:attribute name="id" separator=" "> > <xsl:sequence select="xs:string($Vvar105_fareId_nonNegativeInteger)"/> > </xsl:attribute> > Also when this happen we have got some: > 2008-12-04 12:47:59,500 [192.168.3.17-zzz] [HttpClientWorker-1] DEBUG > SimpleURLRegistry ==> Repository fetch of resource with key : > transform/response.xslt > 2008-12-04 12:47:59,500 [192.168.3.17-zzz] [HttpClientWorker-1] DEBUG > SimpleURLRegistry Perform RegistryEntry lookup for key : > transform/response.xslt > Exception in thread "HttpClientWorker-1" java.lang.StackOverflowError > at > org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:181) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:181) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:181) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:181) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:181) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:181) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:181) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:181) > > Any idea what could be done to repair that? > > Best regards, > Adr >
