[JBoss JIRA] Created: (JBIDE-7551) Instance View: Table Sorting should have 3 states and indicate sorting with arrows
by Andre Dietisheim (JIRA)
Instance View: Table Sorting should have 3 states and indicate sorting with arrows
----------------------------------------------------------------------------------
Key: JBIDE-7551
URL: https://jira.jboss.org/browse/JBIDE-7551
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
How to reproduce:
1) make sure you have instance view opened and a few instances listed
2) click on a column
Result:
the column gets sorted, but there's no icon that shows the sort direction. Furthermore there are only 2 states: sorting ascending or descending
Expected result:
The column gets sorted and an icon shows what direction (ascending/descending) is activated. Furthermore you should be able to toggle between ascending/descending/not sorted by clicking consecutively on the same column
--
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
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-9035) IPublishCopyCallbackHandler#deleteResource returns status but no caller is accounting for
by Andre Dietisheim (JIRA)
IPublishCopyCallbackHandler#deleteResource returns status but no caller is accounting for
-----------------------------------------------------------------------------------------
Key: JBIDE-9035
URL: https://issues.jboss.org/browse/JBIDE-9035
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M1, 3.2.1.M1
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Fix For: 3.3.x
IPublishCopyCallbackHandler#deleteResource returns status instances for the different filesystem operations involved to it but none of the callers take them in account. They all ignore it and return STATUS_OK.
occurrences:
* AltMethodZippedJSTPublisher#removeRemoteDeploymentFolder
* AbstractServerToolsPublisher#fullPublish
* AbstractServerToolsPublisher#unpublish
* JBoss7JSTPublisher#removeDeployedMarkerFile
* PublishCopyUtil#publishDelta
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-8329) Automatic detection of web port does not work for EAP 4.3
by Magnus Mogren (JIRA)
Automatic detection of web port does not work for EAP 4.3
---------------------------------------------------------
Key: JBIDE-8329
URL: https://issues.jboss.org/browse/JBIDE-8329
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR1
Reporter: Magnus Mogren
Assignee: Rob Stryker
The automatic detection of web port does not work for EAP 4.3 servers.
The reason is a faulty XPath expession used to detect the port: //Server/Service[@name='jboss.web']/Connector[count(@sslProtocol) = 0 and (count(@protocol) = 0 or @protocol = 'HTTP/1.1')]
That expression tries to get the value of the Connector element in the server.xml, not the port attribute of the element.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-7924) Allow user to create a web service in custom source root
by Lukas Jungmann (JIRA)
Allow user to create a web service in custom source root
--------------------------------------------------------
Key: JBIDE-7924
URL: https://issues.jboss.org/browse/JBIDE-7924
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Webservices
Affects Versions: 3.2.0.Beta2
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
-create or have a web project with two or more java source roots, say src (default) and src2 (custom)
-create some @WebService class in the src2 source root
-create a Bottom-up web service from the class created in previous step
=> generated classes are in src (default) java source root but I'd expect them in src2 (custom) source root since the class I used is there or I should have an option to choose where to put generated classes
for Top-down ws there's no way to say where to put generated stuff
If I choose to use Axis, I'm given an option to specify target source folder, if I use JBossWS I'm not given any option
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-8075) Cannot create message correlation property using the wizzard.
by Marek Baluch (JIRA)
Cannot create message correlation property using the wizzard.
-------------------------------------------------------------
Key: JBIDE-8075
URL: https://issues.jboss.org/browse/JBIDE-8075
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.2.0.CR1
Environment: JBoss BPEL editor: 1.0.0.v20110106-2124-H21-CR1
Reporter: Marek Baluch
As stated in the summary I cannot create message correlation property using the wizzard. When a property type is selected then the "Create Message Property" dialog will not notice the selection - no type is shown after the "Type:" label and the "New..." alias button remains greyed-out.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months