Re: [Xmltask-users] Invalid XML output

Leyzerzon, Simeon Fri, 22 Oct 2010 21:48:09 -0700

Looks like Weblogic is confused by the namespaces produced.  In an insert, I 
normally specify the namespace inside the element in the CDATA stanza, 
something like this:



<xmltask source="./src/weblogic-application.xml" 
destbuffer="intermediate.weblogic.application.xml.buffer" report="@{report}">

<insert path="/:weblogic-application" position="under">

<![CDATA[

<prefer-application-packages xmlns="http://www.bea.com/ns/weblogic/90";>

<package-name>javax.persistence.*</package-name>

</prefer-application-packages>

]]>

</insert>

</xmltask>

So, in your case I'd try:

<![CDATA[
<jms-system-resource  xmlns="http://www.bea.com/ns/weblogic/920/domain";>
. . . . .

Regards,
Simeon

________________________________
From: V I S H [mailto:vishal.ra...@gmail.com]
Sent: Thursday, October 21, 2010 5:00 PM
To: xmltask-users@lists.sourceforge.net
Subject: [Xmltask-users] Invalid XML output

Hi,

I am using XMLTask for updating weblogic domain config.xml file. Following is 
my code:

<xmltask 
source="${domain.home}/${domain.name<http://domain.name>}/config/config.xml" 
dest="${domain.home}/${domain.name<http://domain.name>}/config/config.xml" 
report="true" failwithoutmatch="true" outputter="simple" preservetype="false" 
expandEntityReferences="false">
<insert path="/:domain/:file-store" position="after">
<![CDATA[
<jms-system-resource>
   <name>res1</name>
   <target>AdminServer</target>
   <sub-deployment>
     <name>res1sub</name>
     <target>testJMSServer</target>
   </sub-deployment>
   <descriptor-file-name>jms/jms1.xml</descriptor-file-name>
 </jms-system-resource>
 <jms-system-resource>
   <name>ModemReset</name>
   <target>AdminServer</target>
   <sub-deployment>
     <name>JMSServer</name>
     <target>testJMSServer</target>
   </sub-deployment>
   <descriptor-file-name>jms/jms2.xml</descriptor-file-name>
 </jms-system-resource>
     ]]>
</insert>
</xmltask>

The output XML generated by this code is not a valid XML file, that's what 
weblogic complains and even if I use same output file again with XMLTask then 
XMLTask also gives invalid XML error.

My Original config file is:
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://www.bea.com/ns/weblogic/920/domain"; 
xmlns:sec="http://www.bea.com/ns/weblogic/90/security"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls"; 
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/xacml 
http://www.bea.com/ns/weblogic/90/security/xacml.xsd 
http://www.bea.com/ns/weblogic/90/security 
http://www.bea.com/ns/weblogic/90/security.xsd 
http://www.bea.com/ns/weblogic/920/domain 
http://www.bea.com/ns/weblogic/920/domain.xsd 
http://www.bea.com/ns/weblogic/90/security/wls 
http://www.bea.com/ns/weblogic/90/security/wls.xsd";>
  <name>testJMS</name>
  <domain-version>9.2.3.0</domain-version>
  <security-configuration>
    <name>testJMS</name>
    <realm>
      <sec:authentication-provider 
xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
      <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
        <sec:active-type>AuthenticatedUser</sec:active-type>
      </sec:authentication-provider>
      <sec:role-mapper 
xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml"; 
xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
      <sec:authorizer 
xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml"; 
xsi:type="xac:xacml-authorizerType"></sec:authorizer>
      <sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
      <sec:credential-mapper 
xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
      <sec:cert-path-provider 
xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
      <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
      <sec:name>myrealm</sec:name>
    </realm>
    <default-realm>myrealm</default-realm>
    
<credential-encrypted>{3DES}9chlAMunFZGk1Y21VwyNNrz2xuR3B97J/zQHctkeQalzeIPxD4MbDrOsp/ioOe8J8OhFN3tYxj9ckbpoAUmPdElIyfXW1RBj</credential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    
<node-manager-password-encrypted>{3DES}OLqeHeXZfknEW4I0J6OhKg==</node-manager-password-encrypted>
  </security-configuration>
  <server>
    <name>AdminServer</name>
    <listen-address>127.0.0.1</listen-address>
  </server>
  <embedded-ldap>
    <name>testJMS</name>
    
<credential-encrypted>{3DES}I9HbR4ChiGS/0ZDYym6o3gK+GAl/E1PCYlDKywX5WUk=</credential-encrypted>
  </embedded-ldap>
  <configuration-version>9.2.3.0</configuration-version>
  <jms-server>
    <name>testJMSServer</name>
    <target>AdminServer</target>
    <persistent-store>testJMSFileStore</persistent-store>
  </jms-server>
  <file-store>
    <name>testJMSFileStore</name>
    <directory>testJMSFileStore</directory>
    <synchronous-write-policy>Direct-Write</synchronous-write-policy>
    <target>AdminServer</target>
  </file-store>
  <admin-server-name>AdminServer</admin-server-name>
</domain>

And the Output generated is:
==========================
<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<domain __NS1:="http://www.bea.com/ns/weblogic/920/domain"; 
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/xacml 
http://www.bea.com/ns/weblogic/90/security/xacml.xsd 
http://www.bea.com/ns/weblogic/90/security 
http://www.bea.com/ns/weblogic/90/security.xsd 
http://www.bea.com/ns/weblogic/920/domain 
http://www.bea.com/ns/weblogic/920/domain.xsd 
http://www.bea.com/ns/weblogic/90/security/wls 
http://www.bea.com/ns/weblogic/90/security/wls.xsd"; 
xmlns="http://www.bea.com/ns/weblogic/920/domain"; 
xmlns:__NS1="http://www.w3.org/2000/xmlns/"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  <name>testJMS</name>
  <domain-version>9.2.3.0</domain-version>
  <security-configuration>
    <name>testJMS</name>
    <realm>
      <sec:authentication-provider xsi:type="wls:default-authenticatorType" 
xmlns:sec="http://www.bea.com/ns/weblogic/90/security";></sec:authentication-provider>
      <sec:authentication-provider xsi:type="wls:default-identity-asserterType" 
xmlns:sec="http://www.bea.com/ns/weblogic/90/security";>
        <sec:active-type>AuthenticatedUser</sec:active-type>
      </sec:authentication-provider>
      <sec:role-mapper xsi:type="xac:xacml-role-mapperType" 
xmlns:sec="http://www.bea.com/ns/weblogic/90/security";></sec:role-mapper>
      <sec:authorizer xsi:type="xac:xacml-authorizerType" 
xmlns:sec="http://www.bea.com/ns/weblogic/90/security";></sec:authorizer>
      <sec:adjudicator xsi:type="wls:default-adjudicatorType" 
xmlns:sec="http://www.bea.com/ns/weblogic/90/security";></sec:adjudicator>
      <sec:credential-mapper xsi:type="wls:default-credential-mapperType" 
xmlns:sec="http://www.bea.com/ns/weblogic/90/security";></sec:credential-mapper>
      <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType" 
xmlns:sec="http://www.bea.com/ns/weblogic/90/security";></sec:cert-path-provider>
      <sec:cert-path-builder 
xmlns:sec="http://www.bea.com/ns/weblogic/90/security";>WebLogicCertPathProvider</sec:cert-path-builder>
      <sec:name 
xmlns:sec="http://www.bea.com/ns/weblogic/90/security";>myrealm</sec:name>
    </realm>
    <default-realm>myrealm</default-realm>
    
<credential-encrypted>{3DES}9chlAMunFZGk1Y21VwyNNrz2xuR3B97J/zQHctkeQalzeIPxD4MbDrOsp/ioOe8J8OhFN3tYxj9ckbpoAUmPdElIyfXW1RBj</credential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    
<node-manager-password-encrypted>{3DES}OLqeHeXZfknEW4I0J6OhKg==</node-manager-password-encrypted>
  </security-configuration>
  <server>
    <name>AdminServer</name>
    <listen-address>127.0.0.1</listen-address>
  </server>
  <embedded-ldap>
    <name>testJMS</name>
    
<credential-encrypted>{3DES}I9HbR4ChiGS/0ZDYym6o3gK+GAl/E1PCYlDKywX5WUk=</credential-encrypted>
  </embedded-ldap>
  <configuration-version>9.2.3.0</configuration-version>
  <jms-server>
    <name>testJMSServer</name>
    <target>AdminServer</target>
    <persistent-store>testJMSFileStore</persistent-store>
  </jms-server>
  <file-store>
    <name>testJMSFileStore</name>
    <directory>testJMSFileStore</directory>
    <synchronous-write-policy>Direct-Write</synchronous-write-policy>
    <target>AdminServer</target>
  </file-store>
  <jms-system-resource __NS1:="" xmlns="">
    <name>res1</name>
    <target>AdminServer</target>
    <sub-deployment>
      <name>res1sub</name>
      <target>testJMSServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/jms1.xml</descriptor-file-name>
  </jms-system-resource>
  <jms-system-resource __NS1:="" xmlns="">
    <name>ModemReset</name>
    <target>AdminServer</target>
    <sub-deployment>
      <name>JMSServer</name>
      <target>testJMSServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/jms2.xml</descriptor-file-name>
  </jms-system-resource>
  <admin-server-name>AdminServer</admin-server-name>
</domain>

Am I missing OR setting wrong value to any attribute ?

Thanks in Advance

------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev

_______________________________________________
Xmltask-users mailing list
Xmltask-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xmltask-users

Re: [Xmltask-users] Invalid XML output

Reply via email to