xslt 1.0 - Transform which produces default namespace convention xmlns="..." -

-

given following xml:

<root xmlns="example.com">   <child /> </root>

what xslt (version 1.0) can used produce:

<newroot xmlns="stackoverflow.com">   <child /> </newroot>

i've tried various combinations of exclude-result-prefixes , namespace-alias. e.g,

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/xsl/transform" xmlns:e="example.com" xmlns:s="stackoverflow.com" exclude-result-prefixes="e">  <xsl:namespace-alias stylesheet-prefix="s" result-prefix="#default" />      <xsl:template match="e:root">         <s:newroot>             <xsl:apply-templates />         </s:newroot>     </xsl:template>      <xsl:template match="e:child">         <s:child />     </xsl:template>  </xsl:stylesheet>

the closest i've come following incorrect xml

<newroot>   <child /> </newroot>

edit: apologize overly simple sample. solution i'm searching change default namespace , make transformations xml. here more sophisticated example of do:

<data xmlns="sample.com/public">   <insured>     <name>sample client</name>     <locations>       <location number="1">         <address>           <city>new york</city>           <state>new york</state>           <street>222 10 street</street>         </address>       </location>       <location number="2">         <address>           <city>new york</city>           <state>new york</state>           <street>3538 27 street</street>         </address>       </location>     </locations>     <coverages>       <locationsplit>         <locationnumber>1</locationnumber>         <clause>           <limit>10000000</limit>         </clause>       </locationsplit>     </coverages>   </insured> </data>

which become

<projection xmlns="sample.com/projected">   <insured>     <name>sample client</name>     <location address="222 10 street new york, new york">       <clause>         <limit>10000000</limit>       </clause>     </location>   </insured> </projection>

i thought exclude-result-prefix , namespace-alias ticket because explicitly use each namespace declaring them in stylesheet , remove /public namespace while aliasing /projection namespace #default. however, alias causes namespace removed.

it difficult understand in question real , example. take example literally (as own answer does), answer be:

xslt 1.0

<xsl:stylesheet version="1.0"  xmlns:xsl="http://www.w3.org/1999/xsl/transform" xmlns="stackoverflow.com" xmlns:e="example.com"  exclude-result-prefixes="e"> <xsl:output method="xml" version="1.0" encoding="utf-8" indent="yes"/> <xsl:strip-space elements="*"/>  <xsl:template match="/e:root">     <newroot>         <xsl:apply-templates />     </newroot> </xsl:template>  <xsl:template match="e:child">     <child/> </xsl:template>  </xsl:stylesheet>

a more generic answer, move all elements existing namespace/s new namespace be:

<xsl:stylesheet version="1.0"  xmlns:xsl="http://www.w3.org/1999/xsl/transform"> <xsl:output method="xml" version="1.0" encoding="utf-8" indent="yes"/> <xsl:strip-space elements="*"/>  <xsl:template match="*">     <xsl:element name="{local-name()}" namespace="stackoverflow.com">         <xsl:apply-templates/>     </xsl:element> </xsl:template>  </xsl:stylesheet>

Comments

Post a Comment

Popular posts from this blog

PHP DOM loadHTML() method unusual warning -

-
i had following code works fine on localhost: $document = new domdocument(); $document->loadhtml($p_result); $form = $document->getelementsbytagname('form')->item(0); // code continues using $form variable after same code updated on outside server, loadhtml() failed , issued warning. warning: domdocument::loadhtml() expects parameter 1 valid path, string given in path/name/to/script.php returned null instead of object code pretty gets fatal error. note contents of $p_result absolutely same on outside server , on localhost. but why displays kind of warning , why not work? doesn't loadhtml() expects argument 1 string in first place? why method expects parameter 1 valid path ? just make clear i'm not calling loadhtmlfile() , i'm calling loadhtml() . thanks. you're affected one of php bugs . issue present in php 5.6.8 , 5.6.9. have affected php version on server, , bug-free version on localhost. the bug forbids null
Read more

python - How to create jsonb index using GIN on SQLAlchemy? -

-
here's current code creating index jsonb. index("mytable_data_idx_id_key", mytable.data['id'].astext, postgresql_using='gin') but got error. sqlalchemy.exc.programmingerror: (psycopg2.programmingerror) data type text has no default operator class access method "gin" hint: must specify operator class index or define default operator class data type. [sql: "create index event_data_idx_id_key on event using gin ((data ->> 'id'))"] is there way create index on sqlalchemy? the postgresql specific sqlalchemy docs @ http://docs.sqlalchemy.org/en/latest/dialects/postgresql.html#operator-classes mention postgresql_ops dictionary provide "operator class" used postgresql, , provide example illustrating use: index('my_index', my_table.c.id, my_table.c.data, postgresql_ops={ 'data': 'text_pattern_ops',
Read more

c# - TransactionScope not rolling back although no complete() is called -

-
i'm using transactionscope rollback transaction fail bool errorreported = false; action<importerrorlog> newerrorcallback = e => { errorreported = true; errorcallback(e); }; using (var transaction = new transactionscope()) { foreach (importtaskdefinition task in taskdefinition) { loader.load(streamfile, newerrorcallback, task.destinationtable, processingtaskid); } if (!errorreported) transaction.complete(); } i'm sure there no transactionscope started ahead or after code. i'm using entity framework insert in db. regardless state of errorreported transaction never rolled in case of error. what missing ? transactionscope sets transaction.current . that's does. wants transacted must @ property. i believe ef each time connection opened reason. probably, connection open when scope installed. open connection inside of scope or enlist manually. ef has nasty "design decision": default opens
Read more