You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2007/05/13 08:15:15 UTC
[jira] Created: (OPENEJB-578) Register SERVICE_ENDPOINT last
Register SERVICE_ENDPOINT last
------------------------------
Key: OPENEJB-578
URL: https://issues.apache.org/jira/browse/OPENEJB-578
Project: OpenEJB
Issue Type: Bug
Reporter: Jarek Gawor
CoreDeploymentInfo.addInterface() function registers the class and its super interfaces with a given interface type. It also always overwrites previous registrations. That means that the registration order might matter in cases two classes of different type share the same interfaces. For example, SEI is set to Foo class, and the remote EJB interface 'Bar' implements 'Foo' interface.
The attached patch makes the SEI registration last to ensure the class is registered with right interface type (as the interface type is used to determine if it is a web service call or not)/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENEJB-578) Register SERVICE_ENDPOINT last
Posted by "Jacek Laskowski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacek Laskowski resolved OPENEJB-578.
-------------------------------------
Resolution: Fixed
Sending container/openejb-core/src/main/java/org/apache/openejb/core/CoreDeploymentInfo.java
Transmitting file data .
Committed revision 538972.
Thanks Jarek for the patch and very sorry that it took so long. I hope it won't hinder your sending us patches ;-)
> Register SERVICE_ENDPOINT last
> ------------------------------
>
> Key: OPENEJB-578
> URL: https://issues.apache.org/jira/browse/OPENEJB-578
> Project: OpenEJB
> Issue Type: Bug
> Reporter: Jarek Gawor
> Assigned To: Jacek Laskowski
> Attachments: OPENEJB-578.patch
>
>
> CoreDeploymentInfo.addInterface() function registers the class and its super interfaces with a given interface type. It also always overwrites previous registrations. That means that the registration order might matter in cases two classes of different type share the same interfaces. For example, SEI is set to Foo class, and the remote EJB interface 'Bar' implements 'Foo' interface.
> The attached patch makes the SEI registration last to ensure the class is registered with right interface type (as the interface type is used to determine if it is a web service call or not)/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OPENEJB-578) Register SERVICE_ENDPOINT last
Posted by "Jacek Laskowski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacek Laskowski reassigned OPENEJB-578:
---------------------------------------
Assignee: Jacek Laskowski
> Register SERVICE_ENDPOINT last
> ------------------------------
>
> Key: OPENEJB-578
> URL: https://issues.apache.org/jira/browse/OPENEJB-578
> Project: OpenEJB
> Issue Type: Bug
> Reporter: Jarek Gawor
> Assigned To: Jacek Laskowski
> Attachments: OPENEJB-578.patch
>
>
> CoreDeploymentInfo.addInterface() function registers the class and its super interfaces with a given interface type. It also always overwrites previous registrations. That means that the registration order might matter in cases two classes of different type share the same interfaces. For example, SEI is set to Foo class, and the remote EJB interface 'Bar' implements 'Foo' interface.
> The attached patch makes the SEI registration last to ensure the class is registered with right interface type (as the interface type is used to determine if it is a web service call or not)/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENEJB-578) Register SERVICE_ENDPOINT last so it
doesn't get overriden
Posted by "Jacek Laskowski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacek Laskowski updated OPENEJB-578:
------------------------------------
Component/s: server
container system
Fix Version/s: 3.0
Assignee: Jarek Gawor (was: Jacek Laskowski)
Affects Version/s: 3.0
Summary: Register SERVICE_ENDPOINT last so it doesn't get overriden (was: Register SERVICE_ENDPOINT last)
> Register SERVICE_ENDPOINT last so it doesn't get overriden
> ----------------------------------------------------------
>
> Key: OPENEJB-578
> URL: https://issues.apache.org/jira/browse/OPENEJB-578
> Project: OpenEJB
> Issue Type: Bug
> Components: container system, server
> Affects Versions: 3.0
> Reporter: Jarek Gawor
> Assigned To: Jarek Gawor
> Fix For: 3.0
>
> Attachments: OPENEJB-578.patch
>
>
> CoreDeploymentInfo.addInterface() function registers the class and its super interfaces with a given interface type. It also always overwrites previous registrations. That means that the registration order might matter in cases two classes of different type share the same interfaces. For example, SEI is set to Foo class, and the remote EJB interface 'Bar' implements 'Foo' interface.
> The attached patch makes the SEI registration last to ensure the class is registered with right interface type (as the interface type is used to determine if it is a web service call or not)/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENEJB-578) Register SERVICE_ENDPOINT last
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor updated OPENEJB-578:
--------------------------------
Attachment: OPENEJB-578.patch
> Register SERVICE_ENDPOINT last
> ------------------------------
>
> Key: OPENEJB-578
> URL: https://issues.apache.org/jira/browse/OPENEJB-578
> Project: OpenEJB
> Issue Type: Bug
> Reporter: Jarek Gawor
> Attachments: OPENEJB-578.patch
>
>
> CoreDeploymentInfo.addInterface() function registers the class and its super interfaces with a given interface type. It also always overwrites previous registrations. That means that the registration order might matter in cases two classes of different type share the same interfaces. For example, SEI is set to Foo class, and the remote EJB interface 'Bar' implements 'Foo' interface.
> The attached patch makes the SEI registration last to ensure the class is registered with right interface type (as the interface type is used to determine if it is a web service call or not)/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.