Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <7099797.1192042610705.JavaMail.jira@brutus>
Date: Wed, 10 Oct 2007 11:56:50 -0700 (PDT)
From: "Jarek Gawor (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Resolved: (GERONIMO-3510) jaxws-tool client does not include
 all java ee specs in classpath
In-Reply-To: <23352373.1191620030830.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Gawor resolved GERONIMO-3510.
-----------------------------------

    Resolution: Won't Fix

On second thought, maybe it shouldn't. As a standalone tool, jaxws-tools should just require the minimal set of jars to make it work. It is responsibility of the user to pass/set the right classpath so that the tool can find the class files (and annotations) referenced from the SEI.


> jaxws-tool client does not include all java ee specs in classpath
> -----------------------------------------------------------------
>
>                 Key: GERONIMO-3510
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3510
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.0.1, 2.0.2, 2.1
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>
> The jaxws-tool should automatically include all java ee specs in classpath. Right now only a selected few are added.

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