"Failed to use non CLS compliant type" when iterating SPLimitedWebPartManager.WebParts

Hi,
I having trouble updating a property of a custom web part with PowerShell, that is installed on a client's environment. The custom web part has a property called RowLimit for which I need to set an integer value.
Basically what my script does is, it gets the page with the web part (SPFile), then I get all the web parts on the page using the SPWeb.GetLimitedWebPartsManager function. Then I iterate all web parts in the manager using a 'foreach' like below:
$webpartmanager = $web.GetLimitedWebPartManager($page.Url, [System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared)
$webParts = $webpartmanager.WebParts
foreach($webPart in $webParts) {
UpdateWebPart $webPart $webPartType $webPartTitle $xmlReader
Now, the first few iterations works fine, I get the OOTB web parts and their properties, but as soon as I hit the custom web part I get this error:
The field/property: "RowLimit" for type: "OurWebPart.WebPart" differs only in case from the field/property: "rowLimit". Failed
to use non CLS compliant type.
So from what I've found online is that the web part possibly has two properties, a 'rowLimit' and a 'RowLimit' (which is legal in C#). And I've thought of ways to get around this when trying to update the property, but I'm not even getting to the point of
making the update.
Unfortunately I don't have access to the source code for the web part, and even if I did we don't have the option of making it CLS compliant and redeploying - we need to work with what is there.
Can anyone please shed some light as how to get around this problem?
Thanks!

Hi,
Thanks for your sharing.
What’s more, per my knowledge, the RowLimit property is the view pagination size for the web part.
There is an article about changing the property, you can refer to it.
http://sharepointblogbyshri.blogspot.com/2013/10/sharepoint-2010-edit-pagination-size.html
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

Similar Messages

Solved: Can't send mail using non AT&T server when have ATT DSL service

We recently started using a third party for our web hosting and set up a domain with our new web host. Let's call it www.XXXX.com. We have email set up as [email protected] When we set up our Mail on our Mac using XXXX.com we could receive mail but not send it. After a ton of investigations and hours with ATT support we were told we were going to have to subscribe to ATT email hosting.
I did more research and found that ATT (and other ISPs) block outgoing email ports to not allow you to use other outgoing servers. This is to stop spam bots.
To fix this I logged into ATT/Yahoo email using our base DSL account (i.e. [email protected]). From there I went into the email options and added [email protected] as an account. When I did this, ATT/Yahoo sent to us a verification email and we verified the code that was in the email. This verified that our XXXX.com was legitimate and that we did want to use this as an outgoing email account. That fixed it and our Mac mail is now being sent via our [email protected] email address.
Hope this may solve problems others may have when they set up their Mail and can send but not receive email.

I have heard that 587 must be SSL but I have 3 accounts using that port and SSL is not selected.
Do you know what would cause the sending to be slow or intermittent? Yesterday one time it actually sent one of my tests that has been in cue. Since then It will not send. It just spins for a minute then gives me a message that I need to check settings or use another SMPT.

JAX-RPC and non-primitive data types

Hello all!
I am using JWSDP v1.3 and i have a problem using non-primitive data types as return types for my operations.
Consider the helloservice example of the JWSDP1.3 tutorial. Now suppose that instead of having the simple operation sayHello() that returns a String, we execute a query on a database, get some ResultSetMetaData and we want these Metadata to be the return type of our operation. I.e. have the operation
public ResultSetMetaData sayHello()
instead of the
public String sayHello()
of the tutorial.
When trying to build the service i get the following error which is normal, because ResultSetMetaData is not a supported JAX-RPC type.
run-wscompile: [echo] Running wscompile: [echo] C:\jwsdp\apache-ant\../jaxrpc/bin/wscompile.bat -define -d build - nd build -classpath build config-interface.xml -model build/model. gz [exec] error: invalid type for JAX-RPC structure: java.sql.ResultSetMetaData [exec] Result: 1
Is there any way to define an operation like this? Can i specify somehow ResultSetMetaData as a supported-type?
I hope someone can give me some advice on it, because i have lost one evening trying to figure it out myself :)
Regards,
Kostas

Courtesy links to crossposts so people don't waste their time answering a question which has already been answered
http://forum.java.sun.com/thread.jsp?thread=482875&forum=59&message=2253704
http://forum.java.sun.com/thread.jsp?thread=482873&forum=331&message=2253699

Problem with DII client for Doc/Literal with non built-in type in WL8.1 Sp2

Hello,
I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.
Any help/input will be greatly appreciated. I have added the code and wsdl below.
BTW this is using the code first approach.
Works perfectly fine with the clientgen generated stubs. But not with DII.
With the stubs, following is the SOAP envelope.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:getType xmlns:n1="http://www.aeb.com/wlws">
     <n2:id xmlns:n2="java:com.aeb.types">XYS</n2:id>
     <n3:name xmlns:n3="java:com.aeb.types">Name</n3:name>
</n1:getType>
</env:Body>
</env:Envelope>
With DII (using the serializer/deserializer generated by clientgen),
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:TestType xmlns:n1="java:com.aeb.types">
     <n1:id>ABC</n1:id>
     <n1:name>Some Name</n1:name>
</n1:TestType>
</env:Body></env:Envelope>
Exception
javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
<n1:TestType xmlns:n1="java:com.aeb.types">
<n1:id>ABC</n1:id>
<n1:name>Some Name</n1:name>
</n1:TestType>.
     Please check your operation name.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
     at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
     at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)
Client
System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
String targetNamespace = "http://www.aeb.com/wlws";
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName = new QName(targetNamespace, "DocWebservice");
QName portName = new QName(targetNamespace, "DocWebservicePort");
QName operationName = new QName(targetNamespace, "getType");
Service service = factory.createService(serviceName);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());
Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");
TestType type = new TestType();
type.setId("ABC");
type.setName("Some Name");
TestType res = (TestType) call.invoke(new Object[] { type });
System.out.println(res.getName());
TestType.java
package com.aeb.types;
import java.io.Serializable;
public class TestType implements Serializable {
     private String id;
     private String name;
     public String getId() {
          return id;
     public void setId(String id) {
          this.id = id;
     public String getName() {
          return name;
     public void setName(String name) {
          this.name = name;
DocWebservice.java
package com.aeb.webservices;
import com.aeb.types.TestType;
public class DocWebservice {
     public TestType getType(TestType type) {
          System.out.println("In Server....");
          System.out.println("Received : " + type.getName());
          return type;
ServiceGen Ant Task
<servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws">
     <service javaClassComponents="com.aeb.webservices.DocWebservice"
          generateTypes="True"
          targetNamespace="http://www.aeb.com/wlws"
          serviceName="DocWebservice"
          serviceURI="/DocWebservice"
          style="document">
          <client packageName="com.aeb.ws.doc.client" />
     </service>
</servicegen>
WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws">
<types xmlns:tns="http://www.aeb.com/wlws"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="http://www.aeb.com/wlws"
xmlns:tp="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://www.aeb.com/wlws">
<xsd:import namespace="java:com.aeb.types">
</xsd:import>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getType"
nillable="true">
</xsd:element>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getTypeResponse"
nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.aeb.types">
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element type="xsd:string"
name="id"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="getType">
<part xmlns:partns="http://www.aeb.com/wlws"
name="testType"
element="partns:getType">
</part>
</message>
<message name="getTypeResponse">
<part xmlns:partns="http://www.aeb.com/wlws"
name="result"
element="partns:getTypeResponse">
</part>
</message>
<portType name="DocWebservicePort">
<operation name="getType">
<input message="tns:getType">
</input>
<output message="tns:getTypeResponse">
</output>
</operation>
</portType>
<binding type="tns:DocWebservicePort"
name="DocWebservicePort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
<operation name="getType">
<soap:operation style="document"
soapAction="">
</soap:operation>
<wsr:reliability persistDuration="60000">
</wsr:reliability>
<input>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</input>
<output>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</output>
</operation>
</binding>
<service name="DocWebservice">
<port name="DocWebservicePort"
binding="tns:DocWebservicePort">
<soap:address location="http://localhost:7001/wlws/DocWebservice">
</soap:address>
</port>
</service>
</definitions>
Thanks
Aspert

Hello,
I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.
Any help/input will be greatly appreciated. I have added the code and wsdl below.
BTW this is using the code first approach.
Works perfectly fine with the clientgen generated stubs. But not with DII.
With the stubs, following is the SOAP envelope.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:getType xmlns:n1="http://www.aeb.com/wlws">
     <n2:id xmlns:n2="java:com.aeb.types">XYS</n2:id>
     <n3:name xmlns:n3="java:com.aeb.types">Name</n3:name>
</n1:getType>
</env:Body>
</env:Envelope>
With DII (using the serializer/deserializer generated by clientgen),
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:TestType xmlns:n1="java:com.aeb.types">
     <n1:id>ABC</n1:id>
     <n1:name>Some Name</n1:name>
</n1:TestType>
</env:Body></env:Envelope>
Exception
javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
<n1:TestType xmlns:n1="java:com.aeb.types">
<n1:id>ABC</n1:id>
<n1:name>Some Name</n1:name>
</n1:TestType>.
     Please check your operation name.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
     at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
     at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)
Client
System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
String targetNamespace = "http://www.aeb.com/wlws";
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName = new QName(targetNamespace, "DocWebservice");
QName portName = new QName(targetNamespace, "DocWebservicePort");
QName operationName = new QName(targetNamespace, "getType");
Service service = factory.createService(serviceName);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());
Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");
TestType type = new TestType();
type.setId("ABC");
type.setName("Some Name");
TestType res = (TestType) call.invoke(new Object[] { type });
System.out.println(res.getName());
TestType.java
package com.aeb.types;
import java.io.Serializable;
public class TestType implements Serializable {
     private String id;
     private String name;
     public String getId() {
          return id;
     public void setId(String id) {
          this.id = id;
     public String getName() {
          return name;
     public void setName(String name) {
          this.name = name;
DocWebservice.java
package com.aeb.webservices;
import com.aeb.types.TestType;
public class DocWebservice {
     public TestType getType(TestType type) {
          System.out.println("In Server....");
          System.out.println("Received : " + type.getName());
          return type;
ServiceGen Ant Task
<servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws">
     <service javaClassComponents="com.aeb.webservices.DocWebservice"
          generateTypes="True"
          targetNamespace="http://www.aeb.com/wlws"
          serviceName="DocWebservice"
          serviceURI="/DocWebservice"
          style="document">
          <client packageName="com.aeb.ws.doc.client" />
     </service>
</servicegen>
WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws">
<types xmlns:tns="http://www.aeb.com/wlws"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="http://www.aeb.com/wlws"
xmlns:tp="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://www.aeb.com/wlws">
<xsd:import namespace="java:com.aeb.types">
</xsd:import>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getType"
nillable="true">
</xsd:element>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getTypeResponse"
nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.aeb.types">
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element type="xsd:string"
name="id"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="getType">
<part xmlns:partns="http://www.aeb.com/wlws"
name="testType"
element="partns:getType">
</part>
</message>
<message name="getTypeResponse">
<part xmlns:partns="http://www.aeb.com/wlws"
name="result"
element="partns:getTypeResponse">
</part>
</message>
<portType name="DocWebservicePort">
<operation name="getType">
<input message="tns:getType">
</input>
<output message="tns:getTypeResponse">
</output>
</operation>
</portType>
<binding type="tns:DocWebservicePort"
name="DocWebservicePort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
<operation name="getType">
<soap:operation style="document"
soapAction="">
</soap:operation>
<wsr:reliability persistDuration="60000">
</wsr:reliability>
<input>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</input>
<output>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</output>
</operation>
</binding>
<service name="DocWebservice">
<port name="DocWebservicePort"
binding="tns:DocWebservicePort">
<soap:address location="http://localhost:7001/wlws/DocWebservice">
</soap:address>
</port>
</service>
</definitions>
Thanks
Aspert

What is "Remediate non Compliant Rule when supported" and how to use it ?

Hi,
now i have created around 10 baselines for the driver compliance check for different make and model of laptops and desktops, the os platform on the computer will be Win 7 X 64 computers
CI's working fine and iam curious to learn what is the ( Remediate non Compliant Rule when supported ) option actually ment for , what all we can use it for ?
and i need a example with complete steps too please
all i can understand from the word Remediate is that it will either run a query or initiate a process such as install the correct version of driver etc , please correct me if iam wrong
Thank you
OSLM ENGINEER - SCCM 2007 & 2012

When creating a CI you can also configure a remediation script, that script will be used to remediate a non-compliant system. Also, some simple things like change the value of an existing registry key from 0 to 1 are supported out-of-the-box for compliance
and remediation.
An example:
http://www.petervanderwoude.nl/post/allow-direct-installation-of-windows-8-apps-via-compliance-settings-in-configmgr-2012/
Another example:
http://www.petervanderwoude.nl/post/go-to-desktop-on-sign-in-on-windows-8-1-via-compliance-settings-in-configmgr-2012/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

How to use a non-standard true type font that won't be changed by the native environment on others' computers when they open the document?

We are using a non-standard true type font (Zurich Ex BT) when creating a .pdf document but when others view it, the font is changed on their computers. How do we use this font and keep it from being changed when others look at it?

This is actually good stuff and well written but I hesitate to advise people to use either the "oven trick" or really even the heat gun method as both are notriously short-lived even if they appear effective. Your far better bet is to send the board in to one of the vendors on the internet who are set up to do a proper reball. Even those fixes are good for maybe 12-18 mos. But again, you get a high grade for spelling it out.

AutoSize not working properly in TextField when using non-zero line spacing

When using non-zero line spacing, the autoSize property is not functioning as expected, causing text fields to scroll that shouldn't. Also, when using device fonts, the sizes of the TextFields are wrong in the Flash IDE.
I have a TextField whose height is supposed to be dynamic, depending the width of the TextField. wordWrap is true, the text is left aligned, and the autoSize value is flash.text.TextFieldAutoSize.LEFT.
When the TextField's width is adjusted, the height increases or decreases as expected, but when I scroll the mouse wheel over the TextField, it allows a single line to scroll out of view. This should not be happening. The autoSize property should ensure the TextField is large enough to neither require nor allow scrolling.
Has anyone else encountered this issue or know how to fix it?
Update: Been a problem since at least 2006! > http://blog.nthsense.net/?p=46
http://www.kirupa.com/forum/showthread.php?288955-Disabling-textfield-scrolling   Bug is caused by using a line height ("line spacing" in Flash) larger than zero, for example 1.0pt. It looks like when I reduce the line spacing of the text field to zero, the issue goes away. There doesn't seem to be anything wrong with how autoSize is calculating the required height of the text (i.e. it is exactly textHeight + 4 pixel gutter, and drawing the rectangle (2,2,textWidth,textHeight) aligns visually with the text), so it must have to do with how the TextField is deciding whether it needs to scroll or not, and that separate calculation is being thrown off by the non-zero line spacing. The additional non-zero spacing at the end of the last line could be making the TextField think it needs to scroll, even though it's hight is sufficient at "textHeight + 4". Apparently the problem manifests when using a non-zero leading value as well.
In fact, it has to be related to the leading value exactly, since the following code stops the textfield from scrolling.
//body is TextField
var tlm:TextLineMetrics = body.getLineMetrics(body.numLines - 1);
trace(tlm.leading); //traces "1" here. traces zero when line spacing is zero, and traces larger values with larger line spacing values
body.autoSize = flash.text.TextFieldAutoSize.NONE; //turn off autosize so the height can be set manually
body.height += tlm.leading; //increase height of textfield by leading value of last line to cause scrolling to be turned off.
Honestly, this is pretty unacceptable bug. First of all, scrolling should not be sensitive to trailing line spacing, because autoSize and textHeight do not include it. It need to be consistent, and I think textHeight and autoSize setting height = textHeight + 4 is correct. Vertical scrolling should use textHeight as it's guage for whether scrolling is necessary, but instead, it's obviously involving the leading values of the last line. At the very least, vertical scrolling should simply be disabled when autoSize is turned on and wordWrap is true, because the TextField should be big enough to fit all the text. The workaround of manually adjusting the height is also no good, since turning autoSize back on will immediately change the size back and trigger scrolling again. I also shouldn't have to set line spacing to zero just to use the autoSize feature, since the scrolling calculations are wrong in this way.

No, lol. Luckly, I replace most of my TextFields on the display list with my subclass TextFieldEx. I just call a clone method that accepts a TextField and returns a TextFieldEx with identical properties.
I corrected the problem via modifying the subclass to behave differently when autoSize is not NONE and wordWrap is true. Under those conditions, the maxScrollV and scrollV property values are fixed at 1, and the class listens for its own SCROLL event and sets scrollV to 1 when it occurs. That allows me to leave everything else alone, including text selection, and use whatever line spacing I want.
The modification seems to work fine so far.
For anyone interested in doing something similar, here is a clone method that will copy a TextField.
public static function clone( t:TextField ):TextFieldEx
                              var te:TextFieldEx = create( "", t.width, t.type, t.multiline, t.wordWrap, t.selectable, t.embedFonts, t.defaultTextFormat );
                              te.alpha = t.alpha;
                              te.alwaysShowSelection = t.alwaysShowSelection;
                              te.antiAliasType = t.antiAliasType;
                              te.autoSize = t.autoSize;
                              te.background = t.background;
                              te.backgroundColor = t.backgroundColor;
                              te.blendMode = t.blendMode;
                              //te.blendShader = t.blendShader;
                              te.border = t.border;
                              te.borderColor = t.borderColor;
                              te.cacheAsBitmap = t.cacheAsBitmap;
                              te.condenseWhite = t.condenseWhite;
                              te.displayAsPassword = t.displayAsPassword;
                              //te.embedFonts = t.embedFonts;
                              te.filters = t.filters;
                              te.gridFitType = t.gridFitType;
                              te.height = t.height;
                              te.opaqueBackground = t.opaqueBackground;
                              te.restrict = t.restrict;
                              //te.selectable = t.selectable;
                              te.sharpness = t.sharpness;
                              te.thickness = t.thickness;
                              te.transform = t.transform;
                              //te.type = t.type;
                              te.useRichTextClipboard = t.useRichTextClipboard;
                              //te.wordWrap = t.wordWrap;
                              //Assign text last
                              te.htmlText = t.htmlText;
                              return te;
//And the create method it uses
public static function create( text:String = "", width:Number = NaN, type:String = null, multiline:Boolean = false, wordWrap:Boolean = false, selectable:Boolean = true, embedFonts:Boolean = false, font_or_textformat:*=null, size:Object=null, color:Object=null, bold:Object=null, italic:Object=null, underline:Object=null, url:String=null, target:String=null, align:String=null, leftMargin:Object=null, rightMargin:Object=null, indent:Object=null, leading:Object=null ):TextFieldEx
                              var tf:TextFieldEx = new TextFieldEx();
                              tf.width = isNaN(width) ? 100 : width;
                              tf.defaultTextFormat = (font_or_textformat is TextFormat) ? (font_or_textformat as TextFormat) : new TextFormat( font_or_textformat as String, size, color, bold, italic, underline, url, target, align, leftMargin, rightMargin, indent, leading );
                              tf.embedFonts = embedFonts;
                              tf.multiline = multiline;
                              tf.wordWrap = wordWrap;
                              tf.selectable = selectable;
                              tf.type = type;
                              tf.text = text; //setting text last ensures the text line metrics returns correct values
                              //Initialize the TextField's size to fit the text.
                              if (!multiline)
                                        //When in single-line mode and no specific width is given,
                                        //expand width to entire line.
                                        if (isNaN(width))
                                                  tf.width = tf.textWidth + 4; //match width of text
                              //Height is always automatically adjusted to fit the text by default.
                              //It's better than the arbitrary 100px default height.
                              var minimum_height = tf.getLineMetrics( 0 ).height;
                              var h:Number = tf.textHeight;
                              tf.height = (h < minimum_height) ? (minimum_height + 4) : (h + 4); //match height of text, ensuring height is at least enough to display one line, even if there is no text
                              return tf;

Jax-ws 2.2.8 and ws-addressing: Client throwing java.lang.NullPointerException on receipt of HTTP 202 when using non-anonymous ReplyTo address

Server: JBoss EAP 6.2.0
Client: JDK 1.7.0_51 x64
JAX-WS: RI 2.2.8 ( via -Djava.endorsed.dirs )
I am getting a java.lang.NullPointerException when calling the operation on the WS endpoint from the client when using non-anonymous replyTo address.
I have simplified the scenario into a small test case that hopefully others can replicate. Since the exception is happening on the client instead of the server, I would think that the container used is irrelevant, but I have specified it nonetheless.
1) WebService:
package test.webservice;
import java.util.Random;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebService;
import javax.jws.soap.SOAPBinding;
import javax.xml.ws.soap.Addressing;
@WebService(targetNamespace="http://services.nowhere.org/")
@Addressing(required=true)
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT)
public class RandomTest {
    @WebMethod
    public long nextRandom(@WebParam boolean forceException) throws Exception {
        if( forceException ) {
            throw new Exception("Some exception");
        Random rand = new Random();
        return rand.nextLong();
2) Generated WSDL by JBossEAP 6.2.2:
<?xml version='1.0' encoding='UTF-8'?><wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:tns="http://webservice.test/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:ns1="http://schemas.xmlsoap.org/soap/http" name="RandomTestService" targetNamespace="http://webservice.test/">
<wsdl:types>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://webservice.test/" elementFormDefault="unqualified" targetNamespace="http://webservice.test/" version="1.0">
<xs:element name="nextRandom" type="tns:nextRandom"/>
<xs:element name="nextRandomResponse" type="tns:nextRandomResponse"/>
<xs:complexType name="nextRandom">
    <xs:sequence/>
</xs:complexType>
<xs:complexType name="nextRandomResponse">
    <xs:sequence>
      <xs:element name="return" type="xs:long"/>
    </xs:sequence>
</xs:complexType>
</xs:schema>
</wsdl:types>
<wsdl:message name="nextRandom">
    <wsdl:part element="tns:nextRandom" name="parameters">
    </wsdl:part>
</wsdl:message>
<wsdl:message name="nextRandomResponse">
    <wsdl:part element="tns:nextRandomResponse" name="parameters">
    </wsdl:part>
</wsdl:message>
<wsdl:portType name="RandomTest">
    <wsdl:operation name="nextRandom">
      <wsdl:input message="tns:nextRandom" name="nextRandom" wsam:Action="http://webservice.test/RandomTest/nextRandomRequest" wsaw:Action="http://webservice.test/RandomTest/nextRandomRequest">
    </wsdl:input>
      <wsdl:output message="tns:nextRandomResponse" name="nextRandomResponse" wsam:Action="http://webservice.test/RandomTest/nextRandomResponse" wsaw:Action="http://webservice.test/RandomTest/nextRandomResponse">
    </wsdl:output>
    </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="RandomTestServiceSoapBinding" type="tns:RandomTest">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsaw:UsingAddressing wsdl:required="true"/>
    <wsp:PolicyReference URI="#RandomTestServiceSoapBinding_WSAM_Addressing_Policy"/>
    <wsdl:operation name="nextRandom">
      <soap:operation soapAction="" style="document"/>
      <wsdl:input name="nextRandom">
        <soap:body use="literal"/>
      </wsdl:input>
      <wsdl:output name="nextRandomResponse">
        <soap:body use="literal"/>
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:service name="RandomTestService">
    <wsdl:port binding="tns:RandomTestServiceSoapBinding" name="RandomTestPort">
      <soap:address location="http://localhost:8080/servertest/RandomTest"/>
    </wsdl:port>
</wsdl:service>
    <wsp:Policy xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="RandomTestServiceSoapBinding_WSAM_Addressing_Policy"><wsam:Addressing><wsp:Policy/></wsam:Addressing></wsp:Policy>
</wsdl:definitions>
3) ant build.xml to generate the client code from WSDL
<?xml version="1.0" encoding="UTF-8"?>
<project default="build" basedir="..">
    <property name="jaxws.classpath" location="C://jaxws-2.2.8/jaxws-ri/lib/*.jar"/>
    <taskdef name="wsimport" classname="com.sun.tools.ws.ant.WsImport">
           <classpath path="${jaxws.classpath}"/>
    </taskdef>
    <target name="build" >
        
        <wsimport wsdl="http://localhost:8080/servertest/RandomTest?wsdl"
               verbose="true"
               sourcedestdir="src"
               destdir="bin"
               keep="true">
               <xjcarg value="-enableIntrospection"/>
        </wsimport>
    </target>
</project>
4) Client code
4a) ClientTest.java - Actual client run from client
package test.wsclient;
import java.util.ArrayList;
import java.util.List;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.Endpoint;
import javax.xml.ws.handler.Handler;
import javax.xml.ws.soap.AddressingFeature;
import org.nowhere.services.RandomTest;
import org.nowhere.services.RandomTestService;
public class ClientTest {
    public static void main(String args[]) throws Exception {
        ClientTest app = new ClientTest();
        app.testAddressing();
    public void testAddressing() throws Exception {
        String REPLY_TO_ADDRESS = "http://localhost:8082/servertest/RandomCallback";
        String FAULT_TO_ADDRESS = "http://localhost:8082/servertest/RandomCallbackFault";
        RandomTestService service = new RandomTestService();
        RandomTest port = service.getRandomTestPort(new AddressingFeature());
        BindingProvider provider = (BindingProvider) port;
        // pass the replyTo address to the handler
        provider.getRequestContext().put("ReplyTo", REPLY_TO_ADDRESS);
        provider.getRequestContext().put("FaultTo", FAULT_TO_ADDRESS);
        // Register handlers to set the ReplyTo and FaultTo on the SOAP request sent to the WS endpoint
        List<Handler> handlerChain = new ArrayList<Handler>();
        handlerChain.add(new ClientHandler());
        provider.getBinding().setHandlerChain(handlerChain);
        // Start endpoint to receive callbacks from WS
        Endpoint endpoint = Endpoint.publish(REPLY_TO_ADDRESS, new CallbackSEI());
        try {
            port.nextRandom(false);
        } catch( Exception ex ) {
            ex.printStackTrace();
        } finally {
            Thread.sleep(10000);
        endpoint.stop();
        System.exit(0);
4b) ClientHandler.java - Used to set the wsa ReplyTo address and FaultTo address when sending SOAP request from client to server
package test.wsclient;
import java.util.Set;
import javax.xml.namespace.QName;
import javax.xml.soap.SOAPEnvelope;
import javax.xml.soap.SOAPHeader;
import javax.xml.ws.handler.MessageContext;
import javax.xml.ws.handler.MessageContext.Scope;
import javax.xml.ws.handler.soap.SOAPHandler;
import javax.xml.ws.handler.soap.SOAPMessageContext;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
public class ClientHandler implements SOAPHandler<SOAPMessageContext> {
    public ClientHandler() {};
    @Override
    public Set<QName> getHeaders() {
        return null;
    @Override
    public void close(MessageContext arg0) {
    @Override
    public boolean handleFault(SOAPMessageContext context) {
        return true;
    protected void setAnAddress(SOAPHeader header, String tagName, String address) {
        NodeList nodeListReplyTo = header.getElementsByTagName(tagName);
        NodeList nodeListAddress = nodeListReplyTo.item(0).getChildNodes();
        for (int i = 0; i < nodeListAddress.getLength(); i++) {
            Node node = nodeListAddress.item(i);
            if ("Address".equals(node.getLocalName())) {
                node.setTextContent(address);
                break;
    protected String getMessageID(SOAPHeader header) {
        NodeList nodeListMessageId = header.getElementsByTagName("MessageID");
        return nodeListMessageId.item(0).getTextContent();
    @Override
    public boolean handleMessage(SOAPMessageContext context) {
        Boolean isOutbound = (Boolean) context.get(SOAPMessageContext.MESSAGE_OUTBOUND_PROPERTY);
        if (isOutbound) {
            try {
                SOAPEnvelope envelope = context.getMessage().getSOAPPart().getEnvelope();
                SOAPHeader header = envelope.getHeader();
                /* extract the generated MessageID */
                String messageID = getMessageID(header);
                context.put("MessageID", messageID);
                context.setScope("MessageID", Scope.APPLICATION);
                /* change ReplyTo address */
                setAnAddress(header, "ReplyTo", (String) context.get("ReplyTo"));
                setAnAddress(header, "FaultTo", (String) context.get("FaultTo"));
            } catch (Exception ex) {
                throw new RuntimeException(ex);
        return true;
4c) CallbackSEI.java - endpoint on the client for server to send the SOAP response back to the client
package test.wsclient;
import javax.annotation.Resource;
import javax.jws.Oneway;
import javax.jws.WebParam;
import javax.jws.WebService;
import javax.xml.ws.Action;
import javax.xml.ws.RequestWrapper;
import javax.xml.ws.WebServiceContext;
import javax.xml.ws.soap.Addressing;
@WebService
@Addressing
//@HandlerChain(file = "/handler-chain.xml")
public class CallbackSEI {
    @Resource
    private WebServiceContext context;
     * If there is no namespace specified in the method below, then the CallbackSEI needs to be in the same package as the
     * WS endpoint.
    @Oneway
    @Action(input="http://services.nowhere.org/RandomTest/nextRandomResponse")
    @RequestWrapper(localName="nextRandomResponse", targetNamespace="http://services.nowhere.org/")
    public void handleNotification(@WebParam(name="return")long random) {
        System.out.println("Asynch response received");
        System.out.println( random );
        //System.out.println("This response relates to the message ID: "+ getMessageID());
In summary:
Server is listening on port 8080
Client will listen in port 8082 for the callback from the server for the SOAP response
Now when I run the client, I see that the proper behaviour as far as ws-addressing is concerned. That is:
client -- SOAP request ( on port 8080 ) --> server
client <-- HTTP 202 ( empty HTTP body ) --- server
client <-- SOAP response ( on port 8082 ) --- server
All well and good, except that I am getting a NullPointerException on the client side when I call the operation.
With debugging of the SOAP request and responses, I get the following output:
---[HTTP request - http://localhost:8080/servertest/RandomTest]---
Accept: text/xml, multipart/related
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://services.nowhere.org/RandomTest/nextRandomRequest"
User-Agent: JAX-WS RI 2.2.8 svn-revision#13980
<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><S:Header><To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/servertest/RandomTest</To><Action xmlns="http://www.w3.org/2005/08/addressing">http://services.nowhere.org/RandomTest/nextRandomRequest</Action><ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
    <Address>http://localhost:8082/servertest/RandomCallback</Address>
</ReplyTo><FaultTo xmlns="http://www.w3.org/2005/08/addressing">
    <Address>http://localhost:8082/servertest/RandomCallbackFault</Address>
</FaultTo><MessageID xmlns="http://www.w3.org/2005/08/addressing">uuid:bcd2f6ef-3034-49e8-b837-dbd6a772fb93</MessageID></S:Header><S:Body><ns2:nextRandom xmlns:ns2="http://services.nowhere.org/"><arg0>false</arg0></ns2:nextRandom></S:Body></S:Envelope>--------------------
---[HTTP response - http://localhost:8080/servertest/RandomTest - 202]---
null: HTTP/1.1 202 Accepted
Content-Length: 0
Content-Type: text/xml;charset=UTF-8
Date: Fri, 18 Jul 2014 08:34:36 GMT
Server: Apache-Coyote/1.1
java.lang.NullPointerException
    at com.sun.proxy.$Proxy38.nextRandom(Unknown Source)
    at test.wsclient.ClientTest.testAddressing(ClientTest.java:43)
    at test.wsclient.ClientTest.main(ClientTest.java:18)
---[HTTP request]---
Cache-control: no-cache
Host: localhost:8082
Content-type: text/xml; charset=UTF-8
Content-length: 704
Connection: keep-alive
Pragma: no-cache
User-agent: Apache CXF 2.7.7.redhat-1
Accept: */*
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">http://services.nowhere.org/RandomTest/nextRandomResponse</Action><MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:65d8d7fc-09e4-494a-a9c5-0a01faf4d7e6</MessageID><To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8082/servertest/RandomCallback</To><RelatesTo xmlns="http://www.w3.org/2005/08/addressing">uuid:bcd2f6ef-3034-49e8-b837-dbd6a772fb93</RelatesTo></soap:Header><soap:Body><ns2:nextRandomResponse xmlns:ns2="http://services.nowhere.org/"><return>2870062781194370669</return></ns2:nextRandomResponse></soap:Body></soap:Envelope>--------------------
Asynch response received
2870062781194370669
As you can see from the output above, the proxy is throwing an Exception when it receives the HTTP 202 response.
Any ideas ?

I think I have found when I get this error and probably I have found a bug. I will appreciate if someone can confirm this.
In my BPEL project setup, my BPEL process's wsdl file imports another wsdl from different namespace. Here is sample snippet -
<wsdl:definitions targetNamespace="http://namespace/1">
<wsdl:import namespace="http://namespace/2" location="resources/another.wsdl"/>
<plnk:partnerLinkType....../>
</wsdl:definitions>
Please let me know. I checked the bundled samples with Oracle BPEL PM and did not find any similar case where process wsdl imports another wsdl.
Thank you.
Meghana

When a context node use non-singleton, how to invoke the supply funtion eve

when a context node use non-singleton, how to invoke the supply funtion everytime the lead selection is changed ?

Hi wei,
<b>Non-singleton nodes:</b>
Web Dynpro allows you to define non-singleton nodes. Each non-singleton node has one node instance for each node element of the parent collection at runtime. The advantage is that each instance can be accessed directly. When using non-singleton nodes, the nodes are only created when the node values are retrieved. This can save resources that otherwise would slow down the performance of the application.
<b>Supply function:</b>
The Web Dynpro tools also automatically enhance the corresponding controller class with a supply function including the user coding area contained in it
Supply functions are implemented as methods of type
<b>public void supplyChildNodeElements(SomeChildNode node,
SomeParentNodeElement)</b>
in a Web Dynpro controller (view controller or custom controller). Supply functions and context nodes have a 1..1 relationship, that is, supply functions are specific for individual context nodes. Under certain conditions, supply functions are called by pages in the Web Dynpro runtime environment.
Hope this helps u,
Regards,
Nagarajan.

Publishing to Azure Web App when using nuget "Microsoft.SqlServer.Types" crashes WebDeploy

I have a project where I use "Microsoft.SqlServer.Types" that loads an assembly manually as part of the package.
The problem arises when I publish this via Visual Studio. I get an error that the file is already in use from WebDeploy. This is probably because of how the assemblies are loaded or something that makes them locked.
Repro steps:
Create an ASP.NET web and add nuget package "Microsoft.SqlServer.Types" and make sure you load the assembly using the provided ReadMe.txt in your App_Start.
Deploy to Azure Web App.
Deplay again when the app is up and running - you'll get the error.
Does WebDeploy have an option for shutting down the site when updating or something like that? This error also apply to any WebJobs that also use the "Microsoft.SqlServer.Types" package.

there is a way to take the site down during publishing please read through this blog post
http://blogs.msdn.com/b/webdev/archive/2013/10/30/web-publishing-updates-for-app-offline-and-usechecksum.aspx
please read the part about appoffline
Thanks, Hosam

Can I use Non-standard XSD Data Types in my XSD; if so how?

Please help if you can, this is a complex question, so bear with me.
Also note that I am in Livecycle 8.2 ES (not ES2 or higher).
I am working on creating XSD schemas to map to form objects.
I have created one master schema document that is wired into multiple forms, and I have one separate schema for reusable form objects, that I refer to as a "common node".
All of my individual form schemas are brought together in this one Master Schema via the use of include statements.
EXAMPLE: This is like my Master Schema
<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" >
<xs:include schemaLocation="./commonElementsNode.xsd" />
<xs:include schemaLocation="./form1111.xsd" />
<xs:include schemaLocation="./form2222.xsd" />
<xs:include schemaLocation="./form3333.xsd" />
<xs:element name="form">
<xs:complexType>
<xs:sequence>
   <xs:element ref="commonElementsNode" />
   <xs:element ref="form1111" />
   <xs:element ref="form2222" />
   <xs:element ref="form3333" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
This works fine.
I can load this up in Designer in the Data View and everything appears in the Data View hierarchy correctly, with "form" as the top node.
And as long as I use standard "xs:" data types - everything works great. So if I go into LiveCycle Designer and I go to File --> Form Properties --> Preview --> Generate Preview Data and generate dummy XML data - it respects my XSD conventions.
Now here is where the problem arises:
In these schemas, I need to define the data types.
The client I am working for needs me to use their data types.
These data types are not standard xs: data types, like "xs:string" or "xs:date".
Rather, the data types are ones that have been defined in other schemas and reserved to a namespace.
For instance, rather than use xs:date I need to use something like: "myns:DateType"
This "myns:DateType" is defined as:
<xs:complexType name="DateType">
<xs:simpleContent>
   <xs:extension base="xs:date">
    <xs:attribute name="format" type="xs:string" use="optional">
     <xs:annotation>
      <xs:documentation xml:lang="en">
       <mydoc:Name>Date Format Text</mydoc:Name>
       <mydoc:Definition>The format of the date content</mydoc:Definition>
       <mydoc:PrimitiveType>string</mydoc:PrimitiveType>
      </xs:documentation>
     </xs:annotation>
    </xs:attribute>
   </xs:extension>
</xs:simpleContent>
</xs:complexType>
Note that I have redacted this data type slightly and changed the namespace to protect the anonymity of my client, but we can assume that their data type is valid and currently in use with other systems.
It conforms to W3 standards.
Note also how this type is an enumeration of the base type "xs:date".
This is defined in a schema called something like "MyCoreTypes.xsd"
There is a namespace reservation in this file that looks something like this:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"
xmlns:myns="http://clinetname.com/schemas/mycoretypes" >
So there is a name space reservation there.
In my aforementioned "Master Schema" file, I have an include statement that looks like this:
<xs:include namespace="http://clinetname.com/schemas/mycoretypes" schemaLocation="./MyCoreTypes.xsd" />
(let's assume that the schema is in the same folder, as the Master Schema, so we can use the "./" relative path.)
Now the problems is that in all my forms, where I have a myns:DateType (e.g.: in form1111, a "Date of Birth" element that looks like this: <xs:element name="OwnerBirthDt" type="myns:DateType"/> ) the XSD is not respected when the XML dummy data is generated in LiveCycle Designer implying that the XSD's data types are not being recognized properly.
Has anyone had this problem before?
Is there a solution?
Is it even possible to use these kind of include or import references in LiveCycle to define a data type other that the standard "xs:" data types?
Please let me know - it would be greatly appreciated.
I am more than willing to clarify the question further if others are willing to help.
Thanks -
Ben Lyons

prf.kishorekumar wrote:
i came here with a hope that I would definitely get some help.
pls.. some one reply1) You got some help. No where do I see thanks or acknowledgment for the information given.
2) Please remember that people on the forum help others voluntarily, it's not their job.
3) Google can often help you here if the forum can't. Using Google I found this interesting link:
http://today.java.net/pub/a/today/2004/05/24/html-pt1.html
It discusses the Swing HTML EditorKit as well as some other free HTML renderers.
Edited by: petes1234 on Oct 24, 2007 7:29 PM

Exchange rate field greyed out when i use custom PO order type

Hi!
Upon creation of PO using SAP standard order type NB, the field exhange rate is editable. While when i used csutom PO order type, it is greyed out. How can we edit this? Where is the configuration of the exchange rate per order type?
If this is configured in IMG please include path, on how exchange rate is configured.
Thanks a lot.

Hi,
Spro>Materials Management>Purchasing>Purchase Order>Define Document Types
Here check the "Field Selection Key" against the PO doc type
(ex: Standard NB doc type the "Field Selection Key" would be "NBF")
Then go to
Spro>Materials Management>Purchasing>Purchase Order>Define Screen Layout at Document Level
Select the " Field Selection Key" of ur doc type..Just Double click on that
then check for field " Exchange rate "
against that field you can see three options, Reqd.entry Opt. entry Display...
Here tick the field "Opt. entry", So that You can get this field in Change mode in ME21N trx...
Thx
Raju

When do we use Non-Cumulative values?

Hi BW Experots?
When do we use Non-Cumulative values?How is it related with exception aggregation
Please tell me .
Thanks in anticipation.

Hi,
Taken from std, doc....
A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory.
http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
Check this out...
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
Pls. assign points if this helps you.. ****
Thanks,
Raj

When I start up FCPX 10.0.1, I get the following message "Failed to save. Unknown store type, format, or version."

When I start up FCPX 10.0.1, I get the following message "Failed to save. Unknown store type, format, or version."

Thanks, Andy. I checked, and it is formatted "Mac OS Extended (Journaled)".
Michael

IMac desktop using OS X Lion. When I type figures in a table in my email. They look straight but when I sent it, they look crooked. How to prevent it? Do I need to pre-type it on excel and copy and paste it on my email. It takes time and troublesome.

iMac desktop using OS X Lion. When I type figures in a table in my email. They look straight but when I sent it, they look crooked. How to prevent it? Do I need to pre-type it on excel and copy and paste it in my email but it takes time and troublesome.

Send the table as an attachment, either a spreadsheet (if the recipient needs to be able to edit it) or a PDF.

"Failed to use non CLS compliant type" when iterating SPLimitedWebPartManager.WebParts

Similar Messages

Maybe you are looking for