Webservice: serialize collections (language builtins)

I use the weblogic ant tasks servicegen and clientgen to generate webservices. I'd like to use about the same valueobject for the client as for the server. Yet a value of type "List" in the server valueobject is generated as type Object[] in the client valueobject.
In the WSDL everything still looks fine:
<xsd:element xmlns:tp="java:language_builtins.util" type="tp:ArrayList" name="addresses" minOccurs="1" nillable="true" maxOccurs="1"></xsd:element>
How can I tell the clientgen task to generate a field "addresses" of Type List (or ArrayList) also in the client valueobject? Instead clientgen generates a field "addresses" of type Object[].

Option useServerTypes="True" in clientgen helps ..
see http://forums.bea.com/bea/message.jspa?messageID=600008880

Similar Messages

  • How to serialize collections (language builtins) in ValueObjects?

    I use the weblogic ant tasks servicegen and clientgen to generate webservices. I'd like to use the same ValueObject for the client as for the server. The ValueObject exchanged over the webservice contains a field "addresses" of type ArrayList. clientgen generates a field "addresses" of type Object[] in the client ValueObject. Does anybody know how to tell the clientgen task to generate a field "addresses" of Type List (or ArrayList) instead of Object[] in the client valueobject?
    Here's the ValueObject on the server (i'd expect the same ValueObject on the client side):
    public class Employee implements Serializable
    private ArrayList addresses;
    public Employee() { }
    public ArrayList getAddresses() {
    return addresses
    public void setAddresses(ArrayList aobj[]) {
    addresses = aobj;
    In the WSDL everything still looks fine (field "addresses" has type ArrayList):
    <xsd:element xmlns:tp="java:language_builtins.util" type="tp:ArrayList" name="addresses" minOccurs="1" nillable="true" maxOccurs="1"></xsd:element>
    The generated client ValueObject:
    public class Employee implements Serializable
    private Object addresses[];
    public Employee() { }
    public Object[] getAddresses() {
    return addresses
    public void setAddresses(Object aobj[]) {
    addresses = aobj;
    Here the standard clientgen task I use (as a additional informaiton):
    <clientgen ear="${build}/${ear_file}" warName="${war_file}" packageName="${package_name}" clientJar="${build}/${client_jar_file}" />

    useServerTypes="true" helps indeed! Now the generated client ValueObject contains a field "addresses" of Type ArrayList. Thanks!
    <clientgen
    ear="${build}/${ear_file}"
    warName="${war_file}"
    packageName="${package_name}"
    clientJar="${build}/${client_jar_file}"
    useServerTypes="true" />

  • Jdeveloper 11.1.1.0.0 - Error when generating webservice from Collection or

    Hello.
    I get the error when I like to publish a method which return a Collection..
    for example I have a Class:
    package in2;
    import java.sql.Connection;
    import java.util.ArrayList;
    import java.util.List;
    import java.util.*;
    import javax.jws.WebMethod;
    import javax.jws.WebService;
    public class servis {
        public servis() {
        public String hello() {
            return "PETER";
        public Collection vrniPodatke() {
            Collection l = new ArrayList();
            l.add ( new OptionList("PTER","VALENCIC"));
            return l;
        public int sestej (int a , int b) {
            return a+b;
    ==========
    package in2;
        public class OptionList {
            String a;
            String b;
            public OptionList(String a, String b) {
                this.a = a;
                this.b = b;
            public void setA(String newa) {
                this.a = newa;
            public String getA() {
                return a;
            public void setB(String newb) {
                this.b = newb;
            public String getB() {
                return b;
        }The error I get is:
    java.lang.RuntimeException: Cannot find namespace for: ns1
         at oracle.j2ee.ws.wsdl.extensions.oracle.schema.BaseSchemaElement.getQNameFromValue(BaseSchemaElement.java:185)
         at oracle.j2ee.ws.wsdl.extensions.oracle.schema.BaseSchemaElement.getAttributeValueAsQNameOrNull(BaseSchemaElement.java:173)
         at oracle.j2ee.ws.wsdl.extensions.oracle.schema.ElementSchemaElement.getTypeAsQName(ElementSchemaElement.java:63)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.SchemaValidator.validate(SchemaValidator.java:145)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.SchemaValidator.validateSequence(SchemaValidator.java:414)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.SchemaValidator.validateComplexType(SchemaValidator.java:224)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.SchemaValidator.validate(SchemaValidator.java:157)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.WSDLValidator.validateElement(WSDLValidator.java:709)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.WSDLValidator.validateParts(WSDLValidator.java:667)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.WSDLValidator.validateMessage(WSDLValidator.java:644)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.WSDLValidator.validateOutput(WSDLValidator.java:604)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.WSDLValidator.validateOperations(WSDLValidator.java:596)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.WSDLValidator.validatePortType(WSDLValidator.java:585)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.WSDLValidator.validateDefinition(WSDLValidator.java:97)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.WSDLValidator.validate(WSDLValidator.java:68)
         at oracle.j2ee.ws.common.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:247)
         at oracle.j2ee.ws.common.processor.config.ModelInfo.buildModel(ModelInfo.java:171)
         at oracle.j2ee.ws.common.processor.Processor.runModeler(Processor.java:73)
         at oracle.j2ee.ws.tools.wsa.AssemblerTool.run(AssemblerTool.java:126)
         at oracle.j2ee.ws.tools.wsa.WsdlToJavaTool.createModel(WsdlToJavaTool.java:471)
         at oracle.j2ee.ws.tools.wsa.Util.createDeploymentDescriptors(Util.java:913)
         at oracle.jdeveloper.webservices.model.generator.GenerateDescriptors.action(GenerateDescriptors.java:146)
         at oracle.jdeveloper.webservices.model.java.generator.JavaEjbGenerateDescriptors.action(JavaEjbGenerateDescriptors.java:78)
         at oracle.jdeveloper.webservices.model.generator.GeneratorAction.run(GeneratorAction.java:151)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:153)
         at java.awt.Dialog$1.run(Dialog.java:525)
         at java.awt.Dialog$2.run(Dialog.java:553)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.awt.Dialog.show(Dialog.java:551)
         at java.awt.Component.show(Component.java:1300)
         at java.awt.Component.setVisible(Component.java:1253)
         at oracle.bali.ewt.dialog.JEWTDialog.runDialog(Unknown Source)
         at oracle.bali.ewt.dialog.JEWTDialog.runDialog(Unknown Source)
         at oracle.ide.dialogs.ProgressBar.start(ProgressBar.java:358)
         at oracle.ide.dialogs.ProgressBar.start(ProgressBar.java:222)
         at oracle.ide.dialogs.ProgressBar.start(ProgressBar.java:194)
         at oracle.jdeveloper.webservices.model.Model.saveEditSync(Model.java:226)
         at oracle.jdevimpl.webservices.wizard.jaxrpc.WebServicesEditor.showDialog(WebServicesEditor.java:296)
         at oracle.jdevimpl.webservices.WebServicesAddin.findAndInvokeWizard(WebServicesAddin.java:1408)
         at oracle.jdevimpl.webservices.WebServicesAddin.handleEvent(WebServicesAddin.java:837)
         at oracle.ide.controller.IdeAction.performAction(IdeAction.java:506)
         at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:779)
         at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:479)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
         at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
         at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
         at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
         at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
         at java.awt.Component.processMouseEvent(Component.java:5501)
         at javax.swing.JComponent.processMouseEvent(JComponent.java:3135)
         at java.awt.Component.processEvent(Component.java:5266)
         at java.awt.Container.processEvent(Container.java:1966)
         at java.awt.Component.dispatchEventImpl(Component.java:3968)
         at java.awt.Container.dispatchEventImpl(Container.java:2024)
         at java.awt.Component.dispatchEvent(Component.java:3803)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
         at java.awt.Container.dispatchEventImpl(Container.java:2010)
         at java.awt.Window.dispatchEventImpl(Window.java:1778)
         at java.awt.Component.dispatchEvent(Component.java:3803)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
    ======================
    What I'am doing wrong?

    I don't know what is happening with Jdeveloper ?!?!
    I have tryed the same example at home with Jdeveloper 11.1.1.0.0 Build JDEVADF_MAIN.DROP5_GENERIC_071218.2321.4796
    All works fine.....
    What you think could be wrong (in my first post)? Why I have received the error? and why the same project works on other computer?
    can someone reply to my post?

  • WebService serialization fails

    Hi,
    I'm not sure if this is a bug or a compatibility issue...
    When I compile the same code in Flex 3 to call a web service
    as I used in Flex 2, the web message (viewed in Fiddler) includes
    namespace definitions on each node in the header which are not
    there in Flex 2. (Example below)
    This means that when the message hits the server it won't
    deserialize.
    Using Fiddler I can remove the namespaces and resubmit the
    request and it works.
    Is there some new functionality in the Flex 3 SDK to specify
    whether the namespaces should appear or is it a bug?
    eg:
    Flex 2:
    <?xml version="1.0" encoding="utf-8"?>
    <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><AuthHeader><BrowserType>test< /BrowserType><Password>test</Password><Logon>test</Logon><MovieVersion>test</MovieVersion> <ScreenSize>test</ScreenSize></AuthHeader></SOAP-ENV:Header><SOAP-ENV:Body><Login
    xmlns="
    http://eCRF.ServiceContracts"
    /></SOAP-ENV:Body></SOAP-ENV:Envelope>
    Flex 3:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="
    http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:s="
    http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="
    http://www.w3.org/2001/XMLSchema-instance">
    <SOAP-ENV:Header>
    <AuthHeader>
    <tns:Logon xmlns:tns="
    http://eCRF.ServiceContracts">test</tns:Logon>
    <tns:Password xmlns:tns="
    http://eCRF.ServiceContracts">test</tns:Password>
    <tns:ScreenSize xmlns:tns="
    http://eCRF.ServiceContracts">test</tns:ScreenSize>
    <tns:BrowserType xmlns:tns="
    http://eCRF.ServiceContracts">test</tns:BrowserType>
    <tns:MovieVersion xmlns:tns="
    http://eCRF.ServiceContracts">test</tns:MovieVersion>
    </AuthHeader>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
    <tns:Login xmlns:tns="
    http://eCRF.ServiceContracts"/>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Thanks
    Dom

    Further , These are the complete requirements for complex type object---->
    J2SE SDK Classes
    JAX-RPC supports the following J2SE SDK classes:
    java.lang.Boolean
    java.lang.Byte
    java.lang.Double
    java.lang.Float
    java.lang.Integer
    java.lang.Long
    java.lang.Short
    java.lang.String
    java.math.BigDecimal
    java.math.BigInteger
    java.net.URI
    java.util.Calendar
    java.util.Date
    Primitives
    JAX-RPC supports the following primitive types of the Java programming language:
    boolean
    byte
    double
    float
    int
    long
    short
    Arrays
    JAX-RPC also supports arrays that have members of supported JAX-RPC types. Examples of supported arrays are int[] and String[]. Multidimensional arrays, such as BigDecimal[][], are also supported.
    <b>Value Types
    A value type is a class whose state can be passed between a client and a remote service as a method parameter or return value. For example, in an application for a university library, a client might call a remote procedure with a value type parameter named Book, a class that contains the fields Title, Author, and Publisher.
    To be supported by JAX-RPC, a value type must conform to the following rules:
    It must have a public default constructor.
    It must not implement (either directly or indirectly) the java.rmi.Remote interface.
    Its fields must be supported JAX-RPC types.
    The value type can contain public, private, or protected fields. The field of a value type must meet these requirements:
    A public field cannot be final or transient.
    A nonpublic field must have corresponding getter and setter methods</b>
    Hope this helps.
    Regards,
    Piyush

  • Webservice in NWDS having JCO code

    Hi All,
    I have a requirement which is to create a JAVA web service in NWDS which can service a .NET internet Application take some data from .NET and
    put it into the SAP by calling a RFC Module...
    I have written a class which has two methods
    it simply connects to SAP & processes the RFC Module...
    This class works fine if i run it as a
    standalone java application with a main
    method.. <b>but it fails</b> when i deploy it as a web service and try to run it through a Standalone
    Client ... it is able to create the
    WSDL and the methods are also visible but it
    fails from the code where JCO logic starts...
    I am getting the error message as
    <b>Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.
    wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    javax.xml.rpc.soap.SOAPFaultException: com/sap/mw/jco/JCO$Exception
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:651)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:742)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1240)
         at proxy.ConfigBindingStub.setCustomerMasterRFC(ConfigBindingStub.java:81)
         at proxy.ConfigBindingStub.setCustomerMasterRFC(ConfigBindingStub.java:112)
         at proxy.DealerClient.main(DealerClient.java:25)</b>
    I am using sapjco.jar in the project properties dialog box but it is not there when the EAR is generated & deployed..
    Can this be a problem ??? If yes where should i put
    this sapjco.jar
    Please help me out as i am really facing a hard time finding out the reason for this

    Hi Maksim,
    Thankyou so much maksim for the jar file path
    you had given , the first error is gone
    when i put the jar file in project
    properties.
    But i am still getting some errors
    because of the JCO library methods that
    i am using ... all other simple web services
    work fine in my system but i am getting
    following errors
    <b>javax.xml.rpc.soap.SOAPFaultException: com/sap/mw/jco/JCO
         at com.sap.engine.services.webservices.jaxrpc.
    wsdl2java.soapbinding.MimeHttpBinding.
    buildFaultException(MimeHttpBinding.java:651)
         at com.sap.engine.services.webservices.jaxrpc.
    wsdl2java.soapbinding.MimeHttpBinding.
    processDocumentFault(MimeHttpBinding.java:742)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1240)
         at proxy.ConfigBindingStub.setEclipseData(ConfigBindingStub.java:80)
         at proxy.ConfigBindingStub.setEclipseData(ConfigBindingStub.java:96)
         at com.carrier.isa.Client.main(Client.java:29)</b>
    when i put a simple code like
                    <b>JCO.Client aConnection=null;
              IRepository aRepository=null;
              try {
                   System.out.println("Creating a client");
                   aConnection=JCO.createClient(
                                                 SAP_CLIENT,
                                                 USER_ID,
                                                 PASSWORD,
                                                 LANGUAGE,
                                                 HOST_NAME,
                                                 SYSTEM_NUMBER);</b>                                             System.out.println(aConnection.toString());
              ArrayList array=new ArrayList();
              array.add("Tarun");
              array.add("Abhay");
              array.add("Sujit");
              array.add("Sandy");
              array.add("Sachin");
              returnStr=array.get(2).toString()"--"test;
              catch(Exception e)
                   e.printStackTrace();
              return returnStr;
    the code above is just a snippet of the whole .
    I have sapjco.jar in project properties in NWDS or eclipse but this jar is missing when
    i build an EAR in the Web services perspective..
    Can the missing of this jar in the
    project EAR be the cause of problem ...
    if yes let me know where should i add it ...
    Also, I created a simple java project so i
    am not having any WEB-INF folder ...
    do i need to create a web project instead ..
    Please help me as you did earlier ..
    I would be highly obliged ....

  • Problem while Consuming Java Webservice from WCF client

    Hi,
    I am trying to Consume Java Webservice from WCF client.The webservice main functionality is digital data management.The client can Query Digital data and upload digital data by calling webservice methods.Problem is when i am trying to call webmethod from WCF client its giving "Unrecognised message versions".I have no idea about how the message objects are processed at serverside.but at server side they have used JAXP for XML document parsing.
    The response content type is Multipart/related and applicatio/XOP+XML.
    Can u plz help me how to handle this situation.I have minimum knowledge in Java WS architecture.Basically i am .Net programmer.
    Can U please guide me in a proper way to resolve the problem.

    Hi Abinash,
    I have the same problem. Have you solve that problem?
    I am using a java program to call a webservice too. And I have generated the client proxy definition for Stand alone proxy using NWDS. When I call the method of the webservice I am getting the correct result but along with the result I am getting one error and one warning message in the output.
    The java code to call the webservice is as follows.
    MIDadosPessoaisSyncService service = new MIDadosPessoaisSyncServiceImpl();
    MIDadosPessoaisSync port = service.getLogicalPort("MIDadosPessoaisSyncPort");
    port._setProperty("javax.xml.rpc.security.auth.username","xpto");
    port._setProperty("javax.xml.rpc.security.auth.password","xpto");
    String out = port.MIDadosPessoaisSync("xpto", "xpto");
    System.out.println(out);
    The result I am getting is :
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    <b>The result of the WS is correct!!!</b>
    The Java project does not have any warning. But the stand alone proxy project has following warnings associated with it.
    This method has a constructor name     MIDadosPessoaisSync.java     
    The import javax.xml.rpc.holders is never used     MIDadosPessoaisSyncBindingStub.java     
    The import javax.xml.rpc.encoding is never used     MIDadosPessoaisSyncBindingStub.java     
    The constructor BaseRuntimeException(ResourceAccessor, String, Throwable) is deprecated     MIDadosPessoaisSyncBindingStub.java
    It is very similar with your problem, could you help me?
    Thanks
    Gustavo Freitas

  • Problem while calling a Webservice from a Stand alone java program

    Hello Everyone,
    I am using a java program to call a webservice as follows. For this I have generated the client proxy definition for Stand alone proxy using NWDS.
    Now when I call the method of the webservice I am getting the correct result but along with the result I am getting one error and one warning message in the output.
    The java code to call the webservice is as follows.
    public class ZMATRDESCProxyClient {
         public static void main(String[] args) throws Exception {
              Z_MATRDESC_WSDService ws = new Z_MATRDESC_WSDServiceImpl();
              Z_MATRDESC_WSD port = (Z_MATRDESC_WSD)ws.getLogicalPort("Z_MATRDESC_WSDSoapBinding",Z_MATRDESC_WSD.class);
              String res = port.zXiTestGetMatrDesc("ABCD134");
              System.out.print(res);
    The result I am getting is :
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    <b>Material Not Found</b> -
    > This is the output of webservice method and it is right.
    Can any one please let me know why I am getting the warning and error message and how can I fix this.
    Thanks
    Abinash

    Hi Abinash,
    I have the same problem. Have you solve that problem?
    I am using a java program to call a webservice too. And I have generated the client proxy definition for Stand alone proxy using NWDS. When I call the method of the webservice I am getting the correct result but along with the result I am getting one error and one warning message in the output.
    The java code to call the webservice is as follows.
    MIDadosPessoaisSyncService service = new MIDadosPessoaisSyncServiceImpl();
    MIDadosPessoaisSync port = service.getLogicalPort("MIDadosPessoaisSyncPort");
    port._setProperty("javax.xml.rpc.security.auth.username","xpto");
    port._setProperty("javax.xml.rpc.security.auth.password","xpto");
    String out = port.MIDadosPessoaisSync("xpto", "xpto");
    System.out.println(out);
    The result I am getting is :
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    <b>The result of the WS is correct!!!</b>
    The Java project does not have any warning. But the stand alone proxy project has following warnings associated with it.
    This method has a constructor name     MIDadosPessoaisSync.java     
    The import javax.xml.rpc.holders is never used     MIDadosPessoaisSyncBindingStub.java     
    The import javax.xml.rpc.encoding is never used     MIDadosPessoaisSyncBindingStub.java     
    The constructor BaseRuntimeException(ResourceAccessor, String, Throwable) is deprecated     MIDadosPessoaisSyncBindingStub.java
    It is very similar with your problem, could you help me?
    Thanks
    Gustavo Freitas

  • SharePoint 2013 Problem with automatic detection of Site language - default language

    Hi all,
    we have a SiteCollection that was created with 'english' as
    default language.
    On our SharePoint 2013 environment we have installed the 'german' and 'french' language pack. Both languages are activated as alternative languages on that SiteCollection.
    But the automatic language detection is not working properly for us.
    Problem description:
    User Browser language = German --> Site language = German
    If you now change the Browser language to 'Italian' then we would expect that the site will be displayed in 'English' because the 'Italian' language pack is not installed and the SiteCollection default language was set to 'English'...
    But the Site will be not displayed in 'English' it will keep the last language in this case 'German'...
    Another example: If you change the browser language to 'French' the whole Site is displayed in French. If you try to switch now to 'Italian' then the Site will be still displayed in 'French' instead of 'English'...
    Any ideas what could cause this problem?
    Regards, Simon

    Hi Simon,
    Here is the order of the language preference showing to users with different settings
    For your issue it may be due to the IE data cache, please clear all the IE data cache, then reopen the IE browser see if it displays the English language as expected.
    http://technet.microsoft.com/en-us/library/ff805087.aspx
    If the User Profile service application is started on the SharePoint Server 2013 farm, the language preferences stored in the user profile are used. For information about how to add a list of languages to user profile settings in SharePoint Server 2013,
    see Add, edit, or delete custom properties in SharePoint Server 2013 user profiles. For information about how to add a list of languages to user profile settings in SharePoint Online Administration Center, see Add and edit user profile properties on Office.com.
    If no language preference is defined in the user profile, or if the server uses SharePoint Foundation 2013, the language preferences stored in the user's language settings for the site collection are used.
    If no language preference is defined in the user's site collection language settings, the language preferences stored in the user's web browser are used.
    If no language preference is defined in the user's web browser, the default site language is used.
    Thanks,
    Daniel Yang
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] 
    Daniel Yang
    TechNet Community Support

  • Webservice: client proxy chokes on (any) reply

    I have made sure that:
    - there is a complete reproduction scenario
    - the webservices are online!
    - the wsdls and eclipse project with proxies and test program calling the proxies are attached
    I can't find any references (SDN/google, posted on SDN) which help me with the errors my proxies (generated in Netweaver Developer Studio) keep getting when reading/processing the response message. Therefore I would be grateful for any pointer which helps me solve/workaround this problem.
    PROBLEM:
    Netweaver Developer Studio generated proxies choke when reading/processing our reply:
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.getResponseDocument(MimeHttpBinding.java:1077)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)
         at com.quintiq.WSNullPointerExceptionProblem.Foo.FooBindingStub.foo(FooBindingStub.java:87)
    FACTS & MY ANALYSIS
    - We are using our own SOAP implementation, just so you know
    - I tried all kinds of webservice signatures (void foo(void), string foo(string) etc...) All give the same problem
    - Error messages work fine! (Our errormessage is read and perfectly converted into an exception)
    - I ran several checkers/validators:
      - EP Web Services Checker has no problem
      - WS-I check reveals that the only problem is that we don't use UTF-8, but iso-8859-1 (I tried using UTF-8 which should be ok, same problem)
      - Mindreef SoapScope gives no problem
      - Several web based WSDL validators (also invoking the service) have no problem
    - I use stateless communication (checkbox in LogicalPort configuration)
    - I am using the sneak preview available for evaluation on SDN: " Sneak Preview SAP NetWeaver 04 - Full Java Edition with SAP NetWeaver Portal,  NW04 SP16 11 Apr 2006"
    - I get a warning (using guidgenerator.jar removes the warning, but does not help with the real problem)
      Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
      Error Message is :com/sap/guid/GUIDGeneratorFactory
    REPRODUCTION
    Using the workspace attached:
    To call webservice Foo: run with the main supplied in class com.quintiq.WSNullPointerExceptionProblem.Foo.Test_Foo
    To call webservice PCT_DUEDATE: run with the main supplied in class com.quintiq.WSNullPointerExceptionProblem.Test_PCT_DUEDATE
    To call both: run with the main supplied in class Main in the default package
    It takes about 5/10 minutes to generate proxies yourself and call the webservice. (Don't forget to check the "stateless communication" checkbox in the LogicalPort configuration!)
    The error is always the same:
    java.rmi.RemoteException: Service call exception; nested exception is:
         java.lang.NullPointerException
         at com.quintiq.WSNullPointerExceptionProblem.Foo.FooBindingStub.foo(FooBindingStub.java:99)
         at com.quintiq.WSNullPointerExceptionProblem.Foo.Test_Foo.main(Test_Foo.java:26)
         at Main.main(Main.java:20)
    Caused by: java.lang.NullPointerException
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.getResponseDocument(MimeHttpBinding.java:1077)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)
         at com.quintiq.WSNullPointerExceptionProblem.Foo.FooBindingStub.foo(FooBindingStub.java:87)
         ... 2 more
    Kind regards,
    Patrick

    Found the problem. We returned HTTP code 202 (Accepted) instead of 200 (OK) when the response was in the body.
    Patrick

  • Handling multi byte languages in Web Service

    Hi,
    I am calling a web service and its working fine with English language i.e web service is returning correct parameters with English.
    But it's returning me Junk characters when i call web service with multi byte languages like Japanese, Russian etc.,
    Generally while configuring Web Service or calling a web service using proxy - it asks for a user id/ Pwd but not a logon language (unlike while you login SAP it asks for Logon Language) so i am thinking since there is no option to enter log on language, its taking a default language i.e English so when i am passing japanese its returning me Junk Values.
    Can any one please help me with this? How to handle multi byte webservice call? I am using ECC 5.0.
    Thanks & Regards,
    Pavan.

    I appreciate your thought but our webservice must be able to handle multiple languages not only Japanese. Users might call webservice in any language they prefer. If i change it my default to Japanese, i will have problem when users call webservice in Russian.

  • Extraction program for EH&S (EH&S to XI scenario)

    Dear Experts,
    I am from the XI background and am new to EH&S. I would like to know whether there exists an extraction program to extract substance data from EH&S(ECC) and send it to XI. If yes then what is it? The EH&S team here doesn't know of any kind. They have only used Change pointers to extract data from one client to the another.
    Please help.
    Thanks,
    Merrilly

    Hello,
    How to set up ALE for substances is described in the IMG / Customizing for EH&S.
    For EH&S 2.7B on R/3 4.6C this is located under:
    Environment, Health & Safety -> Product Safety -> Interfaces -> EH&S Application Link Enabling (ALE) -> ALE for Specification Management.
    All necessary information should be found in 'Set up Distribution of Specification Data':
                                                                                    Set Up Distribution of Specification Data                                                                               
    In this IMG activity you set up the distribution of data on                   
         specifications (see also Information About the Concept in EH&S                
         Application Link Enabling (ALE)).                                                                               
    Requirements                                                                               
    1.  Setting the Active Code Page                                              
             To transfer the data using ALE, you must ensure that the active code      
             pages are the same in the receiving system and sending system as          
             follows:                                                                               
    -   You must select a code page for transfer (for example, SAP(ISO)       
                 code page 1100) that you set up on all SAP Systems that belong        
                 to your ALE distribution model.                                                                               
    -   In Customizing for Product Safety in the IMG activity Specify         
                 Environment Parameters using the environment parameter                
                 ALE_TRANSFER_LANGUAGE, you must specify a language of the             
                 previously selected code page as the transfer language in the         
                 sending system. This language controls which code page is active      
                 in the sending system during data transfer.                                                                               
    -   The RFC destinations of the target systems must be defined with       
                 the logon language that corresponds to the specified code page.                                                                               
    -   If data is to be transferred to different SAP(ISO) code pages,        
                 the operating systems of the sending and receiving systems must       
                 use the same character sets (ASCII or EBCDIC):                                                                               
    Sending system      Receiving system        Transfer possible             
             AS400               AS400                   Yes                           
             UNIX                UNIX                    Yes                           
             NT                  NT                      Yes                           
             NT                  UNIX                    Yes                           
             UNIX                NT                      Yes                           
             AS400               NT                      No                            
             AS400               UNIX                    No                            
             NT                  AS400                   No                            
             UNIX                AS400                   No                                                                               
    For more information, see:                                                                               
    -   The IMG activity Specify Environment Parameters                                                                               
    -   The IMG activity Set Up EH&S Native Language Support                                                                               
    -   The Product Safety documentation in the section EH&S Native           
                 Language Support                                                                               
    2.  Settings in Customizing for Distribution (ALE)                            
             You have made the necessary settings in Customizing for Distribution      
             (ALE).                                                                    
             Also maintain, for example, the sections                                                                               
    -   Basic Settings                                                                               
    -   Communication                                                                               
    3.  Settings in the Product Safety Component                                  
             Make sure that you have fulfilled the following prerequisites:                                                                               
    a)  Maintain the environment variables for serialization                    
                 Serialization collects the IDocs and makes sure that they are           
                 processed in the correct order. For more information, see               
                 section Serialized Distribution in Customizing for Distribution         
                 (ALE).                                                                               
    You specify the serialization number for the sending logical            
                 system in the IMG activity Specify Environment Parameters using         
                 the environment parameter ALE_SERIAL_ID. You specify one unique         
                 channel per logical system.                                                                               
    b)  Specify specifications to be distributed                                
                 If you want to distribute specification data manually, choose           
                 the specification directly from the hit list in specification           
                 management.                                                             
                 For automatic distribution, the specifications must appear in a         
                 set of hits that is assigned to the distribution method. If a           
                 set of hits has not been assigned, all of the specifications are        
                 distributed, providing that you have not defined filters.               
                 Apart from standard filters (see below), you can use the                
                 following customer exits to define further restrictions and             
                 filters:                                                                
                 - Specify Additional Table and Parameter Filter (1)                     
                 - Specify Additional Table and Parameter Filter (2)                                                                               
    c)  Ensure unique identification of specifications                          
                 The specification object must have a unique specification key.          
                 In the standard system, identification is supported by the              
                 specification key.                                                      
                 You can use the customer exit Develop Enhancement for                   
                 Identification to enhance the identification, for example, to           
                 link with one or more identifiers.                                                                               
    d)  Check authorizations                                                    
                 For manual distribution and automatic scheduling, you must have         
                 the read authorization for all the specification data to be             
                 distributed.                                                            
                 You also need the appropriate authorizations for inbound                
                 processing in the target system.                                                                               
    Activities                                                                               
    1.  Maintain the Distribution Model in Distribution (ALE) Customizing           
             In Customizing for Distribution, call the IMG activity Maintain             
             Distribution Model.                                                         
             For more information, see the documentation for the IMG activity.           
             To guarantee communication between systems during distribution, you         
             must make the following entries in the IMG activity Maintain                
             Distribution Model by choosing Add method:                                                                               
    Field             Entry                                                      
            Sender/client:    <Key for EH&S system>                                      
            Receiver/server:  <Key for target system>, for example,                      
                              Sales and Distribution system (SD), on which EH&S          
                              is installed.                                              
            Object name/interface:   Substance (substance(specification),                
         BUS1077)                                                                               
    Method:           SavRepMul (save replicated specifications)                                                                               
    Note:                                                                               
    Message type SUBMAS is supported.                                                                               
    You can set the following filters:                                                                               
    -   Reducing specifications by determining recipients:                               
                 You can reduce the specifications to be distributed by defining                  
                 the following filters:                                                           
                 - Specification type                                                             
                 - Authorization group                                                            
                 - Substance nature                                                               
                 - Set of hits (external key of group object)                                     
                 You can enter several values for a filter field. Individual                      
                 values are linked with OR, whereas the filter groups are linked                  
                 with AND.                                                                               
    If no filters are entered, all specifications are distributed.                                                                               
    -   Reducing specifications using 'IDENTHEADER' filtering                            
                 You define the identification category and identification type                   
                 whose specifications are to be distributed.                                                                               
    -   Reducing data using 'PROPHEADER' filtering                                       
                 You specify the value assignment types for which specification                   
                 data is to be distributed.                                                                               
    -   In Distribution (ALE) Customizing, you can use the IMG activity                  
                 Set Up Segment Filtering to exclude further tables from                          
                 distribution, for example:                                                       
                 - Material assignment                                                            
                 - Regulatory list assignment                                                     
                 - Reference specification assignment                                             
                 - Usage                                                                               
    - Assessment                                                                               
    Then in Distribution (ALE) Customizing, you maintain the IMG                         
             activity Generate Partner Profiles.                                                                               
    2.  Maintain Settings in the Sending and Recipient Systems                               
             The following tables must be maintained in the same way in the                       
             sending and recipient systems:                                                                               
    -   Value assignment type TCG01 and description TCG02 (system                        
                 tables)                                                                               
    -   Table of names for the DDIC objects TCG03 (system table)                                                                               
    -   Table of names for the child DDIC objects TCG04 (system table)                                                                               
    -   Specify Value Assignment Types                                                   
                 Value assignment type TCG11 and description TCG12                                
                 Value assignment type - specification type assignment TCG13                                                                               
    -   Identification category TCG21 and description TCG22 (system                      
                 tables)                                                                               
    -   Check Identification Types                                                       
                 Identification type TCG23 and description TCG24                                                                               
    -   Check Identification Listing                                                     
                 Identification listings TCG26 and description TCG27                              
                 Definition of identification listings TCG28                                                                               
    -   Assign Characteristic-Specific Identification                                    
                 Overriding identification list definitions TCG29                                                                               
    -   Specify Specification Types                                                      
                 Specification type TCG31 and description TCG32                                                                               
    -   Specify Authorization Groups                                                     
                 Authorization object TCG36 and description TCG37                                                                               
    -   Specify Types for User-Defined Texts                                  
                Value assignment text type TCG41 and description TCG42                                                                               
    -   Create Sources                                                        
                Source TCG46                                                                               
    -   Specify Source Types                                                  
                Source type TCG47 and description TCG48                                                                               
    -   Set Up Property Trees                                                 
                Property tree TCG51 and description TCG52                             
                Property tree - value assignment type assignment TCG53                                                                               
    -   Specify Data Origin                                                   
                Data origin TCG56                                                                               
    -   Specify Phrase Libraries and Phrase Groups                            
                Phrase library TCG61 and description TCG62                            
                Phrase group TCG63 and description TCG64                                                                               
    -   Specify Language Selection                                            
                Phrase language (languages supported in phrase library) TCG65                                                                               
    -   Value assignment type class characteristic TCG66                      
                System table, filled using master data matchup                                                                               
    -   Check Value Assignments                                               
                Value assignment assessment TCG71 and description TCG72                                                                               
    -   Specify Component Types for Compositions                              
                Component type TCG76 and description                                                                               
    -   Specify Regulatory Lists                                              
                Regulatory list TCG81 and description TCG82                                                                               
    -   Specify Ratings                                                       
                Value assignment rating TCG86 and description TCG87                                                                               
    -   Specify Validity Areas                                                
                Validity area TCG91 and description TCG92                                                                               
    -   Specify Usage Profiles                                                
                Usage profile TCG96 and description TCG97                             
                Usage profile - rating - validity area assignment TCG98                                                                               
    -   Specify Exchange Profiles                                             
                Exchange profile TCGC3 and description TCGC4                                                                               
    -   Specify Environment Parameters                                        
                General environment parameters TCGENV                                                                               
    -   Protect Characteristics Within Namespace                              
                Namespaces for characteristics TCGK1                                                                               
    -   Manage User Exits                                                     
                User exit parameters from user exit management TCGUEEN                
                User exits from user exit management with function module             
                assignment TCGUEFU                                                    
                Language-dependent user exit names from user exit management          
                TCGUENA                                                               
                User exit categories from user exit management TCGUETY                                                                               
    3.  Check Master Data to Be Distributed                                                                               
    For the ALE process, the following master data must be distributed      
             to all the relevant systems:                                                                               
    -   Phrases                                                                               
    -   Phrase sets (for systems, in which data is created)                                                                               
    -   Classes and characteristics                                                                               
    -   Materials (all material data that is required for                   
                 material-specification assignment)                                                                               
    -   Change numbers                                                      
             Note:                                                                               
    Classes and characteristics are distributed via export and          
                 import. The help texts and phrase sets are also transferred to      
                 other systems along with the classes and characteristics.           
                 Classes and characteristics can also be distributed using ALE.      
             Note:                                                                   
             The required data providers must have been created manually in the      
             Product Safety component under Tools -> Edit addresses -> Data          
             provider before data is distributed in the recipient system. The        
             data providers must be unique with regard to the following three        
             fields:                                                                 
             - Name (NAME1)                                                          
             - City  (CITY1)                                                         
             - Country (COUNTRY)                                                     
             During distribution, the data providers of the specification to be      
             sent are read and also distributed. When writing to the recipient       
             system, the SAP System determines the corresponding address number      
             for the data provider in the recipient system by comparing the three    
             fields Name, City and Country for the address numbers that were         
             sent, and then transfers this address number that was determined to     
             the Data provider field (OWNID).                                                                               
    You can determine the address number of the data provider in            
             Customizing for Product Safety in the IMG activity Specify              
             Authorization Groups.                                                   
             To do this, call the input help for the Data prov. field in the IMG     
             activity. You will find the value you require in the Addr. no.          
             field.                                                                  
             The address number is not displayed in address management in the        
             Product Safety component.                                                                               
    4.  Check Control Data to Be Distributed                                    
             See above: "Maintain Settings in the Sending and Recipient Systems"                                                                               
    5.  Check Consistency                                                       
             A consistency check can be performed for the settings in the            
             distribution model and the partner profiles.                            
             To do this, in Distribution (ALE) Customizing, call the IMG activity    
             Check Partner Profiles and Model Settings.                              
             The distribution model must have been distributed and the partner       
             profiles must have been maintained in all relevant systems.                                                                               
    6.  Error Handling                                                          
             As soon as an error occurs when an IDoc is processed, the whole IDoc    
             is not updated. You can use a workflow to correct errors. IDocs can     
             be modified manually (you can change the identifier, for example)       
             and updated retrospectively.                                                                               
    General Procedure                                                                               
    1.  In a customer reference model you define which data is to be                  
             distributed to which system. You use sets of hits to define the               
             specifications that are to be distributed and specify filters with            
             regard to specifications or specification data as required.                                                                               
    2.  The first time you distribute specifications to the target systems,           
             you do it manually, using the method REPLICATE according to the               
             distribution model. Serialization must be switched off.                                                                               
    3.  You activate serialization and switch on delta distribution as                
             follows:                                                                               
    Activating Serialization                                                                               
    a)  In Customizing for Product Safety, in the IMG activity Specify            
                 Environment Parameters specify the channel for the parameter              
                 ALE_SERIAL_ID through which the ALE data is to be distributed.                                                                               
    b)  In Customizing for Distribution (ALE) choose Set Up Data                  
                 Distribution -> Serialized Distribution -> Serialized                     
                 Distribution Using Object Types -> Activate Inbound Object Types          
                 and specify the inbound object types for which serialization is           
                 to be performed.                                                                               
    c)  Schedule a job (RBDAPP01) that posts the IDocs that arrive in             
                 series in the recipient system.                                                                               
    Switching On Delta Distribution                                                                               
    a)  Activating change pointers for a message type                             
                 Changes to master data objects are logged in the form of change           
                 pointers during master data distribution. To activate the                 
                 writing of change pointers, in Customizing for Distribution               
                 (ALE) choose Set Up Data Distribution -> Master Data                      
                 Distribution -> Activating Change Pointers -> Activate Change             
                 Pointers for Message Types and set the Active indicator for the           
                 message type for which you want to realize delta distribution.                                                                               
    b)  Activating change pointers for each field                                 
                 From the SAP R/3 screen, choose Tools -> Business Framework ->            
                 ALE -> Development -> Master data -> Activate change pointer for          
                 each field and enter the message type for which you want to               
                 determine fields, for which the SAP System writes change                  
                 pointers. All relevant data fields are delivered. If necessary,           
                 adjust the table to your requirements.                                                                               
    c)  Activating change pointers generally                                      
                 To generally activate master data distribution using change               
                 pointers, in Customizing for Distribution (ALE), choose Set Up            
                 Data Distribution -> Master Data Distribution -> Activating               
                 Change Pointers -> Activate Change Pointers (generally) and set           
                 the active indicator.                                                                               
    d)  Scheduling delta distribution as a job                                    
                 You can perform delta distribution manually or schedule it as a           
                 job.                                                                               
    To perform delta distribution manually, from the SAP R/3 screen           
                 choose Tools -> Business Framework -> ALE -> Administration ->            
                 Periodic processing -> Process change pointers and enter the              
                 message type you require and choose Execute.                              
                 To schedule delta distribution as a job, in Customizing for               
                 Distribution (ALE) choose Scheduling Periodic Processing ->               
                 Scheduling Generation of IDocs from Change Pointers -> Define                                                                               
    Variants and create a variant. Then in the IMG activity Schedule       
                 Jobs create a job (RBDMIDOC) for the variant. You can set the          
                 time at which distribution is performed, for example,                  
                 immediately after a change or periodically.                                                                               
    The following applies when transferring data:                                                                               
    o   If a specification is not found in the target system, it is created        
             with the specification key that is transferred.                                                                               
    o   If a specification is available in the target system, its data is          
             updated.                                                                               
    o   When complete specification data is being sent, the specification is       
             locked and no changes can be made to it. If this lock cannot be set,       
             the specification cannot be processed. The IDoc is given the status        
             with error and a work item is created.                                                                               
    Note:                                                                               
    In manual distribution, change pointers are not taken into account.        
             In other words, the entire data record is distributed and delta            
             distribution is not performed.                                                                               
    Note on Executing the Report Program RC1PHDEL:                                 
             You must NOT schedule the report program RC1PHDEL (physical deletion       
             of data) to run in the source system or manually run it between            
             initial distribution and delta distribution, because the keys of           
             logically deleted data records can no longer be read and distributed       
             by delta distribution after the report program has been executed.          
             Before initial distribution you can execute the report in the source       
             system.                                                                    
             In the target system you can execute the report program independent        
             of distribution, as long as the target system does not serve as the        
             source system for further distribution.                                    
             If you want to execute the report program after the first delta            
             distribution, you must first make sure that all change pointers            
             created have been fully processed by the delta distribution and, if        
             possible, that all IDocs (intermediate documents) created were also        
             successfully posted in the target system. Otherwise, there is no           
             guarantee that the source and target systems will be consistent.                                                                               
    Example                                                                    
             The report program RC1PHDEL was executed in the source system so           
             that the deletions of an identifier of the identification category         
             NUM and the identification type CAS and a phrase item were not             
             distributed.                                                               
             Then an identifier of the identification category NUM and                  
             identification type CAS with the identical value that was previously       
             deleted and a phrase item for the same phrase in the previously            
             deleted language are created. The following errors occur in the            
             subsequent delta distribution:                                                                               
    -   The identifier cannot be created because the NUM-CAS value             
                 already exists. The IDoc cannot therefore be posted.                   
                 Notes:                                                                               
    If you attempt to create duplicate identifiers in the dialog,          
                 the same error messages will be displayed as when posting using        
                 ALE.                                                                               
    If the NUM-CAS identifier was not identical to the previously          
                 deleted identifier, the IDoc would be posted successfully and          
                 the identifier would be created in addition.                                                                               
    -   The phrase item cannot be created, because only one phrase item        
                 is permitted for a phrase in each language. The old phrase item                                                                               
    must be deleted first before the IDoc can be posted.                                                                               
    The next section describes the solution for similar error cases. You    
             should, however, try to avoid the need for this procedure by not        
             executing the report program.                                                                               
    e)  In the target system in the dialog, delete the EH&S objects         
                 (specifications, phrases, reports), for which you have already      
                 run delta distribution. These objects are internally marked with    
                 a deletion indicator.                                               
                 Caution:                                                            
                 When you distribute reports, the report bodies are distributed.     
                 To delete these, you simply need to delete all report reference     
                 specifications. Deleting report bodies is not necessary and also    
                 not possible. If you cannot delete objects (such as                 
                 specifications or phrases) owing to their where-used-list, it is    
                 sufficient to delete the 'deleted' detail data in the target        
                 system that has not been distributed. This may require more         
                 processing effort than if you delete all the objects using the      
                 hit list and distribute all the data again in full.                                                                               
    f)  In the target system, set the Set missing deletion indicators       
                 and Delete physically indicators in the RC1PHDEL report program     
                 and execute the report program in the target system.                
                 This triggers the following actions:                                
                 - The deletion indicator is set in the tables that depend on the    
                 header data to be deleted.                                          
                 - All data with deletion indicators is deleted physically.          
                 - The corresponding entries in the table ESTALE (conversion         
                 table for ALE) are deleted physically.                                                                               
    g)  Deactivate the active serialization and the writing of change       
                 pointers and start initial distribution of all objects again.                                                                               
    h)  You can now activate the writing of change pointers and             
                 serialization again and use delta distribution as usual.            
             Note:                                                                   
             If you still have IDocs in the source system or target system that      
             were created before the deletion in your target system, but were not    
             distributed or posted, ignore these IDocs and do not post them. You     
             can do this by changing the channel before repeating the initial        
             distribution by using the environment parameter ALE_SERIAL_ID (for      
             more information on the environment parameter, see the IMG activity     
             Set Up Distribution of Specification Data).                             
    Return ->                                                                       
         Application                                                                               
    Hope this helps
    Mark

  • Com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or passwo

    Hi All,
    I'm configuring the Solution Manager Diagnostics.
    I have all my agent SMD and IS installed.... but when I run the Setup Wizard, I received the following error:
    Step Wilyhost Agent Details
    Created destination BD1_DVEBMGS00_server0
    Created destination SapStartSrv_bnsr3dci_BD1_00
    Created destination BD1|bnsr3dci_BD1_00
    Created action SAP GC|BD1_DVEBMGS00_server0 - SAP GC|BD1_DVEBMGS00_server0
    Created action BD1|bnsr3dci_BD1_00 - SapStartSrv_bnsr3dci_BD1_00
    Created action BD1 - BD1 AbapSystem
    Created action BD1|bnsr3dci_BD1_00 - BD1|bnsr3dci_BD1_00 AbapInstance
    Created 4 action(s).
    0 Wilyhost Agent(s) from host bnsr3dci are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (bnssmpci.bns.local:6001) no Wilyhost Agent was detected from host bnsr3dci. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    and checking the jvm_smdagent.out file on managed system
    Running SMD Agent ...
    [ms://bnssmpci:8101/P4] Agent ready.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Using Java VM version "SAP Java Server VM 1.5.0_17" from SAP AG
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily
    host/IntroscopeSapAgent.profile
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Loaded file from /usr/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/Int
    roscopeSapAgent.profile
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval is set to 1800
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to 500
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is set to 3000
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions director
    y.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] The agent extensions directory /sap_mirrlog/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.ap
    plication.wilyhost/ext was successfully located
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Introscope Agent startup complete.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent SMDA97" based on the value of the System Property "com.wily.introscope.a
    gent.agentName".
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent SMDA97
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Started Error Reporting service
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    10/27/09 02:58:20 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (1).
    Initialization done.
    10/27/09 02:58:30 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (2).
    10/27/09 02:58:40 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (3).
    10/27/09 02:58:50 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (4).
    10/27/09 02:59:00 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (5).
    10/27/09 02:59:11 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (6).
    10/27/09 02:59:21 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (7).
    10/27/09 02:59:31 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (8).
    10/27/09 02:59:41 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (9).
    10/27/09 02:59:51 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (10).
    10/27/09 02:59:51 PM EDT [INFO] [IntroscopeAgent.ConnectionThread] The Agent will continue to attempt to connect to Introscope Enterprise Manager. Further fai
    lures will not be logged.
    [ms://bnssmpci:8101/P4] Agent ready.
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Initialization done.
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    This is error common ?
    Any idea ?
    Weird for me is this line:
    "Failed to connect to the Introscope Enterprise Manager at localhost:6001"
    Because my INtroscope Enterprise Manager name is bnssmpci
    Thanks and Regars,
    Juan.

    SOLVED !!!
    Restart the J2EE Managed System and check the SAP Note - WilyHost agent fails to connect to ABAP stack (bad password

  • Error in transfer with oracle WB transfer

    hi,
    I try to transfer my oracle target module to database (target schema).
    I recieve error as follow :
    **! Transfer logging started at Sat Feb 05 09:21:30 IRST 2005 !**
    OWB Bridge processed arguments
    Bridge Parameters are:
    <BA>=<All Collections>
    <LANGUAGE>=<All Languages>
    <LOCKREPOSITORY>=<True>
    <file>=<C:\TEMP\bridges\null-nullMy_Metadata_Transfer1107582690567.XMI>
    Using attribute sorting
    export to file
    Default local= fa_IR
    Exporting project:KAFA_PROJECT2
    initializing project:KAFA_PROJECT2
    Initializing module :KAFA_DW_MODULE
    exportSchema:KAFA_DW_MODULE SCHM14314
    Exporting cube:EMPLOYEMENT_CUBE
    exportCube:EMPLOYEMENT_CUBE/EMPLOYEMENT_CUBE Cube14396
    exportCubeDimUse:CDU14344FK14400
    exportFactLevelUse:FLU14396FK14400
    exportCubeDimUse:CDU14359FK14403
    exportFactLevelUse:FLU14396FK14403
    exportCubeDimUse:CDU14379FK14397
    exportFactLevelUse:FLU14396FK14397
    exportClassificationEntry for:KAFA_COLLECTION2 CLE_0
    exportMeasure:SALARY/SALARY MEA14410
    Exporting dimension:DEP_DIM
    exportDimension:DEP_DIM/DEP_DIM DIM14359
    exportClassificationEntry for:KAFA_COLLECTION2 CLE_2
    exportLevel:DEP_MAIN/DEP_MAIN LEV14360
    exportClassificationEntry for:Description CLE_3
    exportLevelAttribute:DEP_ID/DEP_ID LATR14363
    exportLevelAttribute:DEP_NAME/DEP_NAME LATR14367
    exportKey:DEP_MAIN_UK/DEP_MAIN_UK KEY14361
    exportKeyAttributeUse:KEYAU14363KEY14361
    exportHierarchy:HIE_DEP/HIE_DEP HEIR14374
    exportHierarchyLevelUse:HLU14374LEV14360
    Exporting dimension:EMP_DIM
    exportDimension:EMP_DIM/EMP_DIM DIM14344
    exportClassificationEntry for:KAFA_COLLECTION2 CLE_5
    exportLevel:EMP_MAIN/EMP_MAIN LEV14345
    exportClassificationEntry for:Description CLE_6
    exportLevelAttribute:EMP_ID/EMP_ID LATR14348
    exportLevelAttribute:EMP_NAME/EMP_NAME LATR14352
    exportKey:EMP_MAIN_UK/EMP_MAIN_UK KEY14346
    exportKeyAttributeUse:KEYAU14348KEY14346
    exportHierarchy:HIE_EMP/HIE_EMP HEIR14354
    exportHierarchyLevelUse:HLU14354LEV14345
    Exporting dimension:JOB_DIM
    exportDimension:JOB_DIM/JOB_DIM DIM14379
    exportClassificationEntry for:KAFA_COLLECTION2 CLE_7
    exportLevel:JOB_MAIN/JOB_MAIN LEV14380
    exportClassificationEntry for:Description CLE_8
    exportLevelAttribute:JOB_ID/JOB_ID LATR14383
    exportLevelAttribute:JOB_NAME/JOB_NAME LATR14389
    exportKey:JOB_MAIN_UK/JOB_MAIN_UK KEY14381
    exportKeyAttributeUse:KEYAU14383KEY14381
    exportHierarchy:HIE_JOB/HIE_JOB HEIR14391
    exportHierarchyLevelUse:HLU14391LEV14380
    Exporting mappings
    exportDimensionTableMap:DTMAP14359
    exportItemMap:IMAP14364
    exportItemUse:TIU14363
    exportItemUse:SIU14364
    exportItemMap:IMAP14368
    exportItemUse:TIU14367
    exportItemUse:SIU14368
    exportDimensionEntityUse:EU_DIM14359
    exportDimensionTableUse:EU_TAB14359
    exportDimensionTableMap:DTMAP14344
    exportItemMap:IMAP14349
    exportItemUse:TIU14348
    exportItemUse:SIU14349
    exportItemMap:IMAP14353
    exportItemUse:TIU14352
    exportItemUse:SIU14353
    exportDimensionEntityUse:EU_DIM14344
    exportDimensionTableUse:EU_TAB14344
    exportDimensionTableMap:DTMAP14379
    exportItemMap:IMAP14384
    exportItemUse:TIU14383
    exportItemUse:SIU14384
    exportItemMap:IMAP14390
    exportItemUse:TIU14389
    exportItemUse:SIU14390
    exportDimensionEntityUse:EU_DIM14379
    exportDimensionTableUse:EU_TAB14379
    exportFactTableMap:FTMAP14396
    exportMapDependency:MAPDEP14396DTMAP14344
    exportMapDependency:MAPDEP14396DTMAP14359
    exportMapDependency:MAPDEP14396DTMAP14379
    exportItemMap:IMAP14410
    exportItemUse:TIU14410
    exportItemUse:SIU14410
    exportCubeEntityUse:EU_Cube14396
    exportFactUse:EU_TAB14396
    exportFactLevelGroup:FLG_TAB14396
    Exporting table:DEP_DIM
    exportTable:DEP_DIM/DEP_DIM TAB14359
    exportKey:DEP_DIM_DEP_MAIN_UK/DEP_DIM_DEP_MAIN_UK KEY14362
    exportKeyAttributeUse:KEYAU14364KEY14362
    exportColumn:DEP_MAIN DEP_ID/DEP_MAIN_DEP_ID COL14364
    exportColumn:DEP_MAIN_DEP_NAME/DEP_MAIN_DEP_NAME COL14368
    exportClassificationEntry for:KAFA_COLLECTION2 CLE_9
    Exporting table:EMP_DIM
    exportTable:EMP_DIM/EMP_DIM TAB14344
    exportKey:EMP_DIM_EMP_MAIN_UK/EMP_DIM_EMP_MAIN_UK KEY14347
    exportKeyAttributeUse:KEYAU14349KEY14347
    exportColumn:EMP_MAIN EMP_ID/EMP_MAIN_EMP_ID COL14349
    exportColumn:EMP_MAIN_EMP_NAME/EMP_MAIN_EMP_NAME COL14353
    exportClassificationEntry for:KAFA_COLLECTION2 CLE_10
    Exporting table:JOB_DIM
    exportTable:JOB_DIM/JOB_DIM TAB14379
    exportKey:JOB_DIM_JOB_MAIN_UK/JOB_DIM_JOB_MAIN_UK KEY14382
    exportKeyAttributeUse:KEYAU14384KEY14382
    exportColumn:JOB_MAIN JOB_ID/JOB_MAIN_JOB_ID COL14384
    exportColumn:JOB_MAIN_JOB_NAME/JOB_MAIN_JOB_NAME COL14390
    exportClassificationEntry for:KAFA_COLLECTION2 CLE_11
    Exporting table:EMPLOYEMENT_CUBE
    exportTable:EMPLOYEMENT_CUBE/EMPLOYEMENT_CUBE TAB14396
    exportKey:SEG_UK_EMPLOYEMENT_CUBE/SEG_UK_EMPLOYEMENT_CUBE KEY14406
    exportKeyAttributeUse:KEYAU14401KEY14406
    exportKeyAttributeUse:KEYAU14404KEY14406
    exportKeyAttributeUse:KEYAU14398KEY14406
    exportForeignKey:FK_EMPLOYEMENT_CUBE_14362/FK_EMPLOYEMENT_CUBE_14362 FK14403
    exportKeyAttributeUse:KEYAU14404FK14403
    exportForeignKey:FK_EMPLOYEMENT_CUBE_14347/FK_EMPLOYEMENT_CUBE_14347 FK14400
    exportKeyAttributeUse:KEYAU14401FK14400
    exportForeignKey:FK_EMPLOYEMENT_CUBE_14382/FK_EMPLOYEMENT_CUBE_14382 FK14397
    exportKeyAttributeUse:KEYAU14398FK14397
    exportColumn:DEP_MAIN_DEP_ID/DEP_MAIN_DEP_ID COL14404
    exportColumn:EMP_MAIN_EMP_ID/EMP_MAIN_EMP_ID COL14401
    exportColumn:JOB_MAIN_JOB_ID/JOB_MAIN_JOB_ID COL14398
    exportColumn:SALARY/SALARY COL14410
    exportClassificationEntry for:KAFA_COLLECTION2 CLE_12
    exportContext:CTXT00
    exportTypeSet:TSET
    Exporting datatypes
    exportScalarDatatype:NUMBER DTYP7836
    exportScalarDatatype:VARCHAR2 DTYP7839
    exportClassification:KAFA_COLLECTION2 CLAS1
    exportClassificationType:Warehouse Builder Business Area CLT13
    exportClassification:Description CLAS4
    exportClassificationType:Dimensional Attribute Descriptor CLT14
    Exporting project KAFA_PROJECT2 complete.
    **! Target bridge jvm parameters = "..\..\..\jdk\jre\bin\javaw" -mx50m -DORCLCWM_META_MODEL_FILE=..\..\bridges\admin\orcl_cwm.xml -classpath .;..\..\bridges\lib\bridge_cwmlite10.jar;..\..\bridges\lib\bridge_parser10.jar;..\..\bridges\lib\vek10.jar;..\..\..\lib\xmlparserv2.jar;..\..\..\jdbc\lib\ojdbc14.jar;..\..\bridges\lib\util10.jar;..\..\lib\int\util.jar;..\..\lib\int\rts.jar;..\..\..\jlib\rts2.jar;..\..\bridges\lib\bridge_cwmlite10.jar;..\..\bridges\lib\bridge_parser10.jar;..\..\bridges\lib\vek10.jar;..\..\..\lib\xmlparserv2.jar;..\..\..\jdbc\lib\ojdbc14.jar;..\..\bridges\lib\util10.jar;..\..\lib\int\util.jar;..\..\lib\int\rts.jar;..\..\..\jlib\rts2.jar;"..\..\..\jdk\jre\lib\rt.jar;..\..\..\jdk\jre\lib\charsets.jar";"..\..\bridges\admin;..\..\bridges\lib\bridge_wrapper10.jar;..\..\bridges\lib\util10.jar;..\..\lib\int\reposimpl.jar;..\..\lib\int\repossdk.jar;..\..\lib\int\rts.jar;..\..\..\jlib\rts2.jar;..\..\lib\int\util.jar" oracle.cwm.tools.bridge.BridgeWrapper -bridge_name oracle.cwm.bridge.cwmlite.ImportMain !**
    **! Target bridge parameters = -log_level 2 -log_file C:\TEMP\bridges\log\null-nullMy_Metadata_Transfer1107582690567.log -olapimp.deploytoaw N -olapimp.awname -olapimp.awobjprefix -olapimp.loadcubedata Y -olapimp.awaggregate 1 -olapimp.dimuniquekeys N -olapimp.awuser -olapimp.createviews N -olapimp.viewprefix -olapimp.viewaccesstype OLAP -olapimp.creatematviews Y -olapimp.viewscriptdir -olapimp.deploy Y -olapimp.username dw_targetschema -olapimp.password password -olapimp.host 200.20.20.11 -olapimp.port 1521 -olapimp.sid ora10g -olapimp.inputfilename C:\TEMP\bridges\null-nullMy_Metadata_Transfer1107582690567.XMI -olapimp.outputfilename C:\Documents and Settings\stabatabaee\Desktop\test.sql -paramfile C:\TEMP\bridges\1107582690832.par !**
    setting parameter: olapimp.deploytoaw = N
    setting parameter: olapimp.awname =
    setting parameter: olapimp.awobjprefix =
    setting parameter: olapimp.loadcubedata = Y
    setting parameter: olapimp.awaggregate = 1
    setting parameter: olapimp.dimuniquekeys = N
    setting parameter: olapimp.awuser =
    setting parameter: olapimp.createviews = N
    setting parameter: olapimp.viewprefix =
    setting parameter: olapimp.viewaccesstype = OLAP
    setting parameter: olapimp.creatematviews = Y
    setting parameter: olapimp.viewscriptdir =
    setting parameter: olapimp.deploy = Y
    setting parameter: olapimp.username = dw_targetschema
    setting parameter: olapimp.host = 200.20.20.11
    setting parameter: olapimp.port = 1521
    setting parameter: olapimp.sid = ora10g
    setting parameter: olapimp.inputfilename = C:\TEMP\bridges\null-nullMy_Metadata_Transfer1107582690567.XMI
    setting parameter: olapimp.outputfilename = C:\Documents and Settings\stabatabaee\Desktop\test.sql
    Loading Metadata
    Loading XMI input file
    connecting ...
    processing dim: DEP_DIM
    processing level: DEP_MAINin dimension DEP_DIM
    processing level attribute use: DEP_MAIN_DEP_ID in level DEP_MAIN for level attribute DEP_ID
    processing level attribute : DEP_ID in level DEP_MAIN
    processing level attribute use: DEP_MAIN_DEP_NAME in level DEP_MAIN for level attribute DEP_NAME
    processing level attribute : DEP_NAME in level DEP_MAIN
    declare
    id number;
    s_id number;
    l_id number;
    levelday_id number;
    levelmonth_id number;
    levelquarter_id number;
    levelyear_id number;
    f_id number;
    begin
    select descriptor_id into l_id from all_olap_descriptors where descriptor_value='Long Description';
    select descriptor_id into s_id from all_olap_descriptors where descriptor_value='Short Description';
    select descriptor_id into levelday_id from all_olap_descriptors where descriptor_value='Day';
    select descriptor_id into levelmonth_id from all_olap_descriptors where descriptor_value='Month';
    select descriptor_id into levelquarter_id from all_olap_descriptors where descriptor_value='Quarter';
    select descriptor_id into levelyear_id from all_olap_descriptors where descriptor_value='Year';
    cwm_olap_dimension.Set_Description (USER, 'DEP_DIM', '');
    cwm_olap_dimension.Set_Display_Name(USER, 'DEP_DIM', 'DEP_DIM');
    cwm_olap_dimension.Set_Plural_Name(USER, 'DEP_DIM', 'DEP_DIM');
    cwm_olap_level.Set_Description (USER, 'DEP_DIM', 'DEP_MAIN', '');
    cwm_olap_level.Set_Display_Name(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_MAIN');
    begin
    cwm_olap_level_attribute.set_name(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_MAIN_DEP_ID', 'DEP_ID');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_Display_Name(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_ID', 'DEP_ID');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_description(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_ID', '');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.set_name(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_MAIN_DEP_NAME', 'DEP_NAME');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_Display_Name(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_NAME', 'DEP_NAME');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_description(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_NAME', '');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_dim_attribute.drop_Dimension_Attribute(USER, 'DEP_DIM', 'Short_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.Create_Dimension_Attribute(USER, 'DEP_DIM', 'Short_Description', 'Short_Description', 'Short Description');
    select descriptor_id into id from all_olap_descriptors where descriptor_value='Short Description';
    cwm_classify.add_entity_descriptor_use(id, cwm_utility.DIMENSION_ATTRIBUTE_TYPE,USER, 'DEP_DIM', 'Short_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.drop_Dimension_Attribute(USER, 'DEP_DIM', 'Long_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.Create_Dimension_Attribute(USER, 'DEP_DIM', 'Long_Description', 'Long_Description', 'Full Description');
    select descriptor_id into id from all_olap_descriptors where descriptor_value='Long Description';
    cwm_classify.add_entity_descriptor_use(id, cwm_utility.DIMENSION_ATTRIBUTE_TYPE,USER, 'DEP_DIM', 'Long_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.Add_Level_Attribute(USER, 'DEP_DIM', 'Short_Description', 'DEP_MAIN', 'DEP_NAME');
    exception when cwm_exceptions.attribute_already_exists then null; when cwm_exceptions.attribute_not_found then null;
    end;
    begin
    cwm_olap_dim_attribute.Add_Level_Attribute(USER, 'DEP_DIM', 'Long_Description', 'DEP_MAIN', 'DEP_NAME');
    exception when cwm_exceptions.attribute_already_exists then null; when cwm_exceptions.attribute_not_found then null;
    end;
    commit;
    exception when others then dbms_output.enable(1000000); cwm_utility.dump_error(); raise program_error;
    end;
    processing dim: EMP_DIM
    processing level: EMP_MAINin dimension EMP_DIM
    processing level attribute use: EMP_MAIN_EMP_ID in level EMP_MAIN for level attribute EMP_ID
    processing level attribute : EMP_ID in level EMP_MAIN
    processing level attribute use: EMP_MAIN_EMP_NAME in level EMP_MAIN for level attribute EMP_NAME
    processing level attribute : EMP_NAME in level EMP_MAIN
    declare
    id number;
    s_id number;
    l_id number;
    levelday_id number;
    levelmonth_id number;
    levelquarter_id number;
    levelyear_id number;
    f_id number;
    begin
    select descriptor_id into l_id from all_olap_descriptors where descriptor_value='Long Description';
    select descriptor_id into s_id from all_olap_descriptors where descriptor_value='Short Description';
    select descriptor_id into levelday_id from all_olap_descriptors where descriptor_value='Day';
    select descriptor_id into levelmonth_id from all_olap_descriptors where descriptor_value='Month';
    select descriptor_id into levelquarter_id from all_olap_descriptors where descriptor_value='Quarter';
    select descriptor_id into levelyear_id from all_olap_descriptors where descriptor_value='Year';
    cwm_olap_dimension.Set_Description (USER, 'EMP_DIM', '');
    cwm_olap_dimension.Set_Display_Name(USER, 'EMP_DIM', 'EMP_DIM');
    cwm_olap_dimension.Set_Plural_Name(USER, 'EMP_DIM', 'EMP_DIM');
    cwm_olap_level.Set_Description (USER, 'EMP_DIM', 'EMP_MAIN', '');
    cwm_olap_level.Set_Display_Name(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_MAIN');
    begin
    cwm_olap_level_attribute.set_name(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_MAIN_EMP_ID', 'EMP_ID');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_Display_Name(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_ID', 'EMP_ID');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_description(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_ID', '');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.set_name(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_MAIN_EMP_NAME', 'EMP_NAME');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_Display_Name(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_NAME', 'EMP_NAME');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_description(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_NAME', '');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_dim_attribute.drop_Dimension_Attribute(USER, 'EMP_DIM', 'Short_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.Create_Dimension_Attribute(USER, 'EMP_DIM', 'Short_Description', 'Short_Description', 'Short Description');
    select descriptor_id into id from all_olap_descriptors where descriptor_value='Short Description';
    cwm_classify.add_entity_descriptor_use(id, cwm_utility.DIMENSION_ATTRIBUTE_TYPE,USER, 'EMP_DIM', 'Short_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.drop_Dimension_Attribute(USER, 'EMP_DIM', 'Long_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.Create_Dimension_Attribute(USER, 'EMP_DIM', 'Long_Description', 'Long_Description', 'Full Description');
    select descriptor_id into id from all_olap_descriptors where descriptor_value='Long Description';
    cwm_classify.add_entity_descriptor_use(id, cwm_utility.DIMENSION_ATTRIBUTE_TYPE,USER, 'EMP_DIM', 'Long_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.Add_Level_Attribute(USER, 'EMP_DIM', 'Short_Description', 'EMP_MAIN', 'EMP_NAME');
    exception when cwm_exceptions.attribute_already_exists then null; when cwm_exceptions.attribute_not_found then null;
    end;
    begin
    cwm_olap_dim_attribute.Add_Level_Attribute(USER, 'EMP_DIM', 'Long_Description', 'EMP_MAIN', 'EMP_NAME');
    exception when cwm_exceptions.attribute_already_exists then null; when cwm_exceptions.attribute_not_found then null;
    end;
    commit;
    exception when others then dbms_output.enable(1000000); cwm_utility.dump_error(); raise program_error;
    end;
    processing dim: JOB_DIM
    processing level: JOB_MAINin dimension JOB_DIM
    processing level attribute use: JOB_MAIN_JOB_ID in level JOB_MAIN for level attribute JOB_ID
    processing level attribute : JOB_ID in level JOB_MAIN
    processing level attribute use: JOB_MAIN_JOB_NAME in level JOB_MAIN for level attribute JOB_NAME
    processing level attribute : JOB_NAME in level JOB_MAIN
    declare
    id number;
    s_id number;
    l_id number;
    levelday_id number;
    levelmonth_id number;
    levelquarter_id number;
    levelyear_id number;
    f_id number;
    begin
    select descriptor_id into l_id from all_olap_descriptors where descriptor_value='Long Description';
    select descriptor_id into s_id from all_olap_descriptors where descriptor_value='Short Description';
    select descriptor_id into levelday_id from all_olap_descriptors where descriptor_value='Day';
    select descriptor_id into levelmonth_id from all_olap_descriptors where descriptor_value='Month';
    select descriptor_id into levelquarter_id from all_olap_descriptors where descriptor_value='Quarter';
    select descriptor_id into levelyear_id from all_olap_descriptors where descriptor_value='Year';
    cwm_olap_dimension.Set_Description (USER, 'JOB_DIM', '');
    cwm_olap_dimension.Set_Display_Name(USER, 'JOB_DIM', 'JOB_DIM');
    cwm_olap_dimension.Set_Plural_Name(USER, 'JOB_DIM', 'JOB_DIM');
    cwm_olap_level.Set_Description (USER, 'JOB_DIM', 'JOB_MAIN', '');
    cwm_olap_level.Set_Display_Name(USER, 'JOB_DIM', 'JOB_MAIN', 'JOB_MAIN');
    begin
    cwm_olap_level_attribute.set_name(USER, 'JOB_DIM', 'JOB_MAIN', 'JOB_MAIN_JOB_ID', 'JOB_ID');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_Display_Name(USER, 'JOB_DIM', 'JOB_MAIN', 'JOB_ID', 'JOB_ID');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_description(USER, 'JOB_DIM', 'JOB_MAIN', 'JOB_ID', '');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.set_name(USER, 'JOB_DIM', 'JOB_MAIN', 'JOB_MAIN_JOB_NAME', 'JOB_NAME');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_Display_Name(USER, 'JOB_DIM', 'JOB_MAIN', 'JOB_NAME', 'JOB_NAME');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_level_attribute.Set_description(USER, 'JOB_DIM', 'JOB_MAIN', 'JOB_NAME', '');
    exception when OTHERS then null;
    end;
    begin
    cwm_olap_dim_attribute.drop_Dimension_Attribute(USER, 'JOB_DIM', 'Short_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.Create_Dimension_Attribute(USER, 'JOB_DIM', 'Short_Description', 'Short_Description', 'Short Description');
    select descriptor_id into id from all_olap_descriptors where descriptor_value='Short Description';
    cwm_classify.add_entity_descriptor_use(id, cwm_utility.DIMENSION_ATTRIBUTE_TYPE,USER, 'JOB_DIM', 'Short_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.drop_Dimension_Attribute(USER, 'JOB_DIM', 'Long_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.Create_Dimension_Attribute(USER, 'JOB_DIM', 'Long_Description', 'Long_Description', 'Full Description');
    select descriptor_id into id from all_olap_descriptors where descriptor_value='Long Description';
    cwm_classify.add_entity_descriptor_use(id, cwm_utility.DIMENSION_ATTRIBUTE_TYPE,USER, 'JOB_DIM', 'Long_Description');
    exception when others then null;
    end;
    begin
    cwm_olap_dim_attribute.Add_Level_Attribute(USER, 'JOB_DIM', 'Short_Description', 'JOB_MAIN', 'JOB_NAME');
    exception when cwm_exceptions.attribute_already_exists then null; when cwm_exceptions.attribute_not_found then null;
    end;
    begin
    cwm_olap_dim_attribute.Add_Level_Attribute(USER, 'JOB_DIM', 'Long_Description', 'JOB_MAIN', 'JOB_NAME');
    exception when cwm_exceptions.attribute_already_exists then null; when cwm_exceptions.attribute_not_found then null;
    end;
    commit;
    exception when others then dbms_output.enable(1000000); cwm_utility.dump_error(); raise program_error;
    end;
    processing cube: EMPLOYEMENT_CUBE
    declare
    id number;
    s_id number;
    l_id number;
    levelday_id number;
    levelmonth_id number;
    levelquarter_id number;
    levelyear_id number;
    f_id number;
    begin
    select descriptor_id into l_id from all_olap_descriptors where descriptor_value='Long Description';
    select descriptor_id into s_id from all_olap_descriptors where descriptor_value='Short Description';
    select descriptor_id into levelday_id from all_olap_descriptors where descriptor_value='Day';
    select descriptor_id into levelmonth_id from all_olap_descriptors where descriptor_value='Month';
    select descriptor_id into levelquarter_id from all_olap_descriptors where descriptor_value='Quarter';
    select descriptor_id into levelyear_id from all_olap_descriptors where descriptor_value='Year';
    begin
    cwm_olap_cube.drop_cube(USER, 'EMPLOYEMENT_CUBE');
    exception when cwm_exceptions.cube_not_found then null;
    end;
    cwm_olap_cube.create_cube(USER, 'EMPLOYEMENT_CUBE', 'EMPLOYEMENT_CUBE', '');
    id := cwm_olap_cube.add_dimension(USER, 'EMPLOYEMENT_CUBE', USER, 'JOB_DIM', 'JOB_DIM');
    id := cwm_olap_cube.add_dimension(USER, 'EMPLOYEMENT_CUBE', USER, 'DEP_DIM', 'DEP_DIM');
    id := cwm_olap_cube.add_dimension(USER, 'EMPLOYEMENT_CUBE', USER, 'EMP_DIM', 'EMP_DIM');
    cwm_olap_cube.map_cube(USER, 'EMPLOYEMENT_CUBE', USER, 'EMPLOYEMENT_CUBE', 'FK_EMPLOYEMENT_CUBE_14382', 'JOB_MAIN', USER, 'JOB_DIM', 'JOB_DIM', false);
    cwm_olap_cube.map_cube(USER, 'EMPLOYEMENT_CUBE', USER, 'EMPLOYEMENT_CUBE', 'FK_EMPLOYEMENT_CUBE_14362', 'DEP_MAIN', USER, 'DEP_DIM', 'DEP_DIM', false);
    cwm_olap_cube.map_cube(USER, 'EMPLOYEMENT_CUBE', USER, 'EMPLOYEMENT_CUBE', 'FK_EMPLOYEMENT_CUBE_14347', 'EMP_MAIN', USER, 'EMP_DIM', 'EMP_DIM', false);
    cwm_olap_measure.create_measure(USER, 'EMPLOYEMENT_CUBE', 'SALARY', 'SALARY', '');
    cwm_olap_measure.set_column_map(USER, 'EMPLOYEMENT_CUBE', 'SALARY', USER, 'EMPLOYEMENT_CUBE', 'SALARY');
    begin
    f_id := cwm_utility.create_function_usage('SUM');
    cwm_olap_measure.set_default_aggregation_method(USER, 'EMPLOYEMENT_CUBE', 'SALARY', f_id, USER, 'JOB_DIM', 'JOB_DIM');
    exception when others then null;
    end;
    begin
    f_id := cwm_utility.create_function_usage('SUM');
    cwm_olap_measure.set_default_aggregation_method(USER, 'EMPLOYEMENT_CUBE', 'SALARY', f_id, USER, 'DEP_DIM', 'DEP_DIM');
    exception when others then null;
    end;
    begin
    f_id := cwm_utility.create_function_usage('SUM');
    cwm_olap_measure.set_default_aggregation_method(USER, 'EMPLOYEMENT_CUBE', 'SALARY', f_id, USER, 'EMP_DIM', 'EMP_DIM');
    exception when others then null;
    end;
    commit;
    exception when others then dbms_output.enable(1000000); cwm_utility.dump_error(); raise program_error;
    end;
    processing classification type is := Warehouse Builder Business Area
    processing catalog name := KAFA_COLLECTION2 ,and description is := KAFA_COLLECTION2
    processing Cube
    processing catalog entity cube := EMPLOYEMENT_CUBE
    processing measure := SALARY , in a cube := EMPLOYEMENT_CUBE
    processing classification type is := Dimensional Attribute Descriptor
    declare
    id number;
    s_id number;
    l_id number;
    levelday_id number;
    levelmonth_id number;
    levelquarter_id number;
    levelyear_id number;
    f_id number;
    begin
    select descriptor_id into l_id from all_olap_descriptors where descriptor_value='Long Description';
    select descriptor_id into s_id from all_olap_descriptors where descriptor_value='Short Description';
    select descriptor_id into levelday_id from all_olap_descriptors where descriptor_value='Day';
    select descriptor_id into levelmonth_id from all_olap_descriptors where descriptor_value='Month';
    select descriptor_id into levelquarter_id from all_olap_descriptors where descriptor_value='Quarter';
    select descriptor_id into levelyear_id from all_olap_descriptors where descriptor_value='Year';
    begin
    id := cwm_classify.create_catalog('KAFA_COLLECTION2', 'KAFA_COLLECTION2');
    exception when cwm_exceptions.catalog_already_exists then
    SELECT catalog_id INTO id from all_olap_catalogs
    WHERE catalog_name = 'KAFA_COLLECTION2'
    AND parent_catalog_id is null;
    end;
    begin
    cwm_classify.add_catalog_entity(id, USER, 'EMPLOYEMENT_CUBE', 'SALARY');
    exception when OTHERS then null;
    end;
    commit;
    exception when others then dbms_output.enable(1000000); cwm_utility.dump_error(); raise program_error;
    end;
    declare
    s_dir varchar2(4000);
    begin
    dbms_odm.createdimlevtuple (USER, 'EMPLOYEMENT_CUBE');
    dbms_odm.createcubeleveltuple (USER, 'EMPLOYEMENT_CUBE');
    dbms_odm.createfactowb (1,USER, 'EMPLOYEMENT_CUBE');
    exception when others then raise program_error;
    end;
    declare
    s_dir varchar2(4000);
    begin
    dbms_odm.createdimowb (2,USER, 'DEP_DIM');
    dbms_odm.createdimowb (3,USER, 'EMP_DIM');
    dbms_odm.createdimowb (4,USER, 'JOB_DIM');
    exception when others then raise program_error;
    end;
    BRD-05030: Error occurred while executing the PL/SQL file, see log file for details.
    ORA-06501: PL/SQL: program error
    ORA-06512: at line 8
    ORA-29283: invalid file operation
    BRD-05030: Error occurred while executing the PL/SQL file, see log file for details.
    disconnecting ...
    closing output file
    closing log stream
    **! Transfer logging stopped at Sat Feb 05 09:21:41 IRST 2005 !**
    thanks,
    shima

    I have run into the same problem using oracle 8.1.6.1 with redhat 6.2..
    I have found out that only when I specify host ip in the mts_dispatchers the mts will work correctly..(specifying host domain name is no use)
    Here is a sample of the configuration, hope that helps..
    mts_dispatchers = "(address=(protocol=tcp)(host=192.168.0.1))(dispatchers=4)"

  • Warning messages thrown while trying to connect to BW Cube

    We have Websphere Application Server to deploy our servlets. The problem is when we connect to BW Server through BI Java SDK, it generates the following WARNING messages:
    [2/9/06 17:48:14:682 CET] 179cdd40 SystemOut     O Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    [2/9/06 17:48:14:682 CET] 179cdd40 SystemOut     O Error Message is :com/sap/guid/GUIDGeneratorFactory
    [2/9/06 17:48:14:688 CET] 179cdd40 SystemOut     O Warning ! Protocol Implementation [com.sap.security.core.client.ws.SecurityProtocol] could not be loaded (ClassNotFound) !
    [2/9/06 17:48:14:688 CET] 179cdd40 SystemOut     O Error Message is :com.sap.security.core.client.ws.SecurityProtocol
    [2/9/06 17:48:20:325 CET] 179cdd40 SystemOut     O Warning ! Provider [SecurityProtocol] not found for feature in logical port [MsXmlAnalysisSoap] !
    [2/9/06 17:49:25:069 CET] 179cdd40 WebGroup      I SRVE0180I: [Shell-CCL] [/Shell-CCL] [Servlet.LOG]: /jsps/cclMyOrderHistory.jsp: init
    [2/9/06 17:51:00:564 CET] 179cdd40 WebGroup      I SRVE0180I: [Shell-CCL] [/Shell-CCL] [Servlet.LOG]: CCLMyOrderHistoryDownloadServlet: init
    [2/9/06 22:08:23:755 CET] 7b749d56 SystemOut     O Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    [2/9/06 22:08:23:755 CET] 7b749d56 SystemOut     O Error Message is :com/sap/guid/GUIDGeneratorFactory
    [2/9/06 22:08:23:762 CET] 7b749d56 SystemOut     O Warning ! Protocol Implementation [com.sap.security.core.client.ws.SecurityProtocol] could not be loaded (ClassNotFound) !
    [2/9/06 22:08:23:762 CET] 7b749d56 SystemOut     O Error Message is :com.sap.security.core.client.ws.SecurityProtocol
    [2/9/06 22:08:24:943 CET] 7b749d56 SystemOut     O Warning ! Provider [SecurityProtocol] not found for feature in logical port [MsXmlAnalysisSoap] !
    Any clues on this one. What causes this and why?
    Thanks in advance.

    http://otn.oracle.com/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm#_59_
    The thin drivers are classes12.zip/classes111.zip. classes12.zip being the most recent release. You can download it from
    http://otn.oracle.com/software/tech/java/sqlj_jdbc/htdocs/winsoft.html
    (the general download site is http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html )
    Jamie

  • Unknown user type: oracle.jbo.domain.Date exception from time to time. How to solve?

    Hi,
    This is the first time I am using Coherence to cache some lists in my ADF Application. This is my objects configuration file:
    <?xml version="1.0"?>
    <!DOCTYPE pof-config SYSTEM "pof-config.dtd">
    <pof-config>
        <user-type-list>
            <!-- coherence POF user types -->
            <include>coherence-pof-config.xml</include>
            <!-- com.tangosol.examples package -->
            <user-type>
                <type-id>1001</type-id>
                <class-name>package.dataproviders.TFDO1Services</class-name>
            </user-type>
            <user-type>
                <type-id>1002</type-id>
                <class-name>package.dataproviders.TFDO2Services</class-name>
            </user-type>
        </user-type-list>
        <allow-interfaces>true</allow-interfaces>
        <allow-subclasses>true</allow-subclasses>
    </pof-config>
    I have implemented the portableObject interface to each of my objects and they look like this:
        @Override
        public void readExternal(PofReader pofReader) throws IOException {
            this.tfMyList = (ArrayList<GenericRowData>) pofReader.readObject(0);
        @Override
        public void writeExternal(PofWriter pofWriter) throws IOException {
            pofWriter.writeObject(0, this.tfMyList);
    Please any help would be great!

    Hi Alejandro,
    Please note that when POF serialize collections it is somewhat lossy, in that when you deserialize the collection you may get a different collection implementation.  I.e. you're list will come out as a an implementation of java.util.List but not necessarily a java.util.ArrayList, so just cast to the List interface.  If you absolutely need a certain class impl type then you can use the readCollection method passing in the list you wish to have populated.
    thanks,
    Mark

Maybe you are looking for

  • Exchange/Return policies

    What are Apple's exchange or return policies? I can't seem to find it anywhere in the support pages.

  • Balance sheet G/L account posting is not captured in the SLR budget report

    My case: While posting a schedule agreement ( which is account assigned to "project make to  order"), to G/L account, the following warning  message comes. " G/L account  is a balance sheet account". Although I am able to post the scheduled agrrement

  • How to hide application id and page number in url

    The url that displays in a live session on the internet displays the application id and the page number. How can I hide this information from the public user? Thanks, Maggie

  • Strange folder associations to dvd player

    Hello! I have very strange problem, some folders are associated within DVD Player. For instance when I click in dock on folder download, it shows me the fun and then when I press the arrow to see more items in folder it opens a DVD Player? Same probl

  • N80 + Ford BT connects for about 1 second

    My N80 connects to my new ford integrated bluetooth for about 1 second only. Ford displayes that phone is connected, Phone displays connection "car" icon and then drops out. I have checked the phones firmware and it is the latest. I believe that it m