Hi David, This mailing list is purely for WTP development. You asked the question on the newsgroup late yesterday afternoon...I am sure with a bit of patience someone would've answered there.
I don't know much about how embedded servers work, but I would suspect they don't ship by default or use the workspace XML catalog. Looking at the problem from a pure XML point of view, I suspect it would be up to the program that parses that XML file to provide an entity resolver, perhaps delegating to an XML catalog to resolve your schema. The schema itself may be located on the web or shipped with your application. I would suggest you ask the Spring folks if they support this scenario. I hope this helps. Cheers, Valentin Baciu Rational XML Web Services Tools From: David Durham <[email protected]> To: [email protected]. Date: 02/04/2010 11:21 AM. Subject: [wtp-dev] Embedded servers should use the XML Catalog user entries Sent by: [email protected] Hi all, I posted this on the newsgroup and didn't get a response. I'm thinking the problem is a bug, and I'll file a bug report, unless someone has a good reason why I shouldn't. Bug details below. I'm extending spring with a namespace. The way that works is you provide a schema xsd file in your jar and hook into spring xml processing for schema validation and such. In eclipse, the schema is expected to be available at a given location. For instance: <beans xmlns="http://www.springframework.org/schema/beans" xmlns:ws="http://mywork/namespace xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5 .xsd http://mywork/namespace http://mywork/namespace.xsd "> So everything works if I actually have an xsd at 'http://mywork/namespace.xsd' I can add an entry in the eclipse XML catalog so that the XML editor works. However, when I launch a webapp with an embedded WTP tomcat instance, I see this error: Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'myelement' This is the same error the editor was giving before I added the user entry to xml catalogs. So, does WTP use those entries as well? It would appear not. Anyone seen this and have a solution? _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
<<inline: graycol.gif>>
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
