JBossToolsWebservices

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
JBIDE-16431 : sanitize URI when opening web tester view

Signed-off-by: Fred Bricon <fbricon@gmail.com>

JBIDE-16431 : sanitize URI when opening web tester view

Signed-off-by: Fred Bricon <fbricon@gmail.com>

JBIDE-16421 - Fixing sonar issues in WS (non RS) code

JBIDE-16313 - Replace AST Visitors with simpler code

Removed all implementations of ASTVisitor in the org.jboss.tools.ws.jaxrs.core.jdt package

Fixed a few JUnit tests

JBIDE-16328 - Buglets in JaxrsResourceMethodValidatorDelegate.validatePublicModifierOnJavaMethod()

Fixed the incomplete validation message ('{0}' was not substitued).

Added an exception if the parent type is an interface.

JBIDE-16328 - Buglets in JaxrsResourceMethodValidatorDelegate.validatePublicModifierOnJavaMethod()

Fixed the incomplete validation message ('{0}' was not substitued).

Added an exception if the parent type is an interface.

JBIDE-16264 - @PathParam with hyphen in value shows as JAX-RS error

Fixing the reported error type (was wrong id)

Allowing for hyphen, underscore and dot characters but in first position

for the path parameters.

Added JUnit tests to cover valid/invalid path param values

JBIDE-16264 - @PathParam with hyphen in value shows as JAX-RS error

Fixing the reported error type (was wrong id)

Allowing for hyphen, underscore and dot characters but in first position

for the path parameters.

Added JUnit tests to cover valid/invalid path param values

JBIDE-16264 - @PathParam with hyphen in value shows as JAX-RS error

Fixing the reported error type (was wrong id)

Allowing for hyphen, underscore and dot characters but in first position

for the path parameters.

Added JUnit tests to cover valid/invalid path param values

JBIDE-16262: Update link to build doc.

JBIDE-16309: Added direct dependencies to necessary JBT components

Updating to alpha2

JBIDE-16207b - For JBIDE 4.1.1.Final: Prepare for Final/GA release [Webservices]

JBIDE-16207 - For JBIDE 4.1.1.Final: Prepare for Final/GA release [Webservices]

JBIDE-16239 - Upversion WS

    • -1
    • +1
    /plugins/org.jboss.tools.ws.core/pom.xml
  1. … 18 more files in changeset.
TOOLSDOC-390: Doc versions updated for 4.1 and 7.1

    • -3
    • +3
    /docs/restful_reference/en-US/master.xml
    • -4
    • +2
    /docs/soap_reference/en-US/Book_Info.xml
    • -11
    • +14
    /docs/soap_reference/en-US/Revision_History.xml
JBIDE-16088 - Updating ant version for Luna

Merge pull request #98 from bfitzpat/jbosstools-4.1.1.x

JBIDE-15946 - Updating pom for 4.1.1.CR1

JBIDE-15946 - Updating pom for 4.1.1.CR1

JBIDE-15946 - Updating pom for 4.1.1.CR1

JBIDE-15908 - Problem decorator is not removed after error was fixed

Bug was that the problemLevel on each JAX-RS Resource Method would not

be reset at the beginning of the validation, and during validation, the

highest problem level is kept. Thus, during the next validation (fixing

the problem), the problem level would remain at its highest (previous)

value.

Added tests to verify the correct behaviour on all validators.

JBIDE-15908 - Problem decorator is not removed after error was fixed

Bug was that the problemLevel on each JAX-RS Resource Method would not

be reset at the beginning of the validation, and during validation, the

highest problem level is kept. Thus, during the next validation (fixing

the problem), the problem level would remain at its highest (previous)

value.

Added tests to verify the correct behaviour on all validators.

JBIDE-15839 - Exception while saving Provider in JAX-RS application

Fixed the problem which occurred only when the problem severity as set to

'ignore' level. In that particular case, no IMarker would be created, thus

returning a null reference, which lead to NPE.

Added JUnit tests to cover all ways to create JAX-RS Markers.

JBIDE-15839 - Exception while saving Provider in JAX-RS application

Fixed the problem which occurred only when the problem severity as set to

'ignore' level. In that particular case, no IMarker would be created, thus

returning a null reference, which lead to NPE.

Added JUnit tests to cover all ways to create JAX-RS Markers.

JIBDE-12860 - JAX-RS validation problems are not linked

Fixed the problem where some markers would not be removed from the resource to be validated between

two validation calls, which meant that duplicate markers for the same problem would exist on each

resource.

Also refactored the search/element retrieval: the JaxrsElementIndexationDelegate now not only

deals with the Lucene indexation and searches, but also uses the metamodel to return List of

JAX-RS elements, Endpoints or workspace Resources.

Renamed some marker deletion/undexing methods to use the "remove" verb (eg: "removeMarker()") and be consistent with the

existing "remove()" methods that remove the elements themselves.

Added JUnit tests to covers the fixes.

This patch also fixes:

- JBIDE-15662: Warning Multiple JAX-RS Activators doesn't disappear

- JBIDE-15664: Application path configured in web.xml causes warning

  1. … 24 more files in changeset.
JIBDE-12860 - JAX-RS validation problems are not linked

Fixed the problem where some markers would not be removed from the resource to be validated between

two validation calls, which meant that duplicate markers for the same problem would exist on each

resource.

Also refactored the search/element retrieval: the JaxrsElementIndexationDelegate now not only

deals with the Lucene indexation and searches, but also uses the metamodel to return List of

JAX-RS elements, Endpoints or workspace Resources.

Renamed some marker deletion/undexing methods to use the "remove" verb (eg: "removeMarker()") and be consistent with the

existing "remove()" methods that remove the elements themselves.

Added JUnit tests to covers the fixes.

This patch also fixes:

- JBIDE-15662: Warning Multiple JAX-RS Activators doesn't disappear

- JBIDE-15664: Application path configured in web.xml causes warning

  1. … 24 more files in changeset.
JIBDE-12860 - JAX-RS validation problems are not linked

Fixed the problem where some markers would not be removed from the resource to be validated between

two validation calls, which meant that duplicate markers for the same problem would exist on each

resource.

Also refactored the search/element retrieval: the JaxrsElementIndexationDelegate now not only

deals with the Lucene indexation and searches, but also uses the metamodel to return List of

JAX-RS elements, Endpoints or workspace Resources.

Renamed some marker deletion/undexing methods to use the "remove" verb (eg: "removeMarker()") and be consistent with the

existing "remove()" methods that remove the elements themselves.

Added JUnit tests to covers the fixes.

This patch also fixes:

- JBIDE-15662: Warning Multiple JAX-RS Activators doesn't disappear

- JBIDE-15664: Application path configured in web.xml causes warning

  1. … 24 more files in changeset.
JBIDE-15699 - For JBIDE 4.1.1.Beta1: Code Freeze + Branch [Webservices]

Bumping parent pom to 4.1.1.Beta1-SNAPSHOT, which also resolves a

problem of missing dependency on org.jboss.tool.tests

JBIDE-15428 - No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

Skipping the Java ElementChangeEvents when the Java Project is not open yet. This avoids race conditions during import.

Bonus: import seem to be twice as fast as before ;-)

Other changes:

- Move the call the JaxrsMetamodel#setBuildStatus() to finally{} blocks of JaxrsMetamodel#processXXX() methods

- Adjusted some javadoc, log messages and catch() blocks (avoiding to catch Exception or Throwable)

- Added a ReadWriteLock on all public methods of the JaxrsMetamodel to avoid concurrent access to the metamodel by different threads, for example if an async build

is still running and the validation is started. This avoids the following type of error:

{code}

!ENTRY org.jboss.tools.common 4 0 2013-10-09 18:17:54.307

!MESSAGE

!STACK 0

org.jboss.tools.common.validation.JBTValidationException

at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101)

at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

Caused by: java.util.ConcurrentModificationException

at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)

at java.util.HashMap$ValueIterator.next(HashMap.java:822)

at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validateAll(JaxrsMetamodelValidator.java:268)

at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:153)

at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:117)

at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)

... 2 more

{code}

- added some tests to increase code coverage

  1. … 7 more files in changeset.
JBIDE-15428 - No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

Skipping the Java ElementChangeEvents when the Java Project is not open yet. This avoids race conditions during import.

Bonus: import seem to be twice as fast as before ;-)

Other changes:

- Move the call the JaxrsMetamodel#setBuildStatus() to finally{} blocks of JaxrsMetamodel#processXXX() methods

- Adjusted some javadoc, log messages and catch() blocks (avoiding to catch Exception or Throwable)

- Added a ReadWriteLock on all public methods of the JaxrsMetamodel to avoid concurrent access to the metamodel by different threads, for example if an async build

is still running and the validation is started. This avoids the following type of error:

{code}

!ENTRY org.jboss.tools.common 4 0 2013-10-09 18:17:54.307

!MESSAGE

!STACK 0

org.jboss.tools.common.validation.JBTValidationException

at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101)

at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

Caused by: java.util.ConcurrentModificationException

at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)

at java.util.HashMap$ValueIterator.next(HashMap.java:822)

at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validateAll(JaxrsMetamodelValidator.java:268)

at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:153)

at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:117)

at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)

... 2 more

{code}

- added some tests to increase code coverage

  1. … 7 more files in changeset.