"unknown element xmlns in taglib" Urgent!

Hi,
I am using IIS 4.0 with Resin 2.0.2. I have created a BC4J
project which is running perfectly well from within JDeveloper.
After I deploy the project, upon running the application, I get
the error message :-
500 Servlet Exception
/webapp/DataTags.tld:3 unknown element `xmlns' in `taglib'
This message appears only in the JSPs where the datatag library
is being referred. Pls help!!
Thanks

We tried using Omniportlet. It expects the resultset in ROWSET/ROW format. Our .Net Webservice doesn't return in rowset/row. We tried transforming using XSL, but even then it didn't work.
Thanks

Similar Messages

Unknown call on skype saying URGENT to call a web ...

Had a skype call from unknown source saying it was "Urgent" for me to contact a website "helpsc.com" as my skype system was not secure. Any ideas if this is real or is it a scam?

Ok thank you. I thought it was because I have never got anything like that before and I've had a mac for almost 7 years now. Just wanted to make sure before I did anything.

Aassign xsi:nill values from element to BPEL variable - Urgent..Plz..

Hi all,I have a BPEL process which calls a Webservice,and at the end it transforms the output of the Webservice to the Output Variable in my BPEL process,but the thing is this process retuns elements with xsi:nil="true" and I get an error which says
*Could not initiate the BPEL process because the input xml is not well formed, the reason is :
Error parsing envelope: (4, 3679) Namespace prefix 'xsi' used but not declared. Please correct the input xml.*
I have verified the WSLD,.bpel file,the xsd..they all have xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Heres the code of the assign
<from xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
variable="Invoke_P_getlV_OutputVariable"
part="parameters"
query="/ns7:getCViewResponse/ns7:getCViewReturn"/>
<to xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
variable="outputVariable" part="payload"
query="/ns1:GetOfferResponse/ns1:getCVResponse/ns1:getCViewReturn"/>
Please temme how do I get this to wrk...I need to get this working immediatly..

If you need to "clean" some xml from null values (empty tags) you can create an XSLT (like RemoveNullTags.xsl) with the following code:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<xsl:apply-templates select="@*|node()"/>
</xsl:template>
<xsl:template match="@*|node()">
<xsl:choose>
<xsl:when test="normalize-space(.)">
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:when>
<xsl:when test="count(./*)">
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:when>
<xsl:otherwise>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:stylesheet>
This xslt will remove all the empty tags on your XML. So after you create this and paste it on your project, you need to use it into an ASSIGN activity like this:
<assign name="Remove_Nulls">
<copy>
<from expression="ora:processXSLT('RemoveNullTags.xsl',bpws:getVariableData('inputVariable','payload'))"/>
<to variable="inputVariable" part="payload"
query="/ns2:writeCollectedDeleteElement"/>
</copy>
<copy>
<from expression="ora:processXSLT('RemoveNullTags.xsl',bpws:getVariableData('inputVariable','payload'))"/>
<to variable="inputVariable" part="payload"
query="/ns2:writeCollectedDeleteElement"/>
</copy>
</assign>
As you can see in this sample, i make 2 copy operations because i have xml arrays, so i need a copy operation for each child the xml element have.
HTH,
Andres

Can't open Photoshop Elements 4 or 6 - URGENT

Hi,
I use both Photoshop Elements 4 and Photoshop Elements 6 in the work I do. The last time I opened either program was Friday of last week. Since I last opened them I have made the following changes to my system:
Unistalled an older version of Adobe Flash Player
Installed the latest version of Adobe Flash Player
Purchased and installed Registry Patrol (but have not run it yet)
Installed Identity Patrol (but have not run it yet)
Now today when I attempted to open Elements 4 - the opening page came up where you choose to create or edit, etc. I clicked on the edit icon and got the following message: "Unable to continue because of a hardware or system error. Sorry, but this error is unrecoverable." There was no application error messsage associated with this message.
Then I attempted to open Elements 6. It seemed to open okay, but then when I clicked on File-Open to retrieve some images - nothing happened. I get no error message - just no response.
PLEASE help! I need these programs to do my work.
Thanks in advance!
Barb

You might have a look at it and then check on some of the things mentioned to resolve the issue.
http://www.johnrellis.com/psedbtool/photoshop-elements-faq.htm
Thanks,
Garry

Jaxb unmarshalling: how to ignore unknown elements?

Hi,
I use jaxb 1.1 for communication with an external partner. (Took schema, compiled it, used generated classes for unmarshalling like this:
Document doc = /* some document building */
JAXBContext jaxbContext = JAXBContext.newInstance(MyConstants.JAXB_PACKAGE);
Unmarshaller unMarshaller = jaxbContext.createUnmarshaller();
myObject = (MyObject) unMarshaller.unmarshal(doc);) Everything worked fine until they decided to add new elements to their xml-Document without notifiing me (nothing very unusual I think...). Now I get a javax.xml.bind.UnmarshallingException with Message "Unexpected Element". Is there any way to ignore such elements and just take the known Elements from the xml-stream?
Thanks in advance
Thomas

Update your schema with the following after you known elements.
<xs:any namespace="##any" processContents="skip" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>An extension point for arbitrary xml value fragments</xs:documentation>
</xs:annotation>
</xs:any>
Hunter

Application.iPhone is an unknown element/attribute

This is driving me insane. I can't compile my .ipa with the iPhone attribute in the app.xml file. I don't know what I'm doing wrong but I'm pretty sure I followed the format correctly. Please help.
I'm using Flash CS 5.5 and Air for iOS
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<application xmlns="http://ns.adobe.com/air/application/2.6">
<id>com.SoggyBread.OverDrawn</id>
<versionNumber>1.0</versionNumber>
<filename>OverDrawn</filename>
<description/>
      <iPhone>
    <InfoAdditions>
         <![CDATA[
        <key>UIDeviceFamily</key>
        <array>
            <string>1</string>
            <string>2</string>
        </array>
        <key>UIApplicationExitsOnSuspend</key>
        <string>YES</string>
     ]]>
       </InfoAdditions>
</iPhone>
I thought I followed the instructions to T, but maybe someone else can identify the problem?
Thanks in advance.

you're, at least, missing an end application tag.

Attrribute and element on one type - URGENT

Hi!
I need have attribute and element in one type.
Example:
<xs:complexType name="EntityE">
<xs:attribute name="value" type="xs:string" use="required"/>
<xs:sequence>
<xs:element name="classCode" type="CS" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
Please, help me!!!
Thanks!

The xs:attribute is after the xs:sequence elment.
<xs:complexType name="EntityE">
<xs:sequence>
<xs:element name="classCode" type="CS" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="value" type="xs:string" use="required"/>
</xs:complexType>
thanks,
Deepak

Xdo delivery config file: unknown server elements

I am working on XML Pubisher for E-Business Suite version 5.6.3 with the EBS Bursting integration patch.
I have created a xdodelivery.cfg config file to include a IPP printer definition:
<config xmlns="http://xmlns.oracle.com/oxp/delivery/config">
<servers>
<server name="fb" type="ipp_printer">
<uri>http://vumc-pr01/printers/FB-PR17/.printer</uri>
<authType>basic</authType>
<username>***</username>
<password>***</password>
</server>
</servers>
</config>
In my bursting control file I use the printer name ("fb") to deliver the bursted output to.
Unfortunately the bursting request produces the following error in the log file:
[080508_015652533][][STATEMENT] ConfigReader: Unknown element:servers
[080508_015652533][][STATEMENT] ConfigReader: Unknown element:server
[080508_015652533][][STATEMENT] ConfigReader: Unknown element:uri
[080508_015652533][][STATEMENT] ConfigReader: Unknown element:authType
[080508_015652533][][STATEMENT] ConfigReader: Unknown element:username
[080508_015652534][][STATEMENT] ConfigReader: Unknown element:password
In the manual it was clearly stated that the element <servers> <server> etc could be used to setup a printer definition.
Anyone any idea what goes wrong here?
Thanks.

I am working on XML Pubisher for E-Business Suite version 5.6.3 with the EBS Bursting integration patch.
I have created a xdodelivery.cfg config file to include a IPP printer definition:
<config xmlns="http://xmlns.oracle.com/oxp/delivery/config">
<servers>
<server name="fb" type="ipp_printer">
<uri>http://vumc-pr01/printers/FB-PR17/.printer</uri>
<authType>basic</authType>
<username>***</username>
<password>***</password>
</server>
</servers>
</config>
In my bursting control file I use the printer name ("fb") to deliver the bursted output to.
Unfortunately the bursting request produces the following error in the log file:
[080508_015652533][][STATEMENT] ConfigReader: Unknown element:servers
[080508_015652533][][STATEMENT] ConfigReader: Unknown element:server
[080508_015652533][][STATEMENT] ConfigReader: Unknown element:uri
[080508_015652533][][STATEMENT] ConfigReader: Unknown element:authType
[080508_015652533][][STATEMENT] ConfigReader: Unknown element:username
[080508_015652534][][STATEMENT] ConfigReader: Unknown element:password
In the manual it was clearly stated that the element <servers> <server> etc could be used to setup a printer definition.
Anyone any idea what goes wrong here?
Thanks.

Native format builder.To seperate body elements which are unbounded and also of different length ,which ends with special character LF if we open in Notepad++

Hi ,
My sample file is like this
RAJNagercoil19910809
JAMBangalore
ABCNagercoil20120304
ABBBangalore20120709
TOM
SAMBangalore20900909
here first 3 characters of each line represents Name,next 9 characters represents city,next 8 characters DOB.
Here everything is of fixedlength but all elements Name,city and DOB are optional they may or may not be in Sample file.
here if we open the above sample file in notepad++ the end of line is represented by LF.
My task is to separate the body elements given above into the following format
<Body>
<Name>Raj</Name>
<City>Nagercoil</City>
<DOB>19910809</DOB>
</Body>
<Body>
<Name>JIN</Name>
<City>Bangalore</City>
<DOB/>
</Body>
<Body>
<Name>ABC</Name>
<City>Nagercoil</City>
<DOB>20120304</DOB>
</Body>
<Body>
<Name>ABB</Name>
<City>Bangalore</City>
<DOB>20120709</DOB>
</Body>
<Body>
<Name>TOM</Name>
<City/>
<DOB/>
</Body>
<Body>
<Name>SAM</Name>
<City>Bangalore</City>
<DOB>20900909</DOB>
</Body>
The schema i designed for my task is like below
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
            xmlns:tns="http://TargetNamespace.com/test"
            targetNamespace="http://TargetNamespace.com/test"
            elementFormDefault="qualified"
            attributeFormDefault="unqualified"
            nxsd:version="NXSD"
            nxsd:stream="chars"
            nxsd:encoding="US-ASCII">
<xsd:element name="Root-Element">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="Body" type="tns:sample" maxOccurs="unbounded" />
      </xsd:sequence>
    </xsd:complexType>
</xsd:element>
<xsd:complexType name="sample">
    <xsd:sequence>
      <xsd:element name="Name" type="xsd:string" nxsd:style="fixedLength" nxsd:length="3" nxsd:padStyle="tail" nxsd:paddedBy=" " minOccurs="0" />
      <xsd:element name="City" type="xsd:string" nxsd:style="fixedLength" nxsd:length="9" nxsd:padStyle="tail" nxsd:paddedBy=" " minOccurs="0"/>
      <xsd:element name="DOB" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" minOccurs="0" />
    </xsd:sequence>
</xsd:complexType>
</xsd:schema>
But it is not producing the result which i want .It is converting as follow.
<?xml version = '1.0' encoding = 'UTF-8'?>
<Root-Element xmlns="http://TargetNamespace.com/test">
   <Body>
      <Name>Raj</Name>
      <City>Nagercoil</City>
      <DOB>19910809</DOB>
   </Body>
   <Body>
      <Name>JIN</Name>
      <City>Bangalore</City>
      <DOB/>
   </Body>
   <Body>
      <Name>ABC</Name>
      <City>Nagercoil</City>
      <DOB>20120304</DOB>
   </Body>
   <Body>
      <Name>ABB</Name>
      <City>Bangalore</City>
      <DOB>20120709</DOB>
   </Body>
   <Body>
      <Name>TOM</Name>
      <City>
SAMBanga</City>
      <DOB>lore20900909</DOB>
   </Body>
</Root-Element>
The body element in red color indicates the issue.I my case i am not supposed to use MFL. Please Help me to Solve this issue and give me correct XSD which satisfies the above Sample.Its Very Urgent
Thanks in Advance...

Alright.. I did some extensive home-work for you and this is what I have got.. You can improvise it further accordingly, but this solution will get you moving.
Native XSD :
=================================================================
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
            xmlns:tns="http://TargetNamespace.com/test"
            targetNamespace="http://TargetNamespace.com/test"
            elementFormDefault="qualified" attributeFormDefault="unqualified"
            nxsd:version="NXSD" nxsd:stream="chars" nxsd:encoding="US-ASCII">
<xsd:element name="root">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="multiple" minOccurs="0" maxOccurs="unbounded">
          <xsd:complexType>
            <xsd:choice>
              <xsd:element name="Body" type="tns:sample" nxsd:lookAhead="20"
                           nxsd:lookFor="${eol}"/>
              <xsd:element name="Body1" type="tns:sample1" nxsd:lookAhead="12"
                           nxsd:lookFor="${eol}"/>
              <xsd:element name="Body2" type="tns:sample2" nxsd:lookAhead="3"
                           nxsd:lookFor="${eol}"/>
            </xsd:choice>
          </xsd:complexType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
</xsd:element>
<xsd:complexType name="sample">
    <xsd:sequence>
      <xsd:element name="Name" type="xsd:string" nxsd:style="fixedLength"
                   nxsd:length="3" minOccurs="0"/>
      <xsd:element name="City" type="xsd:string" nxsd:style="fixedLength"
                   nxsd:length="9" minOccurs="0"/>
      <xsd:element name="DOB" type="xsd:string" nxsd:style="terminated"
                   nxsd:terminatedBy="${eol}" minOccurs="0"/>
    </xsd:sequence>
</xsd:complexType>
<xsd:complexType name="sample2">
    <xsd:sequence>
      <xsd:element name="Name" type="xsd:string" nxsd:style="terminated"
                   nxsd:terminatedBy="${eol}" minOccurs="0"/>
    </xsd:sequence>
</xsd:complexType>
<xsd:complexType name="sample1">
    <xsd:sequence>
      <xsd:element name="Name" type="xsd:string" nxsd:style="fixedLength"
                   nxsd:length="3" minOccurs="0"/>
      <xsd:element name="City" type="xsd:string" nxsd:style="terminated"
                   nxsd:terminatedBy="${eol}" minOccurs="0"/>
    </xsd:sequence>
</xsd:complexType>
</xsd:schema>
=================================================================
When used upon your input file, it produces a output file like the following :
<root xmlns="http://TargetNamespace.com/test">
   <multiple>
      <Body>
         <Name>RAJ</Name>
         <City>Nagercoil</City>
         <DOB>19910809</DOB>
      </Body>
      <Body1>
         <Name>JAM</Name>
         <City>Bangalore</City>
      </Body1>
   </multiple>
   <multiple>
      <Body>
         <Name>ABC</Name>
         <City>Nagercoil</City>
         <DOB>20120304</DOB>
      </Body>
   </multiple>
   <multiple>
      <Body>
         <Name>ABB</Name>
         <City>Bangalore</City>
         <DOB>20120709</DOB>
      </Body>
      <Body2>
         <Name>TOM</Name>
      </Body2>
   </multiple>
   <multiple>
      <Body>
         <Name>SAM</Name>
         <City>Bangalore</City>
         <DOB>20900909</DOB>
      </Body>
   </multiple>
</root>
As I said, you can try out some experiments around this xsd and get the output in the format, you want.
Hope this helps !
Best,
Puneet.

Error 103: application.version is an unexpected element/attribute

Hi guys, while i'm publishing iOS app from Flash, i get that thing
Unexpected or unknown element or attribute in the application descriptor file.
/Users/stockingem/Documents/DWP/1-app.xml(44): error 103: application.version is an unexpected element/attribute
application.version is an unexpected element/attribute
please, help to solve it!

<?xml version="1.0" encoding="utf-8"?>
<application xmlns="http://ns.adobe.com/air/application/2.6">
    <id>test1</id>
    <versionNumber>1.2.0</versionNumber>
    <filename>Untitled-1</filename>
    <description></description>
    
    <name>Untitled-1</name>
    
    <copyright></copyright>
    <initialWindow>
        <content>Untitled-1.swf</content>
        <systemChrome>standard</systemChrome>
        <transparent>false</transparent>
        <visible>true</visible>
        <fullScreen>true</fullScreen>
        <autoOrients>false</autoOrients>
        <aspectRatio>portrait</aspectRatio>
        <renderMode>auto</renderMode>
    </initialWindow>
    <customUpdateUI>false</customUpdateUI>
    <allowBrowserInvocation>false</allowBrowserInvocation>
    <icon>
        <image29x29>AppIconsForPublish/dwp.png</image29x29>
    </icon>
    <iPhone>
        <requestedDisplayResolution>standard</requestedDisplayResolution>
        <InfoAdditions><![CDATA[<key>UIDeviceFamily</key><array><string>1</string></array>]]></In foAdditions>
    </iPhone>
    <version>1.2</version>
</application>

Error: Invalid element 'servlet' in content of 'web-app'

Hi,
I m working on a project that includes JSPs, whenever I wanna add JSP to my project it shows following compilation error:
Invalid element 'servlet' in content of 'web-app', expected elements '[error-page, taglib, resource-env-ref, resource-ref, security-constraint, login-config, security-role, env-entry, ejb-ref, ejb-local-ref]'
I have thoroughly checked the web.xml. It is perfectly alright. It is as follows:
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<description>Empty web.xml file for Web Application</description>
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<mime-mapping>
<extension>html</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
<mime-mapping>
<extension>txt</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
<servlet>
<servlet-name>myServlet</servlet-name>
<servlet-class>com.project.MainServlet</servlet-class>
<init-param>
Long postings are being truncated to ~1 kB at this time.

The Complete web.xml is as follows:
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<description>Empty web.xml file for Web Application</description>
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<mime-mapping>
<extension>html</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
<mime-mapping>
<extension>txt</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
<servlet>
<servlet-name>montana</servlet-name>
<servlet-class>com.masstech.montana.boundary.uii.MainServlet</servlet-class>
<init-param>
<param-name>db</param-name>
<param-value>MontanaDS</param-value>
</init-param>
<init-param>
<param-name>user</param-name>
<param-value>MS</param-value>
</init-param>
<init-param>
<param-name>password</param-name>
<param-value>MS</param-value>
</init-param>
</servlet>
<servlet>
<servlet-n[i]Long postings are being truncated to ~1 kB at this time.

How to allow multiple wildcard elements in biztalk schema

Hi,
In my input xml, I can have one or more unknown elements in the xml. I know I can use <xs:any> in my schema for each of these elements but it does not work when there is unknown number of these unknown elements occuring in the input xml.
I know the location in xml where these unknown elements appear but I dont know how many times they appear in each location.
Any help on how to allow it would be very appreciated
thanks
manibest

Hi manibest,
You're trying to find a technical workaround on how to handle this in schema. But we have to understand that schema is to defining the structure and content of XML and you want a schema which is not going to define the content/structure of your
XML, its basically a flaw to conceive a Schema which has no relation to the XML.
Anyway what do you mean by " xml accepted by the schema" - As mentioned in the
other post you have raised today, if you don't enforce XML validation and if you don't bother about mapping this unknown fields across to the outbound schema or if your orchestration's processing is not bound to these unknown elements then you can
do use it.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Recurring Rebuild Problem: Invalid Element....

I keep getting this recurring error when i try to rebuild my project:
Error(25,16): Invalid element 'mime-mapping' in content of 'web-app',
expected elements '[error-page, taglib, resource-env-ref, resource-ref,
security-constraint, login-config, security-role, env-entry, ejb-ref,
ejb-local-ref]'.I have also seen similar errors such as:
Error(9,11): Invalid element 'servlet' in content of 'web-app',
expected elements '[error-page, taglib, resource-env-ref, resource-ref,
security-constraint, login-config, security-role, env-entry, ejb-ref,
ejb-local-ref]'.I am using JDev 10g Production.
The problem occurs when when trying to compile a jsp using Struts Tiles. Here is a sample of one of the jsps:
<%@ taglib uri="/WEB-INF/struts-tiles.tld" prefix="tiles"%>
<tiles:insert page="layout_main.jsp" flush="true">
    <tiles:put name="title" value="Condo"/>
    <tiles:put name="header" value="header.jsp"/>
    <tiles:put name="left" value="left.jsp"/>
    <tiles:put name="center" value="center_condo.jsp"/>
    <tiles:put name="right" value="right.jsp"/>
</tiles:insert>I have had the project rebuild properly once with this same web.xml file and had no problems. I have not made any changes to the web.xml. I also ran the xml syntax validator on it and it is valid.
This is a very weird problem. Sometimes re-arranging the web.xml file fixes the problem. The sample web.xml may be too big for a single post, but I can email to someone that can help. I have seen others on this forum that have posted the same problem with no solution. Please help. Thanks,
Paul Manning

Figured it out.
When editing the web.xml you need to preserve the order listed in the error message.
So in my case, the "welcome-file-list" needs to appear before tagLibs but after the mimeList.
Hope this helps someone. JDeveloper is not conforming to the Spec on this one but I can cope. In my experience the "welcome-file-list" can appear any where nested in the webapp tag. Oh well, not the end of the world...
Paul Manning

WSDL & local qualified accessors (complex type - child elements)

Why does the WLS8.1 generated WSDL file specify
elementFormDefault="qualified" in the schema for complex types.
The resulting runtime SOAP bodies that are sent have unqualified child
elements and tools like JAX-RPC, determine from the WSDL schema that these
child elements SHOULD be qualified and fail to parse the body. I understand
that the spec states that they should not be qualified but then why does the
schema not specify
elementFormDefault="unqualified"?
I have to manually edit the WSDL (to say "unqualified") to generate a client
using JAX-RPC.
Is there some way I can tell <wsdlgen> task to do this?
Thanks,
M
Here's the excerpt from my WLS 8.1 generated WSDL file:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tp="java:com.xxx.framework.persist"
xmlns:stns="java:com.xxx.businessservices.indexservice.valueobjects"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.xxx.businessservices.indexservice.valueobjects">
<xsd:import namespace="java:com.xxx.framework.persist" />
<xsd:import namespace="java:language_builtins.util" />
<xsd:complexType name="IndexVO">
<xsd:complexContent>
<xsd:extension xmlns:tp="java:com.xxx.framework.persist"
base="tp:FW_PersistentObject">
<xsd:sequence>
<xsd:element type="xsd:string" name="code" minOccurs="1" nillable="true"
maxOccurs="1" />
<xsd:element type="xsd:string" name="description" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="indexID" minOccurs="1" maxOccurs="1"
/>
<xsd:element type="stns:IndexProviderVO" name="indexProviderVO"
minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="stns:IndexSourceVO" name="indexSourceVO" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="name" minOccurs="1" nillable="true"
maxOccurs="1" />
<xsd:element type="xsd:dateTime" name="nextUpdateDate" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="providerID" minOccurs="1"
maxOccurs="1" />
<xsd:element type="xsd:long" name="scheduleID" minOccurs="1"
maxOccurs="1" />
<xsd:element type="stns:UpdateScheduleVO" name="scheduleVO" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="sourceID" minOccurs="1" maxOccurs="1"
/>
<xsd:element xmlns:tp="java:language_builtins.util" type="tp:List"
name="updateFrequencies" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element xmlns:tp="java:com.xxx.framework.persist"
type="xsd:dateTime" name="updatesDisabledDate" minOccurs="1" nillable="true"
maxOccurs="1" />
<xsd:element xmlns:tp="java:language_builtins.util" type="tp:List"
name="values" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
"Scott Ziegler" <[email protected]> wrote in message
news:[email protected]...
On Mon, 21 Jul 2003 09:31:45 -0500, Mark Fine wrote:
I've been debugging an XML-RPC generated client and came across the
following problem:
I have a webserice serialized Object, "IndexVO" that has an attribute
(ie.
element) "code".
The WLS8.1 generated WSDL schema declares that code is in the
"com...valueobjects" namespace by virtue of a default (target)namespace.
At runtime, the SOAP envelope that is created seems to put the
attribute/element "code" in the EMPTY namespace, and not in the
"com...valueobjects" namespace. The XML-RPC generated client code is
looking for "code" in the "com...valueobjects" namespace and skips overit
because it is in the "", blank namespace (according to the XML parser).
I'm not a XML expert but from what I can tell, the SOAP envelope that is
returned does not match the WSDL file with respect to the namespace ofthe
attributes in IndexVO.
Am I reading this wrong?We did this for interoperability reasons. Some other stacks that we were
trying to work with would not work if those elements were qualified. The
problem really stems from SOAP 1.1:http://www.w3.org/TR/SOAP/#_Toc478383520
>
"Accessors whose names are local to their containing types have
unqualified element names; all others have qualified names."
SOAP stacks that are not schema aware basically require this behavior.
You might try using a doc-literal service (which is more faithful to the
schema) if that fits your situation.
--Scott

Currently there is no option to make elementFormDefault
unqualified. I filed an enhancement CR (112776).
Regards,
-manoj
http://manojc.com
"Mark Fine" <[email protected]> wrote in message
news:[email protected]...
Why does the WLS8.1 generated WSDL file specify
elementFormDefault="qualified" in the schema for complex types.
The resulting runtime SOAP bodies that are sent have unqualified child
elements and tools like JAX-RPC, determine from the WSDL schema that these
child elements SHOULD be qualified and fail to parse the body. Iunderstand
that the spec states that they should not be qualified but then why doesthe
schema not specify
elementFormDefault="unqualified"?
I have to manually edit the WSDL (to say "unqualified") to generate aclient
using JAX-RPC.
Is there some way I can tell <wsdlgen> task to do this?
Thanks,
M
Here's the excerpt from my WLS 8.1 generated WSDL file:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tp="java:com.xxx.framework.persist"
xmlns:stns="java:com.xxx.businessservices.indexservice.valueobjects"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.xxx.businessservices.indexservice.valueobjects">
<xsd:import namespace="java:com.xxx.framework.persist" />
<xsd:import namespace="java:language_builtins.util" />
<xsd:complexType name="IndexVO">
<xsd:complexContent>
<xsd:extension xmlns:tp="java:com.xxx.framework.persist"
base="tp:FW_PersistentObject">
<xsd:sequence>
<xsd:element type="xsd:string" name="code" minOccurs="1"nillable="true"
maxOccurs="1" />
<xsd:element type="xsd:string" name="description" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="indexID" minOccurs="1" maxOccurs="1"
/>
<xsd:element type="stns:IndexProviderVO" name="indexProviderVO"
minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="stns:IndexSourceVO" name="indexSourceVO"minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="name" minOccurs="1"nillable="true"
maxOccurs="1" />
<xsd:element type="xsd:dateTime" name="nextUpdateDate" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="providerID" minOccurs="1"
maxOccurs="1" />
<xsd:element type="xsd:long" name="scheduleID" minOccurs="1"
maxOccurs="1" />
<xsd:element type="stns:UpdateScheduleVO" name="scheduleVO"minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="sourceID" minOccurs="1"maxOccurs="1"
/>
<xsd:element xmlns:tp="java:language_builtins.util" type="tp:List"
name="updateFrequencies" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element xmlns:tp="java:com.xxx.framework.persist"
type="xsd:dateTime" name="updatesDisabledDate" minOccurs="1"nillable="true"
maxOccurs="1" />
<xsd:element xmlns:tp="java:language_builtins.util" type="tp:List"
name="values" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
"Scott Ziegler" <[email protected]> wrote in message
news:[email protected]...
On Mon, 21 Jul 2003 09:31:45 -0500, Mark Fine wrote:
I've been debugging an XML-RPC generated client and came across the
following problem:
I have a webserice serialized Object, "IndexVO" that has an attribute
(ie.
element) "code".
The WLS8.1 generated WSDL schema declares that code is in the
"com...valueobjects" namespace by virtue of a default (target)namespace.
At runtime, the SOAP envelope that is created seems to put the
attribute/element "code" in the EMPTY namespace, and not in the
"com...valueobjects" namespace. The XML-RPC generated client code is
looking for "code" in the "com...valueobjects" namespace and skips
over
it
because it is in the "", blank namespace (according to the XML
parser).
>>>
I'm not a XML expert but from what I can tell, the SOAP envelope thatis
returned does not match the WSDL file with respect to the namespace ofthe
attributes in IndexVO.
Am I reading this wrong?We did this for interoperability reasons. Some other stacks that we
were
trying to work with would not work if those elements were qualified.The
problem really stems from SOAP 1.1:
http://www.w3.org/TR/SOAP/#_Toc478383520
"Accessors whose names are local to their containing types have
unqualified element names; all others have qualified names."
SOAP stacks that are not schema aware basically require this behavior.
You might try using a doc-literal service (which is more faithful to the
schema) if that fits your situation.
--Scott

Select namespace attributes from xmlns:

How do I select this information?
<data>
<element xmlns:mynamespace="http://my.namespace.com" >mynamespace:Stuff</element>
<element xmlns:mynamespace="http://other.namespace.com" >mynamespace:Stuff2</element>
</data>I want to come up with an xpath (using Jdom) that selects the http://my.namespace.com and http://other.namespace.com
This is a "local" namespace declaration, which I don't know beforehand, so I can't add the namespace programmatically.
the xmlns:.. part is almost an attribute, but since it's not a regular attribute, I have no way selecting it.
Any tips?
/Tom

To select a node with a namespace, add a namespace to an XPath:
org.jdom.Document jdomDocument ;
XPath xpath =
XPath.newInstance( "/data/element/xmlns:mynamespace");
xpath.addNamespace("mynamespace", "http://my.namespace.com");Select a node with a namespace prefix:
org.jdom.Attribute attr
= (org.jdom.Attribute)
xpath.selectSingleNode(jdomDocument);

"unknown element xmlns in taglib" Urgent!

Similar Messages

Maybe you are looking for