i would like to exclude sitemesh decorator for some of my files in a project. but how to do it. my file names is listApps.jsp
this is my decorators.xml files
<?xml version="1.0" encoding="UTF-8"?>
<decorators defaultdir="/WEB-INF/pages">
<excludes>
<pattern>/j_spring_security_logout</pattern>
<pattern>/pages/logout-redirect.jsp</pattern>
<pattern>/flexweb/*</pattern>
<pattern>/ApplicationScaffold.html</pattern>
<pattern>/listApps.html</pattern>
</excludes>
<decorator name="main" page="main.jsp">
<pattern>/*</pattern>
</decorator>
any help? thanks
well, you could create another template named nothingfancy and you don't do anything special for that one
put it first so it's evaluated before
<?xml version="1.0" encoding="utf-8"?>
<decorators defaultdir="/app/decorators">
<decorator name="nothingfancy" page="nothingfancy.jsp">
<pattern>/j_spring_security_logout</pattern>
<pattern>/pages/logout-redirect.jsp</pattern>
<pattern>/flexweb/*</pattern>
<pattern>/ApplicationScaffold.html</pattern>
<pattern>/listApps.html</pattern>
</decorator>
<decorator name="main" page="main.jsp">
<pattern>/*</pattern>
</decorator>
</decorators>
Related
enter image description here
I find it too beautiful. please help. Thanks very much
You can use spinner here is example
<Spinner
android:id="#+id/planets_spinner"
android:layout_width="fill_parent"
android:layout_height="wrap_content"/>
<?xml version="1.0" encoding="utf-8"?>
And resources:
<resources>
<string-array name="planets_array">
<item>Mercury</item>
<item>Venus</item>
<item>Earth</item>
<item>Mars</item>
<item>Jupiter</item>
<item>Saturn</item>
<item>Uranus</item>
<item>Neptune</item>
</string-array>
</resources>
I have configuration file (file1.config) looking kind of like this:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<myelement>
oldvalue
</myelement>
</configuration>
I want to replace "oldvalue" with "newvalue". For this reason I have created a file (file1.Development.config) looking something like this:
<?xml version="1.0" encoding="utf-8" ?>
<configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform">
<myelement xdt:Transform="Replace">
newvalue
</myelemetn>
</configuration>
The problem is that when I deploy the package with Octopus Deploy I get the following error:
Found multiple target elements, but the 'Replace' Transform only
applies to the first match
I solved the problem by adding an xdt:Locator. So now my transformation file looks like this:
<?xml version="1.0" encoding="utf-8" ?>
<configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform">
<myelement xdt:Transform="Replace" xdt:Locator="XPath(/configuration/myelement)">
newvalue
</myelemetn>
</configuration>
here is the error saying liquibase is not recognized as an internal/external
command in cmd
http://animobile.info/upload/1/error.bmp
lb_update.bat code1:
#echo off call Liquibase --changeLogFile=update.xml
update.xml coode:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<databaseChangeLog xmlns="http://www.Liquibase.org/xml/ns/dbchangelog/1.9"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.Liquibase.org/xml/ns/dbchangelog/1.9 http://www.Liquibase.org/xml/ns/dbchangelog/dbchangelog-1.9.xsd">
<include file="v000/master.xml" />
</databaseChangeLog>
master.xml code:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<databaseChangeLog xmlns="http://www.Liquibase.org/xml/ns/dbchangelog/1.9"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.Liquibase.org/xml/ns/dbchangelog/1.9 http://www.Liquibase.org/xml/ns/dbchangelog/dbchangelog-1.9.xsd">
<preConditions>
<!-- These changes should only be run against a schema with major version 0 -->
<sqlCheck expectedResult="0">
SELECT NVL(MAX(id),0)
FROM databasechangelog
WHERE author='MajorVersion '
</sqlCheck>
</preConditions >
<include file="v000/2009-10-15-73.xml" />
</databaseChangeLog>
The expected result when the lb_update.bat is executed, a confirmation message will appear saying: Migration successful.
How can i fix this please help! Thank you!
Since you have not mentioned the full path of Liquibase.bat file, it will be searched in the current directory which is D:\Projects\lbdemo\trunk in your case. Looks like Liquibase.bat file doesn't exist at the Location D:\Projects\lbdemo\trunk.
I have a problem. I'm learning from MTaulty's video: http://channel9.msdn.com/blogs/mtaulty/prism--silverlight-part-2-dependency-injection-with-unity. And I have a problem with .config file which he creates at 18:00 min. There is no possibility to see what is in
<section type=".."
I wrote:
type="Microsoft.Practises.Unity.Configuration.UnityConfigurationSection, Microsoft.Practises.Unity.Configuration" />
but it does not work. I don't have idea what is wrong. I have a mistake that VisualStudio can't load file'Microsoft.Practises.Unity.Configuration and find a file.
thanks for help!
If you want to specify modules via config file the Prism Guide on MSDN does a good job explaining that.
Quote from the Guide
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
<section name="modules"
type="Microsoft.Practices.Prism.Modularity.ModulesConfigurationSection, Microsoft.Practices.Prism"/>
</configSections>
<modules>
<module assemblyFile="ModularityWithUnity.Desktop.ModuleE.dll" moduleType="ModularityWithUnity.Desktop.ModuleE, ModularityWithUnity.Desktop.ModuleE, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" moduleName="ModuleE" startupLoaded="false" />
<module assemblyFile="ModularityWithUnity.Desktop.ModuleF.dll" moduleType="ModularityWithUnity.Desktop.ModuleF, ModularityWithUnity.Desktop.ModuleF, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" moduleName="ModuleF" startupLoaded="false">
<dependencies>
<dependency moduleName="ModuleE"/>
</dependencies>
</module>
</modules>
</configuration>
For Prism 6.0 section type has changed to Prism.Modularity.ModulesConfigurationSection, Prism.Wpf
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="modules" type="Prism.Modularity.ModulesConfigurationSection, Prism.Wpf" />
</configSections>
<modules>
*** register your modules here ****
</modules>
</configuration>
I had a problem with App.config mapping. The section type was invalid. The right one is:
<section name="modules" type="Microsoft.Practices.Prism.Modularity.ModulesConfigurationSection, Microsoft.Practices.Prism.**Composition**"/>
Hope it helps.
Using the savon gem, I get the following request XML:
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wsdl="URL"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ins0="SOME URL">
<soap:Body>
<ins0:Test xmlns="SOME URL">
</ins0:Test>
</soap:Body>
</soap:Envelope>
But it needs to be this instead:
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wsdl="URL"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<Test xmlns="SOME URL">
</Test>
</soap:Body>
</soap:Envelope>
Notice ins0 was removed.
Any suggestions?
The two XML documents are equivalent, so there should be no issues as long as the document is parsed by an XML compliant agent.
The Savon generated document is simply creating a namespace prefix of ins0 for the "SOME URL" namespace. This is convenient for a large SOAP document with many elements from that namespace. In this example, the prefix is not really necessary.
The only potential issue I can see is that the Savion generated document seems to declare the ins0 namespace twice - once in the soap:Envelope and then again in the soap:Body. Seems superfluous and potentially open to error.