XML Catalog, assistance needed
by Rob Stryker
Hi:
I'm looking at separating out the xml schema catalog entries into their
own plugin, and a request has been made to add even more schemas. But
I'm having a problem discovering how to do it uniformly. There are
several syntaxes used to add entries, and I really don't know which
syntax to use and when:
We use the following syntaxes at varying times:
This first one (FORMAT 1) is most often used by our legacy dtd's, and I
honestly have no idea how it works at all:
<public publicId="-//JBoss//DTD JBOSS 4.0//EN"
uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_4_0.dtd"
webURL="http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd"/>
I've seen this next entry (FORMAT 2) added as well. The thing to note
here is that the name attribute, which I believe represents namespace,
is set to http://www.jboss.com/xml/ns/javaee, but an open jira indicates
this type of catalog entry will form invalid xml files and we should
avoid it.
<uri name="http://www.jboss.com/xml/ns/javaee"
uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jbossws-web-services_1_0.xsd"/>
The next syntax (FORMAT 3) is similar, but seems to have a namespace
that points to a specific xsd file.
<uri name="http://www.jboss.org/j2ee/schema/jboss_5_0.xsd"
uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_5_0.xsd"/>
The fourth (FORMAT 4) seems most often used by our newest schema, and
seems the most successful one.
<uri name="urn:jboss:1.0"
uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_1_0.xsd"/>
The problem for me is that when I look at many other xsd files that
could be added, they don't show namespaces in a urn:jboss format.
Looking at the xsd files directly, they also don't have a string like
"http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" anywhere in the xsd
file, so I can't use formats 4 or 3. I have no idea how format 1 works,
and format 2 has been indicated to be non-functional.
So if I want to add an xsd file that has header like the one below, I
have no idea how to add it:
<xsd:schema
targetNamespace="http://java.sun.com/xml/ns/javaee"
xmlns:javaee="http://java.sun.com/xml/ns/javaee"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
version="2.1">
Ideally, I would make a small script in the plugin to regenerate the
catalog entries based on what files are in the folder. This way it'd be
deterministic, and we can add whole collections of schemas after each
new major release of jee or wildfly. But I really can't figure out which
catalog entry forms to use against what types of xsd files or how to
properly map it at all.
Any help here would be very much appreciated.
11 years, 11 months
Proposed change to JBT 4.40.Beta2-SNAPSHOT target platform: remove GPE/GWT, fix Atlassian
by Nick Boldt
Here is a proposal for a change to the JBoss Tools 4.40.0.Beta2-SNAPSHOT
target platform:
https://github.com/jbosstools/jbosstools-target-platforms/pull/50
https://github.com/jbosstools/jbosstools-target-platforms/pull/49
https://github.com/jbosstools/jbosstools-target-platforms/pull/48
It consists of the following changes:
* JBIDE-16960 Remove unneeded GPE/GWT features/plugins from TP
* JBIDE-16910 Atlassian Connector cannot be installed (missing deps)
--
The above PRs have already been applied, so you can use the following to
try to build the TP locally to test it out:
Build target-platform:
$ cd jbosstools-target-platforms
$ git fetch origin 4.40.x
$ git checkout FETCH_HEAD
$ cd jbosstools/multiple
$ mvn clean install -P \!multiple2repo
Try with just built target-platform:
$ cd /path/to/your/component
$ mvn clean verify -Dtpc.version=4.40.0.Beta2-SNAPSHOT -Pmultiple.target
--
If you want to perform a scripted install of the entire target platform
into your local Eclipse or JBDS instance, you can now do so with this
script:
https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal...
Usage is documented in the above script, and in this README:
https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#upd...
---
More info:
The reason for the removal is that o.j.t.gwt.feature and
o.j.t.maven.gwt.feature have been removed from JBoss Tools
4.2.0.Beta1/Beta2.
You will notice that with the removal of GPE/GWT from the target
platform, its size on disk is now 200M smaller.
Big props to Rob Stryker and Jucia Jelinkova for bringing forth these
problems.
Why remove gwt and maven.gwt, plus the com.google stuff on which they
depend?
For JBT 4.1 / JBDS 7.1, we deprecated org.jboss.tools.gwt.feature - it's
still in 4.1 / 7.1, but it's a hidden feature.
For JBT 4.2 / JBDS 8.0, we have removed
org.jboss.tools.maven.gwt.feature because much of the com.google stuff
on which it depends cannot be installed on Luna. So we either end up
with a partially-working install, or we remove it entirely and wait to
see if Google actually produces a new GPE/GWT for Luna, including
support for Maven.
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
11 years, 11 months
EclipseCon France call for paper: 3 weeks left
by Mickael Istria
Hi all,
Beware that Call For Paper for EclipseCon France -in Toulouse,
(17)-18-19 June- ends in 3 weeks. https://www.eclipsecon.org/france2014/cfp
So anyone interested should start getting approval, budget and talks ready.
There is much space for the topics covered by JBoss Tools,
Cordova/Aerogear, RedHat Developer Kit, OpenShift, Vert.x and so on.
I think it's also a place where it might be possible to demonstrate how
to use Java 8 in a JEE application with Eclipse, or having fun with a
Raspberry Pi as a target server for JEE development for example...
There is no risk in submitting something out of the original scope, so
feel free to submit anything you think can make sense for the audience!
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
11 years, 11 months
