[JBoss JIRA] (JBIDE-15069) Cannot use Web Service Tester to test GET requests returning 404
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15069?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-15069:
-------------------------------------------
I'll look into this...
> Cannot use Web Service Tester to test GET requests returning 404
> ----------------------------------------------------------------
>
> Key: JBIDE-15069
> URL: https://issues.jboss.org/browse/JBIDE-15069
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.1.0.Beta2
> Reporter: Juergen Zimmermann
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.CR1
>
>
> I get a NPE when I submit a GET request in the Web Service tester which should return 404. In Eclipse's .log file I only have these lines:
> !ENTRY org.eclipse.core.jobs 4 2 2013-07-01 16:54:21.954
> !MESSAGE An internal error occurred during: "Invoking web service...".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleRSTest(JAXRSWSTestView2.java:1918)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$33(JAXRSWSTestView2.java:1916)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1723)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
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, 9 months
[JBoss JIRA] (JBIDE-15069) Cannot use Web Service Tester to test GET requests returning 404
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15069?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick reassigned JBIDE-15069:
-----------------------------------------
Assignee: Brian Fitzpatrick
> Cannot use Web Service Tester to test GET requests returning 404
> ----------------------------------------------------------------
>
> Key: JBIDE-15069
> URL: https://issues.jboss.org/browse/JBIDE-15069
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.1.0.Beta2
> Reporter: Juergen Zimmermann
> Assignee: Brian Fitzpatrick
>
> I get a NPE when I submit a GET request in the Web Service tester which should return 404. In Eclipse's .log file I only have these lines:
> !ENTRY org.eclipse.core.jobs 4 2 2013-07-01 16:54:21.954
> !MESSAGE An internal error occurred during: "Invoking web service...".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleRSTest(JAXRSWSTestView2.java:1918)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$33(JAXRSWSTestView2.java:1916)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1723)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
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, 9 months
[JBoss JIRA] (JBIDE-15072) Seam 2.3.1+ examples maven projects "Duplicate component name" errors
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15072?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15072:
----------------------------------------
[~maschmidt], as a workaround maybe.
> Seam 2.3.1+ examples maven projects "Duplicate component name" errors
> ---------------------------------------------------------------------
>
> Key: JBIDE-15072
> URL: https://issues.jboss.org/browse/JBIDE-15072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, Seam 2
> Affects Versions: 4.1.0.Beta2
> Environment: WFK 2.3.0.CR1
> Reporter: Marek Schmidt
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> The new Seam 2.3 examples structure (since WFK 2.3.0.CR1) contains two components.xml files (one real, one for testing is src/test), which confuses JBDS and produces lots of
> Duplicate component name: "..." components.xml /booking-web/src/main/webapp/WEB-INF line 24 Seam Problem
> issues.
> JBDS should understand src/test directory in a Maven project as something test resources go to and not be confused that a test components.xml file is also named components.xml and that it doesn't really conflict with components.xml file that goes into a deployment.
--
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, 9 months
[JBoss JIRA] (JBIDE-15072) Seam 2.3.1+ examples maven projects "Duplicate component name" errors
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15072?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-15072 at 7/1/13 1:24 PM:
----------------------------------------------------------------
[~maschmid], as a workaround maybe.
was (Author: akazakov):
[~maschmidt], as a workaround maybe.
> Seam 2.3.1+ examples maven projects "Duplicate component name" errors
> ---------------------------------------------------------------------
>
> Key: JBIDE-15072
> URL: https://issues.jboss.org/browse/JBIDE-15072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, Seam 2
> Affects Versions: 4.1.0.Beta2
> Environment: WFK 2.3.0.CR1
> Reporter: Marek Schmidt
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> The new Seam 2.3 examples structure (since WFK 2.3.0.CR1) contains two components.xml files (one real, one for testing is src/test), which confuses JBDS and produces lots of
> Duplicate component name: "..." components.xml /booking-web/src/main/webapp/WEB-INF line 24 Seam Problem
> issues.
> JBDS should understand src/test directory in a Maven project as something test resources go to and not be confused that a test components.xml file is also named components.xml and that it doesn't really conflict with components.xml file that goes into a deployment.
--
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, 9 months
[JBoss JIRA] (JBIDE-15072) Seam 2.3.1+ examples maven projects "Duplicate component name" errors
by Marek Schmidt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15072?page=com.atlassian.jira.plugi... ]
Marek Schmidt commented on JBIDE-15072:
---------------------------------------
Wouldn't it be better to just ignore validation of src/test/** for components.xml (and beans.xml for CDI projects? )
> Seam 2.3.1+ examples maven projects "Duplicate component name" errors
> ---------------------------------------------------------------------
>
> Key: JBIDE-15072
> URL: https://issues.jboss.org/browse/JBIDE-15072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, Seam 2
> Affects Versions: 4.1.0.Beta2
> Environment: WFK 2.3.0.CR1
> Reporter: Marek Schmidt
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> The new Seam 2.3 examples structure (since WFK 2.3.0.CR1) contains two components.xml files (one real, one for testing is src/test), which confuses JBDS and produces lots of
> Duplicate component name: "..." components.xml /booking-web/src/main/webapp/WEB-INF line 24 Seam Problem
> issues.
> JBDS should understand src/test directory in a Maven project as something test resources go to and not be confused that a test components.xml file is also named components.xml and that it doesn't really conflict with components.xml file that goes into a deployment.
--
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, 9 months
[JBoss JIRA] (JBIDE-15072) Seam 2.3.1+ examples maven projects "Duplicate component name" errors
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15072?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15072:
----------------------------------------
It's a common problem for Eclipse projects. There is no way to have two classpaths for one Eclipse Java Project.
> Seam 2.3.1+ examples maven projects "Duplicate component name" errors
> ---------------------------------------------------------------------
>
> Key: JBIDE-15072
> URL: https://issues.jboss.org/browse/JBIDE-15072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, Seam 2
> Affects Versions: 4.1.0.Beta2
> Environment: WFK 2.3.0.CR1
> Reporter: Marek Schmidt
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> The new Seam 2.3 examples structure (since WFK 2.3.0.CR1) contains two components.xml files (one real, one for testing is src/test), which confuses JBDS and produces lots of
> Duplicate component name: "..." components.xml /booking-web/src/main/webapp/WEB-INF line 24 Seam Problem
> issues.
> JBDS should understand src/test directory in a Maven project as something test resources go to and not be confused that a test components.xml file is also named components.xml and that it doesn't really conflict with components.xml file that goes into a deployment.
--
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, 9 months
[JBoss JIRA] (JBIDE-15072) Seam 2.3.1+ examples maven projects "Duplicate component name" errors
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15072?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15072:
-----------------------------------
Fix Version/s: 4.2.x
Assignee: Alexey Kazakov
Affects Version/s: 4.1.0.Beta2
> Seam 2.3.1+ examples maven projects "Duplicate component name" errors
> ---------------------------------------------------------------------
>
> Key: JBIDE-15072
> URL: https://issues.jboss.org/browse/JBIDE-15072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, Seam 2
> Affects Versions: 4.1.0.Beta2
> Environment: WFK 2.3.0.CR1
> Reporter: Marek Schmidt
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> The new Seam 2.3 examples structure (since WFK 2.3.0.CR1) contains two components.xml files (one real, one for testing is src/test), which confuses JBDS and produces lots of
> Duplicate component name: "..." components.xml /booking-web/src/main/webapp/WEB-INF line 24 Seam Problem
> issues.
> JBDS should understand src/test directory in a Maven project as something test resources go to and not be confused that a test components.xml file is also named components.xml and that it doesn't really conflict with components.xml file that goes into a deployment.
--
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, 9 months
[JBoss JIRA] (JBDS-2675) Seam 2.3.1+ examples maven projects "Duplicate component name" errors
by Marek Schmidt (JIRA)
Marek Schmidt created JBDS-2675:
-----------------------------------
Summary: Seam 2.3.1+ examples maven projects "Duplicate component name" errors
Key: JBDS-2675
URL: https://issues.jboss.org/browse/JBDS-2675
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: seam
Affects Versions: 7.0.0.Beta2
Environment: WFK 2.3.0.CR1
Reporter: Marek Schmidt
The new Seam 2.3 examples structure (since WFK 2.3.0.CR1) contains two components.xml files (one real, one for testing is src/test), which confuses JBDS and produces lots of
Duplicate component name: "..." components.xml /booking-web/src/main/webapp/WEB-INF line 24 Seam Problem
issues.
JBDS should understand src/test directory in a Maven project as something test resources go to and not be confused that a test components.xml file is also named components.xml and that it doesn't really conflict with components.xml file that goes into a deployment.
--
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, 9 months