WS-A schema access in NB fails..

[Kiran Bhumana-2]

 I am using the WS-A schema in a WSDL,

    <types>
        <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/dynamicPL">
            <xsd:import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"
            schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing/"/>
           
            <xsd:import namespace="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
            schemaLocation="http://docs.oasis-open.org/wsbpel/2.0/OS/process/executable/ws-bpel_executable.xsd"/>
           
           
        </xsd:schema>
    </types>

 NB XSD parser is not able to parse the file. Whether NB downloads this WS-A schema file through populate catalog action or accesses it remotely, it seems to be unable to parse the schema file. When I force it to open in the text mode within NB, I see some additional character at the beginning, a dot. If i delete this "dot" in the file it works fine.




The problem is I am able to open the xsd in the browser, by opening http://schemas.xmlsoap.org/ws/2004/08/addressing/. I also can open the file in notepad and textpad and don't see the additional character. Maybe those editors chose to ignore the "dot"

To test if NB has an issue, I used another remote xsd, http://docs.oasis-open.org/wsbpel/2.0/OS/process/executable/ws-bpel_executable.xsd. And that works fine.

I am using windows XP. Could the XSD model folks or the "catalog" feature folks look at this and confirm that there is in fact no issue with NB?

thanks,
Kiran.

[jqian]

It seems you are running into this BOM issue I filed in 2006: http://www.netbeans.org/issues/show_bug.cgi?id=83321

Jun

Kiran Bhumana wrote:

 I am using the WS-A schema in a WSDL,

    <types>
        <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/dynamicPL">
            <xsd:import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"
            schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing/"/>
           
            <xsd:import namespace="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
            schemaLocation="http://docs.oasis-open.org/wsbpel/2.0/OS/process/executable/ws-bpel_executable.xsd"/>
           
           
        </xsd:schema>
    </types>

 NB XSD parser is not able to parse the file. Whether NB downloads this WS-A schema file through populate catalog action or accesses it remotely, it seems to be unable to parse the schema file. When I force it to open in the text mode within NB, I see some additional character at the beginning, a dot. If i delete this "dot" in the file it works fine.




The problem is I am able to open the xsd in the browser, by opening http://schemas.xmlsoap.org/ws/2004/08/addressing/. I also can open the file in notepad and textpad and don't see the additional character. Maybe those editors chose to ignore the "dot"

To test if NB has an issue, I used another remote xsd, http://docs.oasis-open.org/wsbpel/2.0/OS/process/executable/ws-bpel_executable.xsd. And that works fine.

I am using windows XP. Could the XSD model folks or the "catalog" feature folks look at this and confirm that there is in fact no issue with NB?

thanks,
Kiran.

[Kiran Bhumana-2]

Ok, Thanks. So this is a NB issue and not an issue by the server providing the xsd?
If the file on the server is not edited in windows editors that cause this BOM character, then are you saying NB won't have issue?

-Kiran.

Jun Qian wrote:

It seems you are running into this BOM issue I filed in 2006: http://www.netbeans.org/issues/show_bug.cgi?id=83321

Jun

Kiran Bhumana wrote:

 I am using the WS-A schema in a WSDL,

    <types>
        <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/dynamicPL">
            <xsd:import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"
            schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing/"/>
           
            <xsd:import namespace="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
            schemaLocation="http://docs.oasis-open.org/wsbpel/2.0/OS/process/executable/ws-bpel_executable.xsd"/>
           
           
        </xsd:schema>
    </types>

 NB XSD parser is not able to parse the file. Whether NB downloads this WS-A schema file through populate catalog action or accesses it remotely, it seems to be unable to parse the schema file. When I force it to open in the text mode within NB, I see some additional character at the beginning, a dot. If i delete this "dot" in the file it works fine.




The problem is I am able to open the xsd in the browser, by opening http://schemas.xmlsoap.org/ws/2004/08/addressing/. I also can open the file in notepad and textpad and don't see the additional character. Maybe those editors chose to ignore the "dot"

To test if NB has an issue, I used another remote xsd, http://docs.oasis-open.org/wsbpel/2.0/OS/process/executable/ws-bpel_executable.xsd. And that works fine.

I am using windows XP. Could the XSD model folks or the "catalog" feature folks look at this and confirm that there is in fact no issue with NB?

thanks,
Kiran.

[jqian]

Kiran Bhumana wrote:

Ok, Thanks. So this is a NB issue and not an issue by the server providing the xsd?

Yes

If the file on the server is not edited in windows editors that cause this BOM character, then are you saying NB won't have issue?

Yes

Jun

-Kiran.

Jun Qian wrote:

It seems you are running into this BOM issue I filed in 2006: http://www.netbeans.org/issues/show_bug.cgi?id=83321

Jun

Kiran Bhumana wrote:

 I am using the WS-A schema in a WSDL,

    <types>
        <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/dynamicPL">
            <xsd:import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"
            schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing/"/>
           
            <xsd:import namespace="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
            schemaLocation="http://docs.oasis-open.org/wsbpel/2.0/OS/process/executable/ws-bpel_executable.xsd"/>
           
           
        </xsd:schema>
    </types>

 NB XSD parser is not able to parse the file. Whether NB downloads this WS-A schema file through populate catalog action or accesses it remotely, it seems to be unable to parse the schema file. When I force it to open in the text mode within NB, I see some additional character at the beginning, a dot. If i delete this "dot" in the file it works fine.




The problem is I am able to open the xsd in the browser, by opening http://schemas.xmlsoap.org/ws/2004/08/addressing/. I also can open the file in notepad and textpad and don't see the additional character. Maybe those editors chose to ignore the "dot"

To test if NB has an issue, I used another remote xsd, http://docs.oasis-open.org/wsbpel/2.0/OS/process/executable/ws-bpel_executable.xsd. And that works fine.

I am using windows XP. Could the XSD model folks or the "catalog" feature folks look at this and confirm that there is in fact no issue with NB?

thanks,
Kiran.