[JBoss JIRA] (JBIDE-15488) Web Service Tester doesn't work with https and self-signed certificate
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15488?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-15488:
----------------------------------
Labels: jax-rs (was: )
> Web Service Tester doesn't work with https and self-signed certificate
> ----------------------------------------------------------------------
>
> Key: JBIDE-15488
> URL: https://issues.jboss.org/browse/JBIDE-15488
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Juergen Zimmermann
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.x
>
>
> If I test a RESTful Web Service on WildFly 8 which is configured for https, then I just this error message in the response body (for both GET and POST requests):
> {code}
> sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16066:
----------------------------------
Labels: jax-ws (was: )
> Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-16066
> URL: https://issues.jboss.org/browse/JBIDE-16066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.CR1
> Environment: JBDS 7.1.0 CR1, EAP-6.1
> Reporter: Radoslav Rábara
> Assignee: Brian Fitzpatrick
> Labels: jax-ws
> Fix For: 4.3.0.Alpha1
>
> Attachments: topDownServer.log
>
>
> Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible.
> It works with other slider levels and all levels works when the server isn't started before the web service is created.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-16488) Address issues raised by Sonar report in WS code
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16488?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16488:
----------------------------------
Labels: jax-ws (was: )
> Address issues raised by Sonar report in WS code
> ------------------------------------------------
>
> Key: JBIDE-16488
> URL: https://issues.jboss.org/browse/JBIDE-16488
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.1.x
> Reporter: Xavier Coulon
> Assignee: Brian Fitzpatrick
> Labels: jax-ws
> Fix For: 4.3.x
>
>
> Received an e-mail from Mickael about this Sonar report and think we should definitely take a look. Many of the issues raised could mask problems down the line at the very least and this sort of automated report could be very useful to avoid bugs BEFORE they are reported.
> Here's the e-mail:
> "I don't know if you remember, but some month ago, I did push installation of Sonar on JBoss infrastructure and have used the JBT WS job as a playground.
> So you can see reports at http://sonar.mw.lab.eng.bos.redhat.com/sonar/drilldown/violations/org.jbo...
> The most important ones are the rules violation with severity "Critical". Some of them are potential bugs, some other can cause performance or security issues, some others might show up some useless piece of code. You could use it during this "Quiet period" before GA to make some improvements inside the code.
> If you like it, please tell a word to the JBT team (or JBoss in general). This approach using code inspection to find bugs before they hit market is something that has been measured as a great benefit for a project: http://www.benlinders.com/2013/the-economics-of-software-quality/"
> Xavier and I should take a look at this after GA to try and fix at least the critical ones if possible.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-16734) JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16734?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16734:
----------------------------------
Labels: jax-rs (was: )
> JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16734
> URL: https://issues.jboss.org/browse/JBIDE-16734
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.1.1.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.x
>
>
> JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields.
> Eg:
> {code}
> @Path("resource")
> @Singleton
> public static class MySingletonResource {
>
> @QueryParam("query")
> String param; // WRONG: initialization of application will fail as you cannot
> // inject request specific parameters into a singleton resource.
>
> @GET
> public String get() {
> return "query param: " + param;
> }
> }
> {code}
> The exception exists for specific request objects which can injected even into constructor or class fields. For these objects the runtime will inject proxies which are able to simultaneously server more request. These request objects are HttpHeaders, Request, UriInfo, SecurityContext. These proxies can be injected using the @Context annotation
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months