Namespace error

Hi all
hi Andrei1
I had tried your code and I had extended the class to
MovieClip and used it as document class, but I have this error:
5006: An ActionScript file can not have more than one
externally visible definition: MyPackage.colors, MyPackage.fruits
this is all code:
package MyPackage{
import flash.display.MovieClip;
namespace colors= "
http://www.domainname.com/blah/colors"
namespace fruits= "
http://www.domainname.com/blah/fruits"
public class MyClass extends MovieClip {
// the same variable name - different namespaces
colors var orange:uint = 0xF88017;
fruits var orange:String = "Kind of citrus";
public function MyClass() {
// namespace qualifier is :: - this is how you get the
variables
trace(colors::orange);// Displays: 0xF88017
trace(fruits::orange);// Displays: Kind of citrus
}

I knew the problem it initialize the class before entering
the time line so I put the code in another function and call it
works.

Similar Messages

  • Invalid application discriptor: Unknown namespace error

    Hi all I am using flash Builder 4.6. I am working on google eyes project, this was created on flex 3.1 but I am using flash builder so I need to update it's sdk so i update it's sdk to 4.6.0, here I am getting an compilation error. Invalid application discriptor:Unkown namespace error

    It seems like you  have replaced the folder, /Applications/Adobe\ Flash\ Builder\ 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK
    This folder is used when creating an ActionScript project or ActionScript Mobile project. However, for a Flex Project, the SDK used is the same as used to be previously, /Applications/Adobe Flash Builder 4.7/sdks/4.6.0/ in your case. You will either need to use a ActionScript project or overlay the Flex SDK present at /Applications/Adobe Flash Builder 4.7/sdks/4.6.0/ with the AIR SDK you wish to use.
    You can find instructions for the same at:
    http://helpx.adobe.com/x-productkb/multi/how-overlay-air-sdk-flex-sdk.html
    http://helpx.adobe.com/flash-builder/kb/overlay-air-sdk-flash-builder.html

  • BPEL: invalid namespace error with DB adapter polling and java embedding

    Hello
    I'm using bpel 10.1.3.1.0, and I'm experiencing the following problem: I'm am not able to use the SetTitle() function in a process which polls for records using the db adapter.
    Steps to reproduce the problem:
    - I create a very simple bpel process which poll for records in a table.
    - I deploy it, write manually a record in the polled table and the process start.
    - I can see the record picked up through the visual flow in the console
    - everything looks ok and the process ends correctly
    - now I add a java embedding activities just after the receive
    - I set the instance title like this: setTitle("Go");
    - redeploy, write a record in the polled table and the process start.
    - but the process ends in error with the following message "XMLDOMException has been thrown. invalid namespace for prefix xmlns"
    And there is no way to make it work. Consider:
    If I put the same java embedding activity in another process, for example a simple asynchronous process which just copy the input to the output, and I run from the console, the instance title is set as I want ("Go")
    If I remove the three lines from the polling process
    <bpelx:exec name="Java_Embedding_1" language="java" version="1.3">
    <![CDATA[setTitle("Go");]]>
    </bpelx:exec>
    then the process is executed correctly again. I add them again and then namespace error.
    Whatever statement I put in the java embedding activity (for example a string concatenation or even just a comment I have the same result: invalid namespace for prefix xmlns.
    Does anybody has a suggestion to evercome the problem? I need to set the title because its a mess to find out which instance processed a specific record.
    Thanks by
    Paolo

    I made a lot of further tests, and I can say the problem is related only to the database adapter polling mechanism.
    If I create an asynchronous process, with any kind of database activity (for example select) I can set the title normally.
    If I create a process which start with database table polling, then I cannot use the java embedding.
    try this:
    - create BPEL empty project
    - drop a database adapter service and follow the wizard:
    - select a connection (I tried both oracle or sqlserver connection)
    - select "poll for new or changed record"
    - select any table empty or with few record inside (1 or 2)
    - press next 4 times
    - chose delete record after read (press next)
    - chose order by "no ordering" in polling options (press next 2 times)
    - now drop a receive activity on the process, and connect with the polling partner link
    - drop a java embedding and write any valid java statement
    - deploy; if the table is empty, write a recod in the table
    - the process is instantiated, but the it fails in the --> receive <-- activity with "invalid namespace" error

  • Namespace Error when generating Client Proxy for Java Web Service

    Hi.Experts:
        When I want to generating a Client Proxy for my WSDL file created by JAVA,it seems that some namespace errors occur.
        The error like this:
        "Incorrect value: Unknown Namespace http://sql.java
        Exception of class CX_SLIB "
       I checked all the SOAP runtime,it seems no error.So do I need to create the objects in the Integration Repository??If it is the truth,then how can I do it.
    Best Regards
    Martin Xie

    Hi Martin
    I didn't find this options in SAP GUI Create -->Enterprise Service ->Consumer Service ->url/http
    Maybe my version is different.
    You say that you can select the file ou url.
    Did you select the file or url?
    If was file, open this file, find the tag that you have the wrong namespace and eliminate this tag.
    If was url, access this url, copy the xml and same in one file, then select this file in the step above.
    I don't know if works, its only a suggestion.
    regards
    Marcos

  • Namespace error when reversing xml file

    Hi everybody,
    I am using ODI 11.1.1.5.0 and an Oracle 11g database.
    I have an xml file generated by a web service that I cannot reverse engineer in ODI.
    The xml file is called responseFile. xml on disk C.
    The content of the xml file is like this:
    <?xml version = '1.0' encoding = 'ISO-8859-1'?>
    <n0:ZMODIFY_CLOCO_TASK_LOGResponse xmlns:n0="urn:sap-com:document:sap:rfc:functions">
    <LOG_MESSAGE>
    etc .......
    In topology manager, I created an XML data server:
    daya server Name: F_Response
    JDBC driver: com.sunopsis.jdbc.driver.xml.SnpsXmlDriver
    JDBC url: jdbc:snps:xml?f=c:/responseFileDiesel.xml&s=RESPO
    For the physical schema I specified:
    SCHEMA: RESPO
    WORK SCHEMA: RESPO
    I used the value RESPO for the schema name because the documentation says: 'the schema name (variable s) must be the name of the relational schema where the xml file will b loaded.
    if this property is missing, a schema named after the first five letter of the xml file will automatically be created.'
    When testing the data server in Topolgy or reversing in Designer, I get the error:
    [2012-01-18T15:16:44.157+01:00] [odi] [ERROR] [] [oracle.odi.jdbc.driver.xml] [tid: 3320] [ecid: 0000JJlB4D0FS8T5qBL6iY1F3g1P0000o9,0] ODI-40837: An error occurred during the creation of the schema: ODI-40750: The model generated by the model mapper was not accepted by a validator: Model not accepted: ODI-40817: Namespace not found:
    What is that I do wrong? What is this xml's namespace? Should I use it for the JDBC url?
    I appreciate any help, I am completely blocked.
    thank you,
    Daniela
    Edited by: daniela.alexandru on Jan 18, 2012 4:02 PM

    Hi Daniela,
    The only time I've seen namespace errors was when using the incorrect driver, not XML in my case but the same ODI error.

  • DOM003 Namespace error

    i get a org.w3c.dom.DOMException: DOM003 Namespace error
    when i try to set a name space prefix.
    this is the snippet .
         Document d ;//d is initialised
         org.w3c.dom.Attr at =d.createAttributeNS("http://mydomain","yyy");
                   org.w3c.dom.Element e =dm.createElement("name");
                   e.setAttributeNodeNS(at);
                   e.setPrefix("yyy");
                   dm.appendChild(e);
    am i missing something here?
    this is my expected xml
                   <yyy:name xmlns:yyy="http://mydomain.com/xml/spec">
                        <add> some add</add>
                         <age>25</age>TIA
    vasanth

    thx dossot.
    this was the reply i got from apache user group
    Actually, createAttribute creates an Attr which is not fully compatable
    with namespace-aware processing. It is *NOT* equivalent to calling
    createAttributeNS() with the namespace either blank or null.
    DO NOT use createAttribute(), setAttribute(), setAttributeNode() or
    createElement() if you have any choice whatsoever. Nodes produced using
    DOM2 calls will be compatable with DOM1... but the reverse is *not* true.
    (The DOM Working Group wanted to deprecate these old methods to avoid this
    confusion. But since DOM Level 1 is not itself deprecated, and since we
    wanted to let people use DOM2 parsers with their old DOM1 applications,
    that wasn't an available option. Somewhat unfortunate, but it's what we're
    stuck with now.)
    To create an element with name "name" in namespace "http://mydomain",
    try
    dm.createElementNS("http://mydomain", "name");
    Yep. Obviously you can also use a prefix, if desired:
            dm.createElementNS("http://mydomain", "myprefix:name");
    ... the prefix is not very meaningful to a namespace-aware XML
    application, but it is retained and most serializers will try to use it.
    Note that it's the serializer's responsibility to make sure that an
    appropriate namespace declaration for that prefix is present, either on
    this element or inherited from an ancestor.
    You *can* explicitly create namespace declaration attributes, if you want
    to control where they should appear rather than leaving that up to the
    serializer. The trick is they have to use the "namespace for namespaces"
    -- for example,
    createAttributeNS("http://www.w3.org/2000/xmlns/","xmlns:myprefix","http://mydomain")createAttributeNS("http://www.w3.org/2000/xmlns/","xmlns","http://aDefaultNS");
    But the declarations do not affect which namespaces other nodes are
    actually in; that's set when those nodes are created.
    For the current official word on this topic, see
    http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#Namespaces-Considerations
    DOM Level 3 has proposed adding a standard namespace normalization
    algorithm, which is used by the Load/Safe feature and can also be run on
    request against an in-memory DOM.. Details are still subject to change,
    but the current description can be found in the Working Draft at
    http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations
    (which may also clarify some of the DOM2 language.)
    Hope that helps. Adding namespaces to XML as an afterthought caused a bit
    of a mess, and the DOM APIs happen to be one of the places where that's
    most visible. If we had it all to do over again, I'd have preferred to see
    the Infoset developed first -- with namespaces and schemas and some of the
    other late additions -- and then derive both the DOM API *and* the XML
    syntax from that. But that really wasn't an option given how quickly
    everyone wanted to start _using_ XML. Oh well; maybe someday there'll be
    an XML 2.0 and we'll be able to polish it all to a high gloss...
    "

  • Namespace Errors System Error 1355 - Specified domain does not exist or could not be contacted

    Ok, lets start with my environment:
    dc1 - windows server 2003 r2
    dc2 - windows server 2012 r2
    fs1- windows server 2003 r2
    fs2 - windows server 2012 r2
    Namespace - \\<fqdn>\data  (the fqdn would be like contoso.microsoft.com)
    I am in the process of migrating everything from server1 to server2 (dc and fs listed above).  I am done with mostly everything except DFS.  I have migrated the data, setup permissions, shares, etc. and replicated the data between fs1 and fs2.
     I have verified that all data is currently replicated and up to date, so no backlogs.  I am trying to add dc2 and fs2 as namespace servers.  This is so that I can point all of the referrals to FS2 that way when I remove FS1 no one gets an error
    about not being able to find the files.  The problem is that from all 4 servers, I receive an error message when loading the namespace via DFS Management tool.  I then thought because of the drastic differences between the versions, the next best
    thing would be to export the namespace and then import it into the new server, but even attempting the export command (dfsutil) gives me the same error.  My suspect is that the original namespace server was removed sometime ago without the previous IT
    person properly migrating everything (but I am at a loss cuz here I am).  I then thought if I go through ADSIedit, I can change the namespace server to the new one for all of my shares, and then possibly be able to load the namespace within the MMC tool
    (again just a guess); however, I cannot find anything listed for namespace or remoteservers under the properties of the share.
    Note:  the namespace does work when I navigate to it from a PC.  \\contoso.microsoft.com\data does bring up folders and files.  (changed the name for obvious reasons)
    At this point, I just want to have my new namespace server, so that I can change the referrals, and decommission my other servers.  (And yes there are many other steps I need to perform for the decommissioning, but that's not the point of this).  I
    have read numerous articles on this and haven't found a way to accomplish what I want.  Even though I walked through the steps listed for those issues and unfortunately they either did not apply or did not work.  I prefer to not use ADSIedit if at
    all possible, simply because it's not the "clean" way of doing things, but if I have no other option then I have no other option.
    Edit 1:  In event viewer on dc1, under File Replication Service on the left hand side, I see the following error appear numerous times (not every day, but still a lot).  I have not performed any of the steps listed simply because
    I do not know if this pertains to my problem and I don't want to start troubleshooting a server I plan on decommissioning unless I need to (say for the above issue):
    Event ID:  13568
    Source: NtFrs
    Description:
    The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. 
     Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" 
     Replica root path is   : "c:\windows\sysvol\domain" 
     Replica root volume is : "\\.\C:" 
     A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons. 
     [1] Volume "\\.\C:" has been formatted. 
     [2] The NTFS USN journal on volume "\\.\C:" has been deleted. 
     [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. 
     [4] File Replication Service was not running on this computer for a long time. 
     [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:". 
     Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. 
     [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication
    Service. 
     [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. 
    WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again. 
    To change this registry parameter, run regedit. 
    Click on Start, Run and type regedit. 
    Expand HKEY_LOCAL_MACHINE. 
    Click down the key path: 
       "System\CurrentControlSet\Services\NtFrs\Parameters" 
    Double click on the value name 
       "Enable Journal Wrap Automatic Restore" 
    and update the value. 
    If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Edit 2: I have verified that firewalls are off and I can communicate to all 4 servers from each other.
    Edit 3:  Attempted to try and fix error reported in 'Edit 1'; however the registry key mentioned does not exist (looked at all 4 servers to verify).

    I think in your situation it would be worth trying the things listed under the event. It does have to do with FRS and it's easy to do. I've used it to fix journal errors after a server unexpectedly restarts and sysvol stops replicating.  I
    could see where it could fix your issue, and if it doesn't, you're out 5 minutes. :)
    The listed registry key does not exist
    Expand HKEY_LOCAL_MACHINE. 
    Click down the key path: 
       "System\CurrentControlSet\Services\NtFrs\Parameters" 
    Double click on the value name 
       "Enable Journal Wrap Automatic Restore" 
     

  • Namespace Error, while creating proxy for a WSRP producer(Created on Exo)

    Hi ,
    I have implemented and deployed WSRP producer on Exo portal container. When I was trying to create proxy for the same in weblogic portal 10.2 its giving me the following error. Upon submiting the WSDL URL
    !ENTRY com.bea.wlp.eclipse.common 4 4 2008-12-08 13:46:27.540
    !MESSAGE NAMESPACE_ERR
    !STACK 0
    org.w3c.dom.DOMException: NAMESPACE_ERR
         at weblogic.xml.domimpl.ElementNSImpl.<init>(ElementNSImpl.java:74)
         at weblogic.xml.saaj.SOAPElementImpl.<init>(SOAPElementImpl.java:40)
         at weblogic.xml.saaj.SaajDocument.createElementNS(SaajDocument.java:63)
         at com.bea.wsrp.util.DomUtils.createChildElement(DomUtils.java:386)
         at com.bea.wsrp.util.DomUtils.addChildElement(DomUtils.java:406)
         at com.bea.wsrp.util.DomUtils.addChildElement(DomUtils.java:371)
         at com.bea.wsrp.bind.serviceDescription.GetServiceDescriptionRequest.writeTo(GetServiceDescriptionRequest.java:40)
         at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:129)
         at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:80)
         at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:68)
         at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:57)
         at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.getServiceDescription(ProducerAgent.java:99)
         at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.<init>(ProducerAgent.java:57)
         at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.<init>(ProducerAgent.java:45)
         at com.bea.wlp.eclipse.wsrp.portletbuilder.wizard.wsrp.SelectProducerPanel$ProducerInfoRunner.run(SelectProducerPanel.java:690)
    Could any one help me to solve this problem.
    Thanks & Regards,
    Naresh

    Hi Nate,
    Please find the following wsdl.
    <?xml version="1.0" encoding="UTF-8" ?>
    <wsdl:definitions targetNamespace="http://localhost:8080/wsrp/services/Version" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://localhost:8080/wsrp/services/Version" xmlns:intf="http://localhost:8080/wsrp/services/Version" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <!--
    WSDL created by Apache Axis version: 1.4
    Built on Nov 19, 2006 (02:31:34 GMT+00:00)
    -->
    <wsdl:message name="getVersionRequest" />
    <wsdl:message name="getVersionResponse">
    <wsdl:part name="getVersionReturn" type="soapenc:string" />
    </wsdl:message>
    <wsdl:portType name="Version">
    <wsdl:operation name="getVersion">
    <wsdl:input message="impl:getVersionRequest" name="getVersionRequest" />
    <wsdl:output message="impl:getVersionResponse" name="getVersionResponse" />
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="VersionSoapBinding" type="impl:Version">
    <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="getVersion">
    <wsdlsoap:operation soapAction="" />
    <wsdl:input name="getVersionRequest">
    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://axis.apache.org" use="encoded" />
    </wsdl:input>
    <wsdl:output name="getVersionResponse">
    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/wsrp/services/Version" use="encoded" />
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="VersionService">
    <wsdl:port binding="impl:VersionSoapBinding" name="Version">
    <wsdlsoap:address location="http://localhost:8080/wsrp/services/Version" />
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Thanks & Regards,
    Naresh

  • Can't deploy due to Namespace error in ADF lib

    Hi,
    When deploying I'm getting a Namespace not valid error. Because adf-faces-impl-1013.jar contains XML files with a not valid namespace: http://xmlns.oracle.com/adf/view/faces/agent/capabilities.
    Please find below the error message:
    GRAVE: jar:file:/D:/WebLogic103/user_projects/domains/My_Domain/lib/adf-faces-impl-1013.jar!/META-INF/agent/capabilities.xml: Parsing error, line 2, column 89:
    org.xml.sax.SAXParseException: Espace de noms non valide : http://xmlns.oracle.com/adf/view/faces/agent/capabilities
    at org.apache.myfaces.trinidadinternal.agent.parse.CapabilitiesDocumentParser.startElement(CapabilitiesDocumentParser.java:114)
    Have you got any idea to solve my problem? Either indicating a good namespace which actually I don't know, or configuring Weblogic to avoid this validation? Or something else...
    Environment: eclipse ganymede 3.4 , Oracle Enterprise Pack (OEPE), Weblogic 10.3, ADF faces
    Thank you for your help

    Hi,
    Actually the good library to use is: adf-richclient-impl-11.jar
    After removing the old one from my classpath no more errors.
    (thank you Maroun ;-)

  • Namespace error with axis2

    Hi,
    I have created a simple web service with Eclipse, Axis and 2 plugins Axis Codegen 1.3, Axis Service archiver 1.3 (I do the service according to the guide in this page
    http://wso2.org/library/1719) but I have this error
    org.apache.axis2.AxisFault: namespace mismatch require http://example.ws found http://example.ws/xsd
         at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
         at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
         at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
         at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
         at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
         at ws.example.TemperatureConverterStub.c2FConvertion(TemperatureConverterStub.java:440)
         at ws.example.TemperatureConverterServiceClient.main(TemperatureConverterServiceClient.java:12)
    Please help me !
    Thanks !

    Looks like error is clear namespace mismatch...try changing the following url in wsdl and regen the code
    http://example.ws found http://example.ws/xsd

  • Namespace error with JAXB

    Hello everyone! This is my problem:
    I am using jaxb to unmarshall a xml file. When I unmarshall, the program doesn�t work at this point:
    JAXBContext jc = JAXBContext.newInstance("com.claynet.core.clom");
    Unmarshaller u = jc.createUnmarshaller();
    u.setValidating(true);
    Clom clom =
    (Clom)u.unmarshal(
    new FileInputStream( ".." + File.separatorChar +
    "webapps"+ File.separatorChar + "claybrary" + File.separatorChar
    + "objetosCLOM" + File.separatorChar + file_name.trim()) );
    The error I get is the following one:
    javax.xml.bind.UnmarshalException: Probably namespace URI of tag "clom" is wrong (correct one is "http://www.clayformacion.com/xsd/clomv1.0")
    - with linked exception:
    [com.sun.msv.verifier.ValidityViolation: Probably namespace URI of tag "clom" is wrong (correct one is "http://www.clayformacion.com/xsd/clomv1.0")]
    The problem seems to be a conflict with the namespace, but the schema has the namespace correctly set:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:clom="http://www.clayformacion.com/xsd/clomv1.0" xmlns="http://www.clayformacion.com/xsd/clomv1.0" targetNamespace="http://www.clayformacion.com/xsd/clomv1.0" elementFormDefault="qualified">
    The validation inside the unmarshalling crash.
    Is there any errors with the code? Can Anyone help me?
    Thanks

    Looks like error is clear namespace mismatch...try changing the following url in wsdl and regen the code
    http://example.ws found http://example.ws/xsd

  • BI Template Preview Failing with Namespace error

    Narrowed down my complex report problem to this example -
    1. BI 11g desktop version installed, working with 12i
    2. Created an HelloWorld.rtf from following HellowWorld.xml, validated no errors, preview in PDF from desktop - worked fine.
    3. Created data definition and template in Oracle. Uploaded rtf and xml file.
    4. While preview - exception oracle.xdo.parser.v2.XPathException: Namespace prefix 'ref' used but not declared.
    This xml file provided in BI sample data. When I uploaded Oracle provided rtf and xml it works fine. That means xml file is good, template and data definition are good.
    Here is how i am created template -
    1. Open word 2007
    2. Load xml data, loaded successfully
    3. Open Table/Form - Drag row set - select all nodes
    4. Save
    5. Validate and preview desktop successfully.
    6. Error only after uploading to Oracle
    BI Option - i have right jre path, version 1.6.02. So looks like no issues there....
    What i am missing here? Appreciate your help.
    XML:
    <?xml version="1.0" encoding="UTF-8"?>
    <DATA>
    <NAME>Template Expert</NAME>
    <DESCRIPTION>Congratulations on your first Template</DESCRIPTION>
    </DATA>

    Hi,
    Please add the sapmsSID entries for both systems (java and abap) in the /etc/services file of BOTH SERVERS. This means that each server should have entries for every system in your landscape.
    Additionally, please ensure that this is set to 36<NN> and not 8100 as you mentioned. The reason is that 8100 is ABAP HTTP port, but 36<NN> is message server port. These two are different.
    Try this.
    Regards,
    Shitij

  • 10.1.3.2 migration results in "not a registered TLD namespace error".

    After migrating from 10.1.3.1 to 10.1.3.2 JDEV I received the following error message in many jsps:
    Error(11): "http://jakarta.apache.org/taglibs/xtags-1.0" is not a registered TLD namespace.
    Error(5): "http://jakarta.apache.org/taglibs/dbtags" is not a registered TLD namespace.
    These were not standard taglibs; they were part of the old application. I got the same errors in 10.1.3.1 but got around them by registering the taglibs.
    Here's the web.xml entries from 10.1.3.2. They are identical to the web.xml entries from 10.1.3.1
    <taglib version="2">
    <taglib-uri>http://jakarta.apache.org/taglibs/xtags-1.0</taglib-uri>
    <taglib-location>/WEB-INF/xtags.tld</taglib-location>
    </taglib>
    <taglib version="2">
    <taglib-uri>http://jakarta.apache.org/taglibs/dbtags</taglib-uri>
    <taglib-location>/WEB-INF/dbtags.tld</taglib-location>
    </taglib>
    Any ideas? other places to check?

    Your suggestion helped to resolve my issue. However, in addition to the steps you outlined I had to go into JDev 10.1.3.2 -> Project Properties -> Libraries -> Edit ->
    and edit the library properties to add classpath and sourcepath entries.
    I'd still like to know why the migration from 10.1.3.1 unmapped the libraries.
    --- Original Message ---
    Hello Stephen,
    Here is what I did:
    JDev 10.1.3.2 -> Project Properties -> JSP Tag Libraries ->
    Distributed Libraries -> Add -> User -> New
    and you can import the tld/jar file and it will register the
    library in Jdev.
    After that it works fine, although you have to put (jaxp,
    xalan, crimson, dom4j) in your project lib.
    This setting are good enough for Jdev runtime, but when you
    deploy the application on the server, you also need to have
    web.xml changes as per you mentioned.
    Hope this helps, otherwise let me know and I can send my working
    project with JSPs to you.
    Regards,
    Chintan

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

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

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

  • Clientgen error: Schema namespace error

    Hi
    I am trying to generate a client jar using weblogic 8.1 for a webservice deployed using AXIS and I get the following error:
    generate-client:
    [clientgen] Generating client jar for http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService?wsdl ...
    [clientgen] weblogic.xml.schema.model.XSDException: Unable to resolve definition for ['http://ttdvd12.ebiz.verizon.com
    :8080/baais_wrelay/services/VOIPService']:impl:ArrayOf_xsd_string perhaps due to the lack of an import statement for n
    amespace http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService
    [clientgen] at weblogic.xml.schema.model.XSDSchema.getSchemaForName(XSDSchema.java:1062)
    [clientgen] at weblogic.xml.schema.model.XSDSchema.lookupTopLevelObjectImpl(XSDSchema.java:893)
    [clientgen] at weblogic.xml.schema.model.XSDSchema.lookupTypeImpl(XSDSchema.java:881)
    This seems to be a weblogic specific problem as it seems to work with AXIS client.Appreciate help in resolving this issue.
    Here is the WSDL:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <wsdl:definitions targetNamespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xmlsoap" xmlns:impl="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" xmlns:intf="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="urn:cem_dictionary.dictionary.cem.beans.wrelay" xmlns:tns2="urn:ngvs_dictionary.dictionary.ngvs.beans.wrelay" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <wsdl:types>
              <schema targetNamespace="urn:cem_dictionary.dictionary.cem.beans.wrelay" xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
                   <complexType name="ErrRsp">
                        <sequence>
                             <element name="opcode" nillable="true" type="xsd:int"/>
                             <element name="statusCode" nillable="true" type="xsd:int"/>
                             <element name="statusDesc" nillable="true" type="xsd:string"/>
                             <element name="tid" nillable="true" type="xsd:int"/>
                        </sequence>
                   </complexType>
              </schema>
              <schema targetNamespace="urn:ngvs_dictionary.dictionary.ngvs.beans.wrelay" xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
                   <complexType name="ValidateGwyRsp">
                        <sequence>
                             <element name="statusCode" nillable="true" type="xsd:int"/>
                             <element name="statusDesc" nillable="true" type="xsd:string"/>
                             <element name="trunkGwyName" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
                   <complexType name="ValidateGwyQry">
                        <sequence>
                             <element name="custName" nillable="true" type="xsd:string"/>
                             <element name="lataNumber" nillable="true" type="xsd:int"/>
                             <element name="trunkGwyName" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
                   <complexType name="ValidateEnprIdQry">
                        <sequence>
                             <element name="altEnprIdCnt" nillable="true" type="xsd:int"/>
                             <element name="custName" nillable="true" type="xsd:string"/>
                             <element name="enprId" nillable="true" type="xsd:string"/>
                             <element name="lataNumber" nillable="true" type="xsd:int"/>
                        </sequence>
                   </complexType>
                   <complexType name="ValidateEnprIdRsp">
                        <sequence>
                             <element name="altEnprId" nillable="true" type="impl:ArrayOf_xsd_string"/>
                             <element name="custName" nillable="true" type="xsd:string"/>
                             <element name="lataNumber" nillable="true" type="xsd:int"/>
                             <element name="statusCode" nillable="true" type="xsd:int"/>
                             <element name="statusDesc" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
              </schema>
              <schema targetNamespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
                   <complexType name="ArrayOf_xsd_string">
                        <complexContent>
                             <restriction base="soapenc:Array">
                                  <attribute ref="soapenc:arrayType" wsdl:arrayType="xsd:string[]"/>
                             </restriction>
                        </complexContent>
                   </complexType>
              </schema>
         </wsdl:types>
         <wsdl:message name="sendValidateEnprIdQryResponse">
              <wsdl:part name="sendValidateEnprIdQryReturn" type="xsd:boolean"/>
              <wsdl:part name="arg2" type="tns2:ValidateEnprIdRsp"/>
              <wsdl:part name="arg3" type="tns1:ErrRsp"/>
         </wsdl:message>
         <wsdl:message name="sendValidateEnprIdQryRequest">
              <wsdl:part name="arg1" type="tns2:ValidateEnprIdQry"/>
         </wsdl:message>
         <wsdl:message name="sendValidateGwyQryResponse">
              <wsdl:part name="sendValidateGwyQryReturn" type="xsd:boolean"/>
              <wsdl:part name="arg2" type="tns2:ValidateGwyRsp"/>
              <wsdl:part name="arg3" type="tns1:ErrRsp"/>
         </wsdl:message>
         <wsdl:message name="sendValidateGwyQryRequest">
              <wsdl:part name="arg1" type="tns2:ValidateGwyQry"/>
         </wsdl:message>
         <wsdl:portType name="VOIPService">
              <wsdl:operation name="sendValidateGwyQry" parameterOrder="arg1 arg2 arg3">
                   <wsdl:input message="impl:sendValidateGwyQryRequest" name="sendValidateGwyQryRequest"/>
                   <wsdl:output message="impl:sendValidateGwyQryResponse" name="sendValidateGwyQryResponse"/>
              </wsdl:operation>
              <wsdl:operation name="sendValidateEnprIdQry" parameterOrder="arg1 arg2 arg3">
                   <wsdl:input message="impl:sendValidateEnprIdQryRequest" name="sendValidateEnprIdQryRequest"/>
                   <wsdl:output message="impl:sendValidateEnprIdQryResponse" name="sendValidateEnprIdQryResponse"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="VOIPServiceSoapBinding" type="impl:VOIPService">
              <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="sendValidateGwyQry">
                   <wsdlsoap:operation soapAction=""/>
                   <wsdl:input name="sendValidateGwyQryRequest">
                        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" use="encoded"/>
                   </wsdl:input>
                   <wsdl:output name="sendValidateGwyQryResponse">
                        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" use="encoded"/>
                   </wsdl:output>
              </wsdl:operation>
              <wsdl:operation name="sendValidateEnprIdQry">
                   <wsdlsoap:operation soapAction=""/>
                   <wsdl:input name="sendValidateEnprIdQryRequest">
                        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" use="encoded"/>
                   </wsdl:input>
                   <wsdl:output name="sendValidateEnprIdQryResponse">
                        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" use="encoded"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="VOIPServiceService">
              <wsdl:port binding="impl:VOIPServiceSoapBinding" name="VOIPService">
                   <wsdlsoap:address location="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    Thanks
    Girish

    I am briging some vendor information from R3 system to XI thru IDOC. The IDOC Type is "CREMAS.CREMAS01".
    I am able to import this into Integration Repository in XI. XI is translating this into XML.
    Now insted of creating data types manually, I would like to export this XML into XSD and import into the data type.
    When importing this XSD into data type I am getting this error message.

Maybe you are looking for