> On 7 Mar 2018, at 20.37, Jesper Steen Møller <jes...@selskabet.org> wrote:
>
>
>> On 7 Mar 2018, at 17.40, Nick Boldt <nbo...@redhat.com> wrote:
>> [...]
>> Has anyone started work on JDK 10 support in WTP? Just curious in which
>> projects I sh
> On 7 Mar 2018, at 17.40, Nick Boldt wrote:
> [...]
> Has anyone started work on JDK 10 support in WTP? Just curious in which
> projects I should expect to see changes.
>
I really doubt there's anything to do for WTP for JDK 10, unless there is a
classfile version check
Hi Keith and Rob
(You probably know all this already, but I’ll just add what I know)
I touched some of the validator code a few years back: The number of URI
resolver interfaces is horrible - one from Platform, one from Xerces and one
from WTP as I recall), each introducing a slight impedance
Hi Asiri,
The XPath2 engine is available through the P2 repositories (only - at this
point). If you are using Apache Maven for building, you can use Tycho to fetch
the dependencies through P2, as described at StackOverflow [2]
If you just want the JAR file and play with them, you're probably
Good to hear you're having progress. The real issue is that the DOM and SAX
interfaces do not pass any sort of context down through the layers.
Instantiating a new resolver dynamically would take care of that, but
Eclipse's URIResolvers / URIResolverExtensions are statically instantiated
from the
The XSL tooling plugin uses a resolverExtension to accomplish something
similar. You may be able to find pointers there.
IIRC, it is the core plugin. Mind you, they will be cases where you can't find
a project, in case a resource is loaded directly from the file system, e.g.
with File Open
Hi Suraj
On Fri, Oct 26, 2012 at 11:29 AM, SURAJ RAJYAGURU suraj_rajyag...@yahoo.com
wrote:
I am keen on being part of the Eclipse developer community and make
contribution to Eclipse. Please let me know if there is a possiblity for
the same.
This sounds great! First off, there's a
Hi Mukul
I think it is worth investigating moving the HEAD unit test suite to 1.4 as
well -- surely, Xerces can't stay with the 3.2.x branch forever, it has severe
performance issues (waste of memory), since the processor is at least
compilable under JRE 1.4 in HEAD (using the jsr14
Hi Lance
Indeed this is not the right list. The projects at Eclipse all use Bugzilla
to track enhancement requests (as well as bugs). You should open an account
( https://bugs.eclipse.org/bugs/ ) and create your enhancement request
there, using this categorization:
Classification: WebTools
Hi list
Angel Vera wrote:
When I first read your email I was a little confused about what you were
requesting. Perhaps it was due to my speed reading, but I wanted to sit down
and read it in more details, before I ask any questions. With your second
note things are more clear in my head
Hi Dave
I've been using
org.eclipse.wst.xml.core.internal.contentmodel.modelquery.CMDocumentManager.getCMDocument(String,
String, String), but first you need to set the properties
PROPERTY_AUTO_LOAD = true and PROPERTY_ASYNC_LOAD = false on the
CMDocumentManager.
-Jesper
On Tue, Aug 10, 2010 at
We had this problem in XSL Tools, and ended up writing a specialized
resolver for it which peeked the version and returned the correct
schema. Having to write a resolver for each such schema doesn't scale
well in the general case, and is hidden from the user (i.e. doesn't
show up in the catalog),
Cameron Bateman wrote:
Has any work been done to support DTD ANY and XSD anyType data in the
XML2EMF translators? If not, what is the current design thinking in
this area?
I've thought a bit about its use.
xsd:anyType and friends would need special support in both EMF2SAX and
EMF2DOM and
Raev, Kaloyan wrote:
Hello,
Since there are the minutes are not in the wiki yet, I answer to the
mail.
I want to put a comment on a part of the discussion:
# MA: Is any of this will be in WTP2.0? WTP 1.5.2 is not EJB3
friendly. We need a release of WTP 1.5 that does not complain about
Raev, Kaloyan wrote:
Hi Jesper,
We have taken a look at the J2EE 1.4 models implementation. It did make
impression that there are lots of hand made tweaks there.
I'm a bit confused. You've seen/commented on bug 157185 covering most of
the XML side of J2EE, excluding annotations, so you
David M Williams wrote:
? from Artwaresoft
ajax interest
wondered if work was being done to provide javascript
performance tools (he thought there was
a great need). [I told him there'd been talk between
Ajax team and TPTP, but no concrete plans].
Konstantin Komissarchik wrote:
I will throw something else out for this discussion... The current
(1.4-level) EMF-generated classes that ship with WTP are rather
difficult to use for those adopters who are using java 5.0. The reason
is that as soon as you access this api Eclipse floods you
Hi Janet,
An intriguing task you've got ahead of you. As I see it, the WSDL graph
editor is a recurring source of annoyance: It is simply too wide and
complicated (mirroring WSDL1.1, I suppose...) to give a full overview.
As I see it, it could be simplified a lot in the case of
18 matches
Mail list logo