You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "William Tam (JIRA)" <ji...@apache.org> on 2008/10/06 06:13:44 UTC
[jira] Created: (CXF-1841) Some issues with outbound jca connector
Some issues with outbound jca connector
---------------------------------------
Key: CXF-1841
URL: https://issues.apache.org/jira/browse/CXF-1841
Project: CXF
Issue Type: Bug
Components: Integration
Reporter: William Tam
Fix For: 2.2
1. The client proxy factory does not get configured by Configurer to inject configurations. So, for example, the ws security cannot be enabled in JCA connector.
2. ManagedConnectionImpl should implement equals() ahd hashcode() based on properties as required by JCA 1.5
3. A single bus is shared by multiple web applications. It is not possible to have a per web application bus config.
4. If a bean class is defined in a WAR and it is referenced by bus config, the bus cannot be created when the JCA connector starts in WebSphere 6.1. The reason is JCA connector classloader cannot load the class in belong in a WAR.
5. The outbound connector APIs should be moved to the api module so that javadoc can be produced for them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1841) Some issues with outbound jca connector
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CXF-1841:
---------------------------------
Assignee: Willem Jiang
> Some issues with outbound jca connector
> ---------------------------------------
>
> Key: CXF-1841
> URL: https://issues.apache.org/jira/browse/CXF-1841
> Project: CXF
> Issue Type: Bug
> Components: Integration
> Reporter: William Tam
> Assignee: Willem Jiang
> Fix For: 2.2
>
> Attachments: CXF-1841.patch
>
>
> 1. The client proxy factory does not get configured by Configurer to inject configurations. So, for example, the ws security cannot be enabled in JCA connector.
> 2. ManagedConnectionImpl should implement equals() ahd hashcode() based on properties as required by JCA 1.5
> 3. A single bus is shared by multiple web applications. It is not possible to have a per web application bus config.
> 4. If a bean class is defined in a WAR and it is referenced by bus config, the bus cannot be created when the JCA connector starts in WebSphere 6.1. The reason is JCA connector classloader cannot load the class in belong in a WAR.
> 5. The outbound connector APIs should be moved to the api module so that javadoc can be produced for them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1841) Some issues with outbound jca connector
Posted by "William Tam (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Tam updated CXF-1841:
-----------------------------
Attachment: CXF-1841.patch
I created a patch to address the issues and added a sample. The new inbound connector has been tested with WAS 6.1 but it has not been tested with JBoss. Both the inbound and outbound connector need to be tested with JBoss and resolve any issues that may pop up. Once that's been done, we can remove the old inbound and outbound connector.
> Some issues with outbound jca connector
> ---------------------------------------
>
> Key: CXF-1841
> URL: https://issues.apache.org/jira/browse/CXF-1841
> Project: CXF
> Issue Type: Bug
> Components: Integration
> Reporter: William Tam
> Fix For: 2.2
>
> Attachments: CXF-1841.patch
>
>
> 1. The client proxy factory does not get configured by Configurer to inject configurations. So, for example, the ws security cannot be enabled in JCA connector.
> 2. ManagedConnectionImpl should implement equals() ahd hashcode() based on properties as required by JCA 1.5
> 3. A single bus is shared by multiple web applications. It is not possible to have a per web application bus config.
> 4. If a bean class is defined in a WAR and it is referenced by bus config, the bus cannot be created when the JCA connector starts in WebSphere 6.1. The reason is JCA connector classloader cannot load the class in belong in a WAR.
> 5. The outbound connector APIs should be moved to the api module so that javadoc can be produced for them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1841) Some issues with outbound jca
connector
Posted by "William Tam (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636992#action_12636992 ]
William Tam commented on CXF-1841:
----------------------------------
I'll submit a patch.
> Some issues with outbound jca connector
> ---------------------------------------
>
> Key: CXF-1841
> URL: https://issues.apache.org/jira/browse/CXF-1841
> Project: CXF
> Issue Type: Bug
> Components: Integration
> Reporter: William Tam
> Fix For: 2.2
>
>
> 1. The client proxy factory does not get configured by Configurer to inject configurations. So, for example, the ws security cannot be enabled in JCA connector.
> 2. ManagedConnectionImpl should implement equals() ahd hashcode() based on properties as required by JCA 1.5
> 3. A single bus is shared by multiple web applications. It is not possible to have a per web application bus config.
> 4. If a bean class is defined in a WAR and it is referenced by bus config, the bus cannot be created when the JCA connector starts in WebSphere 6.1. The reason is JCA connector classloader cannot load the class in belong in a WAR.
> 5. The outbound connector APIs should be moved to the api module so that javadoc can be produced for them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1841) Some issues with outbound jca connector
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CXF-1841.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0.9
2.1.3
> Some issues with outbound jca connector
> ---------------------------------------
>
> Key: CXF-1841
> URL: https://issues.apache.org/jira/browse/CXF-1841
> Project: CXF
> Issue Type: Bug
> Components: Integration
> Reporter: William Tam
> Assignee: Willem Jiang
> Fix For: 2.1.3, 2.2, 2.0.9
>
> Attachments: CXF-1841.patch
>
>
> 1. The client proxy factory does not get configured by Configurer to inject configurations. So, for example, the ws security cannot be enabled in JCA connector.
> 2. ManagedConnectionImpl should implement equals() ahd hashcode() based on properties as required by JCA 1.5
> 3. A single bus is shared by multiple web applications. It is not possible to have a per web application bus config.
> 4. If a bean class is defined in a WAR and it is referenced by bus config, the bus cannot be created when the JCA connector starts in WebSphere 6.1. The reason is JCA connector classloader cannot load the class in belong in a WAR.
> 5. The outbound connector APIs should be moved to the api module so that javadoc can be produced for them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-1841) Some issues with outbound jca connector
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang closed CXF-1841.
-----------------------------
> Some issues with outbound jca connector
> ---------------------------------------
>
> Key: CXF-1841
> URL: https://issues.apache.org/jira/browse/CXF-1841
> Project: CXF
> Issue Type: Bug
> Components: Integration
> Reporter: William Tam
> Assignee: Willem Jiang
> Fix For: 2.0.9, 2.1.3, 2.2
>
> Attachments: CXF-1841.patch
>
>
> 1. The client proxy factory does not get configured by Configurer to inject configurations. So, for example, the ws security cannot be enabled in JCA connector.
> 2. ManagedConnectionImpl should implement equals() ahd hashcode() based on properties as required by JCA 1.5
> 3. A single bus is shared by multiple web applications. It is not possible to have a per web application bus config.
> 4. If a bean class is defined in a WAR and it is referenced by bus config, the bus cannot be created when the JCA connector starts in WebSphere 6.1. The reason is JCA connector classloader cannot load the class in belong in a WAR.
> 5. The outbound connector APIs should be moved to the api module so that javadoc can be produced for them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.