You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Paul Hanke (JIRA)" <ji...@apache.org> on 2007/05/31 16:05:16 UTC

[jira] Created: (CXF-696) Spring integration can fail when external Java archives are incorporated.

Spring integration can fail when external Java archives are incorporated.
-------------------------------------------------------------------------

                 Key: CXF-696
                 URL: https://issues.apache.org/jira/browse/CXF-696
             Project: CXF
          Issue Type: Bug
          Components: Integration
         Environment: Java 5
            Reporter: Paul Hanke
            Priority: Minor


Spring integration can fail when external Java archives are incorporated.  I'm not sure this is relevant to this forum, as the problem was encountered using Celtix Enterprise 1.1 ... but here goes: to reproduce the symptom, start with the sample Spring-hosted service endpoint and add a "lib" subdirectory; dump in a wad of Java archives (JBoss Rules should do the trick); add a <lib dir="lib"/> to the create.war task in build.xml; run the create.war task; run the copy.war task; start up the Spring container and watch the fireworks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (CXF-696) Spring integration can fail when external Java archives are incorporated.

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp closed CXF-696.
---------------------------

    Resolution: Invalid

Based on old ObjectWeb celtix code. 

> Spring integration can fail when external Java archives are incorporated.
> -------------------------------------------------------------------------
>
>                 Key: CXF-696
>                 URL: https://issues.apache.org/jira/browse/CXF-696
>             Project: CXF
>          Issue Type: Bug
>          Components: Integration
>         Environment: Java 5
>            Reporter: Paul Hanke
>            Priority: Minor
>
> Spring integration can fail when external Java archives are incorporated.  I'm not sure this is relevant to this forum, as the problem was encountered using Celtix Enterprise 1.1 ... but here goes: to reproduce the symptom, start with the sample Spring-hosted service endpoint and add a "lib" subdirectory; dump in a wad of Java archives (JBoss Rules should do the trick); add a <lib dir="lib"/> to the create.war task in build.xml; run the create.war task; run the copy.war task; start up the Spring container and watch the fireworks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CXF-696) Spring integration can fail when external Java archives are incorporated.

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp updated CXF-696:
----------------------------

    Fix Version/s: Invalid

> Spring integration can fail when external Java archives are incorporated.
> -------------------------------------------------------------------------
>
>                 Key: CXF-696
>                 URL: https://issues.apache.org/jira/browse/CXF-696
>             Project: CXF
>          Issue Type: Bug
>          Components: Integration
>         Environment: Java 5
>            Reporter: Paul Hanke
>            Priority: Minor
>             Fix For: Invalid
>
>
> Spring integration can fail when external Java archives are incorporated.  I'm not sure this is relevant to this forum, as the problem was encountered using Celtix Enterprise 1.1 ... but here goes: to reproduce the symptom, start with the sample Spring-hosted service endpoint and add a "lib" subdirectory; dump in a wad of Java archives (JBoss Rules should do the trick); add a <lib dir="lib"/> to the create.war task in build.xml; run the create.war task; run the copy.war task; start up the Spring container and watch the fireworks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.