Giter VIP home page Giter VIP logo

Comments (5)

lcduarte avatar lcduarte commented on July 21, 2024 1

Hello,

You are very welcome, it is nice to know that this project seems to be helping people other than me :)

Your suggestion seems pretty straightforward and at first glance it doesn't bring any problems so I should be able to perform a new release this weekend.
Regarding your second point, there aren't really plans to solve that issue in the near future. Although it is a necessary feature since most approaches use multiple schemas it would possibly require a reasonable amount of changes in the project and at the moment I don't have the time needed to do that.

Thanks for the issue and input.

Best Regards,
Luís

from xsdparser.

LouizFC avatar LouizFC commented on July 21, 2024

I was messing with the getSchemaNode method and Inoticed that it can take a InputSource as parameter DocumentBuilderFactory.newInstance().newDocumentBuilder().parse accepts a InputSource, which can be created with a InputStream.

I haven't tested it yet, but I think that it would solve my second point, It is possible to create a InputStream from a String

from xsdparser.

lcduarte avatar lcduarte commented on July 21, 2024

Hello,

I've performed a new release, 1.0.17, which allows to pass new configurations in the XsdParser constructor. This should fix your points 1 and 3.

In regards to the InputStream, I can't recall precisely but I think I ended up not using it because I was getting some kind of problem by using it.

Regarding your second point, can you explain it further?

from xsdparser.

LouizFC avatar LouizFC commented on July 21, 2024

Thank you for the speedy release.

My second point is the following:

When parsing a WSDL, I need to strip all the "types" tag content to a different file, that's because XsdParser only accepts a filePath, which works but is kinda undesirable.

The "ideal" way for me would it be able to accept a InputStream, because we could "skip" the types on our main parser, and delegate it to XsdParser on only one read.

Maybe an API that accepts a Node would also work. We use JSoup for commodity, but everything is encapsuled, so switching to org.w3c package would not be hard too.

Edit: Also, I tested the new release just now, it works perfectly. Thank you very much

from xsdparser.

fmcarvalho avatar fmcarvalho commented on July 21, 2024

@LouizFC I noticed that you are not a XsdParser stargazer yet. Could you please give a star to increase popularity. Thanks

from xsdparser.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.