[JBoss JIRA] (JBIDE-15593) WS Tester should put a warning when parameter is not valid
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15593?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-15593:
---------------------------------------
I suggest a warning instead of an error because users may want to try to send request with weird parameters and see how the server behaves.
If the WS Tester is not flexible enough, users may want/need to switch to something else (curl, etc.)
> WS Tester should put a warning when parameter is not valid
> ----------------------------------------------------------
>
> Key: JBIDE-15593
> URL: https://issues.jboss.org/browse/JBIDE-15593
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.1.1.Beta1
>
>
> WS Tester input parameter dialog should display a warning and not prevent dialog close instead of displaying an error if the value of a parameter is not compatible with its type.
> User should be allowed to submit the request with bad parameters if she really wants to.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15597 at 10/2/13 9:53 AM:
-------------------------------------------------------------------
I replaced the separate lists by a table with 2 columns. IMHO I dont see where balsamiq is too limiting, it always works for us and is IMHO far quicker and efficient than screenshotting, editing, commenting about what's different than shown (or even paint the screenshots).
was (Author: adietish):
replaced 2 columns by table
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, manage-keys.png
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15597:
------------------------------------------
replaced 2 columns by table
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, manage-keys.png
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15599) Changes on a subresource locator fields are not propagated to the JAX-RS Explorer
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15599?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-15599:
----------------------------------
Description:
Take the following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@QueryParam("foo")
private String foo;
@Path("/{productType}")
public Object getProductResourceLocator() {
return new BookResource();
}
}
{code}
and
{code}
@Produces({ MediaType.APPLICATION_XML, "application/json" })
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
and modify the @QueryParam value of the "foo" field.
ASSERT: the changes appear in the Project Explorer
FAIL: the old @QueryParam annotation value is still used
WORKAROUND: Clean/build the project then refresh the JAX-RS Web Services node.
was:
Take the following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@QueryParam("foo")
private String foo;
@Path("/{productType}")
public Object getProductResourceLocator() {
return new BookResource();
}
}
{code}
and
{code}
@Produces({ MediaType.APPLICATION_XML, "application/json" })
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
and modify the @QueryParam value of the "foo" field.
ASSERT: the changes appear in the Project Explorer
FAIL: the old @QueryParam annotation value is still used
WORKAROUND: Refresh the JAX-RS Web Services node.
> Changes on a subresource locator fields are not propagated to the JAX-RS Explorer
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-15599
> URL: https://issues.jboss.org/browse/JBIDE-15599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.1.1.Beta1
>
>
> Take the following classes:
> {code}
> @Path("/products")
> public class ProductResourceLocator {
> @QueryParam("foo")
> private String foo;
> @Path("/{productType}")
> public Object getProductResourceLocator() {
> return new BookResource();
> }
> }
> {code}
> and
> {code}
> @Produces({ MediaType.APPLICATION_XML, "application/json" })
> public class BookResource {
> @GET
> @Path("/{id}")
> @Produces({ "application/xml", "application/json" })
> public Book getProduct(@PathParam("id") Integer id) {
> return null;
> }
> }
> {code}
> and modify the @QueryParam value of the "foo" field.
> ASSERT: the changes appear in the Project Explorer
> FAIL: the old @QueryParam annotation value is still used
> WORKAROUND: Clean/build the project then refresh the JAX-RS Web Services node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15599) Changes on a subresource locator fields are not propagated to the JAX-RS Explorer
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15599?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-15599:
---------------------------------------
Looks like both issues are linked
> Changes on a subresource locator fields are not propagated to the JAX-RS Explorer
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-15599
> URL: https://issues.jboss.org/browse/JBIDE-15599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.1.1.Beta1
>
>
> Take the following classes:
> {code}
> @Path("/products")
> public class ProductResourceLocator {
> @QueryParam("foo")
> private String foo;
> @Path("/{productType}")
> public Object getProductResourceLocator() {
> return new BookResource();
> }
> }
> {code}
> and
> {code}
> @Produces({ MediaType.APPLICATION_XML, "application/json" })
> public class BookResource {
> @GET
> @Path("/{id}")
> @Produces({ "application/xml", "application/json" })
> public Book getProduct(@PathParam("id") Integer id) {
> return null;
> }
> }
> {code}
> and modify the @QueryParam value of the "foo" field.
> ASSERT: the changes appear in the Project Explorer
> FAIL: the old @QueryParam annotation value is still used
> WORKAROUND: Refresh the JAX-RS Web Services node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15600) MatrixParam and QueryParam field names are used instead of the annotation values
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-15600:
-------------------------------------
Summary: MatrixParam and QueryParam field names are used instead of the annotation values
Key: JBIDE-15600
URL: https://issues.jboss.org/browse/JBIDE-15600
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.1.0.Final
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.1.1.Beta1
Take the following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@QueryParam("foo1")
private String foo2;
@Path("/{productType}")
public Object getProductResourceLocator() {
return new BookResource();
}
}
{code}
and
{code}
@Produces({ MediaType.APPLICATION_XML, "application/json" })
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
ASSERT: the URL Template for the Endpoint should be something like
{code}
/products/{productType}/{id}?foo1={String}
{code}
FAIL: the URL Template for the Endpoint should be something like
{code}
/products/{productType}/{id}?foo2={String}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15599) Changes on a subresource locator fields are not propagated to the JAX-RS Explorer
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-15599:
-------------------------------------
Summary: Changes on a subresource locator fields are not propagated to the JAX-RS Explorer
Key: JBIDE-15599
URL: https://issues.jboss.org/browse/JBIDE-15599
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.1.0.Final
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.1.1.Beta1
Take the following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@QueryParam("foo")
private String foo;
@Path("/{productType}")
public Object getProductResourceLocator() {
return new BookResource();
}
}
{code}
and
{code}
@Produces({ MediaType.APPLICATION_XML, "application/json" })
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
and modify the @QueryParam value of the "foo" field.
ASSERT: the changes appear in the Project Explorer
FAIL: the old @QueryParam annotation value is still used
WORKAROUND: Refresh the JAX-RS Web Services node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15550) Endpoint from Resource Locator and Subresources don't appear in the Project Explorer
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15550?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-15550:
----------------------------------
Description:
Take the 2 following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@PathParam("productType")
private String productType = null;
@Path("/{productType}")
public Object getProductResourceLocator() {
if ("books".equals(productType)) {
return new BookResource();
}
if ("games".equals(productType)) {
return new GameResource();
}
throw new WebApplicationException(Status.NOT_FOUND);
}
}
{code}
and
{code}
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
The combination of those 2 classes should produce the following endpoint:
{code}
/<rest_app>/products/{productType:String};bar={String}/{id:int}
{code}
but *sometimes*, this endpoint is missing and running a 'Project>Clean' does not solve the problem.
was:
Take the 2 following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@PathParam("productType")
private String productType = null;
@Path("/{productType}")
public Object getProductResourceLocator() {
if ("books".equals(productType)) {
return new BookResource();
}
if ("games".equals(productType)) {
return new GameResource();
}
throw new WebApplicationException(Status.NOT_FOUND);
}
}
{code}
and
{code}
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
The combination of those 2 classes should produce the following endpoint:
/<rest_app>/products/{productType:String};bar={String}/{id:int}
but *sometimes*, this endpoint is missing and running a 'Project>Clean' does not solve the problem.
> Endpoint from Resource Locator and Subresources don't appear in the Project Explorer
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-15550
> URL: https://issues.jboss.org/browse/JBIDE-15550
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> Take the 2 following classes:
> {code}
> @Path("/products")
> public class ProductResourceLocator {
> @PathParam("productType")
> private String productType = null;
>
> @Path("/{productType}")
> public Object getProductResourceLocator() {
> if ("books".equals(productType)) {
> return new BookResource();
> }
> if ("games".equals(productType)) {
> return new GameResource();
> }
> throw new WebApplicationException(Status.NOT_FOUND);
> }
> }
> {code}
> and
> {code}
> public class BookResource {
> @GET
> @Path("/{id}")
> @Produces({ "application/xml", "application/json" })
> public Book getProduct(@PathParam("id") Integer id) {
> return null;
> }
> }
> {code}
> The combination of those 2 classes should produce the following endpoint:
> {code}
> /<rest_app>/products/{productType:String};bar={String}/{id:int}
> {code}
> but *sometimes*, this endpoint is missing and running a 'Project>Clean' does not solve the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-14018) OpenShift commit message references JBoss Tools
by Eric Barber (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14018?page=com.atlassian.jira.plugi... ]
Eric Barber commented on JBIDE-14018:
-------------------------------------
I accept that Team->Show History will allow developers to see the contents of a commit. That said, when 8-12 developers are pushing constantly to multiple branches with cherry picking going on, generic commit messages really complicate the process.
Developers are currently falling back to your second suggested approach. More accurately, they're just using Git's command line interface. That works, but it takes them away from the Eclipse plugins that you've developed and that I think simplify interaction w/ OpenShift.
In short, we're working around this issue, but developing patterns which are leading away from Eclipse and any productivity boosters these plugins can provide. I can only advocate that this issue receive higher priority going forward. Thanks.
> OpenShift commit message references JBoss Tools
> -----------------------------------------------
>
> Key: JBIDE-14018
> URL: https://issues.jboss.org/browse/JBIDE-14018
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: commit_from_JBT.png, Customized Git Commit on Publish.png
>
>
> In Servers tab, when you right-click on an OpenShift server adapter and click Publish, an automatic commit message is generated: "Commit from JBoss Tools".
> This message references JBoss Tools - for JBDS it should mention JBDS. I realise it is difficult to have a different message for JBT and JBDS so I guess the message needs to be changed to not reference either.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months