Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Saxon processor to accept an optional Saxon XML configuration file... #1

Closed
wants to merge 2 commits into from

Conversation

papile
Copy link

@papile papile commented Apr 25, 2014

Hello,
I had the need to set the options in Saxon using a configuration file as in http://www.saxonica.com/documentation/configuration/configuration-file/ so I made the Processor call take an optional config file. If you find it useful you can include it.

…ile. Clean up require statements to conform to gem style conventions.
fidothe added a commit that referenced this pull request Aug 10, 2014
For File and open-uri'd IO's we can grab the path / base_uri and set the
System ID on the StreamSource automatically, partly addressing PR #1.

Update dev dependencies and introduce VCR so we can actually use
`open-uri` correctly (it handles `file://` URLs differently from http
ones)
fidothe added a commit that referenced this pull request Aug 10, 2014
Addresses the last of the System ID stuff in #1
fidothe added a commit that referenced this pull request Aug 10, 2014
This tackles the main part of @papile's #1.

The test for this is messy because it's unclear to me whether the
configuration object is something that should be manipulated after the
processor has been created. Feedback from @michaelhkay @ond1 or @papile
appreciated on that one.
fidothe added a commit that referenced this pull request Aug 10, 2014
This tackles the main part of @papile's #1.

The test for this is messy because it's unclear to me whether the
configuration object is something that should be manipulated after the
processor has been created. Feedback from @michaelhkay @ond1 or @papile
appreciated on that one.
fidothe added a commit that referenced this pull request Aug 10, 2014
This tackles the main part of @papile's #1.

The test for this is messy because it's unclear to me whether the
configuration object is something that should be manipulated after the
processor has been created. Feedback from @michaelhkay @ond1 or @papile
appreciated on that one.
@fidothe
Copy link
Owner

fidothe commented Aug 10, 2014

Thanks for this. I've made the same functionality available on master now, so I won't pull this in. I see you have a 9.5EE branch in your fork. We should chat about how best to make using EE with this gem easy - bundling the jar (as you've done) is probably out because of licensing conditions, right? I'll have a think, anyway.

@fidothe fidothe closed this Aug 10, 2014
@fidothe
Copy link
Owner

fidothe commented Aug 10, 2014

I need to add some Yardoc and pull in HE 9.5 and then I'll cut a new gem release. Should be this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants