[JBoss JIRA] Created: (JBIDE-6499) add '--show-traces' switch to ws related commands
by Lukas Jungmann (JIRA)
add '--show-traces' switch to ws related commands
-------------------------------------------------
Key: JBIDE-6499
URL: https://jira.jboss.org/browse/JBIDE-6499
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Webservices
Affects Versions: 3.2.0.M1
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
currently if there's some error during web service creation the error dialog which appears says only sth like "There was an error, rerun the command with --show-traces switch" - problem with this message is that user has no way to add the switch to the command (at least I haven't found it) and we don't know where exactly the problem is.
To make our's and our users' life easier we should
-use '--show-traces' switch by default
and/or
-provide UI for users so they actually can turn this switch on
and/or
-redirect all output from running command to the console view
--
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
15 years, 8 months
[JBoss JIRA] Created: (JBIDE-6388) StringIndexOutOfBoundsException when moving java class to default package
by Lukas Jungmann (JIRA)
StringIndexOutOfBoundsException when moving java class to default package
-------------------------------------------------------------------------
Key: JBIDE-6388
URL: https://jira.jboss.org/browse/JBIDE-6388
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 3.1.1
Environment: JBDS-3.0.1.v201005270943R-H82-GA
Reporter: Lukas Jungmann
Assignee: Kris Verlaenen
-create new dynamic web project
-create new java class in some package
-use Refactor -> Move to move the class into default package
=>
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1937)
at org.drools.eclipse.refactoring.RuleIFileMoveParticipant.getNewName(RuleIFileMoveParticipant.java:181)
at org.drools.eclipse.refactoring.RuleIFileMoveParticipant.initialize(RuleIFileMoveParticipant.java:118)
at org.eclipse.ltk.core.refactoring.participants.RefactoringParticipant.initialize(RefactoringParticipant.java:105)
at org.eclipse.ltk.core.refactoring.participants.ParticipantExtensionPoint.getParticipants(ParticipantExtensionPoint.java:100)
at org.eclipse.ltk.core.refactoring.participants.ParticipantManager.loadMoveParticipants(ParticipantManager.java:121)
...
--
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
15 years, 8 months
[JBoss JIRA] Created: (JBIDE-6591) Allow user to use default package names in from wsdl scenarios
by Lukas Jungmann (JIRA)
Allow user to use default package names in from wsdl scenarios
--------------------------------------------------------------
Key: JBIDE-6591
URL: https://jira.jboss.org/browse/JBIDE-6591
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Webservices
Affects Versions: 3.2.0.M1
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
Attachments: interfax.wsdl
-create ws or ws client from attached WSDL
=> fails due to:
Failed to Generate Web Service code, please check the log for more details
org.eclipse.core.runtime.CoreException: parsing WSDL...
[ERROR] Two declarations cause a collision in the ObjectFactory class.
line 227 of http://schemas.xmlsoap.org/soap/encoding/
[ERROR] (Related to above error) This is the other declaration.
line 365 of file:/space/workspace-jboss/jbosstools-trunk/ws/tests/org.jboss.tools.ws.ui.test/resources/interfax.wsdl
[ERROR] Two declarations cause a collision in the ObjectFactory class.
line 444 of http://schemas.xmlsoap.org/soap/encoding/
[ERROR] (Related to above error) This is the other declaration.
line 363 of file:/space/workspace-jboss/jbosstools-trunk/ws/tests/org.jboss.tools.ws.ui.test/resources/interfax.wsdl
[ERROR] Two declarations cause a collision in the ObjectFactory class.
line 366 of file:/space/workspace-jboss/jbosstools-trunk/ws/tests/org.jboss.tools.ws.ui.test/resources/interfax.wsdl
[ERROR] (Related to above error) This is the other declaration.
line 453 of http://schemas.xmlsoap.org/soap/encoding/
[ERROR] Two declarations cause a collision in the ObjectFactory class.
line 364 of file:/space/workspace-jboss/jbosstools-trunk/ws/tests/org.jboss.tools.ws.ui.test/resources/interfax.wsdl
[ERROR] (Related to above error) This is the other declaration.
line 291 of http://schemas.xmlsoap.org/soap/encoding/
Workaround: use binding files/inline wsdl customizations to resolve conflicts or switch to command line and use "wsconsume -k interfax.wsdl" (note ommited '-p' argument) to let the tool generate default packages (according to spec) from target namespaces defined in WSDL
problem here is that we, in ws from wsdl and ws client wizards/scenarios, are forcing user to set a package name for generated classes but setting/using package name is not mandatory for under-lied tools (default behaviour is to map namespaces defined in WSDL/XSD to java package names - defined by spec), so we should relax this constraint
--
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
15 years, 8 months
[JBoss JIRA] Created: (JBIDE-6510) [tester] configure monitor action produces invalid service url
by Lukas Jungmann (JIRA)
[tester] configure monitor action produces invalid service url
--------------------------------------------------------------
Key: JBIDE-6510
URL: https://jira.jboss.org/browse/JBIDE-6510
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.M1
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
-have two services running on different ports, ie 7777 (ie. using javax.xml.ws.Endpoint.publish(...)) and 8080 (running on JBoss)
let's test first service - the one runnning on port 7777
1) configure monitor for this service in a tester so the monitoring port is ie 6666
2) invoke tester
=> OK ...but you may sometimes see the progress monitor being shown even after the communication between client and server is finished (not sure about exact steps to reproduce here)
now let's test the second service
3) use "Get from WSDL..." button to change the stuff in the UI
4) tweak soap body if needed
5) click on the "Configure Monitor" button
=> nothing happens - I'd assume that service url will be changed to the one used by the monitor (localhost:8080 shanged to localhost:6666) at least or some UI should be shown
-restart the IDE and try to test the second service again - in the other words repeat steps 3-5
=> service URL is changed from http://localhost:8080/webws/Ws to http://localhost:6666:8080/webws/Ws; it should be only http://localhost:6666/webws/Ws instead
--
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
15 years, 8 months
[JBoss JIRA] Created: (JBIDE-6699) NPE while renaming a file with no extension
by Lukas Jungmann (JIRA)
NPE while renaming a file with no extension
-------------------------------------------
Key: JBIDE-6699
URL: https://jira.jboss.org/browse/JBIDE-6699
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 3.2.0.M2
Reporter: Lukas Jungmann
Assignee: Kris Verlaenen
-create some empty file with no extension, ie 'file'
-invoke Refactoring -> Rename... action on it and rename 'file' to ie 'file.wsdl'
=>
java.lang.NullPointerException
at org.drools.eclipse.refactoring.RuleIFileRenameParticipant.initialize(Unknown Source)
at org.eclipse.ltk.core.refactoring.participants.RefactoringParticipant.initialize(RefactoringParticipant.java:105)
at org.eclipse.ltk.core.refactoring.participants.ParticipantExtensionPoint.getParticipants(ParticipantExtensionPoint.java:100)
at org.eclipse.ltk.core.refactoring.participants.ParticipantManager.loadRenameParticipants(ParticipantManager.java:74)
at org.eclipse.ltk.internal.core.refactoring.resource.RenameResourceProcessor.loadParticipants(RenameResourceProcessor.java:238)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:233)
at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85)
at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121)
at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:209)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
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
15 years, 8 months