This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Reproduced in build070624. Steps to reproduce: - create XSLT service; - deploy and start it. Following errors occured: * Component: sun-xslt-engine ERROR: () Content is not allowed in prolog. * Component: sun-http-binding ERROR: (SOAPBC_INIT_1) Failure during init: java.lang.Exception: An activated endpoint already has the same SOAP
I've fixed design side problem, but the issue still there. server log: -------------------------------------------------- [#|2007-06-27T13:40:40.406+0400|SEVERE|sun-appserver9.1|sun-xslt-engine.com.sun.transform.descriptor.DescriptorParser|_ThreadID=42;_ThreadName=CompositeApp1-XsltModule1;_RequestID=53a1e2f6-17c8-400a-89d0-dfa993c080b6;|Specified input message part "inOpVar1.part1In" does not exist!|#] [#|2007-06-27T13:40:40.406+0400|SEVERE|sun-appserver9.1|sun-xslt-engine.com.sun.transform.descriptor.DescriptorParser|_ThreadID=42;_ThreadName=CompositeApp1-XsltModule1;_RequestID=53a1e2f6-17c8-400a-89d0-dfa993c080b6;|Transform descriptor parsing failed: Specified input message part "inOpVar1.part1In" does not exist! com.sun.transform.descriptor.DescriptorParseException: Specified input message part "inOpVar1.part1In" does not exist! at com.sun.transform.descriptor.DescriptorParser.error(DescriptorParser.java:624) at com.sun.transform.descriptor.DescriptorParser.createTransform(DescriptorParser.java:421) at com.sun.transform.descriptor.DescriptorParser.createTransform(DescriptorParser.java:384) at com.sun.transform.descriptor.DescriptorParser.startElement(DescriptorParser.java:245) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1337) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2740) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:645) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:508) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at com.sun.transform.descriptor.ProcessDescriptor.parse(ProcessDescriptor.java:140) at com.sun.jbi.engine.xslt.endpoint.XsltseDescriptor.parse(XsltseDescriptor.java:70) at com.sun.transform.descriptor.ProcessDescriptor.parse(ProcessDescriptor.java:115) at com.sun.jbi.engine.xslt.endpoint.XsltseEndpointManager.initServiceUnit(XsltseEndpointManager.java:133) at com.sun.jbi.component.lifecycle.impl.AbstractServiceUnitManager.init(AbstractServiceUnitManager.java:144) at com.sun.jbi.framework.ServiceUnitOperation.process(ServiceUnitOperation.java:167) at com.sun.jbi.framework.Operation.run(Operation.java:104) at java.lang.Thread.run(Thread.java:619) |#] -------------------------------------------------- It looks like there is server side issue too. I've filled issue on xslt-se(6574547)
Created attachment 44462 [details] XSLT project
This issue is marked as a stopper for M10. Please provide the fix into the trunk and "release60-m10".
The fix for design side issue was committed into trunk and release60-m10.
Petr, this bug should be fixed on design time side (in XSLT module of NB) and on runtime side (XSLT engine). The fix on design time side is already in place. The fix on runtime is not. I'm figuring out when runtime fix will be available.
Runtime issue was fixed. Need verification in build after 200706272201.
Could you please verify this issue for the latest M10 build? Thanks.
Peter, it can be verified only on the next M10 build which will include new runtimes.
Verified in build070628.
please set up the right Target Milestone