You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by ax...@ws.apache.org on 2004/09/28 16:39:31 UTC
[jira] Created: (AXISCPP-173) Fix classpath issue
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-173
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-173
Summary: Fix classpath issue
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-C++
Components:
Configuration
Fix Fors:
1.3 Beta
Versions:
1.3 Beta
Assignee:
Reporter: John Hawkins
Created: Tue, 28 Sep 2004 7:38 AM
Updated: Tue, 28 Sep 2004 7:38 AM
Due: Thu, 14 Oct 2004 12:00 AM
Description:
When running WSDL2WS you must have Axis C jar file before Axis Java file in your classpath. We can do some checks on the class path environment variable in WSDL2WS to ensure that we do at least print out a messages telling the user that they need to fix this before we go on.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXISCPP-173) Fix classpath issue
Posted by "John Hawkins (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXISCPP-173?page=history ]
John Hawkins closed AXISCPP-173:
--------------------------------
This is closed. WSDL2Ws has been refactored to remove this
> Fix classpath issue
> -------------------
>
> Key: AXISCPP-173
> URL: http://nagoya.apache.org/jira/browse/AXISCPP-173
> Project: Axis-C++
> Type: Bug
> Components: Configuration
> Versions: 1.3 Beta
> Reporter: John Hawkins
> Fix For: 1.3 Beta
>
> When running WSDL2WS you must have Axis C jar file before Axis Java file in your classpath. We can do some checks on the class path environment variable in WSDL2WS to ensure that we do at least print out a messages telling the user that they need to fix this before we go on.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXISCPP-173) Fix classpath issue
Posted by ax...@ws.apache.org.
Message:
The following issue has been resolved as FIXED.
Resolver: John Hawkins
Date: Fri, 15 Oct 2004 3:41 AM
I'm calling this resolved as we are refactoring WSDL2WS for 1.4
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-173
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-173
Summary: Fix classpath issue
Type: Bug
Status: Resolved
Priority: Major
Resolution: FIXED
Project: Axis-C++
Components:
Configuration
Fix Fors:
1.3 Beta
Versions:
1.3 Beta
Assignee:
Reporter: John Hawkins
Created: Tue, 28 Sep 2004 7:38 AM
Updated: Fri, 15 Oct 2004 3:41 AM
Due: Thu, 14 Oct 2004 12:00 AM
Description:
When running WSDL2WS you must have Axis C jar file before Axis Java file in your classpath. We can do some checks on the class path environment variable in WSDL2WS to ensure that we do at least print out a messages telling the user that they need to fix this before we go on.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-173) Fix classpath issue
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: John Hawkins
Created: Wed, 6 Oct 2004 6:50 AM
Body:
I have put in a catch so that if the same error occurs then a nicer message is displayed explaining what probably caused the problem and asking them to check. This is only a temporary fix prior to refactoring WSDL2ws in 1.4
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXISCPP-173?page=comments#action_53756
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-173
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-173
Summary: Fix classpath issue
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-C++
Components:
Configuration
Fix Fors:
1.3 Beta
Versions:
1.3 Beta
Assignee:
Reporter: John Hawkins
Created: Tue, 28 Sep 2004 7:38 AM
Updated: Wed, 6 Oct 2004 6:50 AM
Due: Thu, 14 Oct 2004 12:00 AM
Description:
When running WSDL2WS you must have Axis C jar file before Axis Java file in your classpath. We can do some checks on the class path environment variable in WSDL2WS to ensure that we do at least print out a messages telling the user that they need to fix this before we go on.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-173) Fix classpath issue
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Samisa Abeysinghe
Created: Tue, 28 Sep 2004 7:06 PM
Body:
An easier temporary solution would be to provide a script with proper settings, so that the users do not want to bother about setting the class path.
In te longer run, I think this has to be taken care of the refactoring effort of the WSDL2Ws tool. The problem is C++ tool uses the same package names as of Axis Java. We need to introduce a unique package name for WWSDL2WS tool classes specific to C++ code generation. This would eliminate possible future collision with Axis Java jars as well.
I propose org.apache.axis.cpp.wsdl for package name.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXISCPP-173?page=comments#action_53480
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-173
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-173
Summary: Fix classpath issue
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-C++
Components:
Configuration
Fix Fors:
1.3 Beta
Versions:
1.3 Beta
Assignee:
Reporter: John Hawkins
Created: Tue, 28 Sep 2004 7:38 AM
Updated: Tue, 28 Sep 2004 7:06 PM
Due: Thu, 14 Oct 2004 12:00 AM
Description:
When running WSDL2WS you must have Axis C jar file before Axis Java file in your classpath. We can do some checks on the class path environment variable in WSDL2WS to ensure that we do at least print out a messages telling the user that they need to fix this before we go on.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-173) Fix classpath issue
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: John Hawkins
Created: Wed, 29 Sep 2004 2:50 AM
Body:
I think I'd prefer to leave the user to worry about how they prefer to set up their classpaths (although providing a script would be a nice way of showing all the pre-reqs too!)
I can implement the classpath (or other coded) check quite easily.
I agree about WSDL2WS refactoring being the way to go.
Naming is fine by me !
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXISCPP-173?page=comments#action_53490
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-173
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-173
Summary: Fix classpath issue
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-C++
Components:
Configuration
Fix Fors:
1.3 Beta
Versions:
1.3 Beta
Assignee:
Reporter: John Hawkins
Created: Tue, 28 Sep 2004 7:38 AM
Updated: Wed, 29 Sep 2004 2:50 AM
Due: Thu, 14 Oct 2004 12:00 AM
Description:
When running WSDL2WS you must have Axis C jar file before Axis Java file in your classpath. We can do some checks on the class path environment variable in WSDL2WS to ensure that we do at least print out a messages telling the user that they need to fix this before we go on.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira