JBossToolsWebservices

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
TOOLSDOC-382: Rebuilt doc for customer portal, content unchanged

    • -3
    • +2
    /docs/soap_reference/en-US/Book_Info.xml
    • -0
    • +14
    /docs/soap_reference/en-US/Revision_History.xml
JBIDE-11319: Url for Eclipse-SourceReferences

[JBIDE-13795] Incorrect URL for JBoss Jira on readmes

[JBIDE-13795] Incorrect URL for JBoss Jira on readmes

JBIDE-15314 - fixes for SOAPAction NPE

JBIDE-15314 - fixes for SOAPAction NPE

JBIDE-15280 - Update parent/pom.xml version to 4.2.0.Alpha1

JBIDE-15307 - Fix for SOAP 1.2 detection when testing JAX-WS services

JBIDE-15307 - Fix for SOAP 1.2 detection when testing JAX-WS services

Bump parent pom version in root pom to 4.1.0.Final-SNAPSHOT

JBIDE-13200 As-You-Type Validation should not create any markers on resources

JBIDE-15175 - Fix for one more validation issue with Simple Web Service wizard

JBIDE-15175 - Fix for one more validation issue with Simple Web Service wizard

JBIDE-15118 - Fixing issue with RS & WS wizard validation

JBIDE-15118 - Fixing issue with RS & WS wizard validation

JBIDE-15084 - Failed to build JAX-RS Metamodel when re-opening a closed project

Catching IllegalArgumentException when JDT fails to retrieve return type from MethodBinding

Added 2 JUnit tests to verify that build does not fail

In case of build failure, the JAX-RS metamodel has a build status set to ERROR, otherwise it is set to OK. This

state can be asserted from the JUnit tests.

JBIDE-15084 - Failed to build JAX-RS Metamodel when re-opening a closed project

Catching IllegalArgumentException when JDT fails to retrieve return type from MethodBinding

Added 2 JUnit tests to verify that build does not fail

In case of build failure, the JAX-RS metamodel has a build status set to ERROR, otherwise it is set to OK. This

state can be asserted from the JUnit tests.

Merge pull request #67 from bfitzpat/JBIDE-15069

JBIDE-15069 - Issue with JAX-RS testing

JBIDE-15069 - Issue with JAX-RS testing

JBIDE-15069 - Issue with JAX-RS testing

JBIDE-15067 - BadLocation Exception when validating a project with JAX-RS support

Couldn't reproduce the issue, but meanwhile, added a JUnit test to cover the block of code

where the issue appeared initially.

JBIDE-15067 - BadLocation Exception when validating a project with JAX-RS support

Couldn't reproduce the issue, but meanwhile, added a JUnit test to cover the block of code

where the issue appeared initially.

JBIDE-15039 - JAX-RS Problem decorator not shown on the Project Explorer node

Main refactoring/changes in this PR consist in:

- compare the problem level of each JAX-RS element before vs after the validation, and

in case of change, notify the metamodel. The metamodel will look for all affected Endpoints and

send 'problem level change' notification to the listeners (here, the UI). In turn, the UI will *update*

the associated node (update -> no refresh for sub nodes) to get a proper image decorator.

- same logix with the metamodel itself, except that the public problem level includes the problem level of the

JAX-RS elements, which means that the 'JAX-RS Web Services' node now reflects the whole Metamodel and thus, displays the

global problem level.

This new UI refresh strategy also reduces the number of times refresh occurred (there's now a single refresh per affected element, even

if this element has multiple problems).

- also fixed a problem where the UI listener would only be registered once the "JAX-RS Web Services" node was expended

  1. … 14 more files in changeset.
JBIDE-15039 - JAX-RS Problem decorator not shown on the Project Explorer node

Adding notification each time a JAX-RS element is validated so that it's UI element gets refreshed

Also 'update' the parent node element to show/hide the problem decorator

Merge pull request #63 from bfitzpat/JBIDE-15051

JBIDE-15051 - Updating parent pom for CR1

JBIDE-15051 - Updating parent pom for CR1

JBIDE-15031 - JAX-RS Metamodel builder called too many times during project build

Do not launch a build job when the metamodel already exist and is being initialized.

remove .project folder in root that prevents easy import in eclipse

JBIDE-12690 No JAX-RS problems when importing a project that contains errors

Preventing some NPE

Taking care of having the metamodel build command inserted *before* the validation command

Keeping the validation context in the JAX-RS Metamodel (via the ValidationContextTree) to hold

the context between validation calls.

Merge pull request #59 from bfitzpat/JBIDE-14988

JBIDE-14988 - Force usage of JaxB 2.2 on master