XSLT SE xsl 2.0 and netbean 6.5 issue

[kjain]

Hi,

I have been struggling with trying to make the latest xslt se (with support for 2.0) to work with Netbean design time modules. I followed the steps in:

https://open-esb.dev.java.net/XSLTSE.html

I get the following exception in trying to deploy a composite application project with even a simple xslt service unit.


WARNING: (JBIMA0404) Deployment of service assembly CompositeApp1 succeeded partially; some service units failed to deploy.
    * Component: sun-xslt-engine
      ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU "CompositeApp1-XsltModule1": TRANSL-6001: Failed to parse transformmap descriptor: TRANSL-6017: Transform descriptor is invalid - missing required targetNamespace attribute!


It looks like I have a mismatch between run time and design time support for the xslt service engine. I have tried different combinations of NB nightly builds. Also tried using NB stable build with nightly builds of soarelease netbean modules but nothing seems to work.

Will appreciate any feedback since this is proving to be a show stopper issue.

Thanks.  

[Vitaly Bychkov]

Hi kjain,

You can't use netbeans 6.5 with the latest XSLT SE.
The latest XSLT SE design time modules are netbeans 6.1 compatiable and
are not binary compatible with netbeans 6.5.

Have you tried the OpenESB nightly build:
https://open-esb.dev.java.net/Downloads.html ?
It contains both the latest runtime and design time modules.

The steps in https://open-esb.dev.java.net/XSLTSE.html regarding design
side modules is correct just for the netbeans 6.1.
I'll add note regarding it to the https://open-esb.dev.java.net/XSLTSE.html.

If you have any questions feel free to ask.

Thank you,
Vitaly.

kjain wrote:

> Hi,
>
> I have been struggling with trying to make the latest xslt se (with support
> for 2.0) to work with Netbean design time modules. I followed the steps in:
>
> https://open-esb.dev.java.net/XSLTSE.html
>
> I get the following exception in trying to deploy a composite application
> project with even a simple xslt service unit.
>
>
> WARNING: (JBIMA0404) Deployment of service assembly CompositeApp1 succeeded
> partially; some service units failed to deploy.
>     * Component: sun-xslt-engine
>       ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU
> "CompositeApp1-XsltModule1": TRANSL-6001: Failed to parse transformmap
> descriptor: TRANSL-6017: Transform descriptor is invalid - missing required
> targetNamespace attribute!
>
>
> It looks like I have a mismatch between run time and design time support for
> the xslt service engine. I have tried different combinations of NB nightly
> builds. Also tried using NB stable build with nightly builds of soarelease
> netbean modules but nothing seems to work.
>
> Will appreciate any feedback since this is proving to be a show stopper
> issue.
>
> Thanks.  
>
>
>
>
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[kjain]

Thanks for the quick reply. I was using netbean 6.5 because of the JDBC database wizard support. I did not see that in netbean 6.1. Am I missing something?  

Vitaly Bychkov wrote:

Hi kjain,

You can't use netbeans 6.5 with the latest XSLT SE.
The latest XSLT SE design time modules are netbeans 6.1 compatiable and
are not binary compatible with netbeans 6.5.

Have you tried the OpenESB nightly build:
https://open-esb.dev.java.net/Downloads.html ?
It contains both the latest runtime and design time modules.

The steps in https://open-esb.dev.java.net/XSLTSE.html regarding design
side modules is correct just for the netbeans 6.1.
I'll add note regarding it to the https://open-esb.dev.java.net/XSLTSE.html.

If you have any questions feel free to ask.

Thank you,
Vitaly.

kjain wrote:
> Hi,
>
> I have been struggling with trying to make the latest xslt se (with support
> for 2.0) to work with Netbean design time modules. I followed the steps in:
>
> https://open-esb.dev.java.net/XSLTSE.html
>
> I get the following exception in trying to deploy a composite application
> project with even a simple xslt service unit.
>
>
> WARNING: (JBIMA0404) Deployment of service assembly CompositeApp1 succeeded
> partially; some service units failed to deploy.
>     * Component: sun-xslt-engine
>       ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU
> "CompositeApp1-XsltModule1": TRANSL-6001: Failed to parse transformmap
> descriptor: TRANSL-6017: Transform descriptor is invalid - missing required
> targetNamespace attribute!
>
>
> It looks like I have a mismatch between run time and design time support for
> the xslt service engine. I have tried different combinations of NB nightly
> builds. Also tried using NB stable build with nightly builds of soarelease
> netbean modules but nothing seems to work.
>
> Will appreciate any feedback since this is proving to be a show stopper
> issue.
>
> Thanks.  
>
>
>
>
>
>  


---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]

[kjain]

Thanks. I can get XSLT service to deploy with the nightly build. The issue I am facing now is that when I deploy this xslt service with a bpel process (which invokes the xslt service as part of a process) in a Composite application, I get the following exception though the xsd being mentioned in the exception was imported as a external schema document.Did any one run into the same issue? Thanks again for the help.


      ERROR: (SOAPBC_DEPLOY_2) HTTPBC-E00201: Deployment failed. javax.wsdl.WSDLException: WSDLException (at /definitions/types/xsd:schema/xs:schema/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at ''IC-MSP-InfoPool-v4.1.xsd'', relative to ''file:/mnt/Edrive/sun/GlassFishESB/glassfish/domains/domain1/jbi/service-assemblies/ICMSPCompositeApp/ICMSPCompositeApp-sun-http-binding/sun-http-binding/META-INF/TestBPEL/src/_references/_projects/ICMSPPubKOXsltModule/src/IC-MSP-Report-v4.1.xsd''.: java.io.FileNotFoundException: This file was not found: file:/mnt/Edrive/sun/GlassFishESB/glassfish/domains/domain1/jbi/service-assemblies/ICMSPCompositeApp/ICMSPCompositeApp-sun-http-binding/sun-http-binding/META-INF/TestBPEL/src/_references/_projects/ICMSPPubKOXsltModule/src/IC-MSP-InfoPool-v4.1.xsd

kjain wrote:

Thanks for the quick reply. I was using netbean 6.5 because of the JDBC database wizard support. I did not see that in netbean 6.1. Am I missing something?  

Vitaly Bychkov wrote:

Hi kjain,

You can't use netbeans 6.5 with the latest XSLT SE.
The latest XSLT SE design time modules are netbeans 6.1 compatiable and
are not binary compatible with netbeans 6.5.

Have you tried the OpenESB nightly build:
https://open-esb.dev.java.net/Downloads.html ?
It contains both the latest runtime and design time modules.

The steps in https://open-esb.dev.java.net/XSLTSE.html regarding design
side modules is correct just for the netbeans 6.1.
I'll add note regarding it to the https://open-esb.dev.java.net/XSLTSE.html.

If you have any questions feel free to ask.

Thank you,
Vitaly.

kjain wrote:
> Hi,
>
> I have been struggling with trying to make the latest xslt se (with support
> for 2.0) to work with Netbean design time modules. I followed the steps in:
>
> https://open-esb.dev.java.net/XSLTSE.html
>
> I get the following exception in trying to deploy a composite application
> project with even a simple xslt service unit.
>
>
> WARNING: (JBIMA0404) Deployment of service assembly CompositeApp1 succeeded
> partially; some service units failed to deploy.
>     * Component: sun-xslt-engine
>       ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU
> "CompositeApp1-XsltModule1": TRANSL-6001: Failed to parse transformmap
> descriptor: TRANSL-6017: Transform descriptor is invalid - missing required
> targetNamespace attribute!
>
>
> It looks like I have a mismatch between run time and design time support for
> the xslt service engine. I have tried different combinations of NB nightly
> builds. Also tried using NB stable build with nightly builds of soarelease
> netbean modules but nothing seems to work.
>
> Will appreciate any feedback since this is proving to be a show stopper
> issue.
>
> Thanks.  
>
>
>
>
>
>  


---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]

[kjain]

Folks,

Apologize for another post today. I am stuck with XSLT 2.0 issue for quite a while now. I did make some progress based on earlier feedback but my issue seems to remain. Now I can deploy but get a run time error:

Caused by: javax.xml.transform.TransformerException: java.lang.RuntimeException: Unsupported XSL element 'http://www.w3.org/1999/XSL/Transform:namespace'
        at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:717)
        at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
        at com.sun.transform.engine.xslt.XsltEngine.transform(XsltEngine.java:73)
        ... 12 more
Caused by: java.lang.RuntimeException: Unsupported XSL element 'http://www.w3.org/1999/XSL/Transform:namespace'
        at com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.runTimeError(BasisLibrary.java:1496)
        at com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.runTimeError(BasisLibrary.java:1500)
        at com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.unsupported_Element F(BasisLibrary.java:427)

I have configured xslt-engine to use XSLT_2_0.

Do I need to do anything else?

Thanks.

kjain wrote:

Hi,

I have been struggling with trying to make the latest xslt se (with support for 2.0) to work with Netbean design time modules. I followed the steps in:

https://open-esb.dev.java.net/XSLTSE.html

I get the following exception in trying to deploy a composite application project with even a simple xslt service unit.


WARNING: (JBIMA0404) Deployment of service assembly CompositeApp1 succeeded partially; some service units failed to deploy.
    * Component: sun-xslt-engine
      ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU "CompositeApp1-XsltModule1": TRANSL-6001: Failed to parse transformmap descriptor: TRANSL-6017: Transform descriptor is invalid - missing required targetNamespace attribute!


It looks like I have a mismatch between run time and design time support for the xslt service engine. I have tried different combinations of NB nightly builds. Also tried using NB stable build with nightly builds of soarelease netbean modules but nothing seems to work.

Will appreciate any feedback since this is proving to be a show stopper issue.

Thanks.  

[Vitaly Bychkov]

Some javascript/style in this post has been disabled (why?)

Hi kjain,

OpenESB nightly build contains Database BC(both runtime and design time). 
Db BC have to be used instead JDBC BC and SQL SE.

More detailed description is here:
http://wiki.open-esb.java.net/Wiki.jsp?page=DatabaseBC

http://wiki.open-esb.java.net/Wiki.jsp?page=DBBCAnnouncement

Thank you,
Vitaly.
kjain wrote:

Thanks for the quick reply. I was using netbean 6.5 because of the JDBC
database wizard support. I did not see that in netbean 6.1. Am I missing
something?   



Vitaly Bychkov wrote:
  

Hi kjain,

You can't use netbeans 6.5 with the latest XSLT SE.
The latest XSLT SE design time modules are netbeans 6.1 compatiable and 
are not binary compatible with netbeans 6.5.

Have you tried the OpenESB nightly build: 
https://open-esb.dev.java.net/Downloads.html ?
It contains both the latest runtime and design time modules.

The steps in https://open-esb.dev.java.net/XSLTSE.html regarding design 
side modules is correct just for the netbeans 6.1.
I'll add note regarding it to the
https://open-esb.dev.java.net/XSLTSE.html.

If you have any questions feel free to ask.

Thank you,
Vitaly.

kjain wrote:
    

Hi,

I have been struggling with trying to make the latest xslt se (with
support
for 2.0) to work with Netbean design time modules. I followed the steps
in:

https://open-esb.dev.java.net/XSLTSE.html

I get the following exception in trying to deploy a composite application
project with even a simple xslt service unit.


WARNING: (JBIMA0404) Deployment of service assembly CompositeApp1
succeeded
partially; some service units failed to deploy.
    * Component: sun-xslt-engine
      ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU
"CompositeApp1-XsltModule1": TRANSL-6001: Failed to parse transformmap
descriptor: TRANSL-6017: Transform descriptor is invalid - missing
required
targetNamespace attribute!


It looks like I have a mismatch between run time and design time support
for
the xslt service engine. I have tried different combinations of NB
nightly
builds. Also tried using NB stable build with nightly builds of
soarelease
netbean modules but nothing seems to work.

Will appreciate any feedback since this is proving to be a show stopper
issue.

Thanks.  





  
      

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



    

[Vitaly Bychkov]

Some javascript/style in this post has been disabled (why?)

Hi kjain,

Could you please attach sample project.

Thank you,
Vitaly.

kjain wrote:

Folks,

Apologize for another post today. I am stuck with XSLT 2.0 issue for quite a
while now. I did make some progress based on earlier feedback but my issue
seems to remain. Now I can deploy but get a run time error:

Caused by: javax.xml.transform.TransformerException:
java.lang.RuntimeException: Unsupported XSL element
'http://www.w3.org/1999/XSL/Transform:namespace'
	at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:717)
	at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
	at com.sun.transform.engine.xslt.XsltEngine.transform(XsltEngine.java:73)
	... 12 more
Caused by: java.lang.RuntimeException: Unsupported XSL element
'http://www.w3.org/1999/XSL/Transform:namespace'
	at
com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.runTimeError(BasisLibrary.java:1496)
	at
com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.runTimeError(BasisLibrary.java:1500)
	at
com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.unsupported_Element
F(BasisLibrary.java:427)

I have configured xslt-engine to use XSLT_2_0. 

Do I need to do anything else? 

Thanks.


kjain wrote:
  

Hi,

I have been struggling with trying to make the latest xslt se (with
support for 2.0) to work with Netbean design time modules. I followed the
steps in:

https://open-esb.dev.java.net/XSLTSE.html

I get the following exception in trying to deploy a composite application
project with even a simple xslt service unit.


WARNING: (JBIMA0404) Deployment of service assembly CompositeApp1
succeeded partially; some service units failed to deploy.
    * Component: sun-xslt-engine
      ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU
"CompositeApp1-XsltModule1": TRANSL-6001: Failed to parse transformmap
descriptor: TRANSL-6017: Transform descriptor is invalid - missing
required targetNamespace attribute!


It looks like I have a mismatch between run time and design time support
for the xslt service engine. I have tried different combinations of NB
nightly builds. Also tried using NB stable build with nightly builds of
soarelease netbean modules but nothing seems to work.

Will appreciate any feedback since this is proving to be a show stopper
issue.

Thanks.  






    

[kjain]

Really appreciate the quick replies on this forum.

I did go past this issue. Did not find "'WSDL from Database' Wizard. " but did use esb/binding to create a database binding.

Thanks again.

Vitaly Bychkov wrote:

Hi kjain,

OpenESB nightly build contains Database BC(both runtime and design time).
Db BC have to be used instead JDBC BC and SQL SE.

More detailed description is here:
http://wiki.open-esb.java.net/Wiki.jsp?page=DatabaseBC

http://wiki.open-esb.java.net/Wiki.jsp?page=DBBCAnnouncement


Thank you,
Vitaly.
kjain wrote:
> Thanks for the quick reply. I was using netbean 6.5 because of the JDBC
> database wizard support. I did not see that in netbean 6.1. Am I missing
> something?  
>
>
>
> Vitaly Bychkov wrote:
>  
>> Hi kjain,
>>
>> You can't use netbeans 6.5 with the latest XSLT SE.
>> The latest XSLT SE design time modules are netbeans 6.1 compatiable and
>> are not binary compatible with netbeans 6.5.
>>
>> Have you tried the OpenESB nightly build:
>> https://open-esb.dev.java.net/Downloads.html ?
>> It contains both the latest runtime and design time modules.
>>
>> The steps in https://open-esb.dev.java.net/XSLTSE.html regarding design
>> side modules is correct just for the netbeans 6.1.
>> I'll add note regarding it to the
>> https://open-esb.dev.java.net/XSLTSE.html.
>>
>> If you have any questions feel free to ask.
>>
>> Thank you,
>> Vitaly.
>>
>> kjain wrote:
>>    
>>> Hi,
>>>
>>> I have been struggling with trying to make the latest xslt se (with
>>> support
>>> for 2.0) to work with Netbean design time modules. I followed the steps
>>> in:
>>>
>>> https://open-esb.dev.java.net/XSLTSE.html
>>>
>>> I get the following exception in trying to deploy a composite application
>>> project with even a simple xslt service unit.
>>>
>>>
>>> WARNING: (JBIMA0404) Deployment of service assembly CompositeApp1
>>> succeeded
>>> partially; some service units failed to deploy.
>>>     * Component: sun-xslt-engine
>>>       ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU
>>> "CompositeApp1-XsltModule1": TRANSL-6001: Failed to parse transformmap
>>> descriptor: TRANSL-6017: Transform descriptor is invalid - missing
>>> required
>>> targetNamespace attribute!
>>>
>>>
>>> It looks like I have a mismatch between run time and design time support
>>> for
>>> the xslt service engine. I have tried different combinations of NB
>>> nightly
>>> builds. Also tried using NB stable build with nightly builds of
>>> soarelease
>>> netbean modules but nothing seems to work.
>>>
>>> Will appreciate any feedback since this is proving to be a show stopper
>>> issue.
>>>
>>> Thanks.  
>>>
>>>
>>>
>>>
>>>
>>>  
>>>      
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [e-mail]
>> For additional commands, e-mail: [e-mail]
>>
>>
>>
>>    
>
>  

[kjain]

Thanks for the reply. Went past this issue by manually changing "GlassFishESB/glassfish/domains/domain1/jbi/components/sun-xslt-engine/install_root/workspace/config.properties" to use 2.0. Now it is using Saxon but now get the following error in HTTPBC:

 [#|2009-01-05T23:29:10.028-0500|WARNING|sun-appserver9.1|com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider|_ThreadID=34;_ThreadName=HTTPBC-OutboundReceiver-1;_RequestID=8e391918-bf31-462b-a22d-440123e60dde;|HTTPBC-E00799: Message denormalization failed
javax.jbi.messaging.MessagingException: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
        at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:108)
        at com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.onReply(AsyncJBIProvider.java:274)
        at com.sun.jbi.httpsoapbc.MessageExchangeSupport.notifyOfReply(MessageExchangeSupport.java:126)
        at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:424)
        at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:242)
        at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)

Attaching the CA zip file.
Thanks.

CompositeApp2.zip

Vitaly Bychkov wrote:

Hi kjain,

Could you please attach sample project.

Thank you,
Vitaly.

kjain wrote:
> Folks,
>
> Apologize for another post today. I am stuck with XSLT 2.0 issue for quite a
> while now. I did make some progress based on earlier feedback but my issue
> seems to remain. Now I can deploy but get a run time error:
>
> Caused by: javax.xml.transform.TransformerException:
> java.lang.RuntimeException: Unsupported XSL element
> 'http://www.w3.org/1999/XSL/Transform:namespace'
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:717)
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
> at com.sun.transform.engine.xslt.XsltEngine.transform(XsltEngine.java:73)
> ... 12 more
> Caused by: java.lang.RuntimeException: Unsupported XSL element
> 'http://www.w3.org/1999/XSL/Transform:namespace'
> at
> com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.runTimeError(BasisLibrary.java:1496)
> at
> com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.runTimeError(BasisLibrary.java:1500)
> at
> com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.unsupported_Element
> F(BasisLibrary.java:427)
>
> I have configured xslt-engine to use XSLT_2_0.
>
> Do I need to do anything else?
>
> Thanks.
>
>
> kjain wrote:
>  
>> Hi,
>>
>> I have been struggling with trying to make the latest xslt se (with
>> support for 2.0) to work with Netbean design time modules. I followed the
>> steps in:
>>
>> https://open-esb.dev.java.net/XSLTSE.html
>>
>> I get the following exception in trying to deploy a composite application
>> project with even a simple xslt service unit.
>>
>>
>> WARNING: (JBIMA0404) Deployment of service assembly CompositeApp1
>> succeeded partially; some service units failed to deploy.
>>     * Component: sun-xslt-engine
>>       ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU
>> "CompositeApp1-XsltModule1": TRANSL-6001: Failed to parse transformmap
>> descriptor: TRANSL-6017: Transform descriptor is invalid - missing
>> required targetNamespace attribute!
>>
>>
>> It looks like I have a mismatch between run time and design time support
>> for the xslt service engine. I have tried different combinations of NB
>> nightly builds. Also tried using NB stable build with nightly builds of
>> soarelease netbean modules but nothing seems to work.
>>
>> Will appreciate any feedback since this is proving to be a show stopper
>> issue.
>>
>> Thanks.  
>>
>>
>>
>>
>>
>>
>>    
>

>  

[kjain]

Just wanted to post that I was able to go past the issue.

Thanks.

kjain wrote:

Thanks for the reply. Went past this issue by manually changing "GlassFishESB/glassfish/domains/domain1/jbi/components/sun-xslt-engine/install_root/workspace/config.properties" to use 2.0. Now it is using Saxon but now get the following error in HTTPBC:

 [#|2009-01-05T23:29:10.028-0500|WARNING|sun-appserver9.1|com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider|_ThreadID=34;_ThreadName=HTTPBC-OutboundReceiver-1;_RequestID=8e391918-bf31-462b-a22d-440123e60dde;|HTTPBC-E00799: Message denormalization failed
javax.jbi.messaging.MessagingException: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
        at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:108)
        at com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.onReply(AsyncJBIProvider.java:274)
        at com.sun.jbi.httpsoapbc.MessageExchangeSupport.notifyOfReply(MessageExchangeSupport.java:126)
        at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:424)
        at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:242)
        at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)

Attaching the CA zip file.
Thanks.

CompositeApp2.zip

Vitaly Bychkov wrote:

Hi kjain,

Could you please attach sample project.

Thank you,
Vitaly.

kjain wrote:
> Folks,
>
> Apologize for another post today. I am stuck with XSLT 2.0 issue for quite a
> while now. I did make some progress based on earlier feedback but my issue
> seems to remain. Now I can deploy but get a run time error:
>
> Caused by: javax.xml.transform.TransformerException:
> java.lang.RuntimeException: Unsupported XSL element
> 'http://www.w3.org/1999/XSL/Transform:namespace'
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:717)
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
> at com.sun.transform.engine.xslt.XsltEngine.transform(XsltEngine.java:73)
> ... 12 more
> Caused by: java.lang.RuntimeException: Unsupported XSL element
> 'http://www.w3.org/1999/XSL/Transform:namespace'
> at
> com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.runTimeError(BasisLibrary.java:1496)
> at
> com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.runTimeError(BasisLibrary.java:1500)
> at
> com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.unsupported_Element
> F(BasisLibrary.java:427)
>
> I have configured xslt-engine to use XSLT_2_0.
>
> Do I need to do anything else?
>
> Thanks.
>
>
> kjain wrote:
>  
>> Hi,
>>
>> I have been struggling with trying to make the latest xslt se (with
>> support for 2.0) to work with Netbean design time modules. I followed the
>> steps in:
>>
>> https://open-esb.dev.java.net/XSLTSE.html
>>
>> I get the following exception in trying to deploy a composite application
>> project with even a simple xslt service unit.
>>
>>
>> WARNING: (JBIMA0404) Deployment of service assembly CompositeApp1
>> succeeded partially; some service units failed to deploy.
>>     * Component: sun-xslt-engine
>>       ERROR: (COMPTK_DEPLOY_1) COMPTK-6018: Failed to deploy SU
>> "CompositeApp1-XsltModule1": TRANSL-6001: Failed to parse transformmap
>> descriptor: TRANSL-6017: Transform descriptor is invalid - missing
>> required targetNamespace attribute!
>>
>>
>> It looks like I have a mismatch between run time and design time support
>> for the xslt service engine. I have tried different combinations of NB
>> nightly builds. Also tried using NB stable build with nightly builds of
>> soarelease netbean modules but nothing seems to work.
>>
>> Will appreciate any feedback since this is proving to be a show stopper
>> issue.
>>
>> Thanks.  
>>
>>
>>
>>
>>
>>
>>    
>

>  

[vishal_with_me]

Hi Kjain,

could you please help on this. I am getting the same error in my server.log file-

[#|2009-10-30T15:04:22.818+1100|WARNING|sun-appserver2.1|com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer|_ThreadID=2549;_ThreadName=HTTPBC-InboundReply-1;_RequestID=45b28eeb-880a-4207-8dc5-9bacb443cce5;|HTTPBC-E00639: Failed to initialize SOAP fault with exception information (details below). Raising HTTP exception.
java.lang.NullPointerException
        at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalizeError(JAXWSDenormalizer.java:255)
        at com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.onReply(AsyncJBIProvider.java:353)
        at com.sun.jbi.httpsoapbc.MessageExchangeSupport.notifyOfReply(MessageExchangeSupport.java:126)
        at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:429)
        at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:247)
        at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
        at java.lang.Thread.run(Thread.java:810)

Please suggest if you have any pointer.
Thanks in advance

~best regards,
Vishal