[JBoss JIRA] (JBIDE-13280) Generate Arquillian test code from endpoints
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13280?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-13280:
----------------------------------
Labels: jax-rs (was: )
> Generate Arquillian test code from endpoints
> --------------------------------------------
>
> Key: JBIDE-13280
> URL: https://issues.jboss.org/browse/JBIDE-13280
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: LATER
>
>
> Generate Arquillian JAX-RS test skeleton from:
> - Endpoints in the Project Explorer,
> - Java Methods
> - Wizard
> Client API could be based on:
> - Apache HTTP Client
> - Jersey / RESTEasy (custom) Client API
> - JAX-RS 2.0 (standardized) Client API
> This implies that some Maven dependencies may need to be added into the project.
> Optionally,
> {code}
> @Deployment
> public static JavaArchive createDeployment() {
> ...
> }
> {code}
> could be filled with required dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-13414:
----------------------------------
Labels: jax-ws web_service_client (was: web_service_client)
> No Error reported when WS Client code generation fails
> ------------------------------------------------------
>
> Key: JBIDE-13414
> URL: https://issues.jboss.org/browse/JBIDE-13414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Mustafa Musaji
> Assignee: Brian Fitzpatrick
> Labels: jax-ws, web_service_client
> Fix For: LATER
>
> Attachments: echoService.wsdl
>
>
> If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this:
> Failed to invoke WSDLToJava
> org.apache.cxf.tools.common.ToolException: Thrown by JAXB:
> Thrown by JAXB:
> Two declarations cause a collision in the ObjectFactory class.
> ...
> However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-13578) Provide quickfixes to existing JAX-RS Application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13578?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-13578:
----------------------------------
Labels: jax-rs (was: )
> Provide quickfixes to existing JAX-RS Application
> -------------------------------------------------
>
> Key: JBIDE-13578
> URL: https://issues.jboss.org/browse/JBIDE-13578
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.x
>
>
> A quickfix to annotate the JAX-RS Application with javax.ws.rs.ApplicationPath should be provided if an error is detected.
> ----
> From JAX-RS 1.1 spec, chap 2.3.2:
> When using the pluggability mechanism the following conditions MUST be met:
> • If no Application subclass is present the added servlet MUST be named: javax.ws.rs.core.Application
> and all root resource classes and providers packaged in the web application MUST be included in the published JAX-RS application. The application MUST be packaged with a web.xml that specifies a servlet mapping for the added servlet.
> • If an Application subclass is present and there is already a servlet defined that has a servlet initial- ization parameter named:
> javax.ws.rs.Application
> whose value is the fully qualified name of the Application subclass then no new servlet should be added by the JAX-RS implementation’s ContainerInitializer since the application is already being handled by an existing servlet.
> • If an Application subclass is present that is not being handled by an existing servlet then the servlet added by the ContainerInitializer MUST be named with the fully qualified name of the Application subclass. If the Application subclass is annotated with @ApplicationPath and no servlet-mapping exists for the added servlet then a new servlet mapping is added with the value of the @ApplicationPath annotation with ”/*” appended otherwise the existing mapping is used. If the Application subclass is not annotated with @ApplicationPath then the application MUST be packaged with a web.xml that specifies a servlet mapping for the added servlet. It is an error for more than one application to be deployed at the same effective servlet mapping
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months