SA deployment error with whitespace in jbi.xml <artifacts-zip> value
--------------------------------------------------------------------

                 Key: SM-564
                 URL: https://issues.apache.org/activemq/browse/SM-564
             Project: ServiceMix
          Issue Type: Bug
    Affects Versions: 3.0-M2
         Environment: Apache ServiceMix ESB: 3.0-M2-incubating
windows SP2 
            Reporter: fred smith
            Priority: Minor


I reformatted my Service Assembly's jbi.xml file and the SA failed to deploy.  
Logging shows the following error:

java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
<jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message"; 
version="1.0">
<jbi-task-result>
<frmwk-task-result>
<frmwk-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg>
<msg-loc-info>
<loc-token/>
<loc-message>Artifact     gestalt-jbi-pingpong-ws-lw-su-HEAD.zip not found for 
service unit pingpong-lw-su</loc-message>
</msg-loc-info>
</task-status-msg>
</task-result-details>
</frmwk-task-result-details>
</frmwk-task-result>
</jbi-task-result>
</jbi-task>

The problem can be recreated with whitespace after the <artifacts-zip> tag 
value (shown below). If the whitespace is removed then the SA is deployed 
correctly.

===== incorrect =====
<service-unit>
  <identification>
    <name>pingpong-lw-su</name>
    <description>Contains the binding for the lwcontainer SE</description>
  </identification>
  <target>
    <artifacts-zip>    gestalt-jbi-pingpong-ws-lw-su-HEAD.zip</artifacts-zip>
    <component-name>servicemix-lwcontainer</component-name>
  </target>
</service-unit>

===== correct =====

    <artifacts-zip>gestalt-jbi-pingpong-ws-lw-su-HEAD.zip</artifacts-zip> 


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to