Nabble - Xerces

[jira] Commented: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

2009-12-09T09:19:18Z

[ https://issues.apache.org/jira/browse/XERCESC-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788172#action_12788172 ]

Boris Kolpackov commented on XERCESC-1900:
------------------------------------------

I agree with Scott's reasoning plus I don't think we should create special configurations for this case. We already have a large number of them (Debug/Release x 32/64 x ICU/no-ICU, etc) and it is getting harder and harder to maintain. On the other hand, changing the runtime flag in the existing configuration is trivially easy.

If there are no objections, I would like to close this issue.

> Compile xerces.dll using /MT to remove the dependency on msvcr90.dll
> --------------------------------------------------------------------
>
> Key: XERCESC-1900
> URL: https://issues.apache.org/jira/browse/XERCESC-1900
> Project: Xerces-C++
> Issue Type: Improvement
> Components: Build
> Affects Versions: 3.0.1
> Environment: Windows OS.
> Reporter: David Wendt
> Priority: Trivial
>
> The xerces-c_3_0.dll requires msvc90.dll to be installed. We have found that some of our customers do not have the msvcr90.dll installed on their machines.
> Changing the compile flag from /MD to /MT for the Release configuration will remove the dependency (compiles all needed C-runtime code into the xerces DLL itself). The result is a 90KB bigger DLL which is only about 6% increase in size.
> I can provide the modified .vcproj.
> Another option is to create a separate Release configuration with this compile option too.

--
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: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...

From forum: Xerces - C - Dev

[jira] Commented: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

2009-12-09T08:11:18Z

[ https://issues.apache.org/jira/browse/XERCESC-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788139#action_12788139 ]

David Wendt commented on XERCESC-1900:
--------------------------------------

Ok, I understand. Thanks Scott.

From forum: Xerces - C - Dev

[jira] Commented: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

2009-12-09T08:03:18Z

[ https://issues.apache.org/jira/browse/XERCESC-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788136#action_12788136 ]

Scott Cantor commented on XERCESC-1900:
---------------------------------------

It's not a licensing issue, it's a "if you change this for everybody else, most code in the world using Xerces on Windows will crash" issue.

If they want to add optional build targets, that's fine, but as a default it's entirely the wrong choice.

Note that MS itself now defaults builds to the DLL version, I believe, and has generally steered everybody that way so that they can properly address security fixes to the runtime. Your approach as with all static linking makes you responsible for all fixes.

If you're worried about disk size, just offer it as a separate download.

From forum: Xerces - C - Dev

[jira] Commented: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

2009-12-09T07:57:18Z

[ https://issues.apache.org/jira/browse/XERCESC-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788134#action_12788134 ]

David Wendt commented on XERCESC-1900:
--------------------------------------

The MS runtime merge modules more than doubled our install size. I'm ok with the 90KB increase. The code works great on the test machines we have. Is there any issue (licensing, etc) with me shipping this rebuilt statically linked version? No code was changed. Just the project file.

From forum: Xerces - C - Dev

[jira] Commented: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

2009-12-09T07:39:18Z

[ https://issues.apache.org/jira/browse/XERCESC-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788127#action_12788127 ]

Scott Cantor commented on XERCESC-1900:
---------------------------------------

As an option, it's fine, but 99% of today's apps assume DLL-based runtimes and mixing runtime models in a program stack crashes (or used to) due to memory management issues.

You should probably consider bundling MS' runtime library merge modules into your installer.

From forum: Xerces - C - Dev

[jira] Created: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

2009-12-09T06:29:18Z

Compile xerces.dll using /MT to remove the dependency on msvcr90.dll
--------------------------------------------------------------------

Key: XERCESC-1900
URL: https://issues.apache.org/jira/browse/XERCESC-1900
Project: Xerces-C++
Issue Type: Improvement
Components: Build
Affects Versions: 3.0.1
Environment: Windows OS.
Reporter: David Wendt
Priority: Trivial

The xerces-c_3_0.dll requires msvc90.dll to be installed. We have found that some of our customers do not have the msvcr90.dll installed on their machines.

Changing the compile flag from /MD to /MT for the Release configuration will remove the dependency (compiles all needed C-runtime code into the xerces DLL itself). The result is a 90KB bigger DLL which is only about 6% increase in size.

I can provide the modified .vcproj.
Another option is to create a separate Release configuration with this compile option too.

--
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: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...

From forum: Xerces - C - Dev

[jira] Issue Comment Edited: (XERCESJ-1392) Xerces breakes schema grammar with hints from instance xsi:schemaLocation

2009-12-06T03:03:18Z

[ https://issues.apache.org/jira/browse/XERCESJ-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786504#action_12786504 ]

Ashitkin Alexander edited comment on XERCESJ-1392 at 12/6/09 11:02 AM:
-----------------------------------------------------------------------

Hi Michael, thanks for your response. I don't quite sure i've understood you correctly. If points 1 and 2 are questions, then answers are:
1) i suppose the point 1 is regarding the error.xml instance. I don't see any reason to use schemaLocation specified on the xs:import. From my point of view xs:import is an incapsulated part of the schema and i only should provide valid schemaLocations either by external-schemaLocation property, either by xsi:schemaLocation hint. I hope you agree the xsi:schemaLocation in error.xml is absolutely valid and enough for validation. If you suppose i need to use schemaLocation specified on the xs:import, please explain this.
2) i think the point is inside - out, should be : "Using the URI specified in the instance as a schemaLocation in the xs:import" and if i understood right, this behaviour is just wrong. if i have a set of schemas under the same namespace whose linked relatively, this behaviour will break everything. In a case of honour-all-schemalocations this behaviour even more questionable.

was (Author: ashitkin.alexander):
Hi Michael, thanks for your response. I don't quite sure i've understood you correctly. If points 1 and 2 are questions, then answers are:
1) i suppose the point 1 is regarding the error.xml instance. I don't see any reason to use schemaLocation specified on the xs:import. From my point of view xs:import is an incapsulated part of the schema and i only should provide valid schemaLocations either by external-schemaLocation property, either by xsi:schemaLocation hint. I hope you agree the xsi:schemaLocation in error.xml is absolutely valid and enough for validation. If you suppose i need to use schemaLocation specified on the xs:import, please explain this.
2) from my point of view point is inside - out, should be : "Using the URI specified in the instance as a schemaLocation in the xs:import" i think with behaviour is just wrong. if i have a set of schemas under thesame namespace whish resolves relatively, it will break everything.

> Xerces breakes schema grammar with hints from instance xsi:schemaLocation
> -------------------------------------------------------------------------
>
> Key: XERCESJ-1392
> URL: https://issues.apache.org/jira/browse/XERCESJ-1392
> Project: Xerces2-J
> Issue Type: Bug
> Components: JAXP (javax.xml.validation)
> Affects Versions: 2.9.1
> Environment: Windows XP 2003
> Reporter: Ashitkin Alexander
> Attachments: XercesBug.zip
>
>
> Xerces trying to resolve xs:import in schema using relative paths from xsi:schemaLocation hint. Thus, validation fails with a "Failed to read schema document" message.

--
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: j-dev-unsubscribe@...
For additional commands, e-mail: j-dev-help@...

Nabble - Xerces

[jira] Commented: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

[jira] Commented: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

[jira] Commented: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

[jira] Commented: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

[jira] Commented: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

[jira] Created: (XERCESC-1900) Compile xerces.dll using /MT to remove the dependency on msvcr90.dll

[jira] Issue Comment Edited: (XERCESJ-1392) Xerces breakes schema grammar with hints from instance xsi:schemaLocation

[jira] Commented: (XERCESJ-1408) assertions facet validation rules, implementation improvements

[jira] Assigned: (XERCESJ-1408) assertions facet validation rules, implementation improvements

[jira] Commented: (XERCESJ-1392) Xerces breakes schema grammar with hints from instance xsi:schemaLocation

How to get Xerces configuration on HP-UX ia64 box to work? Missing a transcoder???

Re: Special characters problem while writing XML files using JAXP DOM Parser

Re: Special characters problem while writing XML files using JAXP DOM Parser

Re: Special characters problem while writing XML files using JAXP DOM Parser

Re: External entity in XML causing null pointer exception during DocumentBuilder.parse

External entity in XML causing null pointer exception during DocumentBuilder.parse

Re: Special characters problem while writing XML files using JAXP DOM Parser

[jira] Closed: (XERCESC-1899) XML namespaces with more than one hyphens appear to be broken during validating parse

[jira] Created: (XERCESC-1899) XML namespaces with more than one hyphens appear to be broken during validating parse

Re: Special characters problem while writing XML files using JAXP DOM Parser

Special characters problem while writing XML files using JAXP DOM Parser

Re: Null pointer exception during DocumentBuilder.parse(?file?);

Re: Null pointer exception during DocumentBuilder.parse(?file?);

Null pointer exception during DocumentBuilder.parse(”file”);

[jira] Updated: (XERCESJ-1407) renameNode creates wrong Node Implementation with PSVI, HTML and WML DOM

[jira] Updated: (XERCESJ-1407) renameNode creates wrong Node Implementation with PSVI, HTML and WML DOM

[jira] Updated: (XERCESJ-1301) EventListeners should be garbage collectable if the nodes the listeners are registered upon are garbage collected

[jira] Updated: (XERCESJ-1301) EventListeners should be garbage collectable if the nodes the listeners are registered upon are garbage collected

[jira] Updated: (XERCESJ-1407) renameNode creates wrong Node Implementation with PSVI, HTML and WML DOM

[jira] Updated: (XERCESJ-1407) renameNode creates wrong Node Implementation with PSVI, HTML and WML DOM

[jira] Updated: (XERCESJ-1408) assertions facet validation rules, implementation improvements

[jira] Updated: (XERCESJ-1409) Optimization for random indexed access upon NodeList

[jira] Created: (XERCESJ-1409) Optimization for random indexed access upon NodeList

[jira] Commented: (XERCESJ-1397) After invoking mutating methods upon CharacterData, DOMCharacterDataModified events are always thrown even if the content remains the same (i.e. no change happend)

[jira] Updated: (XERCESJ-1408) assertions facet validation rules, implementation improvements