ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuli (JIRA)" <j...@apache.org>
Subject [jira] Created: (ODE-103) ServiceMixMapper mulfunction in ServiceMix 3.1 clustering mode (fow type = jms)
Date Wed, 21 Mar 2007 14:39:32 GMT
ServiceMixMapper mulfunction in ServiceMix 3.1 clustering mode (fow type =  jms)
--------------------------------------------------------------------------------

                 Key: ODE-103
                 URL: https://issues.apache.org/jira/browse/ODE-103
             Project: Ode
          Issue Type: Bug
          Components: JBI Integration
    Affects Versions: Incubator
         Environment: WIndowsXP Pro, ServiceMix 3.1
            Reporter: Xuli


1. Set "ode-jbi.messageMapper=org.apache.ode.jbi.msgmap.ServiceMixMapper" in "ode-jbi.properties"
of ODE
2. Set flowName="jms" in <sm:container> of servicemix.xml file, then startup ServiceMix
3.1 in clustering mode. 
3. send a request to BPEL service
ODE will throw an exception when it receives a response of SP from NMR. The Normalized Message
content sent to ServiceMixMapper.toODE() is a StringSource, while the default TransformerFactory
set by following lines is Xalan 2.7 in my machine
---------------------------------------------------------------------------------------------------
    protected BaseXmlMapper() {
        _transformerFactory = TransformerFactory.newInstance();
    }
---------------------------------------------------------------------------------------------------
Xalan throws NAMESPACE_ERR while doing identity transformation with StringSource.

I replaced the above lines with
---------------------------------------------------------------------------------------------------
    protected BaseXmlMapper() {
        _transformerFactory = new net.sf.saxon.TransformerFactoryImpl();
    }
---------------------------------------------------------------------------------------------------
to explicitly instantiate a Saxon TransformerFactory, then solved the problem

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message