Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Offline/Local EntityResolver to use?

Do I take that as a blessing to use one of these classes?
If saw, which one do you recommend?

On Tue, Apr 9, 2013 at 3:09 PM, Chuck Bridgham <cbridgha@xxxxxxxxxx> wrote:
All of those classes are considered protected  internal api in spite of the internal package name.   Changing the namespace would have caused too much breakage, so decided to keep as is.

API policy here:

Thanks - Chuck

Senior Architect, RAD Java EE Tools, WTP PMC Lead
IBM Software Lab - Research Triangle Park, NC

From:        Fred Bricon <fbricon@xxxxxxxxx>
To:        "General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
Date:        04/09/2013 05:30 AM
Subject:        [wtp-dev] Offline/Local EntityResolver to use?
Sent by:        wtp-dev-bounces@xxxxxxxxxxx


When I migrated JBoss Tools JSF m2e connector over to m2e-wtp, I removed the use of JBoss Tools own DTDResolver [1][2], but didn't replace it by something equivalent from WTP's API.

This bug [3], while not exactly related, reminded me of the situation. Quickly looking for EntityResolver implementations in WTP's code, I probably missed some of them but I found at least
* org.eclipse.wst.common.componentcore.internal.impl.WTPEntityResolver
* org.eclipse.jst.j2ee.internal.xml.J2EEXmlDtDEntityResolver
* org.eclipse.jst.j2ee.core.internal.plugin.CatalogJ2EEXmlDtDEntityResolver

All of them are internal classes. Any recommendations on the best way to proceed here? Should I just fork say, into m2e-wtp, or call wtp's internal class?



Fred Bricon

"Have you tried turning it off and on again" - The IT Crowd _______________________________________________
wtp-dev mailing list

wtp-dev mailing list

"Have you tried turning it off and on again" - The IT Crowd

Back to the top