[ https://jira.jboss.org/jira/browse/JBIDE-6175?page=com.atlassian.jira.plu... ] Libor Zoubek updated JBIDE-6175: -------------------------------- Attachment: .log -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-6175?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6175: ------------------------------------------ According to Dominik Popisil: "My thoughts are following. EAP 4.2 is not officially supported (according to PRD) and as you said the tooling does not provide EAP 4.2 support explicitly. Also, we have not done compatibility testing with EAP 4.2 (we did with EAP 4.3). So I am fine that this only works with EAP 4.3 and AS 4.2 but not EAP 4.2." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-6175?page=com.atlassian.jira.plu... ] Brian Fitzpatrick updated JBIDE-6175: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 3.2.next 3.1.x If the fix is a simple one to prevent the NPE, we should look at including this in the 3.1.x stream as well as 3.2.next. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-6175?page=com.atlassian.jira.plu... ] Feng Qian commented on JBIDE-6175: ---------------------------------- Brian, Basically, this is a error of web service runtime from EAP4.2. And there is a error of web service command line. It can't give a right status about if the command finishes correctly. I just add something to prevent the NPE and give a error message to user. Please review the patch. If it is ok, I will commit it. If it is simple enough, I will commit it to 3.1.x too. Grid -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-6175?page=com.atlassian.jira.plu... ] Brian Fitzpatrick updated JBIDE-6175: ------------------------------------- Attachment: AddNumbersService.wsdl Libor & Grid, I need a bit more information about how to reproduce this issue. I'm running SOA-P 4.2 CP CP03 and am trying to reproduce the issue with this WSDL (AddNumbersService.wsdl). What specific steps are you following in the WTP Web Service wizard to duplicate the issue? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-6175?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6175: ------------------------------------------ Patch hides the NPE and presents a much more friendly error message to the user. Good job. As for the JUnit test, what are the prerequisites I need to run it? Though in principle I should just be able to run your test suite (JBossWSCreationCoreTests), it's failing all over the place when I try to run it as a JUnit Plugin test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-6175?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6175: ------------------------------------------ Grid, even with changing the path and the jvm arguments, your test doesn't run on my machine. It hangs as it tries to import the project. Couple of things... 1) I'm not a fan of hardcoding server locations in JUnit tests. I think it's a dangerous practice. 2) Talking to Nick Boldt, he suggested providing an external JVM argument to specify the path... Something like -DJBOSSWS_HOME_DEFAULT=D:/softinstall/jboss-4.2.3GA/jboss-4.2.3.GA You could then check to see if that argument is specified and override the internal variable... // if command-line argument is specified, it should take // precedence over the hard-coded value here. // -DJBOSSWS_HOME_DEFAULT=D:/softinstall/jboss-4.2.3GA/jboss-4.2.3.GA // then get the argument with // System.getProperty("JBOSSWS_HOME_DEFAULT"); String cmdlineHomeDefault = System.getProperty("JBOSSWS_HOME_DEFAULT"); if (cmdlineHomeDefault != null && cmdlineHomeDefault.trim().length() > 0) { AbstractJBossWSCommandTest.JBOSSWS_HOME_DEFAULT = cmdlineHomeDefault; System.setProperty(JBOSSWS_42_HOME, JBOSSWS_HOME_DEFAULT); AbstractJBossWSCommandTest.JBOSS_AS_42_HOME = System.getProperty( JBOSSWS_42_HOME, JBOSSWS_HOME_DEFAULT); } That said, this is still failing on RHEL for me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-6175?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6175: ------------------------------------------ After bashing my head against this a while, it turned out to be that my runtime configuration for the JUnit plug-in tests was not right. Somehow additional plug-ins were unchecked beyond the *epp.usagedata* plug-ins. The test and patch seem to both work fine. Grid, once SVN comes back to life, please go ahead and deliver the test and fix to head and the 3.1.1/3.1.x stream. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6175?page=com.atlassian.jira.plugin.s... ] Libor Zoubek closed JBIDE-6175. ------------------------------- verified on trunk and JBDS 3.0.1-H68-GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6175?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen updated JBIDE-6175: --------------------------------------- Fix Version/s: 3.1.1 (was: 3.2.next) (was: 3.1.x) reclosed issues that were set to 3.1.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira