Fully Qualified Field

I have a question about JDBC drivers. I am trying to access a field from a query row using the fully qualified field name. That is, I'm tring to use the <table-name>.<field-name> naming convention. For example:
  SELECT EMPLOYEE.NAME FROM EMPLOYEE ;
The fully qualified name would be EMPLOYEE.NAME. Most SQL servers understand this. I've found that there are JDBC drivers out there that cannot retrieve the field using this fully qualified name:
  rs.getString("EMPLOYEE.NAME") ;
The above statement may throw an exception on one driver and return null for another. I've modified a driver to allow this naming convention, but I'm worried that it's not part of the actual JDBC specification. Is this true?
On the other hand, field alias seems to work:
  SELECT EMPLOYEE.NAME EMPLOYEE_NAME FROM EMPLOYEE ;
  rs.getString("EMPLOYEE_NAME") ;
Most drivers allow this. Although I have seen a few that don't. I can live with having to give a field alias. Should I leave it at that?
Anthony

The issue is the the column name in the returned resultset is not the fully qualified column name. The resultset only returns the column name without the tablename prefix. Even if you have a statment like the following:
select Request.RequestID, RequestStatus.RequestID from Request, RequestStatus
The resultset returned will have two columns named RequestID.
An alternative is to retrieve the resultset using the column number from the resultset( ie. var = rset.getString(1)).

Similar Messages

  • Change Table Names in Universe to a Fully Qualified Table Name

    We have implement the HR Rapid Datamart. The table names just have the table. We need programmically to have the table use a fully qualified name. Example Company table needs to read the schema.table name DM.Company. Is there a way to set it in the Custom Parameters section of the Edit connection window to automatically add the schema name to the table name programmically without having to rename the table names in the universe?

    You can add the schema name for all tables in one pass if you select all of them (press the CTRL key while selecting them) and them go to the properties window and type in the schema name in the owner field.
    Regards,
    Stratos

  • Fully-Qualified Host Name empty in SMSY

    Hello,
    I am facing a problem in the SMSY of Solution Manager.
    I've got some servers listed in the "servers" tree of the landscape components. Fine. But for all of them, the field Fully-Qualified Host Name is empty.
    I need this entry for generating RFC with full host name....
    If I put the full host name manually in this field, the RFC are right generated with the full host name in the technical data. But I would like to know how to retrieve it automatically (from SLD I presume...).
    Anyone could help me ?
    Thanks a lot.
    Regards

    Hi
    Please have a look on the SAP note [Note 1368267 - Transfer fully-qualified host name|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1368267]
    from SLD data capure please refer this
    [http://help.sap.com/saphelp_sm32/helpdata/en/5c/36329947af074182eef7585ba88ee8/content.htm|http://help.sap.com/saphelp_sm32/helpdata/en/5c/36329947af074182eef7585ba88ee8/content.htm]
    Jansi

  • Fully qualified elements in clientgen ant task

    I think that ant clientgen task from WLS 10.3.3 is ignoring XSD parameter elementFormDefault="qualified". I generated client with this task and then sent simple request to webmethods server (i don't know version of this server either implementation of webservices on it) and i received bellow error:
    *javax.xml.ws.soap.SOAPFaultException: [ISS.0088.9112] An Exception was thrown in the server:{0}*
    After some investigation i had notice that webmethods server is answered with followed response:
    +<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Header/><SOAP-ENV:Body>+
    +<SOAP-ENV:Fault>+
    +<faultcode>SOAP-ENV:Server</faultcode>+
    +<faultstring>[ISS.0088.9112] An Exception was thrown in the server:{0}</faultstring>+
    +<faultactor>http://ip:6080/soap/inbound</faultactor>+
    +<detail xmlns:webM="http://www.webMethods.com/2001/10/soap/encoding">+
    +<webM:exception>+
    +<webM:className>com.wm.lang.flow.FlowException<;/webM:className>+
    +<webM:message xml:lang="">java.lang.Exception: missing required parameter 'document'</webM:message>+
    +</webM:exception>+
    +</detail>+
    +</SOAP-ENV:Fault>+
    +</SOAP-ENV:Body>+
    +</SOAP-ENV:Envelope>+
    but request had document element in it:
    +<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Header><metadata xmlns="http://ns"><processGroup>PR</processGroup></metadata></S:Header><S:Body><document xmlns="http://ns"><binary>some binary</binary></document></S:Body></S:Envelope>+
    after some modification i created fixed elements for body tag like this:
    +<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >+
    +<soapenv:Header>+
    +<ns:metadata xmlns:ns="http://ns">+
    +<ns:processGroup>PR</ns:processGroup>+
    +</ns:metadata>+
    +</soapenv:Header>+
    +<soapenv:Body>+
    +<ns:document xmlns:ns="http://ns">+
    +<ns:binary>some binary+
    +</ns:binary>+
    +</ns:document>+
    +</soapenv:Body>+
    sent it ... and response was fine!
    When I create request in Altova XMLSPY or in SOAPUI  requests are correct (with qualified elements - see below)
    Example request from soapui:
    +<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://ns">+
    +<soapenv:Header>+
    +<ns:metadata>+
    +<ns:processGroup>PR</ns:processGroup>+
    +</ns:metadata>+
    +</soapenv:Header>+
    +<soapenv:Body>+
    +<ns:document>+
    +<ns:binary>some binary+
    +</ns:binary>+
    +</ns:document>+
    +</soapenv:Body>+
    My WSDL*
    +<wsdl:definitions xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:wsi="http://ws-i.org/schemas/conformanceClaim/";+
    xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:ns="http://ns" xmlns="http://ns" name="ReceiveRequest" targetNamespace="http://ns">
    +<wsdl:documentation>This WSDL document contains an implementation of the ns Inbound Web Service.</wsdl:documentation>+
    +<wsdl:types>+
    +<xs:schema>+
    +<xs:import schemaLocation="xsd/data.xsd"; namespace="http://ns"/>+
    +</xs:schema>+
    +</wsdl:types>+
    +<wsdl:message name="metadata">+
    +<wsdl:part name="metadata" element="ns:metadata">+
    +<wsdl:documentation>the meta data</wsdl:documentation>+
    +</wsdl:part>+
    +</wsdl:message>+
    +<wsdl:message name="document">+
    +<wsdl:part name="document" element="ns:document">+
    +<wsdl:documentation>the input data</wsdl:documentation>+
    +</wsdl:part>+
    +</wsdl:message>+
    +<wsdl:message name="receiveRequestOutput">+
    +<wsdl:part name="response" element="ns:processingResponse">+
    +<wsdl:documentation>the output data</wsdl:documentation>+
    +</wsdl:part>+
    +</wsdl:message>+
    +<wsdl:portType name="ns_backend_SOAPPortType">+
    +<wsdl:operation name="receiveRequest">+
    +<wsdl:input message="ns:document"/>+
    +<wsdl:output message="ns:receiveRequestOutput"/>+
    +</wsdl:operation>+
    +</wsdl:portType>+
    +<wsdl:binding name="ns_backend_SOAPBinding" type="ns:ns_backend_SOAPPortType">+
    +<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>+
    +<wsdl:operation name="receiveRequest">+
    +<soap:operation soapAction="receiveRequest" style="document"/>+
    +<wsdl:input>+
    +<soap:header message="metadata" part="metadata" use="literal"/>+
    +<soap:body parts="document" use="literal"/>+
    +</wsdl:input>+
    +<wsdl:output>+
    +<soap:header message="metadata" part="metadata" use="literal"/>+
    +<soap:body use="literal"/>+
    +</wsdl:output>+
    +</wsdl:operation>+
    +</wsdl:binding>+
    +<wsdl:service name="ReceiveRequest">+
    +<wsdl:port name="ns_backend_SOAPPort0" binding="ns:ns_backend_SOAPBinding">+
    +<soap:address location="https://ip:6080/soap/inbound"/>+
    +</wsdl:port>+
    +</wsdl:service>+
    +</wsdl:definitions>+
    And XSD*
    +<?xml version="1.0"; encoding="UTF-8"?>+
    +<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://ns" targetNamespace="http://ns" elementFormDefault="qualified" attributeFormDefault="unqualified">+
    +<xs:element name="metadata" type="ns:metadataType"/>+
    +<!-- Request header meta data -->+
    +<xs:complexType name="metadataType">+
    +<xs:sequence>+
    +<xs:element name="processGroup" type="xs:string" nillable="false"/>+
    +<xs:element name="processName" type="xs:string" nillable="false"/>+
    +<xs:element name="applReqID" type="xs:string" nillable="false"/>+
    +<xs:element name="correlationID" type="xs:string" minOccurs="0"/>+
    +<xs:element name="sender" type="xs:string" minOccurs="0"/>+
    +<xs:element name="receiver" type="xs:string" minOccurs="0"/>+
    +<xs:element name="documentVersion" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property1_Name" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property1_Value" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property2_Name" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property2_Value" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property3_Name" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property3_Value" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property4_Name" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property4_Value" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property5_Name" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property5_Value" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property6_Name" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property6_Value" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property7_Name" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property7_Value" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property8_Name" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property8_Value" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property9_Name" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property9_Value" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property10_Name" type="xs:string" minOccurs="0"/>+
    +<xs:element name="property10_Value" type="xs:string" minOccurs="0"/>+
    +<!-- 7.1 fields: typeFlag, replyTo, tags -->+
    +<xs:element name="typeFlag" type="xs:string" minOccurs="0"/>+
    +<xs:element name="replyTo" type="xs:string" minOccurs="0"/>+
    +<xs:element name="tags" type="xs:string" minOccurs="0"/>+
    +</xs:sequence>+
    +</xs:complexType>+
    +<!-- Response body part -->+
    +<xs:element name="processingResponse" type="ns:processingResponseType"/>+
    +<xs:complexType name="processingResponseType">+
    +<xs:all>+
    +<xs:element name="timeStamp" type="xs:string"/>+
    +<xs:element name="processStatus" type="xs:string"/>+
    +<xs:element name="responseMessage" type="xs:string"/>+
    +<xs:element name="applReqID" type="xs:string"/>+
    +<xs:element name="correlationID" type="xs:string"/>+
    +</xs:all>+
    +</xs:complexType>+
    +<!-- Request body part-->+
    +<xs:element name="document" type="ns:documentType"/>+
    +<xs:complexType name="documentType">+
    +<xs:sequence>+
    +<xs:element name="binary" type="xs:base64Binary"/>+
    +</xs:sequence>+
    +</xs:complexType>+
    +</xs:schema>+
    And Ant task*
    +<target name="wsdlc">+
    +<taskdef name="wsdlc" classname="weblogic.wsee.tools.anttasks.WsdlcTask"; classpathref="weblogic.jar.classpath";/>+
    +<wsdlc srcWsdl="wsdls/${wsdl_url}" jaxrpcwrappedarraystyle="false"+
    +destJwsDir="./src/${package_name}/" packageName="pl.nbp.exdi.${package_name}" type="JAXWS"+
    +explode="true" />+
    _*How to force clientgen to create fully qualified elements in request ?*_

    And one more thing: I deploy it on WLS 12c.

  • Fully qualify domain name in CMS_IdNumbers5

    Under CMS D/B, there is a table called u2018CMS_IdNumbers5u2019.
    One of the fields generated during the creation of CMS D/B is always equal to the server name where BOE is installed.
         E.g      If Server Name = Server01
              There will be a field called u2018Server01u2019 under table CMS_IdNumbers5
    In Unix (AIX) environment, it will retrieve the fully qualify domain name and port numbers
         E.g.      If Server Name = Server01.AU.SVR.COM
              Port = 6400
              There will be a field called Server01.AU.SVR.COM:6400 under table CMS_IdNumbers5.
    Questions:
    Where does the fully qualify domain name get pick up from in unix and how does it knows it should point to AU.SVR.COM in the above example?
    Never once have we stated the fully qualify domain name (.AU.SVR.COM) during the creation of CMS D/B (via cmsdbsetup.sh), we only specified u2018Server01u2019.
    When using u2018uname u2013nu2019 or u2018hostnameu2019 commands, it will only return back u2018Server01u2019.
    Client needs to point to a different domain name.
    E.g. Instead of Server01.AU.SVR.COM, they want Server01.AU2.SVR.COM
    Where can this be done?
    Thanks in advance.
    Regards,
    Ken

    Thanks for the quick respond. Yes I am aware changing domain is out of scope from Business Objects perspective.
    My question is more on how and where do the fully qualify domain name get picked up from in unix (AIX). As mentioned in previous note, never once have we stated the fully qualify domain name (.AU.SVR.COM) during the creation of CMS D/B (via cmsdbsetup.sh), we only specified u2018Server01u2019. Yet it was able to determine the fully qualify domain name.

  • Fully qualified class name

    ....one small snippet
    <bean:define id="prodName" name="changeItemProduct" property="productName"/> why the name field does not use fully qualified class(bean) name ?
    Not only this tag but also some other Struts tag dont mention the fully quilied class name . why ? does request.setAttribute() inside the servlet plays any role here ? or whats the reason why Struts dont use fully qualified class name in define :bean or logic:equal tag ?
    P.S : i remember jsp Usebean Id tag uses fully qualified class name whenevr it usues that .

    That tutorail should all gibberish in my browser. But anyway, hope this helps!
    The tutorial has only code snippets and the code written there isn't complete.
    To use that bean class name directly, there has to be an import statement in the JSP which will specify the fully qualified class name.
    I didn't quite get what you are trying to say about the tld's.
    That code snippet is returning a member variable called "map" which is an instance of the java.util.Map. The tutorial hasn't specified the member variables in the code snippet.
    few days ago i posted this Map..someone (sensei )
    told something happening internally . a dark
    area.............And a word of caution! Don't believe in trolls and their sensei... they take pride in talking about dark shit.
    Hope this quenches your thirst for knowing everything! (That's not a left-handed compliment... it's good to be inquisitive)

  • Clientgen does not fully qualify superclasses

    I have datatypes that extend classes in a different package. When I use
    WLS81 ANT task clientgen to generate client-jars from WSDL files obtained
    from web services generated by servicegen, the superclasses are not fully
    qualified in the generated java code, nor are there import statements for
    the superclasses. This causes the generated code to have compile errors.
    Other dependencies are fully qualified in the generated code, but the
    superclass is not.
    There mayThe WSDL is included below. Specifically,
    com.starcomsoft.pp.database.BaseHelper does not get a fully qualifed
    reference in the generated java code.
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions xmlns:tns="http://localhost:7001/webservice/"
    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/2002/12/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://localhost:7001/webservice/">
         <types xmlns:tns="http://localhost:7001/webservice/"
    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/2002/12/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="java:com.starcomsoft.pp.common" elementFormDefault="qualified"
    attributeFormDefault="qualified"
    targetNamespace="java:com.starcomsoft.pp.common">
                   <xsd:complexType name="AbstractSearchCriteria"
    abstract="true">
                        <xsd:sequence>
                             <xsd:element type="xsd:int"
    name="recordStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:schema>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:stns="java:com.starcomsoft.pp.customer"
    elementFormDefault="qualified" attributeFormDefault="qualified"
    targetNamespace="java:com.starcomsoft.pp.customer">
                   <xsd:import namespace="java:com.starcomsoft.pp.database">
    </xsd:import>
                   <xsd:import namespace="java:language_builtins.lang">
    </xsd:import>
                   <xsd:import namespace="java:language_builtins.util">
    </xsd:import>
                   <xsd:import
    namespace="http://schemas.xmlsoap.org/soap/encoding/">
    </xsd:import>
                   <xsd:import namespace="java:com.starcomsoft.pp.common">
    </xsd:import>
                   <xsd:complexType name="Address">
                        <xsd:complexContent>
                             <xsd:extension base="stns:AddressHelper">
    </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="AddressHelper" abstract="true">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
                                  <xsd:sequence>
                                       <xsd:element type="xsd:string"
    name="addressOne" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="addressTwo" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="city" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
    name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="id" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
    name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="recordStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="stateId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="version" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="zipCode" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="ArrayOfCustomerGraphData">
                        <xsd:complexContent>
                             <xsd:restriction
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    base="soapenc:Array">
                                  <xsd:attribute
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType"
    wsdl:arrayType="stns:CustomerGraphData[]">
    </xsd:attribute>
                             </xsd:restriction>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="ArrayOfProfile">
                        <xsd:complexContent>
                             <xsd:restriction
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    base="soapenc:Array">
                                  <xsd:attribute
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType"
    wsdl:arrayType="stns:Profile[]">
    </xsd:attribute>
                             </xsd:restriction>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="Contact">
                        <xsd:complexContent>
                             <xsd:extension base="stns:ContactHelper">
    </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="ContactHelper" abstract="true">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
                                  <xsd:sequence>
                                       <xsd:element type="xsd:boolean"
    name="active" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="contactPoint" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="customerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="departmentId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
    name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="first" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="id" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="last" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
    name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="primaryContact" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="recordStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="title" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="type" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="version" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="Customer">
                        <xsd:complexContent>
                             <xsd:extension base="stns:CustomerHelper">
                                  <xsd:sequence>
                                       <xsd:element type="stns:Address"
    name="billAddressData" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="stns:Address"
    name="billToAddress" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="stns:Address"
    name="shipAddressData" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="stns:Address"
    name="shipToAddress" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="CustomerAdjustment">
                        <xsd:complexContent>
                             <xsd:extension
    base="stns:CustomerAdjustmentHelper">
    </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="CustomerAdjustmentHelper"
    abstract="true">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
                                  <xsd:sequence>
                                       <xsd:element type="xsd:int"
    name="adjustmentId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:double"
    name="amount" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="code" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="customerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
    name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="facilityId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="factorId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="id" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
    name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="methodId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="recordStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="type" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:double"
    name="value" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="version" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="CustomerGraphCollection">
                        <xsd:sequence>
                             <xsd:element
    type="stns:ArrayOfCustomerGraphData" name="customerGraphDataValues"
    minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
                   <xsd:complexType name="CustomerGraphData">
                        <xsd:sequence>
                             <xsd:element type="xsd:string" name="code"
    minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                             <xsd:element type="xsd:int" 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:element type="xsd:int" name="parentId"
    minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
                   <xsd:complexType name="CustomerHelper" abstract="true">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
                                  <xsd:sequence>
                                       <xsd:element type="xsd:int"
    name="accountStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:dateTime"
    name="agingDate" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="agingDays" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="allowSplitOrders" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:double"
    name="balanceDue" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="stns:Address"
    name="billAddressData" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="stns:Address"
    name="billToAddress" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="billToAddressId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="billingAddressSourceCode" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="billingPartnerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="billingPartnerName" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="buyer" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:double"
    name="creditAvailable" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:double"
    name="creditLimit" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="currencyId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="customerCode" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="deliveryPoints" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="departmentCode" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="dropSequence" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
    name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="facilityId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:double"
    name="financeChargePercent" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="fixedTimeForStop" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:double"
    name="freightAmount" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="freightTypeId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="groupId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="gstTaxApplicable" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="hasHistory" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="id" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="importNumber" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="isDirectlyBillable" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="isGroupVolumeDiscounted" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="isRegion" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="isShipTo" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="kitCodeId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="leadTime" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="lockoutControl" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="managerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="mediumRangeZone" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="merchandiserId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
    name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="name" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="packageId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="parentCustomerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="parentName" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="priceListId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="printStatement" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="receivingTimeFrom" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="receivingTimeTo" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="recordStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="requirePO" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="requireSKU" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="salesRepId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="stns:Address"
    name="shipAddressData" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="stns:Address"
    name="shipToAddress" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="shipToAddressId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="shipViaId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="shipZoneId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="shortRangeZone" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="specialCodes" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:dateTime"
    name="startDate" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="storeNumber" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="summaryPrintCodeId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="taxCodeId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="taxNumber" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="termsCodeId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:double"
    name="toBeDue" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="useShippingAddress" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="vendorNumber" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="version" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="warningControl" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="CustomerProfile">
                        <xsd:sequence>
                             <xsd:element type="stns:ArrayOfProfile"
    name="profiles" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
                   <xsd:complexType name="CustomerSearchCriteria">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.common" base="tp:AbstractSearchCriteria">
                                  <xsd:sequence>
                                       <xsd:element type="xsd:int"
    name="billingPartnerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="id" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="isDirectlyBillable" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="isRegion" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:boolean"
    name="isShipTo" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="parentCustomerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="searchString" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="searchType" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="CustomerTypePct">
                        <xsd:complexContent>
                             <xsd:extension
    base="stns:CustomerTypePctHelper">
    </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="CustomerTypePctHelper"
    abstract="true">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
                                  <xsd:sequence>
                                       <xsd:element type="xsd:int"
    name="customerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="customerTypeId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
    name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="id" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
    name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="recordStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="status" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="typePct" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="version" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="MailingListSubscription">
                        <xsd:complexContent>
                             <xsd:extension
    base="stns:MailingListSubscriptionHelper">
    </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="MailingListSubscriptionHelper"
    abstract="true">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
                                  <xsd:sequence>
                                       <xsd:element type="xsd:boolean"
    name="checked" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="customerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
    name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="id" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="mailingListId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="mailingListName" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
    name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="recordStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="version" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="NoteVault">
                        <xsd:complexContent>
                             <xsd:extension base="stns:NoteVaultHelper">
    </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="NoteVaultHelper" abstract="true">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
                                  <xsd:sequence>
                                       <xsd:element
    xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
    name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="id" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
    name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="recordStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="tag" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="text" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="type" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="version" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="Notes">
                        <xsd:complexContent>
                             <xsd:extension base="stns:NotesHelper">
    </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="NotesHelper" abstract="true">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
                                  <xsd:sequence>
                                       <xsd:element type="xsd:int"
    name="customerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:dateTime"
    name="date" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
    name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="id" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
    name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="owner" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="recordStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="reference" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="subtype" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="text" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="type" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="version" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="Profile">
                        <xsd:complexContent>
                             <xsd:extension base="stns:ProfileHelper">
    </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="ProfileHelper" abstract="true">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
                                  <xsd:sequence>
                                       <xsd:element type="xsd:int"
    name="customerId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
    name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="id" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
    name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="numericInfo" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element
    type="stns:ProfileInfo" name="profileInfoData" minOccurs="1" maxOccurs="1"
    nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="profileInfoId" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="recordStatus" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                       <xsd:element type="xsd:string"
    name="textInfo" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element type="xsd:int"
    name="version" minOccurs="1" maxOccurs="1">
    </xsd:element>
                                  </xsd:sequence>
                             </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="ProfileInfo">
                        <xsd:complexContent>
                             <xsd:extension base="stns:ProfileInfoHelper">
    </xsd:extension>
                        </xsd:complexContent>
                   </xsd:complexType>
                   <xsd:complexType name="ProfileInfoHelper"
    abstract="true">
                        <xsd:complexContent>
                             <xsd:extension
    xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
                                  <xsd:sequence>
                                       <xsd:element type="xsd:string"
    name="domainValueName" minOccurs="1" maxOccurs="1" nillable="true">
    </xsd:element>
                                       <xsd:element
    xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
    name="errorMessages" minOccurs="1" maxOccurs="1" nillabl

    Bruce,
    Sorry, I forgot to mention that the WSDL was generated by querying the URL
    of the deployed webservice. If there is something missing from the WSDL,
    it may be due to servicegen, or a problem with deployement. All of this
    used to work in WLS 7.0 sp1.
    I submitted this case (459937) to BEA Support on 11/12/03 and have given
    them my EJB jar file so they can reproduce the problem using servicegen.
    I would appreciate any input you can provide to resolve this problem, but
    you can let Support handle it from here if you wish.
    Thanks,
    Tony
    [email protected] (Bruce Stephens) wrote:
    Hi Tony,
    Could you clarify your starting point; i.e. do you begin with WSDL or
    from java?
    In looking at your WSDL, on the surface I'm concerned that the imports
    should be something like <xsd:import namespace="..."
    schemaLocation="myschema.xsd"/> so it may not be including your
    definitions.
    Thanks,
    Bruce
    Tony Huang wrote:
    I have datatypes that extend classes in a different package. When I
    use WLS81 ANT task clientgen to generate client-jars from WSDL files
    obtained from web services generated by servicegen, the superclasses
    are not fully qualified in the generated java code, nor are there
    import statements for the superclasses. This causes the generated
    code to have compile errors. Other dependencies are fully qualified in
    the generated code, but the superclass is not.
    There mayThe WSDL is included below. Specifically,
    com.starcomsoft.pp.database.BaseHelper does not get a fully qualifed
    reference in the generated java code.

  • Error while inserting value Qualified field in the main table

    Hello,
    I am trying to populate Qualified field in the main table when a new record is inserted in the Products Repository.
    The field is Reference Price and its a qualified lookup field. I am using the below code to create qualified lookup value and create qualified link values.
    QualifiedLookupValue qlvRefPrice = new QualifiedLookupValue();
    TableId qltabid = repSchema.getTableId("ReferencePrices");
    FieldId qlfieldid = repSchema.getFieldId("ReferencePrices","RP_ReferncePrices");
    RecordId rdRefPrice = getRecordId(connPool,session,"RP",qlfieldid,qltabid);
    HashMap map = new HashMap();
    map.put(repSchema.getFieldId("ReferencePrices","StartDate_ReferencePrice"),new DateTimeValue(cal));
    map.put(repSchema.getFieldId("ReferencePrices","EndDate_ReferencePrice"),new DateTimeValue(cal));
    map.put(repSchema.getFieldId("ReferencePrices","ListPrice"),new FloatValue(Float.parseFloat("123.3")));
    map.put(repSchema.getFieldId("ReferencePrices","Currency"),new LookupValue(getLookupRecordId(connPool,session,"Currencies","Currency_Currencies","EUR")));
    QualifiedLinkValue qlvLinkValue = MdmValueFactory.createQualifiedLinkValue(rdRefPrice,map);
    qlvRefPrice.addValue(qlvLinkValue);
    emptyRecord.setFieldValue(fieldIdRefPriceHistory,qlvRefPrice);
    However when the createrecord command is executed I get the following error.
    java.lang.RuntimeException: No matching validation Id 97. at com.sap.mdm.internal.validation.ValidationInfoHelper.retrieveValidations(ValidationInfoHelper.java:71) at com.sap.mdm.data.commands.CreateRecordCommand.execute(CreateRecordCommand.java:246) at com.alcatel_lucent.productdetail.ProductItemDetail_Comp.createProduct(ProductItemDetail_Comp.java:2927) at com.alcatel_lucent.productdetail.wdp.InternalProductItemDetail_Comp.createProduct(InternalProductItemDetail_Comp.java:656) at com.alcatel_lucent.productdetail.ProductItemAddView.onActionSave(ProductItemAddView.java:971) at com.alcatel_lucent.productdetail.wdp.InternalProductItemAddView.wdInvokeEventHandler(InternalProductItemAddView.java:662) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869) at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77) at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1356) at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327) at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)      
    I spoke to my MDM team and they say there is no validation which they have put for Reference Price field. I have tried inserting values in another field of type qualified lookup in the same main table and that works without any issue.
    The code is as below:
    QualifiedLookupValue qlvRating = new QualifiedLookupValue();
    TableId qlvtable = repSchema.getTableId("ProductRatings");
    FieldId qlvratinglink = repSchema.getFieldId("ProductRatings","RatingLink");                    
    RecordId rdidPR = getRecordId(connPool,session,"CI",qlvratinglink,qlvtable);
    wdComponentAPI.getMessageManager().reportSuccess("rdidPR "+rdidPR);
    HashMap mapPR = new HashMap();
    mapPR.put(repSchema.getFieldId("ProductRatings","AvailRating"),new LookupValue(getLookupRecordId(connPool,session,"AvailabilityRatings","AvailabilityRating_AvailabilityRatings","CI")));
    mapPR.put(repSchema.getFieldId("ProductRatings","EffectiveDate"),new DateTimeValue(cal));
    mapPR.put(repSchema.getFieldId("ProductRatings","FERAIndic"),new LookupValue(getLookupRecordId(connPool,session,"ReplacementIndicators","Code","FE")));
    mapPR.put(repSchema.getFieldId("ProductRatings","FERAOrdItem"),new LookupValue(getLookupRecordId(connPool,session,"ReplProducts","ProdID","100008200")));
    QualifiedLinkValue qlvLink = MdmValueFactory.createQualifiedLinkValue(rdidPR,mapPR);
    qlvRating.addValue(qlvLink);
    emptyRecord.setFieldValue(fieldIdRatingHistory,qlvRating);     
    I would really appreciate if someone can help in solving the issue.
    Thanks in advance,
    Aamod

    Hi Aamod,
    Sees that some validation/assignments are getting triggered as soon as you make changes to the record in MDM. Please check once after removing validations/workflow that you may have. This way you may debug the issue.
    Hope this helps!!
    Cheers,
    Arafat

  • SharePoint 2010, Visual Studio 2010, Packaging a solution - The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

    Hi,
    I have a solution that used to contain one SharePoint 2010 project. The project is named along the following lines:
    <Company>.<Product>.SharePoint - let's call it Project1 for future reference. It contains a number of features which have been named according
    to their purpose, some are reasonably long and the paths fairly deep. As far as I am concerned we are using sensible namespaces and these reflect our company policy of "doing things properly".
    I first encountered the following error message when packaging the aforementioned SharePoint project into a wsp:
    "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."
    I went through a great deal of pain in trying to rename the project, shorten feature names and namespaces etc... until I got it working. I then went about gradually
    renaming everything until eventually I had what I started with, and it all worked. So I was none the wiser...not ideal, but I needed to get on and had tight delivery timelines.
    Recently we wanted to add another SharePoint project so that we could move some of our core functinality out into a separate SharePoint solution - e.g. custom workflow
    error logging. So we created another project in Visual Studio called:
    <Company>.<Product>.SharePoint.<Subsystem> - let's call it Project2 for future reference
    And this is when the error has come back and bitten me! The scenario is now as follows:
    1. project1 packages and deploys successfully with long feature names and deep paths.
    2. project2 does not package and has no features in it at all. The project2 name is 13 characters longer than project1
    I am convinced this is a bug with Visual Studio and/or the Package MSBuild target. Why? Let me explain my findings so far:
    1. By doing the following I can get project2 to package
    In Visual Studio 2010 show all files of project2, delete the obj, bin, pkg, pkgobj folders.
    Clean the solution
    Shut down Visual Studio 2010
    Open Visual Studio 2010
    Rebuild the solution
    Package the project2
    et voila the package is generated!
    This demonstrates that the package error message is in fact inaccurate and that it can create the package, it just needs a little help, since Visual Studio seems to
    no longer be hanging onto something.
    Clearly this is fine for a small time project, but try doing this in an environment where we use Continuous Integration, Unit Testing and automatic deployment of SharePoint
    solutions on a Build Server using automated builds.
    2. I have created another project3 which has a ludicrously long name, this packages fine and also has no features contained within it.
    3. I have looked at the length of the path under the pkg folder for project1 and it is large in comparison to the one that is generated for project2, that is when it
    does successfully package using the method outlined in 1. above. This is strange since project1 packages and project2 does not.
    4. If I attempt to add project2 to my command line build using MSBuild then it fails to package and when I then open up Visual Studio and attempt to package project2
    from the Visual Studio UI then it fails with the path too long error message, until I go through the steps outlined in 1. above to get it to package.
    5. DebugView shows nothing useful during the build and packaging of the project.
    6. The error seems to occur in
    CreateSharePointProjectService target called at line 365 of
    Microsoft.VisualStudio.SharePoint.targetsCurrently I am at a loss to work out why this is happening? My next task is to delete
    project2 completely and recreate it and introduce it into my Visual Studio solution.
    Microsoft, can you confirm whether this is a known issue and whether others have encountered this issue? Is it resolved in a hotfix?
    Anybody else, can you confirm whether you have come up with a solution to this issue? When I mean a solution I mean one that does not mean that I have to rename my namespaces,
    project etc... and is actually workable in a meaningful Visual Studio solution.

    Hi
    Yes, I thought I had fixed this my moving my solution from the usual documents  to
    c:\v2010\projectsOverflow\DetailedProjectTimeline
    This builds ok, but when I come to package I get the lovely error:
    Error 2 The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. C:\VS2010\ProjectsOverflow\DetailedProjectTimeline\VisualDetailedProjectTimelineWebPart\Features\Feature1\Feature1.feature VisualDetailedProjectTimeline
    Now, the error seems to be related to 
    Can anyone suggest what might be causing this. Probably some path in an XML file somewhere. Here is my prime suspect!
    <metaData>
    <type name="VisualDetailedProjectTimelineWebPart.VisualProjectTimelineWebPart.VisualProjectTimeline, $SharePoint.Project.AssemblyFullName$" />
    <importErrorMessage>$Resources:core,ImportErrorMessage;</importErrorMessage>
    </metaData>
    <data>
    <properties>
    <property name="Title" type="string">VisualProjectTimelineWebPart</property>
    <property name="Description" type="string">My Visual WebPart</property>
    </properties>
    </data>
    </webPart>
    </webParts>
    .... Unless I can solve this I will have to remove the project and recreate but with simple paths. Tho I will be none the wiser if I come across this again.
    Daniel

  • Microsoft told us to include the iPad's in the true-up as a fully qualified desktop under the Enterprise Agreement?

    Hi,
    I work at Oil company in the UAE and we wanted to use iPads at  work but Microsoft replied with the following & I wanted to verify this from your side:
    Weather iPad is owned by the user or the company, it will require proper softwarelicense right to access Microsoft Software in use by your organization. Beloware different usage scenarios and required licenses:
    iPadwill be used to access
    -       exchangeEmail”: each iPad will require a Windows Server Device CAL, Exchange DeviceCAL, Exchange Enterprise Device CAL*, and Forefront for Exchange CAL*
    -       Intranetrunning IIS only: each iPad will require a Windows Server Device CAL
    -       Portalrunning SharePoint: each iPad will require a Windows Server Device CAL, SQLDevice CAL, SharePoint Standard Device CAL, SharePoint Enterprise Device CAL,and Forefront for SharePoint CAL*
    -       InternalBusiness Applications: Windows Server Device CAL, SQL Device CAL, any other CALused by this application
    -       MicrosoftOffice: each iPad will require and Office license except for 1-1 remote access
    “Notethat for Exchange Email access, this will apply even if the user will use iPademail client, outlook web access, Outlook via HVD or RDS.
    *requiredif this product is in use
    As theenterprise agreement doesn’t include individual CAL’s. there are three ways toacquire those licenses:
    -       Includethe iPad’s in the true-up as a fully qualified desktop under the EnterpriseAgreement
    -       Acquiringthe Enterprise CAL only & SQL CAL for those devices under the EA. We willneed to approve an exception to do that. Please advise me the quantity. Thisscenario will apply only if Office will not be used with the iPad or will beused in 1-1 Remote Access scenario.
    -       Signa separate Select agreement to acquire the individual CAL’s with SA.
    Regards,

    Thank you
    I also found the below useful links
    http://tonymackelworth.wordpress.com/2011/01/01/the-ipad-on-your-network/
    http://tonymackelworth.wordpress.com/2011/03/17/applications-and-os-licensing-re mote-access-and-roaming-use/
    "Remoteaccess to applications on a host PC by the Primary User of that device are covered by the volume licenses for Office assigned to the Primary Work device.
    This option is where the work PC is running back in the office and theend user is “tunnelling in” from another PC. The later introduced roamingrights allows access to virtualized Office, which is run from a server, versusrunning on the licensed PC that existed prior to roaming use rights"

  • TFS Build Error - Exception Message: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters

    I am trying to set-up CI of Orchard CMS and deploy it on Azure using TF service. I am stuck at following error for path being
    longer than 260 characters. However, when counted the total characters in path are 235. Please see the below error :
    Other Errors and Warnings
    1 error(s), 1 warning(s)
    Exception Message: TF400889: The following path contains more than the allowed 259 characters: drop/_PublishedWebsites/Orchard.Web_Package/Archive/Content/C_C/a/src/projects/Orchard/dev/DevAltaf/Orchard/src/Orchard.Web/obj/Debug/Package/PackageTmp/Modules/BrentApart.BannerManager/Scripts/controllers/bannerAssignmentController.js. Specify a shorter path. (type VssServiceException)
    Exception Stack Trace: at Microsoft.TeamFoundation.Build.Workflow.Activities.FileContainerDropProvider.EndCopyDirectory(IAsyncResult result)
    at Microsoft.TeamFoundation.Build.Workflow.Activities.CopyDirectory.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
    at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
    Inner Exception Details:
    Exception Message: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. (type PathTooLongException)
    Did anyone came across such issue while deploying Orchard on Azure with TF service? If yes, how did you sort this freaking error?
    Thanks,
    Altaf B.

    Hi AltafB,
    For your situation, you can short the path for the source code. Or use a short path for build agent folder in your build definition. You can refer to the links below to solve your problem:
    http://blogs.msdn.com/b/aaronhallberg/archive/2007/06/20/team-build-and-260-character-paths.aspx
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/1638a5f0-9321-4ff9-9ee7-6d347badb972/please-some-solution-to-the-specified-path-file-name-or-both-are-too-long?forum=tfsbuild
    Besides, since you deploy Orchard to Azure, you can also publish it directly using publish profile in Visual Stduio or WebMatrix directly.
    Best regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Fully qualified filename (including path)

    I have a sample program I'm playing with to learn a bit about JAVA. In the code below I have variables named 'file1' and 'file2' which are defined with a filenames 'file1.txt' and file2.txt respectively.
    So when the program executes it looks for these files in the current directory. However, if I want to change these values to 'c:\file1.txt' and 'c:\ttmsapps\file2.txt' then I can't compile the program.
    Would someone be able to show me in the code below how to specify a fully qualified filename? I'd certainly appreciate seeing the example.
    import java.io.File;
    import java.lang.Object;
    import java.util.Date;
    import java.text.Format;
    import java.text.DateFormat;
    import java.text.SimpleDateFormat;
    public class CompareFileDates {
      public static void main(String[] args) {
        String fileStatus = " ";
        String file1 = "file1.txt";
        String file2 = "file2.txt";
        long date1 = 0;
        long date2 = 0;
        String finalDate1 = null;
        String finalDate2 = null;
        boolean file1Exists = (new File(file1)).exists();
        boolean file2Exists = (new File(file2)).exists();
        if (file1Exists) {
            // Get the timestamp from file 1 and format it
            date1 = (new File(file1)).lastModified();
         Date newDate1 = new Date(date1);
         DateFormat df = new SimpleDateFormat();
         finalDate1 = df.format(newDate1);
        else {
            // File or directory does not exist
            fileStatus = file1 + " does not exist.  ";
    ...more

    Awesome. I'm getting very close.
    However, in building the variable 'file1' on the Windows-side I will need to be specific to the which Drive Letter the file exists on...for instance I may need to specify 'C:\' as part of the creation of the 'file1' variable. This is because the java program will be executed by people on the File Server on the K: drive, yet I want the program to specify a file on their C: drive. If I do this then the program wouldn't run on UNIX, right? Because UNIX doesn't have Drive Letters (e.g. C:, K:).
    In this case would I have to hard code the Drive Letter for Windows and then edit and remove the Drive Letter before running the program on UNIX?
    Here's my program so far which will run on Windows or UNIX, but it doesn't have the Drive Letter differences required on Windows so the program would have to be executed by the user on the same Drive Letter as the file I'm specifying.
    import java.io.File;
    import java.lang.Object;
    import java.util.Date;
    import java.text.Format;
    import java.text.DateFormat;
    import java.text.SimpleDateFormat;
    public class CompareFileDates {
      public static void main(String[] args) {
        String file1 = File.separator + "exfc" + File.separator + "its" + File.separator + "file1.txt";
        System.out.println(file1);
    }The output on Windows:
    K:\COMMON\ITS\STEVEB\java\CompareFileDates>java CompareFileDates
    \exfc\its\file1.txtThe output on UNIX:
    /data/users/ssbuechl/java/CompareFileDates >java CompareFileDates
    /exfc/its/file1.txt

  • Error in Installing- System dosen't have fully qualified domain name.

    When I try to install Java Enterprise System in my PC, I get the following error message and cannot proceed further:
    System dosen't have fully qualified domain name.
    Setup fully qualified domain name and then continue instalation.
    Please help me to solve this problem.
    About my PC:
    Windows XP Home edition
    1 GB memory
    Thanks.

    Do you have DNS running on the net and configured right? Run "ipconfig" in a Windows XP command line to see if the DNS suffix is set. Another trick is to run "nslookup" in the command line and look up your system's IP address (wehich ipconfig will tell you.) If that doesn't get you a DNS name for the system, you need to fix that in the network connections dialogs.

  • BI 7.0 Java Add-in without fully qualified domain name

    Hi
    I have just installed the Java Add-in for BI 7.0, and now I am trying to set up BEx to work. I have run the template installer, but there seems to be an issue with server names vs. fully qualified domain names. The server name is currently in the format "server.domain", but I suspect that it should/must be "server.domain.com".
    Is it possible to get full functionality without using fully qualified domain names (FQDN)? Is so, how can I acheive this?
    Regards,
    Thomas
    Edited by: Thomas Kjelsrud on Apr 23, 2008 8:39 PM

    This issue is no longer relevant for me. I still wish to find the solution tough, for future reference.
    Tegards,
    Thomas

  • How Oracle Installation cannot get fully qualified name of the server?

    Hi,
    I'm installing Oracle Internet Application Server (10.1.2) on Windows. The Win machine has fully qualified name as myserver.mydomain.com
    However, after the installation, Oracle shows that the URL to Internet Application Server is only
    http://myserver:7777
    I have changed the hosts file of the Win machine and add the line, e.g.,
    10.1.10.10 myserver.mydomain.com myserver
    where 10.1.10.10 is the IP of the Win machine.
    I re-install Oracle Internet Application Server again, but it still cannot picks up the fully qualified name as myserver.mydomain.com for the URL of Internet Application Server page.
    Any ideal?

    I'm installing Oracle Internet Application Server (10.1.2) on Windows. The Win machine has fully qualified name as myserver.mydomain.com
    I have changed the hosts file of the Win machine and add the line, e.g.,
    10.1.10.10 myserver.mydomain.com myserverInstead, use the following in your hosts file, and then try again.
    10.1.10.10 myserver.mydomain.com # myserver

Maybe you are looking for

  • RFC - PI - SOAP - escape characters

    I'm trying to send following payload in an RFC to PI and then onword to SOAP (sharepoint webservice) <Method ID="1" Cmd="New"><Field Name="Title">Added item</Field> However PI replaces "<" into  "& # 60 ;" and  ">" into "& # 62 ;" (placed spaces in t

  • Errors When Installing 0PUR_C01

    Hi Friends,             I get the follwoing error when Installing this cube. (1)Error when reading the update rules fr InfoCube 0DBDUNS_NUM, ISource 0DBDUNS_IMPORT_ATTR in vers.M (2)Transfer rules 0RF_ARTHIER_ACT BWDCLNT100 (3) DataSource 0RF_ARTHIER

  • PSE 13.1 Update Errors

    I got prompted to install PSE 13.1 updates, and did so. Then got the following helpful message. Anyone know what it is? Windows 8.1 system. Photoshop Camera Raw 8.7.1 There was an error installing this update. Please quit and try again later. Error C

  • C5 CHAT not workng

    i just got my NOKIA C5, and i regret it, no comparision to BOLD9700, now i wanna use the chat option but i get this error message error java.lang.error exception in static initializer: java.lang.securityexception: cannot use exit(), use MIDlet notify

  • Get performance when key does not exist

    Hello, I am using BDB version db-4.5.20. I try to get an object which is not present and the performance of this call is extremely slow. The newer versions have an exists call for the key. How can I get better performance in this case. I am using HAS