is legitimate?
> Or point us to the right location for performing this validation?
>
> Regards,
>
> Louis Jacomet
>
> Senior Lead Software Engineer
>
> Gradle
> W. gradle.com
>
>
--
Regards,
Mukul Gandhi
while using the site
https://www.softwarebytes.org/xmlvalidation/.
I'm still, not able to find how to solve this issue. I'll try to solve
this. But that may take little bit of time.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
XML Schema 1.1 build artifacts on Maven central.
This sample, application is located at
https://github.com/mukulga/rest_xml_apis/tree/master.
Please, feel free to let us know your thoughts, about this.
--
Regards,
Mukul Gandhi
---
Thanks, Gary.
(on behalf of Xerces-J team)
On Wed, May 11, 2022 at 12:37 PM Gary Gregory wrote:
>
> Good luck for a future release. I've myself not found the time to work on
> Xalan...
>
> Gary
--
R
ave Xerces-J 2.12.3 release sometime in future,
perhaps with certain changes to the implementation.
On Tue, May 10, 2022 at 10:30 AM Mukul Gandhi wrote:
>
> Hi all,
>Its been a week, that we started vote for this Xerces-J RC. We
> haven't received any vote so far. If anyone
22 at 7:50 PM Mukul Gandhi wrote:
>
> Hi all,
>This is a request to vote, to the Apache Xerces community, to
> release Xerces-J 2.12.3 version.
>
> I've uploaded the release candidate for the Xerces-J 2.12.3 version,
> at [1] for review.
>
> You could see that
asurements, if in case, we'd
implement XSD schema serialization feature.
If possibly, you could create a jira issue (new feature) for this
requirement, that can make this requirement easy to track.
--
Regards,
Mukul Gandhi
hema-1.1/
[4]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351690&styleName=Html&projectId=10520
[5] https://svn.apache.org/repos/asf/xerces/java/trunk/KEYS,
https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/KEYS
https://repo1.maven.org/maven2/xerces/xercesImpl/
>
> https://lists.apache.org/thread/cn7zb160h3p2s5k7dzp1mcr9yd6d5j6l
>
> Regards,
> PJ
>
--
Regards,
Mukul Gandhi
://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12351257
For more information please visit: http://xerces.apache.org/xerces2-j/
--
Regards,
Mukul Gandhi
Hi all,
Its been few days now, that voting has been open for Xerces-J 2.12.2
release.
The voting for this release resulted in three +1 votes (all from PMC
members) and no other votes, as follows,
Michael Glavassevich
Scott Cantor
Mukul Gandhi
The release should be available on the mirror
n.apache.org/viewvc/xerces/java/trunk/NOTICEneeds to be updated
> for 2022.
>
> Thanks.
>
> Michael Glavassevich
> Software Development
> IBM Toronto Lab
> E-mail: mrgla...@ca.ibm.com
> E-mail: mrgla...@apache.org
>
> "Mukul Gandhi" wrote on 2022-01-20 02:33:5
chema-1.1/
[4]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12351257
[5] https://svn.apache.org/repos/asf/xerces/java/trunk/KEYS,
https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/KEYS
--
Regards,
Mukul Gandhi
mpl-2.12.1.jar:./lib/xercesSamples-2.12.1.jar
> sax.Counter -np -n -v -s "$1"
>
I think that, the Xerces-J sample sax.Counter only supports XML Schema 1.0
validation at the moment. Can you please, try using the Xerces-J
sample jaxp.SourceValidator to run XML Schema 1.1 validation, and let us
know if you experience same issues?
--
Regards,
Mukul Gandhi
ding the last two (i.e 'XML Schema 1.1
Structures and Datatypes Recommendations' & 'XML Schema Definition Language
(XSD): Component Designators (SCD) Candidate Recommendation (January 2010)'
are not provided by "Xerces2 Java 2.12.1").
--
Regards,
Mukul Gandhi
large number of
iterations it shall be, and the memory requirements do not grow after a
certain maximum.
I hope that, this mail has been useful.
--
Regards,
Mukul Gandhi
all be prudent that XSD 1.0 users should consider adopting
XSD 1.1.
--
Regards,
Mukul Gandhi
. From my point of view, this issue won't likely result in
Xerces XSD 1.1 implementation code improvements.
--
Regards,
Mukul Gandhi
hin my XML input documents), and I don't see with my test cases
the sorts of bugs which you've found. I've attached my test cases to the
Jira issue XERCESJ-1726.
I'd suggest that, let's continue this discussion on the Jira issue itself.
--
Regards,
Mukul Gandhi
ithin this thread & the Jira issue
(those that are provided by John).
--
Regards,
Mukul Gandhi
> I wonder whether it would help my case, if you could add your supporting
> information, that you had succeeded in replicating the problem, to the Jira
> case itself?
>
I've made few comments on the Xerces-J Jira issue you've posted, some time
ago.
--
Regards,
Mukul Gandhi
utput
displays nothing (except the time it took for the XSD validation to take
place).
--
Regards,
Mukul Gandhi
and do an analysis.
--
Regards,
Mukul Gandhi
g the XML prolog as ,
solves this problem for me.
--
Regards,
Mukul Gandhi
pe definition
2) Write the xs:assert as following
(the above suggested XSD fragments, are not tested from my side)
Another minor point. I had to add the following XML prolog to your XML
documents that are to be validated,
(your XML documents contain few characters, that cannot be represented with
the default encoding UTF-8).
--
Regards,
Mukul Gandhi
ML sibling invalid elements are large
(say couple of hundred or even thousands), then IMHO your suggested error
reporting would not look ok.
--
Regards,
Mukul Gandhi
t;
> I want to see both element 'A' and element 'B' being reported in the
> output.
>
For your requirements stated above, I could probably suggest the following
XML Schema 1.1 document (which makes the intent of XML Schema logic more
clear),
http://www.w3.org/2001/XMLSchema";>
--
Regards,
Mukul Gandhi
g the site
https://www.softwarebytes.org/xmlvalidation/, was to build it over Xerces-J.
Therefore, I shall follow as per my new thoughts.
On Mon, Jun 8, 2020 at 9:25 AM Mukul Gandhi wrote:
> Hi all,
>Sometime ago, I had deployed an 'online XML Schema validation service'
>
a validation
service' (i.e, as per my proposal, the preceding mentioned
site shall provide both Xerces-J and Saxon as options. I guess, that would
be more useful to users of the preceding mentioned site). If anyone has any
concerns about this, please let us know.
--
Regards,
Mukul Gandhi
. I expect
this link to be stable.
Any comments about usage of this service, would be welcome.
--
Regards,
Mukul Gandhi
also includes a few other minor enhancements.
Specifically, the changes introduced in this release are:
* Implemented few fixes for XML Schema identity constraints, within
Xerces's XML Schema 1.0 and 1.1 validators. [Sandy Gao, Mukul Gandhi]
* When XML Schema 1.1 validations are done,
eleaseNote.jspa?projectId=10520&styleName=Html&version=12346610
[5] https://svn.apache.org/repos/asf/xerces/java/trunk/KEYS,
https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/KEYS
On Mon, Dec 23, 2019 at 10:04 AM Mukul Gandhi wrote:
> Hi all,
>I'm think
unk, and 1.4 for build from xsd 1.1 dev branch) up to 13
(the latest we support).
For any concerns, please let us know.
On Mon, Dec 23, 2019 at 10:04 AM Mukul Gandhi wrote:
> Hi all,
>I'm thinking to initiate a revised vote for 2.12.1 release, during
> early January next year, due
Hi all,
I'm thinking to initiate a revised vote for 2.12.1 release, during early
January next year, due to an assumption that quite many people on Xerces
lists might be on holiday during this time.
I hope this would be fine.
On Mon, Dec 16, 2019 at 11:59 AM Mukul Gandhi wrote:
>
.12.1 version as
per the currently made release candidate (particularly any pmc member or a
long time committer, and also if suggested by pmc chair), and suggests to
address above mentioned jira issues as part of a release beyond 2.12.1
release.
Many thanks.
On Mon, Dec 16, 2019 at 11:59 AM Mukul
ache.org/jira/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12346610
--
Regards,
Mukul Gandhi
n use all other functionality provided by
Xerces-J). If you also wish, you may work with Xerces's source code and
produce a fix locally, and could also share best practices and any fix
patches with us.
--
Regards,
Mukul Gandhi
x27;;
> > Path schema = Paths.get(dir + "schema.xsd");
> > Files.write(schema, schemaString.getBytes());
> > Path catalog = Paths.get(dir + "catalog.xml");
> > Files.write(catalog, catalogString.getBytes());
> >
> > SchemaFactory sf = new XMLSchema11Factory();
> > XMLCatalogResolver r = new XMLCatalogResolver(new String[] {
> catalog.toUri().toString() });
> > sf.setResourceResolver(r);
> > sf.newSchema(schema.toFile());
> > }
> > }
>
--
Regards,
Mukul Gandhi
t;
> No SchemaFactory that implements the schema language specified by:
> http://www.w3.org/XML/XMLSchema/v1.1 could be loaded
>
This looks to me a classpath issue.
SchemaFactory sf = SchemaFactory.newInstance("
http://www.w3.org/XML/XMLSchema/v1.1";);
works for me.
--
Regards,
Mukul Gandhi
to this just now. Not much experience with kotlin
at the moment. Though I've worked with gradle & java combination.
--
Regards,
Mukul Gandhi
a 1.1?
>
I guess, you're looking for the information,
http://xerces.apache.org/xerces2-j/xml-schema.html#supported-schema-1.1-features
.
--
Regards,
Mukul Gandhi
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Saxon correctly evaluates that the XML is valid.
>
>
>
> XercesJ emits the following error:
>
> [Error] Test3.xml:11:8: cvc-assertion: Assertion evaluation
> ('empty(r/Date[xs:gYearMonth(xs:date(.)) ne
> ../../xs:gYearMonth(@DataFeed)])') for element 'root' on schema type
> '#AnonType_root' did not succeed.
>
--
Regards,
Mukul Gandhi
currently we don't have commit rights on that
project. Therefore as of now, we're not in position to fix any XPath 2.0
bugs identified after Xerces 2.12.0 release. I apologize, if you find this
current situation inconvenient.
--
Regards,
Mukul Gandhi
makes use of the syntax,
xs:gYearMonth(xs:date(.)). This form of constructor for xs:gYearMonth which
takes xs:date as argument,
doesn't seem to be supported properly by our XPath 2.0 processor. I also
can't find anywhere in the XPath 2.0 & related specifications, where this
is allowed and the
semantics of it.
--
Regards,
Mukul Gandhi
I believe.
--
Regards,
Mukul Gandhi
d)
--
Regards,
Mukul Gandhi
x27;s Jira site.
also, jaxp.SourceValidator is just a sample. You might try writing a Java
component from scratch using XSD 1.1 support available in Xerces, using
JAXP API for XSD 1.1 validation. That should work I believe, for your
scenario.
--
Regards,
Mukul Gandhi
ml
>
> You seem to be using the base-uri(.) function in your xs:assert. As I said
earlier, Xerces's xs:assert evaluation does not preserve the URI of XML
file that is being validated, that can be returned by the base-uri(.) call
in an xs:assert. Therefore, while using XSD 1.1 validation (spec
.com/xml/note.xml";.
For the future, requesting you to please provide a minimal XML and XSD
sample that is focused only on the actual issue. That makes it easier to
debug on our side.
--
Regards,
Mukul Gandhi
t mean, that Xerces
cannot run on higher version JREs (I've personally tested, that Xerces
2.12.0 can run fine up to JDK 9).
May be its time, we need to revisit the min JDK levels for Xerces. Michael
Glavassevich needs to organize consensus on this.
--
Regards,
Mukul Gandhi
y an Eclipse IDE problem (I'm
using the 2014 edition). I had given the XSD 1.1 project as a dependency to
my own project, and this should have provided xml-apis.jar to my own
project.
Thanks for your help.
--
Regards,
Mukul Gandhi
using JDK 1.4.2 within the mentioned Eclipse workspace.
--
Regards,
Mukul Gandhi
>
>
>
>
>
>
>
> Rule #1
> string literal, passed<
> /xs:documentation>
>
>
>
>
> Rule #2
> string from country element value,
> fails
>
>
>
>
> Rule #3
> cast as string from country element
> value, passed
>
>
>
>
>
>
>
>
>
--
Regards,
Mukul Gandhi
tractInterestExpense) -
> sum(ContractLineItems/ContractLineItem/IFRSAdjustmentsCurrentMonth)) le
> subsequence((0.05, 0.1, 0.05, 0.05, 0.05, 0.05, 0.05),
> index-of(('BO','CO','GT','HN','PY','SV','TZ'), CountryCode), 1)) then
> true() else false()') for element 'r' on schema type '#AnonType_r' did not
> succeed. XPTY0004 - Value does not match a required type.
>
> [Error] id0001_TZ20180100_IFRS15_CBCOutput_3TZ005.xml:213:8:
> cvc-assertion: Assertion evaluation ('if (abs((ContractValueShortTerm +
> ContractValueLongTerm) - ContractValue) le subsequence((0.05, 0.1, 0.05,
> 0.05, 0.05, 0.05, 0.05), index-of(('BO','CO','GT','HN','PY','SV','TZ'),
> CountryCode), 1)) then true() else false()') for element 'r' on schema type
> '#AnonType_r' did not succeed. XPTY0004 - Value does not match a required
> type.
>
> [Error] id0001_TZ20180100_IFRS15_CBCOutput_3TZ005.xml:213:8:
> cvc-assertion: Assertion evaluation ('if (abs((ContractValueShortTermT0 +
> ContractValueLongTermT0) - ContractValueT0) le subsequence((0.05, 0.1,
> 0.05, 0.05, 0.05, 0.05, 0.05), index-of(('BO','CO','GT','HN','PY','SV','TZ'),
> CountryCode), 1)) then true() else false()') for element 'r' on schema type
> '#AnonType_r' did not succeed. XPTY0004 - Value does not match a required
> type.
>
> [Error] id0001_TZ20180100_IFRS15_CBCOutput_3TZ005.xml:213:8:
> cvc-assertion: Assertion evaluation ('if (abs((ContractAssetShortTerm +
> ContractAssetLongTerm) - ContractAsset) le subsequence((0.05, 0.1, 0.05,
> 0.05, 0.05, 0.05, 0.05), index-of(('BO','CO','GT','HN','PY','SV','TZ'),
> CountryCode), 1)) then true() else false()') for element 'r' on schema type
> '#AnonType_r' did not succeed. XPTY0004 - Value does not match a required
> type.
>
> [Error] id0001_TZ20180100_IFRS15_CBCOutput_3TZ005.xml:213:8:
> cvc-assertion: Assertion evaluation ('if (abs((ContractLiabilityShortTerm
> + ContractLiabilityLongTerm) - ContractLiability) le subsequence((0.05,
> 0.1, 0.05, 0.05, 0.05, 0.05, 0.05),
> index-of(('BO','CO','GT','HN','PY','SV','TZ'),
> CountryCode), 1)) then true() else false()') for element 'r' on schema type
> '#AnonType_r' did not succeed. XPTY0004 - Value does not match a required
> type.
>
> [Error] id0001_TZ20180100_IFRS15_CBCOutput_3TZ005.xml:213:8:
> cvc-assertion: Assertion evaluation ('if (abs(ContractNetContractPositionT0
> - sum(ContractLineItems/ContractLineItem[./MaterialCategory eq
> 'HARDWARE']/(RelativeStandaloneSellingPriceTotal -
> TransactionPriceTotal)) +
> sum(ContractLineItems/ContractLineItem[./MaterialCategory
> = 'FEE']/TransactionPriceTotal)) le subsequence((0.05, 0.1, 0.05, 0.05,
> 0.05, 0.05, 0.05), index-of(('BO','CO','GT','HN','PY','SV','TZ'),
> CountryCode), 1)) then true() else false()') for element 'r' on schema type
> '#AnonType_r' did not succeed. XPTY0004 - Value does not match a required
> type.
>
> file:///d:/Temp/CDW/IFRS/IFRS15_CBC_Out/TanzaniaZantel/
> id0001_TZ20180100_IFRS15_CBCOutput_3TZ005.xml: 278 ms
>
>
>
>
>
>
>
>
>
> Regards,
>
> Yitzhak Khabinsky
>
> Technical Services Lead
>
> Millicom International Services LLC
>
> 396 Alhambra Circle, Suite 1100
>
> Coral Gables, FL 33134
>
> Skype4B: +1 (305) 445-4172
>
> Tel: (954) 684-8673
>
> *yitzhak.khabin...@millicom.com <.khabin...@millicom.com>*
>
> www.millicom.com
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.millicom.com%2F&data=02%7C01%7CMalcolm.Stewart%40microsoft.com%7C9338023699c2494d08be08d4ad12ce55%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636323743686702678&sdata=DxQ9dfL259rpdVZ9seOAcR6bvgxRobyIerOgvTgPc90%3D&reserved=0>
>
>
>
--
Regards,
Mukul Gandhi
ork prior to JDK 1.9. With JDK 1.9 and above, simply placing the new
Xerces jars in the system classpath shall work. Starting from JDK 1.9,
the jre\lib\endorsed
method has been removed from the JDK.
--
Regards,
Mukul Gandhi
ent describes how to release Maven artifacts.
*These are optional*..
--
Regards,
Mukul Gandhi
clearly, 2) is also another method. Of course, 3)
above is also yet another method for fetching Maven dependencies.
--
Regards,
Mukul Gandhi
l. With Gradle,
it can be done via following syntax,
repositories {
flatDir {
dirs 'libs'
}
}
(a Jar needs to be simply available in a local "libs" folder, for Gradle to
pick it).
Any good java build system, ought to provide methods to have local
standalone Jars as part of builds.
--
Regards,
Mukul Gandhi
l.html.
--
Regards,
Mukul Gandhi
ever been part of our release process. Other people from the
community would have uploaded those previous releases."
I hope that could answer the question.
--
Regards,
Mukul Gandhi
chael Glavassevich]
* Implemented improvements to XML Schema 1.1 CTA implementation and
inheritable attributes. [Mukul Gandhi, Hiranya Jayathilaka]
* Implemented improved error/warning message reporting for various XML
Schema use cases. [Mukul Gandhi]
* Implemented few performance enhancements (affe
else could also comment.
--
Regards,
Mukul Gandhi
Hi all,
On Tue, May 1, 2018 at 10:49 AM, Mukul Gandhi wrote:
>
> Presently we're experiencing some issues, making Xerces-J 2.12.0 files
> available at http://xerces.apache.org/mirrors.cgi. We're seeking help
> from Henk (apache infra, and other members of private@xerces
ts
about the Xerces 2.12.0 release.
--
Regards,
Mukul Gandhi
On Mon, Apr 30, 2018 at 9:15 AM, Mukul Gandhi wrote:
> Hi all,
>The vote to release Xerces-J 2.12.0 resulted in 3 +1 votes (all from
> PMC members) and no other votes:
>
> +1 by: Gareth Reakes (PMC) Michael Glavassevich (PMC) Mukul Gandhi (PMC)
>
> The release should
Hi all,
The vote to release Xerces-J 2.12.0 resulted in 3 +1 votes (all
from PMC members)
and no other votes:
+1 by: Gareth Reakes (PMC) Michael Glavassevich (PMC) Mukul Gandhi (PMC)
The release should be up on the mirror sites very soon.
On Mon, Apr 23, 2018 at 5:36 PM, Mukul Gandhi wrote
. (suggestions from sebb, seb...@gmail.com during
this voting)
--
Regards,
Mukul Gandhi
generally
> moved / deleted after use.
> And indeed re-used, as here.
I've deleted the .md5 files from the location,
https://dist.apache.org/repos/dist/dev/xerces/j/2.12.0/.
I'll write a new voting mail again, as a continuation of this thread.
--
Regards,
Mukul Gandhi
talking about the revision number I've marked in bold emphasis? Do
you require mentioning this revision number in voting mails (along side the
link, https://dist.apache.org/repos/dist/dev/xerces/j/2.12.0/) ?
--
Regards,
Mukul Gandhi
amp;version=12336542
[5] https://markmail.org/message/54obpdyqrn6nfzgi : discussion about
previous RC, suggesting a revote.
--
Regards,
Mukul Gandhi
these issues.
> >
> > Thanks.
> >
> > Michael Glavassevich
> > XML Technologies and WAS Development
> > IBM Toronto Lab
> > E-mail: mrgla...@ca.ibm.com
> > E-mail: mrgla...@apache.org
--
Regards,
Mukul Gandhi
erces/java/tags/Xerces-J_2_12_0/
[3]
http://svn.apache.org/viewvc/xerces/java/tags/Xerces-J_2_12_0-xml-schema-1.1/
[4]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10520&version=12336542
--
Regards,
Mukul Gandhi
ml-apis.jar
%JAVA_HOME%\bin\java -classpath %CP% jaxp.SourceValidator -i %1 -a %2 -f
-xsd11
Therefore I can claim,
XercesJ XSD 1.1 runs fine on Java 1.4.x upto Java 9,
&
XercesJ on trunk runs fine on Java 1.3.x upto Java 9.
--
Regards,
Mukul Gandhi
Thanks, David. Great to see you on these lists.
Regards,
Mukul Gandhi
On 11 October 2016 at 11:23, David Williams
wrote:
> On 10/10/2016 01:59 AM, Mukul Gandhi wrote:
>
> Hi all,
>I was unsubscribed to these Xerces lists for some time. I've subscribed
> again. I'm
Hi all,
I was unsubscribed to these Xerces lists for some time. I've subscribed
again. I'm testing my membership in this mail. Apologies for inconvenience.
If one of you can reply, that my mails were received on both these lists
it'll help me.
Regards,
Mukul Gandhi
gards,
Mukul gandhi
s are failing and which tests have been
> corrected in the Rackspace branch.
>
>
> -jOrGe W.
>
>
>
> --
> *From:* Mukul Gandhi
> *Sent:* Friday, June 24, 2016 3:58 AM
> *To:* j-users@xerces.apache.org
> *Cc:* s...@tunnelvisionlabs.com
>
r1396551) was made in the "xml-schema-1.1-dev"
> >>>> branch, not trunk, so that branch would have to be merged back to
> >>>> trunk (or the fix duplicated in trunk) in order for a 2.12.0 release
> >>>> to benefit my organization.
> >>
> >>
> >> From: Michael Glavassevich
> >>> I'll take a look at the original fix. Assuming it applies to XML
> > Schema
> >>> 1.0, it should have been committed at the same time to the trunk.
> >>
> >>
> >> That would be appreciated, Michael. Thanks.
> >>
>
> --
> Regards,
> Mukul Gandhi
>
open in JIRA? Or am I misunderstanding
> something about XML?
>
> -
> To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
> For additional commands, e-mail: j-users-h...@xerces.apache.org
>
> --
> Regards,
> Mukul Gandhi
>
D 1.0 and 1.1 code bases.
>
> Sorry for the typo.
>
>
>
> On 15 September 2015 at 18:43, Mukul Gandhi wrote:
>
>
>
> Hello there,
>I've been thinking on this for a while, and now I'm ready to share the
> outcomes with Xerces forums. I've dev
f a valid document against a XML Schema 1.1
> with one included schema. It worked great. I tested a couple of times
> invalidating the data and it seems to respond accordingly. Have you
> executed the full test suite on it?
>
>
> On Tue, Sep 15, 2015 at 10:13 AM, Mukul Gandhi
I meant, This app uses the _latest_ XercesJ XSD 1.0 and 1.1 code bases.
Sorry for the typo.
On 15 September 2015 at 18:43, Mukul Gandhi wrote:
>
> Hello there,
>I've been thinking on this for a while, and now I'm ready to share the
> outcomes with Xerces forums. I
link to this app is
http://xmlvalidation-mukulga.rhcloud.com
This app uses the last XercesJ XSD 1.0 and 1.1 code bases. It'll be great
if any of you folks give this app a try, and post comments on this list.
--
Regards,
Mukul Gandhi
On 17 July 2014 21:19, sshanmug wrote:
> Thanks for the response. I added the assert and it's working.
> Basically I added the following assert
>
>
That shall also work. Its upto you. If you wish to save few keystrokes, you
can opt for the I mentioned.
--
Regards,
Mukul Gandhi
ion
within your type abstract-comp-type,
This will work for your requirement, because asserts are derived all the
way down the type hierarchy.
--
Regards,
Mukul Gandhi
o do not know if there is a class in
> Xerces where I could check every element that is validated, not only those
> that issues an error.
>
> Thanks for the help.
>
> Best regards,
> Vinícius
>
>
>
> Regards,
> Mukul Gandhi
>
In Xerces
> main page, it says assertions are supported, so I believe I may be doing
> something wrong, but I haven't been able to find the mistake. Do you have
> any suggestions ?
>
> Thanks,
> Vinícius
>
--
Regards,
Mukul Gandhi
more challenging way may be
to, read it directly from DTD), and during serialization use this extra
information to affect the serialization in your desired way. Another
approach may be to, let the serializer emit the unspecified attributes and
then use this output with a DTD or an external metadata as a unit for your
application.
>
> --
> Regards,
> Mukul Gandhi
>
>
>
>
>
>
>
> B.xsd
>
>
>
> http://www.w3.org/2001/XMLSchema";>
>
>
>
>
>
>
>
>
>
>
>
>
> Thank you very much
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
>
> Now, I would like to use as key not "AddressID" but the pair ("Street","City")
> How should I modify the xsd file?
>
> Thnaks in advance
>
> Roberto
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
cal error in my schema, or if I’m not using some element
> correctly. Can someone give me some hints on how to debug the assertion’s
> application?
>
>
>
> Thanks in advance,
>
> Jim Barnett
--
Regards,
Mukul Gandhi
---
;
>
>maxOccurs="1"
> minOccurs="0"/>
>maxOccurs="1"
> minOccurs="0"/>
>maxOccurs="1"
> minOccurs="0&q
Its my pleasure to be of help.
On Mon, Apr 22, 2013 at 2:49 AM, Jim Barnett wrote:
> Mukul,
>
> Yes, you are right. Count() works as you say.
>
>
>
> Thank you for your help.
>
>
>
> -
), fails:
>
>
>
>
>
>
>
>
>
> What am I doing wrong?
>
>
>
> Thanks,
>
> Jim
--
Regards,
Mukul Gandhi
##targetNamespace"' attribute is something I
> stumbled across when trying to get some other assertions to work, but I admit
> that I don't really understand what effects it may be having.
>
> Thank you for your help.
>
> - Jim
--
Regards,
Mukul Gandhi
--
alidation? I am applying an assertion to an element with a ‘target’
> attribute whose value is “s1 s2”, yet the following assertion is failing:
>
>
>
> xpathDefaultNamespace="##targetNamespace"/>
>
>
>
> Any guidance would be appreciat
ry if this is not helpful.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
xml is not valid.
>
> I'm grateful for some hints.
>
> Thanks!
>
> Best regards,
> Ronny
>
> ---------
> To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
> For additional commands, e-mail:
t; Av. Sao Francisco, 98
>
> 18.095-450 Sorocaba
>
> BRASIL
>
> ** **
>
> T +55 15 3332 9720
>
> F +55 15 3332 9711
>
> constantino.cronember...@gft.com
>
> www.gft.com/br
>
> www.gft-blog.com.br
>
> www.twitter.com/gft_br
>
>
> _
>
>
>
>
--
Regards,
Mukul Gandhi
_
>
>
>
> * <http://www.gft.com/cebit>*
>
> *
> GFT Brasil Consultoria Informática Ltda.*
> **
>
> **
>
> Av. Sao Francisco, 98
>
> 18.095-450 Sorocaba
>
> BRASIL
>
> ** **
>
> T +55 15 3332 9720
>
> F +55 15 3332 9711
>
> constantino.cronember...@gft.com
>
> www.gft.com/br
>
> www.gft-blog.com.br
>
> www.twitter.com/gft_br
>
>
> _
>
>
> --
> Regards,
> Mukul Gandhi
>
>
<>
1 - 100 of 220 matches
Mail list logo
