Jai som.vistech compilation problem

Hello!
The problem is that when I try to import a class from com.vistech, I get a "packave com.vistech.jai.imageio does not exist".
The strange thing is that I can import classes form com.sun and javax.media so I suppose the installation has been made ok.
What could be the problem?
Please help!!!

is the package is pre defined in java? ( I Think that package is not a predefined package from java. It is user defined pacakage). If not u have to set classpath to that package first and then u have to compile.
since com.sun and javax.media are predefined they will be automatically added to classpath but user defined packages will not be added.

Similar Messages

Re: [iPlanet-JATO] sp3 jsp compiler problem

Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text
substitution situations, and as a completely independent tool its use is not
restricted to migration situations (or file types for that matter).
Second, I sympathize with the unfortunate trouble you are experiencing due to
Jasper's (perhaps more strict) compilation, but in what way did the iMT
automated translation contribute to these inconsistencies that you cited?
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a
translation situation, the only way "OnClick" would have been introduced was if
it had been part of the pre-existing project's "extraHTML" (which was written
by the original customer and just passed through unchanged by the iMT) or if it
was added manually by the post-migration developer.
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
similar to the OnClick situation described above?
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no
equivalent in the NetDynamics world, so any content tags in your code must have
been introduced by your developers manually. Its a shame that jasper is so
particular, but the iMT could not help you out here even if we wanted to. The
constants that are used by the iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
[Non-text portions of this message have been removed]

Thanks a lot Matt and Mike for your prompt replies.
I agree completely that iMT doesn't introduce the inconsistencies.
About the three cases I mentioned, the third one happens only in
manually created JSPs. So it has nothing to do with iMT. The first
two are mainly due to the existing HTML code, as you rightly pointed
out.
The reason I made the suggestion is since we know that case 1 and 2
won't pass the japser compiler in sp3, we have to do something about
it. The best place to do this, in my mind, is iMT. Of course, there
might be some twists that make it impossible or difficult to do this
kind of case manipulation or attribute discard.
Weiguo
--- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
tool its use is not restricted to migration situations (or file types
for that matter).
>
Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
in what way did the iMT automated translation contribute to these
inconsistencies that you cited?
>
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
introduced was if it had been part of the pre-existing
project's "extraHTML" (which was written by the original customer and
just passed through unchanged by the iMT) or if it was added manually
by the post-migration developer.
>
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
>
>
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
in your code must have been introduced by your developers manually.
Its a shame that jasper is so particular, but the iMT could not help
you out here even if we wanted to. The constants that are used by the
iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
see, the only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
>
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as
what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
>>
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
Service.
>
>
>
[Non-text portions of this message have been removed]

Compilation problem in a JSP page

Hi all,
I'm trying to write a jsp page and some java stuff in it.
It goes something like this -
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@ page contentType="text/html;charset=windows-1255"%>
<html>
<head>
    <meta http-equiv="Content-Type" content="text/html; charset=windows-1255"/>
    <title>Michael</title>
</head>
<body>
<%
          String strError="";
%>
</body>Now the problem is that I get compilation problem about the use in java -
"String cannot be resolved to a type"
I know for sure that in other computers it's work, the question is what I'm missing?
I have Java VM installed and I've downloaded and installed the latest JDK, what else?
thanks,
Michael.

Michael4488 wrote:
BalusC wrote:
Then you should be using JSTL/EL.I don't familiar with this technology, any way - Its work on one computer so in my understanding it should work on the other as well.It is not related to the actual problem. It was just a comment on your code. Using scriptlets is considered as bad practice.
I understand that of course, but I don't use any configuration file or set any special parameters in my computer.
What exactly does the compiler need in order to recognize the Java code in the JSP page? If i manually add the JAVA_HOME environment variable it will work?
where should I refer it to? "..\Java\jre1.6.0_07\lib" will do?It must point to the root installation directory of the JDK (thus not the JRE!).

Compilation problem on solaris9 x86

I am working on JAVA/J2EE . Am new to solaris9 . My requirement is to compile a source distribution of MOD-JK 1.2.21 (apache 2.0 server connector)and to produce binary distribution (*.so file) in solaris9 X86 box. But i got only source distribution of solaris10 X86 platform . Even with this source i tried to compile in solaris9 box its giving some error message and i can't able to make a executable file. Below i pasted the error message .
# ./configure -with-apxs=/usr/apache2/bin/apxs
checking build system type... i386-pc-solaris2.10
checking host system type... i386-pc-solaris2.10
checking target system type... i386-pc-solaris2.10
checking for a BSD-compatible install... scripts/build/unix/install-sh -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... no
checking for gcc... no
checking for cc... cc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
Can any body help me in this regards. Even i don't know, am proceeding in right direction to compile this file. If any body having the binary distribution for the same MOD-JK1.2.21 on solaris9 or solaris10 X86 platform for apache2.0 . please help me to compile this file .I given below the config.log file entries also.
Thanks in advance..........
karthikeyan.u
[email protected]
AIM or AOL :: karthikeyanu
CONFIG.log entries......
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ ./configure -with-apxs=/usr/apache2/bin/apxs
## Platform. ##
hostname = Solaris
uname -m = i86pc
uname -r = 5.10
uname -s = SunOS
uname -v = Generic_118844-26
/usr/bin/uname -p = i386
/bin/uname -X = System = SunOS
Node = Solaris
Release = 5.10
KernelID = Generic_118844-26
Machine = i86pc
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 1
/bin/arch = i86pc
/usr/bin/arch -k = i86pc
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/sbin
PATH: /usr/bin
PATH: /usr/openwin/bin
PATH: /usr/ucb
## Core tests. ##
configure:1546: checking build system type
configure:1564: result: i386-pc-solaris2.10
configure:1572: checking host system type
configure:1586: result: i386-pc-solaris2.10
configure:1594: checking target system type
configure:1608: result: i386-pc-solaris2.10
configure:1640: checking for a BSD-compatible install
configure:1695: result: scripts/build/unix/install-sh -c
configure:1706: checking whether build environment is sane
configure:1749: result: yes
configure:1814: checking for gawk
configure:1843: result: no
configure:1814: checking for mawk
configure:1843: result: no
configure:1814: checking for nawk
configure:1830: found /usr/bin/nawk
configure:1840: result: nawk
configure:1850: checking whether make sets $(MAKE)
configure:1874: result: no
configure:2085: checking for gcc
configure:2114: result: no
configure:2165: checking for cc
configure:2181: found /usr/ucb/cc
configure:2191: result: cc
configure:2355: checking for C compiler version
configure:2358: cc --version </dev/null >&5
/usr/ucb/cc: language optional software package not installed
configure:2361: $? = 1
configure:2363: cc -v </dev/null >&5
/usr/ucb/cc: language optional software package not installed
configure:2366: $? = 1
configure:2368: cc -V </dev/null >&5
/usr/ucb/cc: language optional software package not installed
configure:2371: $? = 1
configure:2394: checking for C compiler default output file name
configure:2397: cc conftest.c >&5
/usr/ucb/cc: language optional software package not installed
configure:2400: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "mod_jk"
| #define VERSION "1.2.21"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2439: error: C compiler cannot create executables
See `config.log' for more details.
## Cache variables. ##
ac_cv_build=i386-pc-solaris2.10
ac_cv_build_alias=i386-pc-solaris2.10
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_F77_set=
ac_cv_env_F77_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=i386-pc-solaris2.10
ac_cv_host_alias=i386-pc-solaris2.10
ac_cv_prog_AWK=nawk
ac_cv_prog_ac_ct_CC=cc
ac_cv_prog_make_make_set=no
ac_cv_target=i386-pc-solaris2.10
ac_cv_target_alias=i386-pc-solaris2.10
## Output variables. ##
ACLOCAL='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run aclocal-1.9'
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run tar'
APACHE20_OEXT=''
APACHE_CONFIG_VARS=''
APACHE_DIR=''
APXS=''
APXSCFLAGS=''
APXSCPPFLAGS=''
APXSLDFLAGS=''
AR=''
AUTOCONF='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run autoconf'
AUTOHEADER='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run autoheader'
AUTOMAKE='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run automake-1.9'
AWK='nawk'
CC='cc'
CCDEPMODE=''
CFLAGS=''
CP=''
CPP=''
CPPFLAGS=''
CXX=''
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS=''
CYGPATH_W='echo'
DEFS=''
DEPDIR=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
F77=''
FFLAGS=''
GREP=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
INSTALL_TYPE=''
JAVA_HOME=''
JK_JNI_WORKER=''
LDFLAGS=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LIB_JK_TYPE=''
LN_S=''
LTLIBOBJS=''
MAKEINFO='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run makeinfo'
MAKE_DYNAMIC_APACHE_FALSE=''
MAKE_DYNAMIC_APACHE_TRUE=''
MKDIR=''
OBJEXT=''
OS=''
PACKAGE='mod_jk'
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
PERL=''
RANLIB=''
RM=''
SED=''
SET_MAKE='MAKE=make'
SHELL='/bin/bash'
STRIP=''
TEST=''
VERSION='1.2.21'
WEBSERVER=''
ac_ct_AR=''
ac_ct_CC='cc'
ac_ct_CXX=''
ac_ct_F77=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__fastdepCXX_FALSE=''
am__fastdepCXX_TRUE=''
am__include=''
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
apache_include=''
bindir='${exec_prefix}/bin'
build='i386-pc-solaris2.10'
build_alias=''
build_cpu='i386'
build_os='solaris2.10'
build_vendor='pc'
datadir='${prefix}/share'
exec_prefix='NONE'
host='i386-pc-solaris2.10'
host_alias=''
host_cpu='i386'
host_os='solaris2.10'
host_vendor='pc'
includedir='${prefix}/include'
infodir='${prefix}/info'
install_sh='/export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/install-sh'
int32_t_fmt=''
int32_value=''
int64_t_fmt=''
int64_value=''
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='${prefix}/var'
mandir='${prefix}/man'
mkdir_p='$(install_sh) -d'
oldincludedir='/usr/include'
prefix='NONE'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target='i386-pc-solaris2.10'
target_alias=''
target_cpu='i386'
target_os='solaris2.10'
target_vendor='pc'
uint32_t_fmt=''
uint32_t_hex_fmt=''
uint64_t_fmt=''
uint64_t_hex_fmt=''
## confdefs.h. ##
#define PACKAGE "mod_jk"
#define PACKAGE_BUGREPORT ""
#define PACKAGE_NAME ""
#define PACKAGE_STRING ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define VERSION "1.2.21"
configure: exit 77

You need to make sure the source is for the same version i.e. if you run apache 2.0.52 you need the source of 2.0.52. I successfully ran mixed installs, but I would not recommend it. You can download the required source from Apache.
As for your compiler problem, make sure you have �/usr/ccs/bin/� in the your path, if you do not have it installed you will have to add the pkg �SUNWsprot�. You do not have 'make' in yout path.
Make sure you have the following packages installed:
SUNWbtool, SUNWsprot, SUNWtoo
SUNWhea, SUNWarc, SUNWlibm, SUNWlibms
SUNWdfbh, SUNWcg6h, SUNWxwinc, SUNWolinc,
SUNWxglh,SUNWarcx, SUNWbtoox, SUNWdplx,
SUNWscpux, SUNWsprox, SUNWlmsx, SUNWlmx
SUNWlibCx, SUNWtoox, SUNWsra, SUNWsrh

Compilation problem with templates while using option -m64

Hi,
I have compilation problem with template while using option -m64.
No problem while using option -m32.
@ uname -a
SunOS snt5010 5.10 Generic_127111-11 sun4v sparc SUNW,SPARC-Enterprise-T5220
$ CC -V
CC: Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
Here is some C++ program
############# foo5.cpp #############
template <typename T, T N, unsigned long S = sizeof(T) * 8>
struct static_number_of_ones
static const T m_value = static_number_of_ones<T, N, S - 1>::m_value >> 1;
static const unsigned long m_count = static_number_of_ones<T, N, S - 1>::m_count + (static_number_of_ones<T, N, S - 1>::m_value & 0x1);
template <typename T, T N>
struct static_number_of_ones<T, N, 0>
static const T m_value = N;
static const unsigned long m_count = 0;
template <typename T, T N>
struct static_is_power_of_2
static const bool m_result = (static_number_of_ones<T,N>::m_count == 1);
template <unsigned long N>
struct static_number_is_power_of_2
static const bool m_result = (static_number_of_ones<unsigned long, N>::m_count == 1);
int main(int argc)
int ret = 0;
if (argc > 1)
ret += static_is_power_of_2<unsigned short, 16>::m_result;
ret += static_is_power_of_2<unsigned int, 16>::m_result;
ret += static_is_power_of_2<unsigned long, 16>::m_result;
ret += static_number_is_power_of_2<16>::m_result;
else
ret += static_is_power_of_2<unsigned short, 17>::m_result;
ret += static_is_power_of_2<unsigned int, 17>::m_result;
ret += static_is_power_of_2<unsigned long, 17>::m_result;
ret += static_number_is_power_of_2<17>::m_result;
return ret;
Compiation:
@ CC -m32 foo5.cpp
// No problem
@ CC -m64 foo5.cpp
"foo5.cpp", line 20: Error: An integer constant expression is required here.
"foo5.cpp", line 36: Where: While specializing "static_is_power_of_2<unsigned long, 16>".
"foo5.cpp", line 36: Where: Specialized in non-template code.
"foo5.cpp", line 26: Error: An integer constant expression is required here.
"foo5.cpp", line 37: Where: While specializing "static_number_is_power_of_2<16>".
"foo5.cpp", line 37: Where: Specialized in non-template code.
"foo5.cpp", line 20: Error: An integer constant expression is required here.
"foo5.cpp", line 43: Where: While specializing "static_is_power_of_2<unsigned long, 17>".
"foo5.cpp", line 43: Where: Specialized in non-template code.
"foo5.cpp", line 26: Error: An integer constant expression is required here.
"foo5.cpp", line 44: Where: While specializing "static_number_is_power_of_2<17>".
"foo5.cpp", line 44: Where: Specialized in non-template code.
4 Error(s) detected.
Predefined macro:
@ CC -m32 -xdumpmacros=defs foo5.cpp | & tee log32
@ CC -m64 -xdumpmacros=defs foo5.cpp | & tee log64
@ diff log32 log64
7c7
< #define __TIME__ "09:24:58"
#define __TIME__ "09:25:38"20c20
< #define __sparcv8plus 1
#define __sparcv9 1[snipped]
=========================
What is wrong?
Thanks,
Alex Vinokur

Bug 6749491 has been filed for this problem. It will be visible at [http://bugs.sun.com] in a day or two.
If you have a service contract with Sun, you can ask to have this bug's priority raised, and get a pre-release version of a compiler patch that fixes the problem.
Otherwise, you can check for new patches from time to time at
[http://developers.sun.com/sunstudio/downloads/patches/]
and see whether this bug is listed as fixed.

RE: RE : Compile problems

Doug,
I also had a very similar error. At first I thought it might have been
similar to the technote 38525, but in the end I force compiled the workspace
and re made the distribution and the fcompile worked like normal. So if you
don't think the technote matches your situation then I recommend force
compiling your workspace.
Regards,
Allister
-----Original Message-----
From: [email protected]
[<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Ajith Kallambella
Sent: Thursday, 6 May 1999 23:01
To: [email protected]; [email protected]
Subject: RE : Compile problems
Doug,
Your method is probably returning a data type that the codegenerator
is misinterpreting.
It could be related to a documented problem where a return statement
returning an unsigned long( or a few other type ) value generates a
GENERICRETURN instruction, which codegen erroneously believed
to have no
operands, causing decompilation errors.
Take a look at Bug # 38525.
The suggested work around is not to return unsigned long( or a few other
data types ).
Ajith Kallambella M
Subject: Compile problems
Has anyone ever seen this error when using fcompile to compile their
partitions?? The create/compile of the workspace & the
partitioning of the
application all went fine. It seems to indicate there may be a
problem with
the fetchEncounterWithItsClaim method. What's the IRBlock ?? Any
help would
be greatly appreciated!!
Processing partition generation file:
/usr/local/bin/forte3j/appdist/hcssdeve/hcssmain/cl27/codegen/hcss
ma8/hcssma
8.pgf
Creating and initializing code generator, this could take some time.
ERROR: Exiting due to following exception:
SYSTEM ERROR: Client partition FTCompile_cl0_Client was terminated by
escaped
exception. See the remainder of the error stack for more information.
Class: qqsp_ResourceException
Error #: [1001, 3]
Detected at: qqrt_ForteExecAgent::LoadPartition at 1
Error Time: Wed May 5 17:38:50
Exception occurred (locally) on partition "Forte_Executor",
(partitionId
=
25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
[25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in application
"FTCompile_cl0", pid 13061 on node gromit.HealthPartners.com in
environment <unknown>.
SYSTEM ERROR: Variable index 71 is outside the range 0 to 26 for the
IRBlock fetchEncounterWithItsClaim.
Class: qqsp_Exception
Error #: [1001, 203]
Detected at: qqrt_IRBlock::GetTypeIndex at 1
Last TOOL statement: method ForteCompiler.ProcessPGF
Error Time: Wed May 5 17:38:50
Exception occurred (locally) on partition "Forte_Executor",
(partitionId =
25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
[25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in application
"FTCompile_cl0", pid 13061 on node gromit.HealthPartners.com in
environment <unknown>.
Doug Scurr
HealthPartners
8100 34th Avenue South
9th Floor
Minneapolis, MN 55440-1309
(612)883-7317
- att-1.unk
Get Free Email and Do More On The Web. Visit <a href=
"http://www.msn.com">http://www.msn.com</a>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:<a href=
"http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:<a href=
"http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

Allister,
That's the only thing(force compile) I could think of to try, so I did & re
made the distribution last night & it worked fine!!
Doug Scurr
HealthPartners
8100 34th Avenue South
9th Floor
Minneapolis, MN 55440-1309
(612)883-7317
-----Original Message-----
From: Allister Dickson [SMTP:[email protected]]
Sent: Friday, May 07, 1999 1:23 AM
To: Ajith Kallambella; [email protected];
[email protected]
Subject: RE: RE : Compile problems
Doug,
I also had a very similar error. At first I thought it might have
been
similar to the technote 38525, but in the end I force compiled the
workspace
and re made the distribution and the fcompile worked like normal. So
if you
don't think the technote matches your situation then I recommend
force
compiling your workspace.
Regards,
Allister
> -----Original Message-----
> From: [email protected]
> [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Ajith
Kallambella
> Sent: Thursday, 6 May 1999 23:01
> To: [email protected]; [email protected]
> Subject: RE : Compile problems
>
>
> Doug,
>
> Your method is probably returning a data type that the
codegenerator
> is misinterpreting.
>
> It could be related to a documented problem where a return
statement
> returning an unsigned long( or a few other type ) value generates
a
> GENERICRETURN instruction, which codegen erroneously believed
> to have no
> operands, causing decompilation errors.
>
> Take a look at Bug # 38525.
>
> The suggested work around is not to return unsigned long( or a few
other
> data types ).
>
>
> Ajith Kallambella M
>
>
> Subject: Compile problems
>
>
> Has anyone ever seen this error when using fcompile to compile
their
> partitions?? The create/compile of the workspace & the
> partitioning of the
> application all went fine. It seems to indicate there may be a
> problem with
> the fetchEncounterWithItsClaim method. What's the IRBlock ?? Any
> help would
> be greatly appreciated!!
>
> Processing partition generation file:
> /usr/local/bin/forte3j/appdist/hcssdeve/hcssmain/cl27/codegen/hcss
> ma8/hcssma
> 8.pgf
> Creating and initializing code generator, this could take some
time.
> ERROR: Exiting due to following exception:
>
> SYSTEM ERROR: Client partition FTCompile_cl0_Client was terminated
by
> escaped
> exception. See the remainder of the error stack for more
information.
> Class: qqsp_ResourceException
> Error #: [1001, 3]
> Detected at: qqrt_ForteExecAgent::LoadPartition at 1
> Error Time: Wed May 5 17:38:50
> Exception occurred (locally) on partition "Forte_Executor",
> (partitionId
> =
> 25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
> [25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in application
> "FTCompile_cl0", pid 13061 on node gromit.HealthPartners.com
in
> environment <unknown>.
>
> SYSTEM ERROR: Variable index 71 is outside the range 0 to 26
for the
> IRBlock fetchEncounterWithItsClaim.
> Class: qqsp_Exception
> Error #: [1001, 203]
> Detected at: qqrt_IRBlock::GetTypeIndex at 1
> Last TOOL statement: method ForteCompiler.ProcessPGF
> Error Time: Wed May 5 17:38:50
> Exception occurred (locally) on partition
"Forte_Executor",
> (partitionId =
> 25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
> [25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in
application
> "FTCompile_cl0", pid 13061 on node
gromit.HealthPartners.com in
> environment <unknown>.
>
> Doug Scurr
> HealthPartners
> 8100 34th Avenue South
> 9th Floor
> Minneapolis, MN 55440-1309
> (612)883-7317
>
>
> - att-1.unk
>
>
> _______________________________________________________________
> Get Free Email and Do More On The Web. Visit <a href=
"http://www.msn.com">http://www.msn.com</a>
> -
> To unsubscribe, email '[email protected]' with
> 'unsubscribe forte-users' as the body of the message.
> Searchable thread archive
<URL:<a href=
"http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:<a href=
"http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

Jdev 10G Custom Tag compilation problems

Hi,
I noticed that new tld's are added to "src/META-INF/."
When i compile my jsp to reference the tld it is not successful b/c it is looking for the tlds within the "public_html" or somewhere within it. I turned off tld and web.xml validation, but jdev 10G still validates the location of the tld. Is there way to configure Jdev to put the tld in another location?
I know i can work around this by building w/ ant or someother compiler external to Jdev, but would like to remedy this problem so i can use jdeveloper as it is.
hope someone can shed some light, i've been working on this all day long...
Thanks in advance,
Eugene

i am referenceing the tld via the web.xml alias entry. I found a work around where i copy the tld to somewhere in the public_html location of the project. I guess Jdeveloper doesn't look for the tld within META-INF which is embedded in the src directory structure of the project. For some reason, Jdeveloper doesn't look there for the TLD where it writes the tld to. it's interesting that jdeveloper doesn't look for the tld where it writes to. :)
from the server side, when i deploy, it works okay. but to get around the compilation problem, i have to copy the tld or softlink it to the META-INF location of the original tld.
I tried turning off web.xml, tld, and jsp validation of TLDs to get around this problem, but that doesn't seem to "turn it off."
How do you approach this problem? do you use ant or some other external build process?
thanks!

Exception in thread "main" java.lang.Error: Unresolved compilation problem

The following code:
     public boolean find(MusbachJ_Person person,BstNode node)
          //p.l(person);p.l(node.intData);
          if(node.intData.compareTo(person)==0)
               return true;
          if( node.leftNode != null ) find(person,node.leftNode );
          if( node.rightNode != null ) find( person, node.rightNode);
          else
               return false;
     }returns the following compilation error:
Exception in thread "main" java.lang.Error: Unresolved compilation problem:
     This method must return a result of type boolean
     at MusbachJ_TreeNode.find(MusbachJ_TreeNode.java:32)
     at MusbachJ_PeopleTree.main(MusbachJ_PeopleTree.java:91)
But I don't understand, the else statement is right there, what more does it want? Thanks! :)

John_Musbach wrote:
Exception in thread "main" java.lang.Error: Unresolved compilation problem: Unresolved compilation problem is an error that you'll only ever see if you're using an IDE. If you used the javac compiler, then you would have seen that the code doesn't even compile.
The reason (as others have pointed out) is, that some paths through your method don't return a value.
I'll re-write your code in the code-style that I usually use, because then it might be easier for you to see the problem:
public boolean find(MusbachJ_Person person,BstNode node)
     if(node.intData.compareTo(person)==0) {
          return true;
     if( node.leftNode != null ) {
          find(person,node.leftNode );
     if( node.rightNode != null ) {
          find( person, node.rightNode);
     else {
          return false;
}There are two prolbems. I'll spell out the first and let the other one for you to find:
1.) you don't do anything with the return-values of the find-methods you are calling. What do you want to do with them?
2.) What do you return if the current node is not the one that you want and you've got a right node?

HELP.....!!!!! Chinese jsp compilation problem.....

Hi,
Could someone please help on the above mentioned?
I'm using JDeveloper 3.2.3 for my program development under Chinese windows platform. I have created a simple JSP page, which contains few static Chinese words and I have included the line
<%@ page contentType="text/html;charset=UTF-8"%>
at the top of the page. When I tried to compile it using encoding "UTF8" (under compiler option), the compiler gave me this error:
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.jsp
Error: (0) sun.io.MalformedInputException.
Btw, when I have removed the line <%@ page contentType="text/html;charset=UTF-8"%> from the page and compile, I've got this error:
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.jsp
Warning: (0) ISO-8859-1 character set may not match project compiler setting.
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.java
Error: (0) malformed input character in C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.java.
I do appreciate your help on this. Thank you.

Here's some info one of the JSP Developers sent me:
1. HELP.....!!!!! Chinese jsp compilation problem.....
The customer is trying to parse a document generated by
Windows's notepad. When saved in UTF-8, the byte
order mark is saved too. We have a know bug that
JSP parser doesn't recognize Byte Order Mark. The
bug is : 1915285.
2. CHINESE CHARACTER ON JSP
. SQLPLUS depends on NLS_LANG setting. If you
check the windows registry, the default of NLS_LANG
depends on the OS. The user environment is Traditional
Chinese, so does NLS_LANG. If we set NLS_LANG
to .UTF8, SQLPLUS dumps the data in UTF8, however,
the command prompt will have problem displaying them.
. For JSP, as mentioned in a previous mail:
<%@ page contentType="text/html;charset=UTF-8" %> for all languages
<%@ page contentType="text/html;charset=GB2312" %> for simplified Chinese
<%@ page contentType="text/html;charset=Big5" %> for traditional Chinese
. When you enter Chinese characters on a browser,
the data is automatically converted to page encoding
(UTF-8 in your case) before sent back to the server.
But your receiving servlet/JSP needs to have request
encoding set correctly.
    I'm not sure about the JDeveloper environment,
but here is a simple JSP you may try to verify your
OC4J environment:
a.    To set up the schema:
connect scott/tiger
create table tab01(col varchar2(100));
b. Edit the connect string in nls.jsp
c. Run the nls.jsp in oc4j instance.

<%@ page contentType="text/html; charset=UTF-8" %>
<%@ page import="oracle.jdbc.*,java.sql.*,java.io.*"%>
<HTML>
<HEAD>
<TITLE>Hello</TITLE></HEAD>
<BODY>
<%
request.setCharacterEncoding("UTF-8");
String sampledata="\u7D20";
String paramValue = request.getParameter("myparam");
String connStr = "jdbc:oracle:thin:@dlsun478:5521:j2ee01";
String user = "scott";
String passwd = "tiger";
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection(connStr, user, passwd);
if (paramValue == null || paramValue.length() == 0) { %>
   <FORM METHOD="GET">
   Please input your name: <INPUT TYPE="TEXT" NAME="myparam"
value="<%=sampledata%>" size=20>
<BR>
   <INPUT TYPE="SUBMIT" value="Insert Data">
   </FORM>
<%
selectData(conn, out);
else
%>
   <H1> Insert Data: <%= paramValue %> </H1>
   <br/>
<%
insertData(conn, paramValue);
%>
<a href="nls.jsp">back</a>
<%
%>
</BODY>
</HTML>
<%!
public void insertData(Connection aConn, String myval)
    try {
      PreparedStatement stmt = aConn.prepareStatement("insert into tab01
values(?)");
      stmt.setString(1, myval);
      stmt.executeUpdate();
      aConn.close();
    catch (SQLException e) {
      e.printStackTrace();
public void selectData (Connection aConn, JspWriter out)
    try {
      Statement stmt = aConn.createStatement( );
      ResultSet r = stmt.executeQuery("SELECT col FROM tab01");
      out.println("<H1>List of Data:</H1>");
      while (r.next()) {
        out.println(r.getString(1)+"<br/>");
      aConn.close();
    catch (SQLException e) {
      e.printStackTrace();
    catch (IOException e) {
      e.printStackTrace();
%>

Unresolve compilation problems

I have narrowed a bug down to three lines of code. I do not see what is wrong with this code. In fact I am so sure of the code I was wondering if it may be a bug in 1.5
I get the error:
Exception in thread "main" java.lang.Error: Unresolved compilation problems:
     Syntax error, insert "AssignmentOperator Expression" to complete Assignment
     Syntax error, insert ";" to complete Statement
     LVN cannot be resolved
     foo cannot be resolved
     e cannot be resolved
on the the last line of :
if (useLVN)
         for(Enumeration e = ilocGen.getRoutines().elements(); e.hasMoreElements();)
              LVN foo = new LVN((BasicBlock) e.nextElement());LVN is a class who's constructor takes a BasicBlock as an argument. iloc.getRoutines() returns a vector and useLVN is a boolean that is set earlier in the program. The program was fully functional until I inserted these three lines. if I replace the body of the for loop with ";" the code will still execute.
Has anyone seen this kind of error before? Can someone clue me into what I am doing wrong? or is this something that should be taken to a bug report of some kind?

I recreated the issue. The error appears in the last line of source code. Below is the full source code for all of the classes. As a note I am using jre1.5.0_06 and eclipse 3.2.1 as my IDE. The operating system I am currently using is Windows XP Pro. (Obviously not that it should matter based on the language in question.)
File:
BasicBlock.java
public class BasicBlock {
     public String str;
     public BasicBlock(String in){
          str = in;
IlocGenerator.java
import java.util.Vector;
public class IlocGenerator {
      Vector routines = new Vector();
      public Vector getRoutines() {
              return routines;
      public void addRoutine(IlocRoutine in){
          routines.add(in);
LVN.java
public class LVN {
     public LVN(BasicBlock in){
          System.out.println(in.str);
IlocRoutine.java
import java.util.*;
public class IlocRoutine {
     private Vector Blocks;
     public IlocRoutine(){
          Blocks = new Vector();
     public void addBasicBlock(BasicBlock in){
          Blocks.add(in);
     public Vector getBasicBlocks() {
         return Blocks;
MainProg.java
import java.util.Enumeration;
public class MainProg {
     public static void main(String[] args) {
          boolean useLVN = true;
          IlocGenerator ilocGen = new IlocGenerator();
          IlocRoutine iR = new IlocRoutine();
          BasicBlock bB = new BasicBlock("one");
          iR.addBasicBlock(bB);
          bB = new BasicBlock("two");
          iR.addBasicBlock(bB);
          ilocGen.addRoutine(iR);
          iR = new IlocRoutine();
          bB = new BasicBlock("three");
          iR.addBasicBlock(bB);
          bB = new BasicBlock("four");
          iR.addBasicBlock(bB);
          ilocGen.addRoutine(iR);
         if (useLVN)
              for(Enumeration e = ilocGen.getRoutines().elements(); e.hasMoreElements();)
                   for (Enumeration f = ((IlocRoutine) e.nextElement()).getBasicBlocks().elements(); f.hasMoreElements();)
                        LVN foo = new LVN((BasicBlock) f.nextElement());
}Message was edited by:
mtu9000 (added environment information)

Compiling problem related to library conflict

Hi everybody,
As I used JDeveloper 10.1.3.0.3 to compile my program, I encounted a compiling problem.
In my user library, I have a class named Number.
In J2SE 1.5, there is also a class named Number at java.lang.Number.
So as I compiled the program, the compiler always tried to find the java.lang.Number first, then I got the compiling errors related to the class java.lang.Number.
I have added the jar file of my own package in the classpath, but I still got the compiling error.
But If I directly use JDK instead of JDeveloper to compiler the program, there is no such kind of problem.
Can somebody help me with that.
I really apprecaite your help.
William

Looks like I've been dumbed down by Java simpliciy. I'm referencing some source code that calls a function from this particular library. When I am compiling my code that makes the same call, I assume I need that library to be called out for the linker (link.exe). Do I also need any other libraries that this library calls and so on? How do I determine that the extent of what I need. The source code I'm referncing does include a make file. This was to create and exe file. Is it possible that I can edit this and have it make a dll instead?

JSP Compilation Problems With JSTL tags

My JSP worked well when I used JSP expressions, scriptlets, .... I tried to use JSTL instead and encountered some compilation problems. I am unable to see my mistakes and need help:
Problme #1:
int offset = 0;
try
   <c:set var="offset" value="${requestScope.offset}" />
catch ( Exception e )
    // do nothing
}The above code has two compilation errors:
Generated servlet error:
[javac] Compiling 1 source file
illegal start of expression
<c:set var="offset" value="${requestScope.offset}" />
^
Generated servlet error:
';' expected
<c:set var="offset" value="${requestScope.offset}" />
^
Problem #2:
<c:set var="threadBean" value="${requestScope.ThreadBean}" />
int threadID_int = ParamUtil.getParameterInt( request, "thread" );
<c:if test="${threadBean.threadID} != threadID_int">
    throw new AssertionException( "The two threadID are not the same." );
</c:if>Generated servlet error:
illegal start of expression
<c:if test="${threadBean.threadID != threadID_int}">
^

I have deleted the Java code around the JSTL tags. Now, what is wrong with this <c:if test=" ... "> tag? It seems that I have problems to get JSTL tags right.
It seems that I have problems to get JSTL tags right....
<c:if test="${attachBean.attachMimeType.startsWith('image/')}">
     <html:img page="getattachment?attach=<c:out value='${attachBean.attachID}' />" alt="<c:out value='${attachBean.attachFilename}' />" title="<c:out value='${attachBean.attachFilename}' />" border="0" />
</c:if>error message:
74: tag = 'if' / attribute = 'test': An error occurred while parsing custom action attribute "test" with value "${attachBean.attachMimeType.startsWith('image/')}": Encountered "(", expected one of ["}", ".", ">", "gt", "<", "lt", "==", "eq", "<=", "le", ">=", "ge", "!=", "ne", "[", "+", "-", "*", "/", "div", "%", "mod", "and", "&&", "or", "||"]

Removing compiler problem markers

Does anybody know why I keep getting a pop up window that is
telling me it can't find a marker id at some location number? I am
getting one of these messages about every other time I save and
compile and it is getting RATHER ANNOYING!!! What does it mean and
how do I eliminate it???
Thanks in advance for helping me lower my blood pressure!!!
Have an Ordinary Day...
KomputerMan ~|:-)

Yes, I am now getting the same error - but slightly different
wording
Removing compile problem markers (Time of error: blah blah
blah...)
The details section states:
An internal error occurred during "Removing compiler problem
markers".
java.lang.NullPointerException
I'm able to compile the same code with no problem from the
command line on a Linux box. Running the clean comand doesn't fix
this unfortunately.
Some background info: I'm running a FDS project against a
JBoss server on a windows XP machine.
So, I deleted my project and shut down flex builder. Then
removed the project files (.actionScriptProperties, .project, &
.flexProperties) and removed the project folder from the flex.war
folder in the jboss server. Restarted Flex Builder and created a
new project the same way the project was built. And wa-la the
problem is gone.
So, something has gone bad with the project, but I am not
sure what because a look a the previous project files and they all
seem normal. I was having problems with the project trying to
create the "Output Directory" early, but a rebuild of the project
seemed to fix that too.
hope this helps.
--Andy

IRC compilation problem

import org.jibble.pircbot.*;
import com.sun.speech.freetts.*;
import com.sun.speech.freetts.audio.*;
import javax.sound.sampled.*;
import java.io.File;
public class SpeechBot extends PircBot {
    private Voice voice;
    public SpeechBot(String name) {
        setName(name);
        // Choose the voice for the speech synthesizer.
        String voiceName = "kevin16";
        VoiceManager voiceManager =
VoiceManager.getInstance();
        voice = voiceManager.getVoice(voiceName);
        if (voice == null) {
            System.out.println("Voice not found.");
            System.exit(1);
        voice.allocate();
        // Set up the output format.
        AudioPlayer voicePlayer = new JavaClipAudioPlayer();
        voicePlayer.setAudioFormat(new AudioFormat(8000,
16, 1, false, true));
        voice.setAudioPlayer(voicePlayer);
    public void onMessage(String channel, String sender,
String login, String hostname, String message) {
        // Send all IRC messages to the voice
synthesizer.
        message = message.trim();
        String input = sender + " on " + channel + "
says: " + message;
        voice.speak(input);
    public static void main(String[] args) throws
Exception {
        if (args.length < 2) {
            System.out.println("Usage: java SpeechBot
<server> <channel>");
            System.exit(1);
        SpeechBot bot = new SpeechBot("SpeechBot");
        bot.connect(args[0]);
        bot.joinChannel(args[1]);
}This is my code,i have downloaded all the jar files needed for it,but its not getting compiled
please tell me the correct statement of the compilation.......

In your last thread (which you crossposted around) I told you that you need to spend some time with the networking tutorials. Perhaps you really need to spend time with the basic Java tutorials instead?
There are a bunch of problems with this post anyway like
1) It doesn't belong in this forum, but most likely New to Java or Java Programming. Simple compilation problems go into those forums.
2) You didn't provide the most important information anyway. The statement "its not getting compiled" tells us nothing. It's totally useless.
3) Posting about problems with third-party libaries as you are here is also discouraged. You should ask the people/person who wrote the class for help
But again, based on both this and your previous thread, it seems pretty clear to me that you are attempting to bite off far more than you can know chew. If you are student trying to learn, again I urge you to stop and spend a good amount of time with the basic Java tutorials. Learn how basic Java code is structured and how to solve simple classpath and syntax compilation errors. If you are employed then you got this job by lying so my advice to you would be to quit. You're at least 6 months away from being safe to let work on any code.

Servlet Compilation Problem !

Hi,
I am just starting to learn servlets and I got problem in compiling them. I got compilation error in
import javax.servlet.*;statement. Seems that the compiler cannot find the servlet package. I got J2EE 1.4 beta installed on my machine but there is no servlet.jar package. I am using J2SDK 1.4.1_02, J2EE 1.4 beta and Tomcat 4.1.24.
Can anyone help me with my servlet compilation problem?
Thanks in advance!
Josh

servlet.jar is here :
<tomcatdir>\common\lib
add it to your compiler classpath

Jai som.vistech compilation problem

Similar Messages

Maybe you are looking for