Error in importing the jar

Question

PS: We are using ALSB 2.5
We have got the exported jar from another ALSB environment, but while trying to import, we are getting following error:
The import failed with exception: com.bea.wli.config.component.ValidationException: Validation failed with diagnostic messages. Diagnostics for BusinessService CoverageVerification_IAA/BusinessService/VerifyCoverageBusinessService
ERROR: <0> Invalid xml: Expected attribute: name in element coreEntry@http://www.bea.com/wli/sb/services Location: <ser:coreEntry isProxy="false" isEnabled="true" isAutoPublish="false" xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http">
<ser:description/>
<ser:binding type="SOAP" isSoap12="false" xsi:type="con:SoapBindingType" xmlns:con="http://www.bea.com/wli/sb/services/bindings/config">
<con:wsdl ref="CoverageVerification_IAA/WSDL/VerifyCoverageWSDL"/>
<con:port>
<con:name>VerifyCoveragePort</con:name>
<con:namespace>http://www.ibm.com/industries/financialservices/ValidateCoverage</con:namespace>
</con:port>
<con:WSI-compliant>false</con:WSI-compliant>
</ser:binding>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
</ser:monitoring>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
</ser:coreEntry>
ERROR: <0> Invalid xml: Attribute not allowed (no wildcards allowed): isSoap12 in element binding@http://www.bea.com/wli/sb/services Location: <xml-fragment isSoap12="false" xmlns:con="http://www.bea.com/wli/sb/services/bindings/config" xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http"/>
ERROR: <0> Invalid xml: Expected elements 'registryName@http://www.bea.com/wli/sb/services uddiServiceKey@http://www.bea.com/wli/sb/services modifiedTimeInRegistry@http://www.bea.com/wli/sb/services timeImportedFromRegistry@http://www.bea.com/wli/sb/services' instead of 'sla-alerting@http://www.bea.com/wli/sb/services' here in element coreEntry@http://www.bea.com/wli/sb/services Location: <ser:sla-alerting isEnabled="true" xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
Any help on this would be appreciated.
Rajesh

Answer 1

It seems you are trying to import a configuration generated from ALSB 2.6 into 2.5. In that particular case your configuration contains SOAP 1.2 services that were only introduced in ALSB 2.6 so you will get an error on 2.5.
ASLB guarantees configuration backward compatibility not forward compatibility :)
Gregory Haardt
ALSB Prg. Manager
[email protected]