10:32 p.m.
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://jira.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
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
10:34 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://jira.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.syst...
]
Dan Allen updated ARQ-308:
--------------------------
Attachment: ARQ-308.patch
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://jira.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
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
10:36 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://jira.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-308:
-------------------------------
Given that the OpenEJB FAQ describes using AppInfo.jarPath to undeploy an application, I
have to believe that this API change is accidental. I'll ping David about this.
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://jira.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
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
10:46 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://jira.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-308:
-------------------------------
Reference to FAQ: http://openejb.apache.org/faq.html
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://jira.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
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
4:05 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://jira.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-308:
-------------------------------
David says,
"Not sure if this helps, but I added in 3.1.3 a 'public void
destroyApplication(AppInfo appInfo) throws UndeployException' method to Assembler.
That method is actually there pre-3.1.3, but it is scoped 'private'. Would still
involve a little reflection, but maybe better?"
That would be an ideal solution for future proofing our adapter. I'm thinking we
compile against 3.1.3 and use destoryApplication(AppInfo). We'll put a try/catch
around that call to catch the NoSuchMethodException. In the catch block, we'll use
reflection to get AppInfo.jarPath value and call destroyApplication(String path).
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://jira.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
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
4:05 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://jira.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.syst...
]
Dan Allen edited comment on ARQ-308 at 10/6/10 10:05 PM:
---------------------------------------------------------
David says,
"Not sure if this helps, but I added in 3.1.3 a 'public void
destroyApplication(AppInfo appInfo) throws UndeployException' method to Assembler.
That method is actually there pre-3.1.3, but it is scoped 'private'. Would still
involve a little reflection, but maybe better?"
That would be an ideal solution for future proofing our adapter. I'm thinking we
compile against 3.1.3 and use destroyApplication(AppInfo). We'll put a try/catch
around that call to catch the NoSuchMethodException for pre-3.1.3 runtimes. In the catch
block, we'll use reflection to get AppInfo.jarPath value and call
destroyApplication(String path).
was (Author: dan.j.allen):
David says,
"Not sure if this helps, but I added in 3.1.3 a 'public void
destroyApplication(AppInfo appInfo) throws UndeployException' method to Assembler.
That method is actually there pre-3.1.3, but it is scoped 'private'. Would still
involve a little reflection, but maybe better?"
That would be an ideal solution for future proofing our adapter. I'm thinking we
compile against 3.1.3 and use destroyApplication(AppInfo). We'll put a try/catch
around that call to catch the NoSuchMethodException. In the catch block, we'll use
reflection to get AppInfo.jarPath value and call destroyApplication(String path).
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://jira.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
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
4:05 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://jira.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.syst...
]
Dan Allen edited comment on ARQ-308 at 10/6/10 10:04 PM:
---------------------------------------------------------
David says,
"Not sure if this helps, but I added in 3.1.3 a 'public void
destroyApplication(AppInfo appInfo) throws UndeployException' method to Assembler.
That method is actually there pre-3.1.3, but it is scoped 'private'. Would still
involve a little reflection, but maybe better?"
That would be an ideal solution for future proofing our adapter. I'm thinking we
compile against 3.1.3 and use destroyApplication(AppInfo). We'll put a try/catch
around that call to catch the NoSuchMethodException. In the catch block, we'll use
reflection to get AppInfo.jarPath value and call destroyApplication(String path).
was (Author: dan.j.allen):
David says,
"Not sure if this helps, but I added in 3.1.3 a 'public void
destroyApplication(AppInfo appInfo) throws UndeployException' method to Assembler.
That method is actually there pre-3.1.3, but it is scoped 'private'. Would still
involve a little reflection, but maybe better?"
That would be an ideal solution for future proofing our adapter. I'm thinking we
compile against 3.1.3 and use destoryApplication(AppInfo). We'll put a try/catch
around that call to catch the NoSuchMethodException. In the catch block, we'll use
reflection to get AppInfo.jarPath value and call destroyApplication(String path).
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://jira.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
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
7:30 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://jira.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-308:
-------------------------------
Link to ARQ-308 branch for applied patch reference:
http://github.com/mojavelinux/arquillian/tree/ARQ-308
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://jira.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
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
3:45 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://issues.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-308:
------------------------------
Assignee: Aslak Knutsen
Fix Version/s: 1.0.0.Alpha5
(was: 1.0.0.Beta1)
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://issues.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha5
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:01 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://issues.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-308:
------------------------------
Fix Version/s: 1.0.0.Beta1
(was: 1.0.0.Alpha5)
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://issues.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Beta1
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:20 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://issues.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-308:
------------------------------
Fix Version/s: 1.1.0.CR1
(was: 1.0.0.Beta1)
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://issues.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.1.0.CR1
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:15 p.m.
New subject: [JBoss JIRA] (ARQ-308) Patch to support OpenEJB 3.2 API change
[
https://issues.jboss.org/browse/ARQ-308?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-308:
------------------------------
Fix Version/s: openejb_1.0.0.next
(was: 1.1.0.CR1)
Patch to support OpenEJB 3.2 API change
---------------------------------------
Key: ARQ-308
URL: https://issues.jboss.org/browse/ARQ-308
Project: Arquillian
Issue Type: Patch
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: openejb_1.0.0.next
Attachments: ARQ-308.patch
The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the
exception of one field reference. The public field AppInfo#jarPath was renamed to
AppInfo#path. Attached is a patch which will determine the correct field name through
reflection so both APIs can be supported.
Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables
people to use it), and may be unnecessary if we find out why the field name was change.
Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary.
Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4596
days inactive
4972
days old
arquillian-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Aslak Knutsen (JIRA) -
Aslak Knutsen (Updated) (JIRA)
-
Dan Allen (JIRA)