[JBoss JIRA] (JBIDE-13419) Support invocation handler binding extension of Deltaspike
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13419?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-13419:
------------------------------------------
Description:
Objects:
1. Binding Annotations - annotation type with @InvocationHandlerBinding.
2. Partial Beans - abstract classes and interfaces annotated with a binding annotation.
3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation.
Validation rules:
1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler.
Error text: "Binding annotation %annotationName% can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler."
2. There should be no more than one invocation handler for each binding annotation.
Error text: "Multiple handlers are found for binding annotation %annotationName%."
3. Invocation handler class should be normal-scoped.
Error text: "Invocation handler class should be a normal-scoped bean."
4. Each partial bean should be bound to an invocation handler.
Error text: "Partial bean %className% should have an invocation handler for binding annotation %annotationName%."
5. Deltaspike implementation of the extension reads the first binding annotation on a class and ignores the next ones. Hence, they should be marked with a warning:
"Binding annotation %annotationName% is ignored because class is already annotated with binding annotation %firstAnnotationName%."
was:
Objects:
1. Binding Annotations - annotation type with @InvocationHandlerBinding.
2. Partial Beans - abstract classes and interfaces annotated with a binding annotation.
3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation.
Validation rules:
1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler.
Error text: "Binding annotation %annotationName% can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler."
2. There should be no more than one invocation handler for each binding annotation.
Error text: "Multiple handlers are found for binding annotation %annotationName%."
3. Invocation handler class should be normal-scoped.
Error text: "Invocation handler class should be a normal-scoped bean."
4. Each partial bean should be bound to an invocation handler.
Error text: "Partial bean %className% should have an invocation handler for binding annotation %annotationName%."
> Support invocation handler binding extension of Deltaspike
> ----------------------------------------------------------
>
> Key: JBIDE-13419
> URL: https://issues.jboss.org/browse/JBIDE-13419
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: CDI extensions
> Affects Versions: 4.0.0.Final
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha1
>
>
> Objects:
> 1. Binding Annotations - annotation type with @InvocationHandlerBinding.
> 2. Partial Beans - abstract classes and interfaces annotated with a binding annotation.
> 3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation.
> Validation rules:
> 1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler.
> Error text: "Binding annotation %annotationName% can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler."
> 2. There should be no more than one invocation handler for each binding annotation.
> Error text: "Multiple handlers are found for binding annotation %annotationName%."
> 3. Invocation handler class should be normal-scoped.
> Error text: "Invocation handler class should be a normal-scoped bean."
> 4. Each partial bean should be bound to an invocation handler.
> Error text: "Partial bean %className% should have an invocation handler for binding annotation %annotationName%."
> 5. Deltaspike implementation of the extension reads the first binding annotation on a class and ignores the next ones. Hence, they should be marked with a warning:
> "Binding annotation %annotationName% is ignored because class is already annotated with binding annotation %firstAnnotationName%."
--
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-13419) Support invocation handler binding extension of Deltaspike
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13419?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-13419:
------------------------------------------
Description:
Objects:
1. Binding Annotations - annotation type with @InvocationHandlerBinding.
2. Partial Beans - abstract classes and interfaces annotated with a binding annotation.
3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation.
Validation rules:
1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler.
Error text: "Binding annotation %annotationName% can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler."
2. There should be no more than one invocation handler for each binding annotation.
Error text: "Multiple handlers are found for binding annotation %annotationName%."
3. Invocation handler class should be normal-scoped.
Error text: "Invocation handler class should be a normal-scoped bean."
4. Each partial bean should be bound to an invocation handler.
Error text: "Partial bean %className% should have an invocation handler for binding annotation %annotationName%."
was:
Objects:
1. Binding Annotations - annotation type with @InvocationHandlerBinding.
2. Partial Beans - abstract classes and interfaces annotated with a binding annotation.
3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation.
Validation rules:
1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler.
Error text: "Binding annotation {annotationName} can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler."
2. There should be no more than one invocation handler for each binding annotation.
Error text: "Multiple handlers are found for binding annotation {annotationName}."
3. Invocation handler class should be normal-scoped.
Error text: "Invocation handler class should be a normal-scoped bean."
4. Each partial bean should be bound to an invocation handler.
Error text: "Partial bean {className} should have an invocation handler for binding annotation {annotationName}."
> Support invocation handler binding extension of Deltaspike
> ----------------------------------------------------------
>
> Key: JBIDE-13419
> URL: https://issues.jboss.org/browse/JBIDE-13419
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: CDI extensions
> Affects Versions: 4.0.0.Final
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha1
>
>
> Objects:
> 1. Binding Annotations - annotation type with @InvocationHandlerBinding.
> 2. Partial Beans - abstract classes and interfaces annotated with a binding annotation.
> 3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation.
> Validation rules:
> 1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler.
> Error text: "Binding annotation %annotationName% can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler."
> 2. There should be no more than one invocation handler for each binding annotation.
> Error text: "Multiple handlers are found for binding annotation %annotationName%."
> 3. Invocation handler class should be normal-scoped.
> Error text: "Invocation handler class should be a normal-scoped bean."
> 4. Each partial bean should be bound to an invocation handler.
> Error text: "Partial bean %className% should have an invocation handler for binding annotation %annotationName%."
--
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-13419) Support invocation handler binding extension of Deltaspike
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-13419:
---------------------------------------------
Summary: Support invocation handler binding extension of Deltaspike
Key: JBIDE-13419
URL: https://issues.jboss.org/browse/JBIDE-13419
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: CDI extensions
Affects Versions: 4.0.0.Final
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.1.0.Alpha1
Objects:
1. Binding Annotations - annotation type with @InvocationHandlerBinding.
2. Partial Beans - abstract classes and interfaces annotated with a binding annotation.
3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation.
Validation rules:
1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler.
Error text: "Binding annotation {annotationName} can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler."
2. There should be no more than one invocation handler for each binding annotation.
Error text: "Multiple handlers are found for binding annotation {annotationName}."
3. Invocation handler class should be normal-scoped.
Error text: "Invocation handler class should be a normal-scoped bean."
4. Each partial bean should be bound to an invocation handler.
Error text: "Partial bean {className} should have an invocation handler for binding annotation {annotationName}."
--
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-2448) New ESB wizard - version mismatch errors - and a warning message that is not erased
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBDS-2448?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick resolved JBDS-2448.
-------------------------------------
Resolution: Done
The changes we discussed have been made to the 3.3.x, 4.0.x, and 4.1.x streams, so we should be good to go.
The new functionality should appear in the next builds of those codebases.
> New ESB wizard - version mismatch errors - and a warning message that is not erased
> -----------------------------------------------------------------------------------
>
> Key: JBDS-2448
> URL: https://issues.jboss.org/browse/JBDS-2448
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.3.GA-SOA
> Environment: Version: 5.0.2.GA
> Build id: v20130119-0035-H249-GA
> Build date: 20130119-0035
> md5sum esb.site.zip
> 4c149c52a6058edabe0ad84747443877 esb.site.zip
> Reporter: Len DiMaggio
> Assignee: Brian Fitzpatrick
> Fix For: 5.0.3.GA-SOA
>
> Attachments: JBDS-2448-3.3.x.patch, JBDS-2448-git-4.1.x.patch
>
>
> Steps:
> 1) Create new ESB runtime, select the SOA Platform dir path
> 2) Accept default version, specify a name for the new run-time
> 3) Then - before saving the new ESB runtime change the version number - the results are:
> With an SOA-P 5.2 server (ESB 4.10):
> * The default ESB version displayed is 4.10
> * If this is changed to 4.11, this warning is displayed:
> No exact match found for ESB runtime version 4.10. Assuming compatible with latest version: 4.7.
> * If the version is changed back to 4.10, the error is still displayed in the wizard
> With an SOA-P 5.3 server (ESB 4.11):
> * The default ESB version displayed is 4.11
> * If this is changed to 4.12, this warning is displayed:
> No exact match found for ESB runtime version 4.11. Assuming compatible with latest version: 4.12.
> * If the version is changed back to 4.11, the error is still displayed in the wizard
> With an SOA-P 5.3.1.ER3 server (ESB 4.11.1):
> * The default ESB version displayed is 4.11
> * If this is changed to 4.12, this warning is displayed:
> No exact match found for ESB runtime version 4.11. Assuming compatible with latest version: 4.12.
> * If the version is changed back to 4.11, the error is still displayed in the wizard
> With an SOA-P 5.3.1.ER4 server (edited VERSION file in rosetta.jar to be ESB 4.12):
> * The default ESB version displayed is 4.12
> * If this is changed to 4.11, this warning is displayed:
> No exact match found for ESB runtime version 4.12. Assuming compatible with latest version: 4.11.
> * If the version is changed back to 4.12, the error is still displayed in the wizard
--
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 Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13381:
-------------------------------------------
The new functionality should appear in the next build.
> 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] (JBDS-2448) New ESB wizard - version mismatch errors - and a warning message that is not erased
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBDS-2448?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBDS-2448:
-----------------------------------------
4.1.x/master changes done with https://github.com/jbosstools/jbosstools-esb/pull/15
> New ESB wizard - version mismatch errors - and a warning message that is not erased
> -----------------------------------------------------------------------------------
>
> Key: JBDS-2448
> URL: https://issues.jboss.org/browse/JBDS-2448
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.3.GA-SOA
> Environment: Version: 5.0.2.GA
> Build id: v20130119-0035-H249-GA
> Build date: 20130119-0035
> md5sum esb.site.zip
> 4c149c52a6058edabe0ad84747443877 esb.site.zip
> Reporter: Len DiMaggio
> Assignee: Brian Fitzpatrick
> Fix For: 5.0.3.GA-SOA
>
> Attachments: JBDS-2448-3.3.x.patch, JBDS-2448-git-4.1.x.patch
>
>
> Steps:
> 1) Create new ESB runtime, select the SOA Platform dir path
> 2) Accept default version, specify a name for the new run-time
> 3) Then - before saving the new ESB runtime change the version number - the results are:
> With an SOA-P 5.2 server (ESB 4.10):
> * The default ESB version displayed is 4.10
> * If this is changed to 4.11, this warning is displayed:
> No exact match found for ESB runtime version 4.10. Assuming compatible with latest version: 4.7.
> * If the version is changed back to 4.10, the error is still displayed in the wizard
> With an SOA-P 5.3 server (ESB 4.11):
> * The default ESB version displayed is 4.11
> * If this is changed to 4.12, this warning is displayed:
> No exact match found for ESB runtime version 4.11. Assuming compatible with latest version: 4.12.
> * If the version is changed back to 4.11, the error is still displayed in the wizard
> With an SOA-P 5.3.1.ER3 server (ESB 4.11.1):
> * The default ESB version displayed is 4.11
> * If this is changed to 4.12, this warning is displayed:
> No exact match found for ESB runtime version 4.11. Assuming compatible with latest version: 4.12.
> * If the version is changed back to 4.11, the error is still displayed in the wizard
> With an SOA-P 5.3.1.ER4 server (edited VERSION file in rosetta.jar to be ESB 4.12):
> * The default ESB version displayed is 4.12
> * If this is changed to 4.11, this warning is displayed:
> No exact match found for ESB runtime version 4.12. Assuming compatible with latest version: 4.11.
> * If the version is changed back to 4.12, the error is still displayed in the wizard
--
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-2448) New ESB wizard - version mismatch errors - and a warning message that is not erased
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBDS-2448?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBDS-2448:
-----------------------------------------
4.0.x changes done with https://github.com/jbosstools/jbosstools-esb/pull/14
> New ESB wizard - version mismatch errors - and a warning message that is not erased
> -----------------------------------------------------------------------------------
>
> Key: JBDS-2448
> URL: https://issues.jboss.org/browse/JBDS-2448
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.3.GA-SOA
> Environment: Version: 5.0.2.GA
> Build id: v20130119-0035-H249-GA
> Build date: 20130119-0035
> md5sum esb.site.zip
> 4c149c52a6058edabe0ad84747443877 esb.site.zip
> Reporter: Len DiMaggio
> Assignee: Brian Fitzpatrick
> Fix For: 5.0.3.GA-SOA
>
> Attachments: JBDS-2448-3.3.x.patch, JBDS-2448-git-4.1.x.patch
>
>
> Steps:
> 1) Create new ESB runtime, select the SOA Platform dir path
> 2) Accept default version, specify a name for the new run-time
> 3) Then - before saving the new ESB runtime change the version number - the results are:
> With an SOA-P 5.2 server (ESB 4.10):
> * The default ESB version displayed is 4.10
> * If this is changed to 4.11, this warning is displayed:
> No exact match found for ESB runtime version 4.10. Assuming compatible with latest version: 4.7.
> * If the version is changed back to 4.10, the error is still displayed in the wizard
> With an SOA-P 5.3 server (ESB 4.11):
> * The default ESB version displayed is 4.11
> * If this is changed to 4.12, this warning is displayed:
> No exact match found for ESB runtime version 4.11. Assuming compatible with latest version: 4.12.
> * If the version is changed back to 4.11, the error is still displayed in the wizard
> With an SOA-P 5.3.1.ER3 server (ESB 4.11.1):
> * The default ESB version displayed is 4.11
> * If this is changed to 4.12, this warning is displayed:
> No exact match found for ESB runtime version 4.11. Assuming compatible with latest version: 4.12.
> * If the version is changed back to 4.11, the error is still displayed in the wizard
> With an SOA-P 5.3.1.ER4 server (edited VERSION file in rosetta.jar to be ESB 4.12):
> * The default ESB version displayed is 4.12
> * If this is changed to 4.11, this warning is displayed:
> No exact match found for ESB runtime version 4.12. Assuming compatible with latest version: 4.11.
> * If the version is changed back to 4.12, the error is still displayed in the wizard
--
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