[JBoss JIRA] (JBIDE-13481) When runtime is not found, ask user before adding path to list for scanning
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13481?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13481:
------------------------------------
Description:
1. Click Window > Preferences > JBoss Tools > JBoss Tools Runtime Detection
2. Click Add and select a random directory without a runtime
3. Next window displays 'No runtime found' (as expected!)
4. Click Cancel
5. Despite no runtime being found this path has been added to the list of paths to scan.
I can understand that some users might want to add paths despite runtimes not being found - hence current behavior. But some users might just be searching for a runtime location using trial and error and it can become frustrating to have to then select the path and click Remove.
Could this be improved by adding a step between 4 and 5? So after clicking Cancel a message is displayed to say 'No runtime was found. Are you sure you want to add this path?' with yes/no options, where yes adds the path and no doesn't add it.
was:
1. Click Window > Preferences > JBoss Tools > JBoss Tools Runtime Detection
2. Click Add and select a random directory without a runtime
3. Next window displays 'No runtime found' (as expected!)
4. Click Cancel
5. Despite no runtime being found this path has been added to the list of paths to scan.
I can understand that some users might want to add paths despite runtimes not being found - hence current behavior. But some users might just be searching for a runtime location using trial and error and it can become frustration to have to then select the path and click Remove.
Could this be improved by adding a step between 4 and 5? So after clicking Cancel a message is displayed to say 'No runtime was found. Are you sure you want to add this path?' with yes/no options, where yes adds the path and no doesn't add it.
> When runtime is not found, ask user before adding path to list for scanning
> ---------------------------------------------------------------------------
>
> Key: JBIDE-13481
> URL: https://issues.jboss.org/browse/JBIDE-13481
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection
> Affects Versions: 4.0.0.Final
> Reporter: Michelle Murray
> Assignee: Snjezana Peco
>
> 1. Click Window > Preferences > JBoss Tools > JBoss Tools Runtime Detection
> 2. Click Add and select a random directory without a runtime
> 3. Next window displays 'No runtime found' (as expected!)
> 4. Click Cancel
> 5. Despite no runtime being found this path has been added to the list of paths to scan.
> I can understand that some users might want to add paths despite runtimes not being found - hence current behavior. But some users might just be searching for a runtime location using trial and error and it can become frustrating to have to then select the path and click Remove.
> Could this be improved by adding a step between 4 and 5? So after clicking Cancel a message is displayed to say 'No runtime was found. Are you sure you want to add this path?' with yes/no options, where yes adds the path and no doesn't add it.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13481) When runtime is not found, ask user before adding path to list for scanning
by Michelle Murray (JIRA)
Michelle Murray created JBIDE-13481:
---------------------------------------
Summary: When runtime is not found, ask user before adding path to list for scanning
Key: JBIDE-13481
URL: https://issues.jboss.org/browse/JBIDE-13481
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: runtime-detection
Affects Versions: 4.0.0.Final
Reporter: Michelle Murray
Assignee: Snjezana Peco
1. Click Window > Preferences > JBoss Tools > JBoss Tools Runtime Detection
2. Click Add and select a random directory without a runtime
3. Next window displays 'No runtime found' (as expected!)
4. Click Cancel
5. Despite no runtime being found this path has been added to the list of paths to scan.
I can understand that some users might want to add paths despite runtimes not being found - hence current behavior. But some users might just be searching for a runtime location using trial and error and it can become frustration to have to then select the path and click Remove.
Could this be improved by adding a step between 4 and 5? So after clicking Cancel a message is displayed to say 'No runtime was found. Are you sure you want to add this path?' with yes/no options, where yes adds the path and no doesn't add it.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13479) Update minor version for common, jst, jsf, seam, cdi components
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13479?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13479:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/41, https://github.com/jbosstools/jbosstools-jst/pull/35, https://github.com/jbosstools/jbosstools-javaee/pull/44 (was: https://github.com/jbosstools/jbosstools-base/pull/41, https://github.com/jbosstools/jbosstools-jst/pull/35)
> Update minor version for common, jst, jsf, seam, cdi components
> ---------------------------------------------------------------
>
> Key: JBIDE-13479
> URL: https://issues.jboss.org/browse/JBIDE-13479
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: CDI, common/jst/core, JSF, Seam 2
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Alpha1
>
>
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13381) ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-13381:
-----------------------------------------------
In the description of this issue element <http-client-property> is inside <property> element. New screenshot shows that it is a child of <action> element. ESB editor always supported only <property> children in <action>. Supported schemas jbossesb-1.2.0.xsd, jbossesb-1.3.0.xsd, jbossesb-1.3.1.xsd say that <property> can have any content, but content of <action> can have only <property> elements.
Did editor put <http-client-property> into a wrong place after editing the file in UI form, or was that element initially where it is shown?
> ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13381
> URL: https://issues.jboss.org/browse/JBIDE-13381
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 3.3.0.Final-SOA
> Reporter: Brian Fitzpatrick
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 3.3.x, 4.0.x
>
> Attachments: JBIDE-13381-3.3.x.patch, jbide-13381.patch, JBIDE-13381_error.png, JBIDE-13381_error_source.png
>
>
> When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way.
> When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername">
> <http-client-property name="file" value="httpclient.properties" />
> </property>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited)
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1-edited">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername"/>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine.
--
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
13 years, 2 months
[JBoss JIRA] (JBDS-2458) JBDS uninstaller doesn't actually remove JBDS
by Michelle Murray (JIRA)
Michelle Murray created JBDS-2458:
-------------------------------------
Summary: JBDS uninstaller doesn't actually remove JBDS
Key: JBDS-2458
URL: https://issues.jboss.org/browse/JBDS-2458
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.GA
Environment: Fedora 17
Reporter: Michelle Murray
The uninstaller has two options:
1. force deletion of installation folder (select check box)
2 don't force the deletion of the installation folder (don't select check box)
I would expect option 1 to delete the whole installation folder including any files I might have added in there. It does. :)
I would expect option 2 to delete anything to do with JBDS but leave the folder and any files I have created in it. It doesn't. It leaves a studio folder full of JBDS files and a shortcut by which I can still launch what appears to be a working JBDS. As a user I would assume that the uninstaller would remove JBDS at the very least and I shouldn't still be able to launch it. :(
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13479) Update minor version for common, jst, jsf, seam, cdi components
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13479?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13479:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/41, https://github.com/jbosstools/jbosstools-jst/pull/35 (was: https://github.com/jbosstools/jbosstools-base/pull/41)
> Update minor version for common, jst, jsf, seam, cdi components
> ---------------------------------------------------------------
>
> Key: JBIDE-13479
> URL: https://issues.jboss.org/browse/JBIDE-13479
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: CDI, common/jst/core, JSF, Seam 2
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Alpha1
>
>
--
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
13 years, 2 months