Namespaces question

I have been converting some code I had over to the new ExtensibleEnvironment stuff and this has been going quite well. Everything I have done so far has been to configure stand-alone things like message listerners etc. What I cannot figure out is how to do something that needs to be triggered in response to an "event" (in particular creation of a cache).
For example, suppose I want to configure custom indexes. I might do the following:
    <cache-mapping>
      <cache-name>dist-*</cache-name>
      <scheme-name>dist-default</scheme-name>
      <idx:indexes>
        <idx:index ordered="true">
          <idx:extractor>
            <instance:class classname="my.package.SomeExtractor"/>
          </idx:extractor>
          <idx:comparator>
            <instance:class classname="my.package.SomeComparator"/>
          </idx:comparator>
        </idx:index>
        <idx:index ordered="false">
          <idx:extractor>
            <instance:class classname="my.package.AnotherExtractor"/>
          </idx:extractor>
        </idx:index>
      </idx:indexes>
    </cache-mapping>At the moment the XML is processed as everything starts up but I only want to actually create the indexes when an instance of a cache is created (in the example above any cache with a named prefixed with "dist-".
Is there anything in the new Incubator release to allow me to do what I want or will I need to come up with my own solution? Is this what the Events or Dependencies packages are for; if it is can I see some documentation or an example?
Cheers,
JK

Jonathan,
As part of processing your namespace you can register resources with the Environment that implement the DependentResource interface.
Your registered resource will then be queried for its dependencies by calling the getDepedencyReferences method.
    public Set<DependencyReference> getDependencyReferences();When the dependencies are satisfied, the onDependenciesSatisfied method will be called by the Environment.
This mechanism is mainly there to allow you to manage dependencies when starting and shutting down a system properly, and not to provide a callback while the system is running.
One DependencyReference that might be useful for you is the NamedCacheReference which will be satisfied when the underlying cache service is started. You can find example uses of the DependentResource mechanism in the Processing Pattern.
Unfortunately, there is no way of getting an event when a cache is created which was what you really were looking for.
/Christer
Edited by: Christer Fahlgren on Mar 4, 2010 2:10 PM

Similar Messages

  • Basic namespace question

    Hello,
    A (possibly dumb) namespace question - a schema that we are coding against has the following declaration:
    <xs:schema xmlns="http://webservices.myco.com/mycoXML/2003/07" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://webservices.myco.com/mycoXML/2003/07" elementFormDefault="qualified">When this schema is xjc'ed and then the associated java objects populated, then marshalled into an xml request, it prefixes "ns2" to all the elements within the XML, possibly because there are 2 namespaces specified.
    the web service however throws a "Could not find element" error, because it's not expecting the ns2 prefix.
    The questions are:
    1. could this ns2 be suppressed?
    2. does it make sense to suppress it?
    any other background/info about this and the right way to resolve it would be greatly appreciated.
    [edit]
    I may have a partial answer to my question - w3.org's primer told me that since the elementFormDefault is set to qualified, and attributeFormDefault is (by default) unqualified, it uses the ns2 to differentiate between the two.
    when i added attributeFormDefault="qualified", it prefixed everything with an ns1, which the web service seems to be quite happy with.
    if anyone has any other comments/insights, i'd appreciate it.
    Thanks,
    Nilesh
    Edited by: nthali on Apr 15, 2010 2:04 PM

    Just to add to Tims response
    If you do calc dim on account first and then aggregate sparse dimensions, then its best to Fix on Level 0 of all the Sparse dimensions for the calc dim and then aggregate the sparse. Otherwise when you run the calc the second time the calculation will calc dim on all levels of all sparse dimension combinations (there will be data there from the previous aggregation). This can be very very slow. So see below
    FIX("Local", "HSP_InputValue", "Actual",  "Final", "Jan", "FY15")
      FIX(@RELATIVE("Entity",0),@RELATIVE("Product",0), @RELATIVE("Channel",0),@RELATIVE("Project",0))
    CALC DIM ("Account");
    ENDFIX
    AGG ("Entity","Product", "Channel", "Project",);
    ENDFIX;

  • Transport namespace question

    Hello everyone,
    Small question. I have 2 development systems, I have to transport my things from the 1st development system to the 2nd and only then I can transport to the quality system. But someone else is doing work in the 2nd development system and created some namespaces in the same software component I am working on. So there are more namespaces in the 2nd system then in the 1st. My question is, when I transport the namespace definition for that software component from the 1st development system to the 2nd will those namespaces that do not exist in the 1st be deleted or will the transport only append my namespaces?
    Thanks

    Hi,
    According to my understanding,Unless the namespace in both the system look like the transports will not be affected.It will not delete any namespace, it will always append to the software component.
    Thanks,
    Uaruna

  • StAX namespace question

    Hello,
    Looking at this soap fault document:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
    <soapenv:Fault>
      <faultcode>21</faultcode>
      <faultstring>Login error</faultstring>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>The 'faultcode' element has no prefix associated, but it belongs to ''http://schemas.xmlsoap.org/soap/envelope/" URI. When I'm positioned on 'faultcode' element, the XmlStreamReader.getNamespaceURI() call gets null, because there is no namespace directly associated to this element. The question is that I need all the namespaces associated to this element. The specification talks about a "namespace stack" -> NamespaceContext, but this is not useful for me because I'd need an iterator with all namespaces of this element (and with NamespaceContext you always need to pass a prefix or a URI as parameters to methods).
    Is there any way to achieve this, or should I program it?
    Thanks a lot,
    Joan

    Thank you for the message.
    I know the config.xml file is eventually passed to java.exe and the error is from there. Since namespace is just a token to distinguish one from another, I don't understand why the default namespace has to be kept and can not be changed.
    Can you please explain it more to me? If my webservice is under that namespace and you too have a webservice under the same namespace, what's going to happen if we 2 accidently give the same name to our webservices? Is there any conflict going on?
    Thanks

  • Namespace question with caringorm3

    Hi,guys.
    Studying with cairngorm3 demo, it does not work when I put  ' xmlns:cairngorm="http://ns.adobe.com/cairngorm"  '  in xxx.mxml,
    instead, something like ' xmlns:cairngorm="com.adobe.cairngorm.popup.*"  '  is OK.
    why? please,

    Namespace in the XI holds the design time objects of a particular interface that you develop, it;s like a folder name, when you create a namespace it provides you standrd template under it....
    it can be
    a)Equivalent to function group Name
    b) Equivalent to development class Nmae
    c) Equivalent to function module Name
    d) Equivalent to BAPI Name

  • XML Namespace Question

    Hi folks,
    I'm new to XML, and have been trying to validate an XML document against a schema using an online validator.
    I have given ultra-simple examples of my schema and document below:
    Schema
    <?xml version="1.0"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.example.com"
    xmlns="http://www.example.com">
         <xs:element name="letter">
                   <xs:complexType>
                        <xs:sequence>
                             <xs:element name="to" type="xs:string"/>
                             <xs:element name="from" type="xs:string"/>
                        </xs:sequence>
                   </xs:complexType>
         </xs:element>
    </xs:schema>
    Document
    <?xml version='1.0' ?>
    <letter xmlns="http://www.example.com">
              <to>You</to>
              <from>Me</from>
    </letter>When I try to validate the document against this schema I get the following errors:
    Validation error:
    Error at (3,4): The element 'http://www.example.com:letter' has invalid child element 'http://www.example.com:to'. Expected 'to'.
    Error at (3,4): The 'http://www.example.com:to' element is not declared. An error occurred at , (3, 4).<to>You</to>
    Error at (4,4): The 'http://www.example.com:from' element is not declared. An error occurred at , (4, 4).<from>Me</from> </letter>
    I must be doing something wrong when declaring namespaces, but I can't see what. Can anyone point me in the right direction, please?
    Thanks,
    s.

    This is what I have for your code:
    import java.io.IOException;
    import javax.xml.parsers.DocumentBuilderFactory;
    import javax.xml.parsers.DocumentBuilder;
    import javax.xml.parsers.ParserConfigurationException;
    import org.w3c.dom.Document;
    import org.w3c.dom.Element;
    import org.w3c.dom.Node;
    import org.w3c.dom.NodeList;
    import org.w3c.dom.NamedNodeMap;
    import org.xml.sax.SAXException;
    import org.xml.sax.SAXParseException;
    import org.xml.sax.helpers.DefaultHandler;
    public class JAXPValidator
         public void validateXML(String XmlDocumentUrl) throws Exception
              System.setProperty( "javax.xml.parsers.DocumentBuilderFactory",
                                       "org.apache.xerces.jaxp.DocumentBuilderFactoryImpl");
              DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
              factory.setNamespaceAware(true);
              factory.setValidating(true);
              factory.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaLanguage",
                                        "http://www.w3.org/2001/XMLSchema");
              DocumentBuilder builder = factory.newDocumentBuilder();
              Validator handler = new Validator();
              builder.setErrorHandler(handler);
              Document doc = builder.parse(XmlDocumentUrl);
              if( handler.hasValidationError() )
                   throw( handler.getParseException() );
    // these simple loops assume that the xml has already been validated!
              NodeList letters = doc.getElementsByTagName( "letter" );
              for( int i = 0; i < letters.getLength(); i++ )
                   NodeList letterChildren = letters.item( i ).getChildNodes();
                   for( int j = 0; j < letterChildren.getLength(); j++ )
                        Node nextNode = letterChildren.item(j);
                        if( nextNode.getNodeType() == Node.ELEMENT_NODE )
                             Node nextNodeValue = nextNode.getFirstChild();
                             System.out.println( "nextNode.getLocalName() is " + nextNode.getLocalName() );
                             System.out.println( "nextNodeValue.getNodeValue() is " + nextNodeValue.getNodeValue() );
         private class Validator extends DefaultHandler
              private boolean validationError = false;
              private SAXParseException saxParseException = null;
              public boolean hasValidationError()
                   return( validationError );
              public Exception getParseException()
                   return( saxParseException );
              public void error(SAXParseException exception) throws SAXException
                   validationError = true;
                   saxParseException = exception;
              public void fatalError(SAXParseException exception) throws SAXException
                   validationError = true;
                   saxParseException = exception;
              public void warning(SAXParseException exception) throws SAXException
                   validationError = true;
                   saxParseException = exception;
         public static void main(String[] argv)
              JAXPValidator validator = new JAXPValidator();
              try
                   validator.validateXML(argv[0]);
              catch( Exception e )
                   e.printStackTrace( System.err );
    }This was compiled with:
    javac -classpath .;..\xerces-2_7_0\xercesImpl.jar;..\xerces-2_7_0\xml-apis.jar JAXPValidator.javaand run with
    java -classpath .;..\xerces-2_7_0\xercesImpl.jar;..\xerces-2_7_0\xml-apis.jar JAXPValidator sunforum.xmlIt assumes that the XML and XSD that I posted before are in the same directory as the program is being run from.

  • Namespace question

    Dear SDN,
    A message mapping is raising the following error:
    RuntimeException in Message-Mapping transformatio~
    The reason is that the inbound payload has not namespace therefore mapping raises a not well formed inbound message error.  My guess!
    The inbound message is generated by an external system without explicit namespace:
    <root>
    </root>
    when manually editing the message and adding to it namespace, message process successfully:
    <ns0:root xmlns:ns0="...">
    </ns0:root>
    How can I omit this namespace check, o can I create a message type without namespace?

    I just found a way to solve it.
    Yes you're right, I am not using an external definition, I created a data type importing the xsd file, and then created a message type referencing such data type.
    How I solved it was quite simple. I just export the message type to an xsd archive, edited it to remove namespace definition, and then imported it as source structure into the message mapping.  Now the scenario works fine.
    Thanks a lot.

  • JAXB - Java to XML namespaces question

    I want the following XML to be produced:
    <service
    xmlns="http://www.example.org/service"
    xmlns:db="http://www.example.org/db"
    >
    <firstElement>
       <db:title>Testing</db:title>
    </firstElement>
    </service>However, this is proving to be impossible in JAXB. If I put any namespace within any annotation within my java bean I get unwanted prefixes everywhere. If I use the XmlSchema at the package level and specify prefixes with @XmlNs that doesn't even show up in the XML.
    I feel I am almost at a loss?

    Well, i got it to work in JAXB 1, w/o xfire, schema-to-java. Marshall and unmarshall.
    But w/ xfire, it doesn't appear to be possible. Would probably require implementing it for them myself...

  • X-Path & Namespace question

    Hi,
    In x-path version 2.0, one can write a * for an arbitrary namespace, is something possible in version 1.0 ?
    Example x-path '/MESSAGES/*:HEADER/PRIORITY'
    returns leaf-node value of priority as of
    /MESSAGES/msg1:HEADER/PRIORITY with xmlns:msg1="http//example.org/msg1.xsd"
    /MESSAGES/msg2:HEADER/PRIORITY with xmlns:msg2="http//example.org/msg2.xsd"
    etc etc
    If this isn't possible, is there a workaround,
    or in what version of the database is it possible ?
    Regards,
    Art

    I have a table based on a schema (object-relational) which only purpose is storage of xml-messages send over a network.
    The database should by queryable on on elements that are available in all message but in different namespaces / paths.
    I can offcourse make a b-tree index on each leafnode in all namespaces that I want to query, but I was wondering if I could use an index with the above mentioned X-Path 2.0 behavior. I think if it is possible it will be a function based index, but that should be okay.
    Any thoughts ?

  • Simple namespace question

    Hi:
    I am working with XMP SDK, I saw the documentation having example to GetProperty:
    meta.GetProperty( kXMP_NS_XMP, "CreatorTool", &value, &opts );
    The first arguement is the namespace, but I do not know what is my name space? Can someone make some example of rdf file and what the namespace argument should be?
    An example of a rdf file is:
    <rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
         <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1/'>
              <dc:subject>
                   <rdf:Bag>
                        <rdf:li>XMP</rdf:li>
                        <rdf:li>SDK</rdf:li>
                        <rdf:li>Sample</rdf:li>
                   </rdf:Bag>
              </dc:subject>
              <dc:format>image/jpeg</dc:format>
         </rdf:Description>
    </rdf:RDF>
    Thanks.

    Greetings,
                 the xmlns creates a namespace, so from what I have seen,
    xmlns:dc='http://purl.org/dc/elements/1.1/'
    Your namespace is dc I think, and your namespace URI is http://purl.org/dc/elements/1.1/
    Carl

  • A namespace question

    In an application file, I entered a namespace info as
    follows:
    xmlns:boxExample="com.myself.here.*"
    In the same folder, there are 4 classes, only one is listed
    in the hint that is popup when I enter "<boxExample:".
    Why? thanks in advance.

    Greg,
    Thanks for your help. Again, I finally found the reason: the
    class I was building extends UIComponent, the auto popup did not
    work until I import it.

  • Azure VM DNS Namespacing Question

    Hi all. In the process of getting our AWS machines up in Azure, and running into a simple but annoying issue wrt DNS names for our instances.
    Understanding that the DNS entry must be globally unique, we're trying to use a DNS name along the lines of:
    COMPANY-ENVIRONMENT-MACHINETYPE-NUMBER.cloudapp.net.
    A real world example would be:
    fiftymission-prod-app-1.cloudapp.net
    We are of cource running into the Azure DNS name limitation of 3-15 characters, meaning we're going to have to choose a more cryptic name like:
    fifty-p-a-1.cloudapp.net.
    Before we go ahead and provision everything, just looking to confirm that 15 chars is the limit and if anyone has any namespacing tricks to ensure consistency and uniqueness.
    Cheers

    Hi,
    Based on my experience, the DNS name of the cloud service must be globally unique. When you create a cloud service, the DNS name(except for the “.cloudapp.net”) contains only letters, numbers, hyphens and the first and last character in the field must be a
    letter or number. Trademarks, reserved words, and offensive words are not allowed.
    In addition, I tried on my side and the limitation is 63 characters.
    Did you want to create each VM in a cloud service? How many VMs did you want to create? Why don’t you create them in the same cloud service? The VMs in the same cloud service share the same public IP address and can be connect between each other via a private
    channel.
    Best regards,
    Susie
    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]

  • Debugging UIX 2.2.15 apps with JDev 10.1.3 [JSP TLD Namespace error]

    Hi,
    I am trying to get JDeveloper 10.1.3 (JTINTEG_MAIN_NT_050601.1217.428) to work with UIX 2.2.15 (*not* UIX 3.x/ADF).
    I am currently getting the following "not a registered TLD namespace" JSP errors during compiling.
    Project: C:\jdev1013\jdev\mywork\VTFLite322\VTFLite322\VTFLite322.jpr
    C:\jdev1013\jdev\mywork\VTFLite322\VTFLite322\public_html\cabo\bi\jsp\selectItemsShuttle.jsp
    Error(1): "http://xmlns.oracle.com/bibeans/jsp" is not a registered TLD namespace
    C:\jdev1013\jdev\mywork\VTFLite322\VTFLite322\public_html\cabo\bi\jsp\save.jsp
    Error(1): "http://xmlns.oracle.com/bibeans/jsp" is not a registered TLD namespace
    C:\jdev1013\jdev\mywork\VTFLite322\VTFLite322\public_html\cabo\bi\jsp\refineSelections.jsp
    Error(1): "http://xmlns.oracle.com/bibeans/jsp" is not a registered TLD namespace
    C:\jdev1013\jdev\mywork\VTFLite322\VTFLite322\public_html\cabo\bi\jsp\printerFriendly.jsp
    Error(1): "http://xmlns.oracle.com/bibeans/jsp" is not a registered TLD namespace
    C:\jdev1013\jdev\mywork\VTFLite322\VTFLite322\public_html\cabo\bi\jsp\printOptions.jsp
    Error(1): "http://xmlns.oracle.com/bibeans/jsp" is not a registered TLD namespace
    Question:
    Is it possible to configure JDeveloper 10.1.3 to work with older versions of UIX (e.g. 2.2.x)?
    Am I missing something obvious? I have tried various things on OTN that didn't work (i.e. searched JDeveloper forum for 'TLD namespace' and 'UIX 2.2').
    I am currently not having problems debugging Thick Java components, but would like to standardize development/debugging for both Thick (Java) and Thin (UIX 2.2.x) on one 10.1.3 JDeveloper platform.
    For reference, I am currently trying to migrate from the production JDeveloper 10.1.2.0.0 (Build 1811) release, where UIX 2.2.x applications work fine. Near term I do not have a need migrate previous applications to UIX 3.x/ADF.
    Thanks

    The PDK parts of JDeveloper are developed by the WebCenter/Portal team, so you might want to cross post here:
    http://forums.oracle.com/forums/forum.jspa?forumID=4
    WebCenter Portal

  • Change security question & answer programmatically

    Hi all
    I've had a look at the security api documentation on SAP help, but I can't find where to programmatically set the security question & answer for a user. I am developing a custom self-registration application, which needs to allow the user to define these two attributes - but I can't see where to do it.
    Please could someone help point me in the right direction here?
    Thanks
    Stuart

    I also faced the issue for almost every Web-Channel project I have and I currently have again the same issue.
    These are the main technical issues
    1) The Logon module is not provided with the source code, so knowone can use the NWDS to download the project from the NWDI and modify it as required. 
    2) All libraries used by the Logon module are protected, so you can't simply create a own project and just copy and paste the frontend code into your own project as you can't assign the required DCs directly to your own SC/DC.
    3) There is almost no extension mechanism to include some own logic as example to validate provided details such as the business partner.
    To change the look & feel of the component, you have to modify the logon module directly on the J2EE instance by replacing the relevant JSP files .... already quite strange. but it is getting less professional as this method is actually the recommended method if you follow the OSS notes!
    Ok, that's all worthless for me as I have to deliver real solutions to my customers and not a never ending workaround. I wrote my own loggon module.
    As I currently have also the security question requirement, I will solve it as follow
    - Define 2 additional customer attributes within the UME (<namespace>:question & <namespace>:answer)
    - On registration, collect the question & answer and fill both attributes into the User Object. The UMEFactory provides you an Object, where you can read & write the attributes
    - On passwort reset, just read out the attributes and compare it with the provided customer input.
    If you have more questions, please feel free to contact me
    Andreas Halbig
    SAP CRM, Web-Channel & Mobile Application Consultant
    andreas.halbig(a-t)ecomize.com

  • Cleint Proxy error

    After installing SP15 we are having problems with a Client Proxy.
    Scenario.
    request message
    <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
         <soap-env:Header>
              <n0:Trace xmlns:n0="http://www.sap.com/webas/630/soap/features/runtime/tracing/">
                   <n0:TraceLevel>Full</n0:TraceLevel>
                   <n0:TraceContext>
                        <TRC_PATTERN>WSTEST</TRC_PATTERN>
                        <TRC_KEY>7087C948F31B1C74E1000000C0A8E00C</TRC_KEY>
                        <TRC_SSID>DEV_10</TRC_SSID>
                        <TRC_USER>PSC</TRC_USER>
                        <TRC_TS>20080916081559</TRC_TS>
                        <TRC_COUNTER>98</TRC_COUNTER>
                        <TRC_EXTERN></TRC_EXTERN>
                   </n0:TraceContext>
              </n0:Trace>
         </soap-env:Header>
         <soap-env:Body>
              <n0:get-challenge xmlns:n0="http://xml.nccw.nl//xml/wms/" xmlns:prx="urn:sap.com:proxy:DEV:/1SAI/TAS662C7654907010C13388:700:2008/01/11">This is a string 3</n0:get-challenge>
         </soap-env:Body>
    </soap-env:Envelope>
    Response message
    <?xml version="1.0" encoding="utf-8"?>
    <SOAP-ENV:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
         <SOAP-ENV:Body>
              <nonce>5dee62bf0bf0c80011c6a3aeda95ad78</nonce>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    using the TEST Service Consumer i am getting an error
    Error durring Proxy processing (PART UNKNOWN (NULL))
    I think it's caused by the response not containing a namespace, question is how to solve.
    PS it worked prior to SP15 (ECC6.0)
    WSDL
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://xml.nccw.nl//xml/wms/" xmlns:auth="http://xml.nccw.nl//xml/soap-auth/" targetNamespace="http://xml.nccw.nl//xml/wms/">
         <types>
              <xs:schema targetNamespace="http://xml.nccw.nl//xml/wms/">
                   <!--               <xs:import namespace="http://xml.nccw.nl//xml/soap-auth/" schemaLocation="authenticatie_hw.xsd"/> -->
                   <xs:element name="get-challenge" type="xs:string"/>
                   <xs:element name="nonce" type="xs:string"/>
                   <xs:element name="auth" type="xs:string"/>
                   <xs:element name="ident" type="xs:string"/>
                   <xs:element name="leegmelding">
                        <xs:complexType>
                                  <xs:sequence>
                                       <xs:element name="woning">
                                            <xs:annotation>
                                                 <xs:documentation>Root van de woning</xs:documentation>
                                            </xs:annotation>
                                            <xs:complexType>
                                                 <xs:sequence>
                                                      <xs:element name="row">
                                                           <xs:complexType>
                                                                <xs:all>
                                                                     <xs:element name="adres">
                                                                          <xs:annotation>
                                                                               <xs:documentation>Adresgegevens</xs:documentation>
                                                                          </xs:annotation>
                                                                          <xs:complexType>
                                                                               <xs:all>
                                                                                    <xs:element name="straatnaam">
                                                                                         <xs:simpleType>
                                                                                              <xs:restriction base="xs:string">
                                                                                                   <xs:length value="43"/>
                                                                                              </xs:restriction>
                                                                                         </xs:simpleType>
                                                                                    </xs:element>
                                                                                    <xs:element name="huisnummer">
                                                                                         <xs:simpleType>
                                                                                              <xs:restriction base="xs:string">
                                                                                                   <xs:length value="12"/>
                                                                                              </xs:restriction>
                                                                                         </xs:simpleType>
                                                                                    </xs:element>
                                                                                    <xs:element name="toevoeging" minOccurs="0">
                                                                                         <xs:simpleType>
                                                                                              <xs:restriction base="xs:string">
                                                                                                   <xs:length value="10"/>
                                                                                              </xs:restriction>
                                                                                         </xs:simpleType>
                                                                                    </xs:element>
                                                                                    <xs:element name="postcode">
                                                                                         <xs:simpleType>
                                                                                              <xs:restriction base="xs:string">
                                                                                                   <xs:length value="6"/>
                                                                                                   <xs:pattern value="[1-9][0-9][A-Z]"/>
                                                                                              </xs:restriction>
                                                                                         </xs:simpleType>
                                                                                    </xs:element>
                                                                                    <xs:element name="woonplaats">
                                                                                         <xs:simpleType>
                                                                                              <xs:restriction base="xs:string">
                                                                                                   <xs:length value="43"/>
                                                                                              </xs:restriction>
                                                                                         </xs:simpleType>
                                                                                    </xs:element>
                                                                                    <xs:element name="land" minOccurs="0">
                                                                                         <xs:simpleType>
                                                                                              <xs:restriction base="xs:string">
                                                                                                   <xs:length value="43"/>
                                                                                              </xs:restriction>
                                                                                         </xs:simpleType>
                                                                                    </xs:element>
                                                                               </xs:all>
                                                                          </xs:complexType>
                                                                     </xs:element>
                                                                     <xs:element name="admin_unit">
                                                                          <xs:annotation>
                                                                               <xs:documentation>Admin Units</xs:documentation>
                                                                          </xs:annotation>
                                                                          <xs:complexType>
                                                                               <xs:sequence minOccurs="0" maxOccurs="unbounded">
                                                                                    <xs:annotation>
                                                                                         <xs:documentation>Indien Admin_unit_item met Type = 'VST' aanwezig, dan ook Admin_unit_item met type = 'CRP' verplicht</xs:documentation>
                                                                                    </xs:annotation>
                                                                                    <xs:element name="admin_unit_item">
                                                                                         <xs:annotation>
                                                                                              <xs:documentation>Admin Unit Item</xs:documentation>
                                                                                         </xs:annotation>
                                                                                         <xs:complexType>
                                                                                              <xs:all>
                                                                                                   <xs:element name="alt_ref" type="xs:string">
                                                                                                        <xs:annotation>
                                                                                                             <xs:documentation>Enumeratie nog niet bekend</xs:documentation>
                                                                                                        </xs:annotation>
                                                                                                   </xs:element>
                                                                                                   <xs:element name="type">
                                                                                                        <xs:simpleType>
                                                                                                             <xs:restriction base="xs:string">
                                                                                                                  <xs:enumeration value="CRP">
                                                                                                                       <xs:annotation>
                                                                                                                            <xs:documentation>corporatie</xs:documentation>
                                                                                                                       </xs:annotation>
                                                                                                                  </xs:enumeration>
                                                                                                                  <xs:enumeration value="VST">
                                                                                                                       <xs:annotation>
                                                                                                                            <xs:documentation>vestiging</xs:documentation>
                                                                                                                       </xs:annotation>
                                                                                                                  </xs:enumeration>
                                                                                                                  <xs:enumeration value="SWV">
                                                                                                                       <xs:annotation>
                                                                                                                            <xs:documentation>samenwerkingsverband</xs:documentation>
                                                                                                                       </xs:annotation>
                                                                                                                  </xs:enumeration>
                                                                                                             </xs:restriction>
                                                                                                        </xs:simpleType>
                                                                                                   </xs:element>
                                                                                              </xs:all>
                                                                                         </xs:complexType>
                                                                                    </xs:element>
                                                                               </xs:sequence>
                                                                          </xs:complexType>
                                                                     </xs:element>
                                                                     <xs:element name="status">
                                                                          <xs:annotation>
                                                                               <xs:documentation>Statusinformatie</xs:documentation>
                                                                          </xs:annotation>
                                                                          <xs:complexType>
                                                                               <xs:sequence>
                                                                                    <xs:element name="ingangsdatum">
                                                                                         <xs:simpleType>
                                                                                              <xs:restriction base="xs:string">
                                                                                                 <xs:length value="8"/>
                                                                                            </xs:restriction>
                                                                                         </xs:simpleType>
                                                                                    </xs:element>
                                                                                    <xs:element name="reden_niet_bschikbr">
                                                                                         <xs:annotation>
                                                                                              <xs:documentation>Niet beschikbaar</xs:documentation>
                                                                                         </xs:annotation>
                                                                                         <xs:simpleType>
                                                                                              <xs:restriction base="xs:string">
                                                                                                   <xs:enumeration value="REN">
                                                                                                        <xs:annotation>
                                                                                                             <xs:documentation>Renovatie</xs:documentation>
                                                                                                        </xs:annotation>
                                                                                                   </xs:enumeration>
                                                                                                   <xs:enumeration value="SLP">
                                                                                                        <xs:annotation>
                                                                                                             <xs:documentation>Sloop</xs:documentation>
                                                                                                        </xs:annotation>
                                                                                                   </xs:enumeration>
                                                                                                   <xs:enumeration value="VERH">
                                                                                                        <xs:annotation>
                                                                                                             <xs:documentation>Verhuurd</xs:documentation>
                                                                                                        </xs:annotation>
                                                                                                   </xs:enumeration>
                                                                                                   <xs:enumeration value="VERK">
                                                                                                        <xs:annotation>
                                                                                                             <xs:documentation>Verkocht</xs:documentation>
                                                                                                        </xs:annotation>
                                                                                                   </xs:enumeration>
                                                                                                   <xs:enumeration value="WONR">
                                                                                                        <xs:annotation>
                                                                                                             <xs:documentation>Woningruil</xs:documentation>
                                                                                                        </xs:annotation>
                                                                                                   </xs:enumeration>
                                                                                                   <xs:enumeration value="SAMV">
                                                                                                        <xs:annotation>
                                                                                                             <xs:documentation>Samenvoeging</xs:documentation>
                                                                                                        </xs:annotation>
                                                                                                   </xs:enumeration>
                                                                                                   <xs:enumeration value="PROF">
                                                                                                        <xs:annotation>
                                                                                                             <xs:documentation>Pro forma</xs:documentation>
                                                                                                        </xs:annotation>
                                                                                                   </xs:enumeration>
                                                                                              </xs:restriction>
                                                                                         </xs:simpleType>
                                                                                    </xs:element>
                                                                                    <xs:sequence>
                                                                                         <xs:annotation>
                                                                                              <xs:documentation>Wel beschikbaar</xs:documentation>
                                                                                         </xs:annotation>
                                                                                         <xs:element name="reden_bschikbr">
                                                                                              <xs:simpleType>
                                                                                                   <xs:restriction base="xs:string">
                                                                                                        <xs:enumeration value="MUT">
                                                                                                             <xs:annotation>
                                                                                                                  <xs:documentation>Mutatie</xs:documentation>
                                                                                                             </xs:annotation>
                                                                                                        </xs:enumeration>
                                                                                                        <xs:enumeration value="NWB">
                                                                                                             <xs:annotation>
                                                                                                                  <xs:documentation>Nieuwbouw</xs:documentation>
                                                                                                             </xs:annotation>
                                                                                                        </xs:enumeration>
                                                                                                   </xs:restriction>
                                                                                              </xs:simpleType>
                                                                                         </xs:element>
                                                                                         <xs:element name="soort_bschikbrheid">
                                                                                              <xs:simpleType>
                                                                                                   <xs:restriction base="xs:string">
                                                                                                        <xs:enumeration value="HUUR">
                                                                                                             <xs:annotation>
                                                                                                                  <xs:documentation>Te huur (regulier)</xs:documentation>
                                                                                                             </xs:annotation>
                                                                                                        </xs:enumeration>
                                                                                                        <xs:enumeration value="HRTY">
                                                                                                             <xs:annotation>
                                                                                                                  <xs:documentation>Te huur (tijdelijk)</xs:documentation>
                                                                                                             </xs:annotation>
                                                                                                        </xs:enumeration>
                                                                                                        <xs:enumeration value="KOOP">
                                                                                                             <xs:annotation>
                                                                                                                  <xs:documentation>Te koop</xs:documentation>
                                                                                                             </xs:annotation>
                                                                                                        </xs:enumeration>
                                                                                                        <xs:enumeration value="WOON">
                                                                                                             <xs:annotation>
                                                                                                                  <xs:documentation>Te woon</xs:documentation>
                                                                                                             </xs:annotation>
                                                                                                        </xs:enumeration>
                                                                                                   </xs:restriction>
                                                                                              </xs:simpleType>
                                                                                         </xs:element>
                                                                                    </xs:sequence>
                                                                                    <xs:element name="einddatum">
                                                                                         <xs:simpleType>
                                                                                              <xs:restriction base="xs:string">
                                                                                                 <xs:length value="8"/>
                                                                                            </xs:restriction>
                                                                                         </xs:simpleType>
                                                                                    </xs:element>
                                                                               </xs:sequence>
                                                                          </xs:complexType>
                                                                     </xs:element>
                                                                     <xs:element name="prijs">
                                                                          <xs:annotation>
                                                                               <xs:documentation>Prijzen</xs:documentation>
                                                                          </xs:annotation>
                                                                          <xs:complexType>
                                                                               <xs:sequence minOccurs="0" maxOccurs="unbounded">
                                                                                    <xs:element name="prijs_item">
                                                                                         <xs:annotation>
                                                                                              <xs:documentation>Prijsinformatie</xs:documentation>
                                                                                         </xs:annotation>
                                                                                         <xs:complexType>
                                                                                              <xs:all>
                                                                                                   <xs:element name="type_vgeprijs">
                                                                                                        <xs:simpleType>
                                                                                                             <xs:restriction base="xs:string">
                                                                                                                  <xs:length value="10"/>
                                                                                                                  <xs:enumeration value="STKK">
                                                                                                                       <xs:annotation>
                                                                                                                            <xs:documentation>Stookkosten</xs:documentation>
                                                                                                                       </xs:annotation>
                                                                                                                  </xs:enumeration>
                                                                                                                  <xs:enumeration value="BRUT">
                                                                                                                       <xs:annotation>
                                                                                                                            <xs:documentation>Bruto maandhuur</xs:documentation>
                                                                                                                       </xs:annotation>
                                                                                                                  </xs:enumeration>
                                                                                                                  <xs:enumeration value="KOOP">
                                                                                                                       <xs:annotation>
                                                                                                                            <xs:documentation>Koopprijs</xs:documentation>
                                                                                                                       </xs:annotation>
                                                                                                                  </xs:enumeration>
                                                                                                                  <xs:enumeration value="NETT">
                                                                                                                       <xs:annotation>
                                                                                                                            <xs:documentation>Netto maandhuur</xs:documentation>
                                                                                                                       </xs:annotation>
                                                                                                                  </xs:enumeration>
                                                                                                                  <xs:enumeration value="SERV">
                                                                                                                       <xs:annotation>
                                                                                                                            <xs:documentation>Servicekosten</xs:documentation>
                                                                                                                       </xs:annotation>
                                                                                                                  </xs:enumeration>
                                                                                                                  <xs:enumeration value="SUBS">
                                                                                                                       <xs:annotation>
                                                                                                                            <xs:documentation>Subsidiabele maandhuur</xs:documentation>
                                                                          

    Hello Schults,
    I am facing same problem.
    I created a ABAP proxy from a WSDL.
    When a method is called for this proxy response is blank.
    response message contents are null.
    I am also getting the error message
    GENERAL_ERROR Error duing proxy processing (PART
    UNKNOWN (NULL) )
    Any thoughts how I can resolve this?
    Thanks  Schults.
    Bhushan

Maybe you are looking for

  • Null values passed into the servlet

    Hi all, I keep getting null values for all the params that I pass into the servlet i.e. sqltype, producttype, process, instance etc....I have attempted to print some of them out on the screen but I keep getting the 'NullPointerException' error messag

  • Reports for display secondary cost element

    Dear SAP consultant After run settlement cycles we going to display reports for secondary cost elements but it is return zero balance, i know that when i am trying to drill down it will get the whole data. but it is not practical because the huge amo

  • How can I uninstall ClicktoFlash from Safari under OS X Lion server?

    ClicktoFlash is installed on my Lion server (mac mini) and it's driving me crazy. I can't figure out how to uninstall it since it doesn't even list under the Help>Installed Plug-ins and I can't find a ~/Library folder (secondary question: does Lion s

  • Automatic creation of deliveries in back ground

    Hi All,           I want to create a automatic delivery via background scheduling. I have created the variant for the program RVV50R10C. I have created the role. can u please tell me how to assign the role in the program? The role field in user role

  • Problem with 7.0.4 update on iPad Mini Retina

    Hello, I just got my iPad Mini Retina today and after setting up the iPad I get a message that a new OS update 7.0.4 is available for the iPad so I accept and go with the update. But the Apple device is rebooting and is not finishing the update. All