[jira] Updated: (XERCESC-1667) problem getting PSVI Informations while using a grammar pool

2007-01-31 Thread olivier pharabot (JIRA)

 [ 
https://issues.apache.org/jira/browse/XERCESC-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

olivier pharabot updated XERCESC-1667:
--

Attachment: screenshot-1.jpg

> problem getting PSVI Informations while using a grammar pool
> 
>
> Key: XERCESC-1667
> URL: https://issues.apache.org/jira/browse/XERCESC-1667
> Project: Xerces-C++
>  Issue Type: Bug
>Affects Versions: 2.7.0
> Environment: Windows XP, VC7.1 & VC8
>Reporter: olivier pharabot
> Attachments: screenshot-1.jpg, TypeInfo2.zip
>
>
> We've been using successfully xerces 2.5 lately and when migrating to VC8, we 
> decided to use xerces v2.7. And the PSVI information we've been relying on 
> are no longer available, whether we specify the option :
>   builder->setFeature(XMLUni::fgXercesDOMHasPSVIInfo,true);
> To narrow the problem, i've modified the TypeInfo test project slightly to 
> use a grammar pool (attached)
> And the result is, this test fail...  (see screenshot attached)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (XERCESC-1667) problem getting PSVI Informations while using a grammar pool

2007-01-17 Thread olivier pharabot (JIRA)

 [ 
https://issues.apache.org/jira/browse/XERCESC-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

olivier pharabot updated XERCESC-1667:
--

Description: 
We've been using successfully xerces 2.5 lately and when migrating to VC8, we 
decided to use xerces v2.7. And the PSVI information we've been relying on are 
no longer available, whether we specify the option :
builder->setFeature(XMLUni::fgXercesDOMHasPSVIInfo,true);

To narrow the problem, i've modified the TypeInfo test project slightly to use 
a grammar pool (attached)
And the result is, this test fail...  (see screenshot attached)




  was:
We've been using successfully xerces 2.5 lately and when migrating to VC8, we 
decided to use xerces v2.7. And the PSVI information we've been relying on are 
no longer available, whether we specify the option :
builder->setFeature(XMLUni::fgXercesDOMHasPSVIInfo,true);
To narrow the problem, i've modified the TypeInfo test project the following (i 
dunno how to attach file with this bug report tool):

data/typeInfo.xml:
change the line 2 into:
http://www.w3.org/2001/XMLSchema-instance";  
xmlns:xhtml="http://www.w3.org/1999/xhtml"; xmlns:ss="http://www.secondSchema"; 
xmlns="http://www.firstSchema";>

data/TypeInfo.xsd
change the line 2 into:
http://www.firstSchema"; 
xmlns:foo="http://anothernamespace.com"; >

TypeInfo.cpp:
add line 25:
#include 

add line 828 (just after new XercesDOMParser):

ti.parser->loadGrammar("data/TypeInfo.xsd",Grammar::SchemaGrammarType,true);


And the result is, all tests fail... 





> problem getting PSVI Informations while using a grammar pool
> 
>
> Key: XERCESC-1667
> URL: https://issues.apache.org/jira/browse/XERCESC-1667
> Project: Xerces-C++
>  Issue Type: Bug
>Affects Versions: 2.7.0
> Environment: Windows XP, VC7.1 & VC8
>Reporter: olivier pharabot
> Attachments: TypeInfo2.zip
>
>
> We've been using successfully xerces 2.5 lately and when migrating to VC8, we 
> decided to use xerces v2.7. And the PSVI information we've been relying on 
> are no longer available, whether we specify the option :
>   builder->setFeature(XMLUni::fgXercesDOMHasPSVIInfo,true);
> To narrow the problem, i've modified the TypeInfo test project slightly to 
> use a grammar pool (attached)
> And the result is, this test fail...  (see screenshot attached)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (XERCESC-1667) problem getting PSVI Informations while using a grammar pool

2007-01-17 Thread olivier pharabot (JIRA)

 [ 
https://issues.apache.org/jira/browse/XERCESC-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

olivier pharabot updated XERCESC-1667:
--

Attachment: TypeInfo2.zip

> problem getting PSVI Informations while using a grammar pool
> 
>
> Key: XERCESC-1667
> URL: https://issues.apache.org/jira/browse/XERCESC-1667
> Project: Xerces-C++
>  Issue Type: Bug
>Affects Versions: 2.7.0
> Environment: Windows XP, VC7.1 & VC8
>Reporter: olivier pharabot
> Attachments: TypeInfo2.zip
>
>
> We've been using successfully xerces 2.5 lately and when migrating to VC8, we 
> decided to use xerces v2.7. And the PSVI information we've been relying on 
> are no longer available, whether we specify the option :
>   builder->setFeature(XMLUni::fgXercesDOMHasPSVIInfo,true);
> To narrow the problem, i've modified the TypeInfo test project the following 
> (i dunno how to attach file with this bug report tool):
> data/typeInfo.xml:
> change the line 2 into:
> http://www.w3.org/2001/XMLSchema-instance";  
> xmlns:xhtml="http://www.w3.org/1999/xhtml"; xmlns:ss="http://www.secondSchema"; 
> xmlns="http://www.firstSchema";>
> data/TypeInfo.xsd
> change the line 2 into:
>  elementFormDefault="unqualified" targetNamespace="http://www.firstSchema"; 
> xmlns:foo="http://anothernamespace.com"; >
> TypeInfo.cpp:
> add line 25:
> #include 
> add line 828 (just after new XercesDOMParser):
>   
> ti.parser->loadGrammar("data/TypeInfo.xsd",Grammar::SchemaGrammarType,true);
> And the result is, all tests fail... 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]