[JBoss JIRA] (JBIDE-13381) ESB Editor removes "http-client-property" property (JBDS-2446)
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-13381:
-----------------------------------------------
It seems SVN and GIT patches are incompatible, I applied changes to 3.3.x, and just in case attached SVN patch file: JBIDE-13381-3.3.x.patch.
> ESB Editor removes "http-client-property" property (JBDS-2446)
> --------------------------------------------------------------
>
> 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
>
>
> 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] (JBIDE-13381) ESB Editor removes "http-client-property" property (JBDS-2446)
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-13381:
------------------------------------------
Attachment: JBIDE-13381-3.3.x.patch
> ESB Editor removes "http-client-property" property (JBDS-2446)
> --------------------------------------------------------------
>
> 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
>
>
> 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] (JBIDE-13404) Support for Deltaspike 0.3 (0.4)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13404?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13404:
-----------------------------------
Release Notes Text: (was: Pushed to master.)
> Support for Deltaspike 0.3 (0.4)
> --------------------------------
>
> Key: JBIDE-13404
> URL: https://issues.jboss.org/browse/JBIDE-13404
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: CDI extensions
> Affects Versions: 4.0.0.Final
> Reporter: Jaroslav Jankovič
> Assignee: Viacheslav Kabanovich
> Fix For: 4.1.0.Alpha1
>
>
> At this moment, deltaspike tooling supports deltaspike release version 0.2 incubation. In 0.3 a change in secure module was made (declaration of SecurityExtension in META-INF/services/javax.enterprise.inject.spi.Extension) and tooling doesn't support it yet. This should be fixed
--
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-13404) Support for Deltaspike 0.3 (0.4)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13404?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-13404:
----------------------------------------
Pushed to master.
> Support for Deltaspike 0.3 (0.4)
> --------------------------------
>
> Key: JBIDE-13404
> URL: https://issues.jboss.org/browse/JBIDE-13404
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: CDI extensions
> Affects Versions: 4.0.0.Final
> Reporter: Jaroslav Jankovič
> Assignee: Viacheslav Kabanovich
> Fix For: 4.1.0.Alpha1
>
>
> At this moment, deltaspike tooling supports deltaspike release version 0.2 incubation. In 0.3 a change in secure module was made (declaration of SecurityExtension in META-INF/services/javax.enterprise.inject.spi.Extension) and tooling doesn't support it yet. This should be fixed
--
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-12175) Automatic namespace completion in Facelets files
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12175?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-12175:
------------------------------------
Fix Version/s: 4.1.0.Alpha1
> Automatic namespace completion in Facelets files
> ------------------------------------------------
>
> Key: JBIDE-12175
> URL: https://issues.jboss.org/browse/JBIDE-12175
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JSF
> Affects Versions: 3.3.0.CR1
> Reporter: Lukáš Fryč
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha1, 4.1.x
>
>
> RichFaces community is complaining about complexity of maintaining namespaces through the JSF projects [1]
> as the sample could be following project file:
> https://github.com/richfaces/sandbox/blob/760fca06c7db23b542fa8d077f73dfe...
> It is very hard to maintain namespaces through project.
> ----
> What are current options when using JBoss Tools?
> * modify Facelets file templates for creating new files and list all favorite namespaces there
> * use autocompletion of detected namespaces (write {{xmlns:xyz="..."}} and autocompletion will offer you available namespaces)
> But both of the solutions are not as straight-forward as it could be.
> ----
> Tools could help and store the preferences for namespaces,
> so user would need only to start typing tag with prefix of the namespace (e.g. {{<a4j:}} and once he will complete the tag {{<a4j:ajax>}}, the namespace will be automatically added to the root of the XML file. ({{xmlns:a4j="http://richfaces.org/a4j"}}).
> ----
> The information about the prefixes could be retrieved from:
> * faces-config.xml generated by RichFaces CDK: {{faces-config/faces-config-extension/cdk:prefix}}
> * scanning the Facelets (XHTML) files in a project and collecting used namespace prefixes ({{xmlns:*}})
> [1] https://community.jboss.org/message/738739#738739
--
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-12175) Automatic namespace completion in Facelets files
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12175?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-12175:
------------------------------------
Fix Version/s: (was: 4.1.x)
> Automatic namespace completion in Facelets files
> ------------------------------------------------
>
> Key: JBIDE-12175
> URL: https://issues.jboss.org/browse/JBIDE-12175
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JSF
> Affects Versions: 3.3.0.CR1
> Reporter: Lukáš Fryč
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha1
>
>
> RichFaces community is complaining about complexity of maintaining namespaces through the JSF projects [1]
> as the sample could be following project file:
> https://github.com/richfaces/sandbox/blob/760fca06c7db23b542fa8d077f73dfe...
> It is very hard to maintain namespaces through project.
> ----
> What are current options when using JBoss Tools?
> * modify Facelets file templates for creating new files and list all favorite namespaces there
> * use autocompletion of detected namespaces (write {{xmlns:xyz="..."}} and autocompletion will offer you available namespaces)
> But both of the solutions are not as straight-forward as it could be.
> ----
> Tools could help and store the preferences for namespaces,
> so user would need only to start typing tag with prefix of the namespace (e.g. {{<a4j:}} and once he will complete the tag {{<a4j:ajax>}}, the namespace will be automatically added to the root of the XML file. ({{xmlns:a4j="http://richfaces.org/a4j"}}).
> ----
> The information about the prefixes could be retrieved from:
> * faces-config.xml generated by RichFaces CDK: {{faces-config/faces-config-extension/cdk:prefix}}
> * scanning the Facelets (XHTML) files in a project and collecting used namespace prefixes ({{xmlns:*}})
> [1] https://community.jboss.org/message/738739#738739
--
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-2038) JBDS installer should open JBDS upon completion
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBDS-2038?page=com.atlassian.jira.plugin.... ]
Daniel Azarov edited comment on JBDS-2038 at 1/24/13 12:35 PM:
---------------------------------------------------------------
Fred, you probably right!
I googled "Installation Complete" images, most of such phrases look like "Launch <product>"
I saw few cases with "Run" or "Start <product> now"
I think we should do "Launch JBoss Developer Studio".
Thanks Fred
was (Author: dazarov):
Fred, you probably right!
I googled "Installation Complete" images, most of such phrases look like "Launch <product>"
I saw few cases with "Run" or "Start <product> now"
I think we should do "Launch JBoss Developer Studio".
> JBDS installer should open JBDS upon completion
> -----------------------------------------------
>
> Key: JBDS-2038
> URL: https://issues.jboss.org/browse/JBDS-2038
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Environment: jbdevstudio-product-win32-x86_64-5.0.0.v201202250031M-H77-Beta1.jar
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Fix For: 7.0.x
>
> Attachments: JBDS-2038.patch, RunJBDSAfterInstallation.png
>
>
> As a user, once the JBDS installer completes, I expect it to open the newly installed JBDS.
> On the last page of the installer, there should be a checkbox asking the user if he wants to open JBDS immediately.
--
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