JTA not fully implemented in J2EE (Sun Ref.) V1.4?

I have researched high & low on the internet, but have yet to find a success story where someone
has successfully acquired a reference to a "UserTransaction" object from within an EJB client.
(I am refering to Sun's J2EE Reference Implementation V1.4 only)
I have a simple client that attempts to lookup a UserTransaction, using "java:comp/UserTransaction",
so that I can drive a Transaction from the client. However, I get back the NameNotFoundException
exception from the JNDI lookup. (Note that I tried every other JNDI name suggested on the
internet as well with no luck. After reading the J2EE sources*, I have figured out that the above is
the 'official' JNDI name used to get the UserTransaction...if it exists at all.)
*In trying to figure out why this was happening, I downloaded the J2EE sources.   In them, I found
the classes that look like they implement this functionality. The package is:
com.sun.enterprise.distributedtx.
Unfortunately, none of the classes in this package seem to be in the binaries that ship as part of
Sun's J2EE ref Implementation V1.4. Did they get left out on purpose? Was it an oversight?
Am I missing something here?
I going to stop banging my head against the wall for a little while and just wait for a response.
Thanks,
Phil

Hi Phil,
As Alex mentioned, you will be able to access UserTransaction only from the web components and EJB components. J2EE spec does not require the transactions to be avaiable for appclients and other java clients.
From the web components, you should be able to lookup the UserTransaction by
InitialContext ctx = new InitialContext();
UserTransaction utx = (UserTransaction) ctx.lookup("java:comp/UserTransaction");
Same can be done from a BMT EJB. You could get UserTransaction from EJBContext also.
regards
sankar

Similar Messages

  • How much effort to do workflow if OM not fully implemented

    My client has only implemented a mini master HR to support their SAP Travel management. SAP is interfaced to Peoplesoft to populate the necessary HR infotypes.  OM has not been implemented.
    Ideally the client would like to provide workflow to improve on the existing Travel processes.
    Am I correct that OM must be populated with the necessary Org. structure & positions and associated Workflow necessary relationships.  Also employees would need to be linked, via integration to the positions.
    Finally they would like to implement Structural authorizations.
    My guess is that this would be a significant amount of work, not to mention ongoing maintenance, given that Peoplesoft is actually the HR system of record.
    Am I correct or is there a minimal way of doing this? 
    TIA,
    Ed

    Hello Ed,
    I am working with a client who is interested in creating an HR mini master to support the use of CATS integration with Timelink for tracking indirect labor among other things.  Peoplesoft is there system of record for HR data.  They are interested in finding out what options are available to interface SAP to Peoplesoft to keep the HR mini master synchronized between systems.  I see from your posting you have a client who has such an interface.  I owe my customer an estimate on what it will take to build this interface.  Can you give me an idea of what was involved?
    Thanks,
    Gary

  • Sub-administration seems to be not fully implemented

    Post Author: mrivney
    CA Forum: Administration
    Hi,
      I administrate a BOE XI rel 2 server (and a test/development one too). I see a flaw or limitation with 'sub-administration'. I can set up a folder for an application and then grant rights to the application's administrator. This application administrator or 'sub-administrator' can then create sub-folders, publish reports to the sub-folders, schedule reports, etc. However, I as the top administrator have to create the sub-administrator's groups and then give rights to the application administrator to update the group. 
      I can't truly give a 'slice-of-the-pie' administrative rights to an application administrator. The limitiation is that I still have to create the groups. If I allow rights to user groups for the sub-administrator, then the sub-administrator has rights to all the groups, which I don't want. Am I right? Any ideas to get around this?
    Regards, mrivney

    See the sample implementation code present in the class.
    CL_EXM_IM_ME_GUI_PO_CUST
    You need to implement the following methods
    need to create the function group, and 2 functions for setting and getting the values. and a sub screen.
    the same will be used in the below methods.
    SUBSCRIBE  " <---- Subscribe you need map the function group program , screen number etc
    MAP_DYNPRO_FIELDS " <--Mapping
    TRANSPORT_TO_DYNP "<--- Call the Function module to Set the value to screen
    TRANSPORT_FROM_DYNP "<--Call the function module to Get the value from screen

  • JNDI issue on sun ref app server

    I want to lookup a bean (Session/Entity/Message Bean) deployed on a SUN REF APP. SERVER from a different client machine. What should be specified for the JNDI lookup ?
    Note : If the bean is accessed from the same machine it is working properly.

    Using a Stand-Alone Client to Access an EJB Component
    To access an EJB component from a stand-alone client, perform the following steps:
    1. In your client code, instantiate the InitialContext:
    InitialContext ctx = new InitialContext();
    It is not necessary to explicitly instantiate a naming context that points to the CosNaming service.
    2. In the client code, look up the home object by specifying the JNDI name of the home object. For example:
    Object ref = ctx.lookup("jndi-name");
    BeanAHome = (BeanAHome)PortableRemoteObject.narrow(ref,BeanAHome.class);
    For more information about naming and lookups, see �Accessing the Naming Context� on page 239.
    3. Deploy the EJB component to be accessed. For more information on deployment, see �Tools for Deployment� on page 88.
    4. Copy the following JAR files to the client machine and include them in the classpath on the client side:
    * appserv-rt.jar - available at install_dir/lib
    * j2ee.jar - available at install_dir/lib
    5. To access EJB components that are residing in a remote system, set the values for the Java Virtual Machine startup options:
    jvmarg value = "-Dorg.omg.CORBA.ORBInitialHost=${ORBhost}"
    jvmarg value = "-Dorg.omg.CORBA.ORBInitialPort=${ORBport}"
    Here ORBhost is the Application Server hostname and ORBport is the ORB port number (default is 3700).
    This information can be obtained from the domain.xml file on the remote system. For more information on domain.xml file, see the Sun Java System Application Server Administration Reference.
    6. Run the stand-alone client. As long as the client environment is set appropriately and the JVM is compatible, you merely need to run the main class.

  • Creating an application server stub until the JCA is fully implemented

    Greetings,
              We have pretty much decided that the Java Connector Architecture is the
              way to go, when it comes down to integrating with EIS systems.
              However, the problem still remains that the JCA spec is not fully
              supported in the current beta release of the Connector implementation
              within WLS 6.0. In particular,
              I see that only non-transaction Resource Adapters can be deployed in
              this release (local transaction and XA transaction ones will have to
              wait until the full release in the summer).
              However, what our group wants to do is write XA-compliant Resource
              Adapters, even ahead of the actual support for them in the product. The
              issue for us is how to structyure our implementation so that we end up
              with a minimal re-write when the full implementation of the spec
              arrives.
              It seems to me that if I wanted to have support for XA-compliant
              Resource Adapters NOW, I would have to actually write some of the code,
              that would otherwise be part of the application server/container,
              myself. In particular, it is the code that "enlists" the XAResource
              object, which is associated with the ManagedConnection that an
              application bean asks for, with the Transaction Manager that is later
              going to coordinate things in the global XA transaction.
              Let me describe how I see things:
              when the application component calls into the Resource Adapter for a
              connection handle, the ConnectionFactory class according to the spec)
              delegates the call to the application server ConnectionManager (that it
              has been initialised with, typically at creation time), which in turn
              calls the createManagedConnection method of the ManagedConnectionFactory
              class inside the Resource Adapter.
              Now, I want to emulate the application server so that the
              ConnectionManager class is in fact implemented in my Resource Adapter.
              That I guess will not be a problem. However, the next thing IS (in the
              current BETA release): the application server code would normally
              retrieve the XAResource instance that is "hanging" off the
              ManagedConnection that has just been created and would "enlist" this
              with the Transaction Manager. Thereafter, everything would follow the
              normal XA transaction route, as the Transaction Manager would start
              calling back into the XAResource, notifying it on the status of the
              global XA transaction (start, end, prepare, commit, abort).
              Looking at the JTA specification, an in particular at what the
              application server code has to do, I see the following set of
              interactions:
              TransactionalResource res = ResourceFactory.getTransactionalResource();
              XAResource xaRes = res.getXAResource();
              (TransactionManager.getTransaction()).enlistResource(xaRes);
              <<<<<<<<<------------ how do/can I, in
              application code, within the Resource Adapter in fact, get hold of the
              TransactionManager instance? This is trivial when it is implemented
              within the app server code, but could I also do this?
              This will obviously be an interim solution for us: we will implement a
              very small part of the appliction server logic (you could call it a
              stub) around the registration of the XA resource with the global
              transaction manager. The aim is really to write something that will
              appear to our application beans as well as to the rest of the Resource
              Adapter as something that is behaving in the same way as the application
              server would (in the full implementation of the JCA spec), and would
              also ensure that neither our application component code nor our Adapter
              code would not have to be dramatically changed when that app server
              piece of the JCA-specified system contract implementation is in place.
              I realise that the APIs to the Transaction Manager implementation within
              WLS are "private" and that people may not want us to be using them. But
              it is the only way that I see for us to create something (Resource
              Adapters) which are a)XA compliant and b) will only have to change
              minimally, if at all, when the actual implementation is in place.
              I would appreciate any thoughts from BEA folks out there. Also, if you
              see another way of solving my problem (support global XA transaction
              within my Resource Adapters, AND minimal re-write) that I may be
              missing, I would appreciate your feeback around that.
              Many thanks in advance
              Kostas
              Kostas Karagianidis
              Technical Consultant
              PricewaterhouseCoopers
              Delta 602, Delta Business Park
              Swindon SN5 7XJ, Wiltshire
              United Kingdom
              Tel: +44 1793 536291
              Fax: +44 1793 529641
              Mobile: +44 7768 083452
              e-mail: [email protected]
              The information transmitted is intended only for the person or
              entity to which it is addressed and may contain confidential and/or
              privileged material. Any review, retransmission, dissemination or other
              use of, or taking of any action in reliance upon, this information by
              persons or entities other than the intended recipient is prohibited.
              If you received this in error, please contact the sender and delete the
              material from any computer.
              

    Did you sign your jar file for JWS? I don't think the security manager will allow a filebrowser if the jar is not signed.
    Edited by: Plee on Dec 29, 2008 6:54 AM

  • Goods receipt before an order is not fully consumed

    Hi all,
    can anybody tell me how to stop goods receipt before an order is not fully consumed?
    In my case the goods receipt is executing automatically by the confirmation.
    Thanks for your answers!

    Hi,
    You can control this requirement by activate User Exit or BADI, see below source code
    Take help with your ABAPer on this and modify as per your required
    User Exit
    Enhancement: MBCF0002
    Function module: EXIT_SAPMM07M_001
    Code for your copy pasting in the source code of ZXMBCU02.
    Remember to activate the program. In SMOD enter the enhancement, press F8 and then click on activate button.
    *& Include ZXMBCU02
    data: lt_resb type standard table of resb,
    wa_resb type resb.
    select * from resb into table lt_resb where aufnr eq i_mseg-aufnr and xloek eq space and bdmng gt 0.
    check sy-subrc eq 0.
    loop at lt_resb into wa_resb.
    if wa_resb-enmng < wa_resb-bdmng.
    message E499(sy) with 'Order is not fully consumed. Processing is STOPed'.
    endif.
    endloop.
    BADI
    Implement the BADI - WORKORDER_GOODSMVT in this there is method
    MANUAL_GOODS_RECEIPT under that
    write this code
    if_ex_workorder_goodsmvt~manual_goods_receipt.
    data: lt_resb type standard table of resb,
    wa_resb type resb.
    select * from resb into table lt_resb where rsnum eq i_order_header-rsnum and xloek eq space and bdmng gt 0.
    check sy-subrc eq 0.
    loop at lt_resb into wa_resb.
    if wa_resb-enmng < wa_resb-bdmng.
    message E499(sy) with 'Order is not fully consumed. Processing is STOPed'.
    endif.
    endloop.
    endmethod.
    Pls refer below thread
    https://forums.sdn.sap.com/post!reply.jspa?threadID=1284289
    Regards,
    Sankaran

  • Clientgen does not fully qualify superclasses

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

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

  • How to install j2ee sun app server 8.0 in debain linux

    hi guys
    i am new to linux and i have downloaded the j2ee sun app server 8.0(linuxversion) from sun.java
    in sun.java documentation says first we have to change the mode to excecutable
    then he is saying to do this
    1. To run the installation program that uses a graphical interface, at the command prompt type the name of the bundle file at the command prompt.
    2.To run the installation program that uses the command-line interface, at the command prompt type the name of the bundle file followed by the -console option.
    after chmod + x <bundle name >
    the next step i am not able to do it
    what to do next
    any suggestions
    regards
    sandeep

    Hi rlubke
    Thanks for the suggestion
    1.Change the permission of the bundle file so that you have execute access:
    chmod +x <bundle-file-name>
    2. To run the installation program that uses a graphical interface, at the command prompt type the name of the bundle file at the command prompt.
    3.To run the installation program that uses the command-line interface, at the command prompt type the name of the bundle file followed by the -console option.
    Step 1. After chmod + x <bundle name >
    Step 2. sun/appserver/# <bundle name>
    bash: <bundle name>: command not found
    Step 3. sun/appserver# <bundle name>
    bash: <bundle name#>: command not found
    any suggestions
    i have done what u have said now
    Step 1. After chmod + x <bundle name >
    Step 2. sun/appserver/#./ <bundle name>
    Checking available disk space....
    Checking Java(TM) 2 Runtime Environment...
    Extracting Java(TM) 2 Runtime Environment files...
    Extracting installation files...
    Launching Java(TM) 2 Runtime Environment....
    Error: There are no files requiring installation.
    Deleting Temporary files...
    Step 3. sun/appserver# <bundle name>
    Checking available disk space....
    Checking Java(TM) 2 Runtime Environment...
    Extracting Java(TM) 2 Runtime Environment files...
    Extracting installation files...
    Launching Java(TM) 2 Runtime Environment....
    Error: There are no files requiring installation.
    Deleting Temporary files...
    this is what happening excatly

  • Xsl:output function fully implemented in XSL-processor?

    I'm using XSL-processor as contained in the XML-parser version 2.0.2 in C.
    When changing the referring DTD of an incoming XML-message with following XSL-stylesheet
    <xsl:output method="xml"/>
    <xsl:output ommit-xml-declaration="no"/>
    <xsl:output standalone="no"/>
    <xsl:output doctype-system="someOther.dtd"/>
    nothing seems to happen.
    Is <xsl:output> already fully implemented in this C-version of the XSL-processor?
    Erwin

    Hi,
    The xsl:output is not yet implemented. This was specified in the README file.
    Thanks,
    Oracle XML Team
    null

  • Migrating Not fully paid  and Onhold invoices

    Hi All,
    we are reimplementing R12 from 11i and the requirement like need to migrate the "NOT FULLY PAID INVOICES" and "INVOICES ON HOLD". Can any one suggest me the process to do it. Please provide me the process or any PL/SQL packages available to do it or any reusable scripts to acheive this. The requirement is these type of invoices should migrated to new instance as it is.
    Edited by: 901928 on Dec 28, 2011 4:30 AM

    Hi,
    In case of a re-implementation, the process to be followed for any data migration is similar to that of a Go Live Cut-over from legacy system. However, in this case legacy is the R11 instance. The general process that is followed for migration of partly paid invoices is to migrate the unpaid amount only. The original invoice amount may be put in either description or any other narration/DFF. We had followed this approach for a customer and it was well accepted.
    We analyzed the option of bringing original invoice amount and found out that it would require bringing the associated payments and associated credit/debit notes. this meant bringing in a whole lot of data that was closed before.
    Regards,
    Udit

  • Method not yet implemented at javax.mail.internet.MimeMessage

    What will cause the following error?
    java.lang.UnsupportedOperationException: Method not yet implemented
         at javax.mail.internet.MimeMessage.<init>(MimeMessage.java:89)
         at com.pe.app.inhouse.module.util.DateUtilTest.testBB(DateUtilTest.java:61)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at junit.framework.TestCase.runTest(TestCase.java:154)
         at junit.framework.TestCase.runBare(TestCase.java:127)
         at junit.framework.TestResult$1.protect(TestResult.java:106)
         at junit.framework.TestResult.runProtected(TestResult.java:124)
         at junit.framework.TestResult.run(TestResult.java:109)
         at junit.framework.TestCase.run(TestCase.java:118)
         at junit.framework.TestSuite.runTest(TestSuite.java:208)
         at junit.framework.TestSuite.run(TestSuite.java:203)
         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478)
         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344)
         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)

    [http://www.google.com/search?hl=en&q=javax.mail.internet.MimeMessage+jar+download]

  • Xsl:output not yet implemented??

    Is the xsl:output tag implemented in oracle
    xslt?
    I've tryed this in an xsl file:
    <xsl:output method="xml" encoding="ISO-8859-1" omit-xml-declaration="no" doctype-system="Segnatura.dtd" indent="yes" />
    With another xslt processor produces this header:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE Segnatura SYSTEM "Segnatura.dtd">
    while with xdk the header is empty!!
    I'm doing something wrong or not?
    Please I really nead help on this topic.
    Thanks
    mauro

    We fully implement <xsl:output>
    the most common error is that programmer's accidentally use:
    DocumentFragment processXSL(xsl,xml)
    instead of the:
    void processXSL(xsl,xml,PrintWriter)
    Only the latter gives the XSLT processor a chance to control the serialization and implement the <xsl:output> hints.

  • EAC is not fully loading

    I'm using Exchange 2013 and after we restart the server the ECP page is not fully loading.
    I tried restart again and keeps the same. Can someone help me how to fix it?

    Hi,
    According to your description, I can understand that you can access EAC in exchange 2013 successfully, but there is an issue with incomplete page display. Have you tried it in other browsers?
    Please make sure you are using supported browsers for EAC access. If the issue also happens in IE, I suggest we can try to add this website into compatibility list to check whether the issue persists. To do it, we can try:
    Press Alt + T, and then click on Compatibility view settings, add this URL into compatibility list. For detailed information about this setting, please refer to:
    http://windows.microsoft.com/en-us/internet-explorer/use-compatibility-view#ie=ie-11-win-7
    Thanks,
    Winnie Liang
    TechNet Community Support

  • LSMW - RMDATIND - You have not fully maintained the tax classifications

    Hi,
    I am trying to extend existing materials to new sales organization through LSMW and direct input. I have only one file containing a "header" for the material general data, and "line items" to manage material taxes for other countries than the one defined for the current sales organization.
    I have created 2 nested structures as following:
    ZMATERIAL_ALL (parent structure)
              |__ ZMATERIAL_TAXES (child structure)
    In the structure fields, the first field is the header or line identifier:
    ZMATERIAL_ALL
              |__ HEADER -> With Identifying Field Content = H
              |__  ZMATERIAL_TAXES
                    |__ LINE -> With Identifying Field Content = L
    Header and line item have a common field MATNR and VKORG. ZMATERIAL_ALL contains data for sales org GI37, Japan. ZMATERIAL_TAXES contains data for France taxes (sales org GI10).
    The structure of my file is the following:
    H
    MATNR
    VKORG
    VTWEG
    SPART
    WERKS
    DWERK
    VERSG
    KTGRM
    MTPOS
    MTVFP
    LADGR
    J_3APIND
    VMSTA
    VMSTD
    DISMM
    DISPO
    DISLS
    FHORI
    MRPPP
    PLIFZ
    J_3AMSTATC
    TATYP1
    TAXKM1
    L
    MATNR
    VKORG
    ALAND1
    TATYP1
    TAXKM1
    ALAND2
    TATYP2
    TAXKM2
    In LSMW step 5, I associate ZMATERIAL_ALL structure tax values to BMMH1, because this taxe correspond to the tax for the current sales org defined in the current country:
    TATY1          Tax category (sales tax, federal sales tax,...)
                        Source:  ZMATERIAL_ALL-TATY1 (Tax category (sales tax, federal sales tax,
                        Rule :   Transfer (MOVE)
                        Code:    BMMH1-TATY1 = ZMATERIAL_ALL-TATY1.
    TAXM1         Tax classification material
                        Source:  ZMATERIAL_ALL-TAXM1 (Tax classification material)
                        Rule :   Transfer (MOVE)
                        Code:    BMMH1-TAXM1 = ZMATERIAL_ALL-TAXM1.
    Then in BMMH2, I associate tax values from ZMATERIAL_TAXES structure:
    __END_OF_RECORD__   After Using Conversion Rules
                        Rule :   Default Settings Modified
                        Code:    bmmh2-aland = zmaterial_TAXES-ALAND1.
                                 bmmh2-TATY1 = zmaterial_TAXES-TATYP1.
                                 bmmh2-TAXM1 = zmaterial_TAXES-TAXKM1.
                                 transfer_record.
                                 bmmh2-aland = zmaterial_TAXES-ALAND2.
                                 bmmh2-TATY2 = zmaterial_TAXES-TATYP2.
                                 bmmh2-TAXM2 = zmaterial_TAXES-TAXKM2.
                                 transfer_record.
    In LSMW step 7, I specify my single file with option "Data for multiple source structures".
    In step 8, I assign my file to both ZMATERIAL_ALL and ZMATERIAL_TAXES structures.
    In step 9 and 10, I can successfully read and display data. ZMATERIAL_ALL and ZMATERIAL_TAXES structures are well populated.
    The conversion is ok, then I run the RMDATIND program to perform the material creation.
    The result is "You have not fully maintained the tax classifications"
    Any idea what I am missing ?
    Thanks in advance for your help.
    Thibault

    The solution was to implement SAP Note 1730652, and it solved the issue !
    This was a standard SAP issue, and not an implementing issue.

  • Network Not Fully Routed & DNS Resolution

    I have a large domain with multiple sites, recently we have been bringing up new sites that are connected via VPN, unfortunately these are not fully routed to the other sites, and only have routes to the main hub data centre. We have been trialling RODC's
    at these new sites due to the insecure nature of the server locations.
    These have been adding new challenges with resolving our DNS domain name, the local DNS server hands back a list of servers that are authoritative for the domain, but due to the nature of the network routing the clients at these sites may only be able to reach
    5% of the servers. This results in slow machine startup times, as an isolated event we could live with this, but we also use domain based DFS and this is also affected with very slow performance as the clients try to resolve the UNC
    example: \\domain.local\Data1
    Where domain.local resolves to 50 IP addresses, and only a small percentage can be reached.
    We have been adding host files to the clients at these sites, but I was wondering if there was a more elegant solution to the issue, I'm sure that many people are in the same position and I think I may be missing something here.

    hi,
    For Branch office site where you have implemented RODC that site users will initially synch there password first time with RWDC. Once there password is cache users will be able to query and authenticate to local RODC. If users experiencing the
    slowness while access the files in that case what is the bandwidth consume during that period. Also possible check the following ports are open
    DC --> RODC
    ===========
    TCP 135               
    TCP Static 53248  
    TCP 389               LDAP
    RODC --> DC
    ===========
    TCP 49152-65535             LSASS                                   
    2
    TCP 57344                       DRSUAPI, LsaRpc, NetLgonR     3
    TCP Static 53248              FrsRpc                                   
    1
    TCP 135                          EPM
    TCP 389                          LDAP
    TCP 3268                        GC, LDAP
    TCP 445                          DFS, LsaRpc, NbtSS, NetLogonR, SamR, SMB, SrvSvc
    TCP 53                            DNS
    TCP 88                            Kerberos
    UDP 123                          NTP
    UDP 389                          C-LDAP
    UDP 53                           DNS
    TCP 5722                        DFS-R
    TCP and UDP 464             Kerberos Change/Set Password
    you said you are making entries in host files for DNS name resolutions. go though below link and forum which will help you troubleshoot further.
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/76e8654a-fbba-49af-b6d6-e8d9d127bf03/firewall-ports-for-rodcs-in-a-dmz-a-definitive-list
    https://technet.microsoft.com/en-us/library/dd728028(WS.10).aspx

Maybe you are looking for

  • How to find the path of Files (e.g. *.PDF,DOC,XLS) seen on PLMCfolders web?

    Hi, I am working on a requirment "Passing Cfolders documents/attachments to a third party document managemnt system. Question : Is it possible to see all the files which are uploaded in Cfolders like the ones seen in R/3 transaction AL11 at Unix leve

  • Problem with the Value property node (MacOS)

    As far as I have tested it, Value Property nodes (and Value (signaling)) don't work in MacOS : The value property appears as a boolean, the value(signaling) as a cluster (width, height). Even with boolean controls, the node is not working. No such pr

  • How to enable/disable the input fields based on the data entered/user action in the web dynpro abap?

    How to enable/disable the input fields based on the data entered in the web dynpro application abap?  If the user enters data in one input field then only the next input field should be enabled else it should be in disabled state. Please guide.

  • 2 Milllion Pixels

    Hi. After uploading my ePub file using iTunes Producer, I got an email from apple: Your book, vendor ID: ... , could not be delivered. The following images are larger than two million pixels and must be resized: I had a look at all my images that I'm

  • My question hasn't appeared in the forum ...

    Earlier today I posted a question on this forum - now, there's no sign of it; not in the general forum, or listed in my stuff.  This is the first time I've used this forum and I'm wondering if I'm doing something wrong?  My post was there immediately