ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ciramella, EJ" <>
Subject RE: websphere jsp precompile problems...<SOLUTION>
Date Wed, 12 Nov 2003 16:05:32 GMT
Here's the official response from IBM:

Hi Ciramella,                                                           
This is Eng Kian and I would be working on this PMR with regards to the 
WAS 5.0 JspC task not recognize classpath attribute.                    
I searched in our database to know that it is a known problem and has   
been fixed in an e-fix which has an APAR number: PQ74731.               
APAR number: PQ74731                                                    
Description/symptom of problem:                                         
WebSphere ant task wsjspc does not use the classpath classref attribute.
If user specify these two attribute in the xml, user may get            
You can download this e-fix as is from the WAS Support website below    
and apply it on WAS 5.0.0 and WAS 5.0.1.                                
PQ74731: WSJSPC does not use "CLASSPATH" OR "CLASSPATHREF" attribute.
Or, alternative. This e-fix has also been packaged as part of the       
latest Fixpack 2 Cumulative Fix 1. Therefore, you may want to apply the 
latest Fixpack 2 first and then the cumulative fix 1 on your existing   
WAS 5.0. This will ensure your WAS 5.0 is at the latest fixlevel which  
has all the latest cumulative fixes since 5.0.0.                        
Please let me know if you have any question or if the efix or FP2-cf1   
helps to resolve the problem. If yes, please let me know if I may       
close the PMR ?                                                         
Eng Kian Tan                                                            
IBM WebSphere Competency Center

-----Original Message-----
From: Donal Quinlan []
Sent: Tuesday, November 11, 2003 7:16 PM
To: Ant Users List
Subject: Re: websphere jsp precompile problems...

The classpath gets set in WebSphere\AppServer\setupCmdLine.bat.
ws_ant calls the bat file before doing anything else. I have never 
succeeded in using the classpath/classpathref parameters. The workaround 
for me was to put the jar files in the WEB-INF/lib.



Ciramella, EJ wrote:

>Has anybody used the jspc task for precompiling jsps for WebSphere?
>I'm having mucho difficulty...
>The task has classpath and classpathref parameters, neither of which are
>used when the task gets executed.
>Can anyone help me here?
>     [copy] D:\ePASSV4.1WAS50Build0198\deploy\war\WEB-INF\web.xml omitted
>bInterface\public_html\en\WEB-INF\web.xml is up to date.
>Class loaded from parent loader
> +User task: wsjspc
>   +Task: wsjspc
>   [wsjspc] Executing 'C:\ePASSTOOLS\jdk1.3.1_07\jre\bin\java.exe' with
>   [wsjspc] '-Dws.output.encoding=console'
>   [wsjspc]
>   [wsjspc]
>   [wsjspc] '-Dwebsphere.lib.dir=C:\ePASSTools\WebSphere\AppServer\lib'
>   [wsjspc]
>\runtime;C:\ePASSTOOLS\IBM\WebSphere MQ\java
>   [wsjspc] '-Dwas.install.root=C:\ePASSTools\WebSphere\AppServer'
>   [wsjspc] ''
>   [wsjspc] ''
>   [wsjspc] ''
>   [wsjspc] ''
>   [wsjspc] ''
>   [wsjspc] '-DenableJava2Security=true'
>   [wsjspc]
>   [wsjspc] '-Xmx256M'
>   [wsjspc] '-classpath'
>Note that the classpath below is defined elsewhere and I can't seem to
>change it!
>   [wsjspc]
>   [wsjspc] ''
>   [wsjspc] ''
>   [wsjspc] '-appDir'
>   [wsjspc]
>   [wsjspc] '-tmpDir'
>   [wsjspc] 'D:\ePASSV4.1WAS50Build0198/MyServer/classfiles/'
>   [wsjspc]
>   [wsjspc] The ' characters around the executable and arguments are
>   [wsjspc] not part of the command.

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message