Enum documentation is deprecated

The Java 5 Enum documentation :
(at http://java.sun.com/j2se/1.5.0/docs/guide/language/enums.html)
is deprecated.
In one of the examples:
public enum Planet {
 MERCURY (3.303e+23, 2.4397e6),
 VENUS (4.869e+24, 6.0518e6),
 EARTH (5.976e+24, 6.37814e6),
 MARS (6.421e+23, 3.3972e6),
 JUPITER (1.9e+27, 7.1492e7),
 SATURN (5.688e+26, 6.0268e7),
 URANUS (8.686e+25, 2.5559e7),
 NEPTUNE (1.024e+26, 2.4746e7),
PLUTO (1.27e+22, 1.137e6); <<<< (...)
}Pluto is no longer a planet!
Bubble

I never quite understood the big mnemonic flap over the planets. There are only 9 of them. It's not like
there are 37 or something.
It brings to mind...
"scientists have discovered that even monkeys can memorize ten numbers. Are you stupider than a
monkey?" - Phoney McRingRing
Never heard that about a monkey. But, people like mnemonics, I guess. I don't know if I needed it to remember the planet names, but I did remember the mnemonic, anyway. Who really needs to know the planets' names, anyway? Not something I use every day, certainly. People make mnemonics for even shorter things (HOMES = Huron, Ontario, Michigan, Erie, Superior). "A Rat In The House May Eat The Ice Cream"--might as well just learn to spell the word--it is spelled just as it sounds.

Similar Messages

Deprecated Keyword?

It seems to me that the support for deprecation in the Java language could use a little help. As it stands, the compiler looks for the @deprecated JavaDoc tag to tell if a type, method, or field has been deprecated or not. If it is, it places a Deprecated attribute in the class file to indicate the deprecation. Does this seem a little weird to you? The compiler is taking information out of comments to create the class file! Shouldn't the comments be ingored completely by the compiler? I would suggest adding a "deprecated" keyword to the language as a modifier for types, methods, and fields. What do you guys think?

As for adding a keyword into the Java language, note
that deprecated is NOT a language feature, it is a
documentation feature.
Not sure that is the best way to express that. For example "@return" is a documentation feature. And 'deprecated', at least now is not part of the Java language. But it is certainly part of the JVM Spec, where other documentation features, like "@return" are not.
And that at least suggests that it is different than other documentation.
Deprecating a method in no way stops you from using it
however you should know that this method may not be
guaranteed to work in either this release or in future
releases of those classes.
Indeed, you can switch off deprecated warnings in your
compiler and be blissfully unaware of possible
problems.
Having the @deprecated attribute in JavaDoc is also a
polite reminder that you should document your code
properly, especially the API. Adding a keyword would
mean you not having that kind of incentive.All true, but could you explain how any of that is relevant to this post?

BEA WebLogic jDriver for Microsoft SQL Server

Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future product development direction.
Thank you for your attention regarding this matter.

Actually, this driver is already documented as deprecated. We intended to remove it from a future
release (most likely, the release after WLS 8.1).
The plan is to ship another driver out-of-the-box. We have been evaluating various drivers
for features, quality, and performance. We are pushing very hard to have this replacement
driver available in 8.1SP01, which will also ship with the WLI/Portal/WLW GA (announced to
ship in July). The most likely candidate is already in testing both at the WLS level and
with the layered products. It also did quite well in an internal performance comparison.
"Joseph Weinstein" <[email protected]_this> wrote in message news:[email protected]_this...
>
>
Peter Foskaris wrote:
Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though
BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future
product development direction.
>>
Thank you for your attention regarding this matter.Hi. We intend to deprecate it. We may or may not fix bugs that are found in it in future, and will likely
not do any more development on it, such as implementing any JDBC 2.0 methods. It will be in
our next major release (8), but may not be in future ones.
Joe Weinstein at BEA

[Solved]New Fontconfig (even with same config) Causes Odd Rendering

I'm on the Ubuntu-patched version, using these /etc/fonts/conf.d symlinks with no modification:
10-antialias.conf
10-sub-pixel-rgb.conf
10-unhinted.conf
11-lcd-filter-lcddefault.conf
30-metric-aliases.conf
30-urw-aliases.conf
31-cantarell.conf
44-wqy-microhei.conf
45-latin.conf
49-sansserif.conf
53-monospace-lcd-filter.conf
60-latin.conf
90-synthetic.conf
It should look like this in Chrome Dev:
After the upgrade to Fontconfig 2.10.1-3 I remade all the links from conf.avail as instructed so that the configs remain the same as above. However the font still looks very deformed:
What could've gone wrong?
Last edited by Vrantheo (2012-09-26 15:26:40)

My random meddling with 10-unhinted.conf turned out as a successful workaround:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>

<match target="font">

<edit name="hinting" mode="assign"><bool>false</bool></edit>
</match>
</fontconfig>
Just turning it back to "assign" works, but still it's documented as deprecated. I hope this would get fixed internally soon.

Custom MBean - Attribute Display Order & Documentation

Hi All,
I've implemented custom security providers for one of our customers. All Providers are working very well. However I've problems about displaying attributes of my MBeans in WLS console. Attributes of my custom mbean definitions are displayed in console in unsorted manner. They're not sorted as I put them in mbean definition file and as I know there is also no display order attribute specified in "commo.dtd". I also checked [MBean Definition|http://download.oracle.com/docs/cd/E15523_01/web.1111/e13718/mdf_ref.htm#i1035144] . Is there a way to specify display order of managed bean attributes that placed in mbean definition file ?
My second question is about generating description to display WLS console. I first tried to use "Description" attribute of MBeanAttribute element. It didn't worked. So I checked out out-of-the-box security providers to how they've done this before. I created "-doc.xml" files that uses "commodoc.dtd" schema and my attribute element's "Description" attributes as "See ...-doc.xml" in mbean definition file. It also didn't worked. I need to find a way to put my descriptions in WLS console . Any help would be appreciated.
I'm including sample mbean definition, mbean documentation definition and my mbean generation ant comments. By the way I'm trying all this by using WLS 10.3.2 environment with Sun JDK 1.6.0.18.
Thanks in advance.
ANT TASK
<java classname="weblogic.management.commo.WebLogicMBeanMaker" fork="true"
failonerror="true" >
 <jvmarg line=" -DdoCheckDescription=true -Dfiles=${build_dir} -DMDFDIR=${build_dir} -DMJF=${build_dir}/${myproviderjar} -DtargetNameSpace=${namespace} -DcreateStubs=true -Dverbose=true"/>
</java>
MBEAN DEFINITION
<?xml version="1.0" encoding="windows-1252" ?>
<!DOCTYPE MBeanType SYSTEM "commo.dtd">
<MBeanType Name="SpnegoCredentialMapper" DisplayName="SpnegoCredentialMapper"
 Package="com.dflora.security.wls.cm.spnego" Extends="weblogic.management.security.credentials.CredentialMapper"
 PersistPolicy="OnUpdate" Description="See SpnegoCredentialMapper-doc.xml.">
 
 <MBeanAttribute Name="ProviderClassName" Type="java.lang.String"
 Writeable="false"
 Preprocessor="weblogic.management.configuration.LegalHelper.checkClassName(value)"
 Default=""com.dflora.security.wls.cm.spnego.SpnegoCredentialMapperProviderImpl""
 Description="See SpnegoCredentialMapper-doc.xml." />
 <MBeanAttribute Name="Description" Type="java.lang.String"
 Writeable="false"
 Default="" DFlora's Identity Assertion Provider for Spnego Tokens ""
 Description="See SpnegoCredentialMapper-doc.xml." />
 <MBeanAttribute Name="Version" Type="java.lang.String"
 Writeable="false" Default=""1.0"" Description="See SpnegoCredentialMapper-doc.xml." />
 
 <MBeanAttribute Name="Debug" Type="boolean" Writeable="true"
 Default="false" Description="See SpnegoCredentialMapper-doc.xml." />
 <MBeanAttribute Name="ForwardTicket" Type="boolean"
 Writeable="true" Default="true" Description="See SpnegoCredentialMapper-doc.xml." />
</MBeanType>
MBEAN-DOC
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE MBeanType SYSTEM "commodoc.dtd">
<?xml-stylesheet alternate="yes" href="commodoc.css" type="text/css"?>
<MBeanType Name="SpnegoCredentialMapper"
Package="com.dflora.security.wls.cm.spnego">
<Description>
<Lead>
This MBean represents configuration information for the Spnego credential mapper.
</Lead>
<Detail>
Deprecation of MBeanHome and Type-Safe Interfaces
Additional description about mbean 
</Detail>
</Description>
<MBeanAttribute Name="Debug">
<Description>
<Lead>
Enables Disables Debug
</Lead>
<Detail>
Detailed description of debug attribute.
</Detail>
</Description>
</MBeanAttribute>
</MBeanType>

Yes the description attribute doesnt work anymore the way it used to work in prev versions.
On further research it was found that the Mbean required for generating description was missing.
A bug was filed with the engineering the engineering team. I am not sure what happend after that.
Let me try to find out.
If the mean while if any one of u guys have a support contract, you can go ahead and open a case with Oracle.
As for the order on display in the console, it shows in the order in which its defined in the MDF, m not sure why its behaving differently in your case.
-Faisal
http://www.weblogic-wonders.com/weblogic/

How do I find out if a class file has deprecated functions

Currently I'm having problems with a old Visual Cafe class.
It is definately using deprecated awt funcions.
My question is..
1) Without the source code how do I find out what deprecated functions the CLASS file is using.
2) Has any deprecated class been truly scrapped ? If so, I cannot find
it in the JDK API documentation or the java.sun.com search engine..

Here is what I did, to answer your question. I unzipped the symantec jar and used a decompiler (JAD works fine, or cavaj) to create an entire src tree (you can do this with 1 command). Then, compile using your target version of Java. There are well over 100 warnings (with -deprecation on) ranging from Cafe's use of awt.Component methods (mostly), Thread.suspend in their Timer class, to the use of java.util.Date in their Calendar component.
Cheers!

Where can I find a method to return the number of constants in an enum?

I'd like to get the number of constants in an enum, but can not find any documentation on the topic.
The only method I find reference to is the values() method.
Are there other methods?
Is there a method to return the number of items in the values array?
Thanks,
Norm

Encephalopathic wrote:
A_Sailor wrote:
I had a mental block there.In my field, we call this a "cerebral spasm".From what I know of your field, that's a strange place to keep your cerebrum ;-)

String deprecation

I have a warning when compiling a jdk1.1 file under j2sdk1.4
the String(byte[],int)has been deprecated and I didn't understand how to change the instruction using string constructors as it is said in the note in the documentation.
please tell me how.
thanks

If you look at the Documentation for String:
http://java.sun.com/j2se/1.4.1/docs/api/java/lang/String.html#constructor_summary
It says:
String(byte[] ascii, int hibyte)
Deprecated. This method does not properly convert bytes into characters. As of JDK 1.1, the preferred way to do this is via the String constructors that take a charset name or that use the platform's default charset.
And here is that constructor
String(byte[] bytes, String charsetName)
Constructs a new String by decoding the specified array of bytes using the specified charset.
You can start with this "ISO-8859-1" as charsetName, then look here is you want something different.
http://java.sun.com/j2se/1.3/docs/api/java/lang/package-summary.html#charenc

The Best Way to Assign an Enum to the Corresponds value of a String?

I am reading from and xml file configuration file. The data being returned is stored as a String and corresponds to a Enum value. My question is - What is the best way to assign the enum the value that corresponds to value of the string?
public enum Names { BOB, FRED, JIM, SAM }
String name = "FRED"; // This is the data retuned from the xml file.
Names n = // I want to assign n the value of Names.FREDI know I could do an "if" statement. However, this is a contrived example with only a few enum values. In the real world, this enum list could be quite large.
I have looked into reflection, but I don't know whether there is an easier way to achieve my objective?
Thank you for your time,
Harold Clements

dcminter wrote:
But for looking up "how do I do X with a subclass of type Y", I think the API documentation should be able to answer that.I think I disagree when it's a language feature.That's definitely a point worth observing.
By that reasoning you'd expect to populate the API docs with definitions for class (and this and super) all over the place.I think you're exaggerate, and you know it ;-)
If those were to be mentioned in the JavaDoc, they should obviously go into the documentation of java.lang.Object only.
I suppose you could have a "synthetics" section to the docs in much the same way that the inherited methods and fields are defined but it doesn't seem very useful.It's not useful if it's just clutter that's the same everywhere, of course.
But in this particular case a simple "note that enum classes have a syntetic valueOf() method that does foo bar baz" in the body of the class documentation would have been a nice guesture (especially since that part is pretty small here anyway).
And yes, I also think that the length field of arrays should find some mention in the JavaDoc. I don't know how and where, 'though.

Deprecated and obsolete parameters in 10gR2

From the oracle documentation, the following initialization parameters have been deprecated or obsoleted in this release. in some cases, oracle specifies what superceded the original parameter but in most cases not. does anyone know how to find out more about what was replaced and by what?
see the following:
Appendix A: Initialization Parameters Obsolete in 10g
ENQUEUE_RESOURCES
DBLINK_ENCRYPT_LOGIN
HASH_JOIN_ENABLED
LOG_PARALLELISM
MAX_ROLLBACK_SEGMENTS
MTS_CIRCUITS
MTS_DISPATCHERS
MTS_LISTENER_ADDRESS
MTS_MAX_DISPATCHERS
MTS_MAX_SERVERS
MTS_MULTIPLE_LISTENERS
MTS_SERVERS
MTS_SERVICE
MTS_SESSIONS
OPTIMIZER_MAX_PERMUTATIONS
ORACLE_TRACE_COLLECTION_NAME
ORACLE_TRACE_COLLECTION_PATH
ORACLE_TRACE_COLLECTION_SIZE
ORACLE_TRACE_ENABLE
ORACLE_TRACE_FACILITY_NAME
ORACLE_TRACE_FACILITY_PATH
PARTITION_VIEW_ENABLED
PLSQL_NATIVE_C_COMPILER
PLSQL_NATIVE_LINKER
PLSQL_NATIVE_MAKE_FILE_NAME
PLSQL_NATIVE_MAKE_UTILITY
ROW_LOCKING
SERIALIZABLE
TRANSACTION_AUDITING
UNDO_SUPPRESS_ERRORS
Appendix B: Initialization Parameters Deprecated in 10g
LOGMNR_MAX_PERSISTENT_SESSIONS
MAX_COMMIT_PROPAGATION_DELAY
REMOTE_ARCHIVE_ENABLE
SERIAL_REUSE
SQL_TRACE
BUFFER_POOL_KEEP (replaced by DB_KEEP_CACHE_SIZE)
BUFFER_POOL_RECYCLE (replaced by DB_RECYCLE_CACHE_SIZE)
GLOBAL_CONTEXT_POOL_SIZE
LOCK_NAME_SPACE
LOG_ARCHIVE_START
MAX_ENABLED_ROLES
PARALLEL_AUTOMATIC_TUNING
PLSQL_COMPILER_FLAGS (replaced by PLSQL_CODE_TYPE and PLSQL_DEBUG)
my boss is pushing for explanations and i have no idea how to find the information (i personally am of the school that says if during the database creation, you get warning messages, it's gone and you just accept it...maybe i have been working with oracle too long?)
Thanks for any assistance.

Hi,
Check for these parameters in Oracle9i documentation. There are some mentioning of new parameters to be used for the deprecated parameters. Ofcourse, not all are available.
HTH
Regards,
Badri.

Composite key field is not a simple type or enum

According to the docs here - http://www.oracle.com/technology/documentation/berkeley-db/je/java/index.html?com/sleepycat/persist/model/PrimaryKey.html - you can use "A composite key class containing one or more simple type or enum fields" as a key field. When we try that we get "java.lang.IllegalArgumentException: Composite key field is not a simple type or enum: Result$Key.recordId". Am I misreading the docs?
Thanks,
Trevor
@Persistent
public final class RecordKey {
@KeyField(1)
private final String name;
@KeyField(2)
private final int duplicateNumber;
RecordKey(final String name, final int duplicateNumber) {
this.name = name;
this.duplicateNumber = duplicateNumber;
RecordKey() {
this.name = null;
this.duplicateNumber = -1;
@Persistent
static final class Key {
@KeyField(1)
private final RecordKey recordId;
@KeyField(2)
private final String key;
Key(final RecordKey recordId, final String key) {
this.recordId = recordId;
this.key = key;
Key() {
this.recordId = null;
this.key = null;
}

Hi Trevor,
You're nesting one key class inside another. All fields of a key class must be simple types or enums, which is what the exception message is trying to say. If you want all those fields in your key class, you'll have to include them in a single flattened class.
Neither nesting of key classes nor inheritance of key classes is supported. We have enhancements filed to support these in the future, but no concrete plans.
--mark

Documentation and info for MusicPlayer API?

Is there documentation and info about the status of the MusicPlayer API from MusicPlayer.h in the AudioToolbox framework? Will this API be around for a long time or will it be deprecated?

Hi Pasquale,
The steps for installing a Metadata Repository into
a RAC database are in the Oracle Application Server
Metadata Repository Creation Assistant User's Guide.
Details on creating various high availability
environments that include a RAC database are in
the Oracle Application Server Installation Guide.
More details on managing these environments are
in the Oracle Application Server High Availability Guide.
Hope this helps,
Beth

Class, interface, or enum expected?

Ok I keep getting that error. Here is my java file that it is in.
package server.main.project12.skills;
import java.io.*;
import server.main.project12.*;
public class fireMaking {
public int xpgained = 1;//Change this and the fire xp will be times by that, so 40 time 1 = 40, 40
times 100 = 4000.
 public void WalkTo(int x, int y) {
 newWalkCmdSteps = (Math.abs((x+y)));
 if(newWalkCmdSteps % 1 != 0)
 newWalkCmdSteps /= 1;
 if(++newWalkCmdSteps > walkingQueueSize) {
 println("Warning: WalkTo("+packetType+") command contains too many steps
("+newWalkCmdSteps+").");
 newWalkCmdSteps = 0;
 int firstStepX = absX;
 int tmpFSX = firstStepX;
 firstStepX -= mapRegionX*8;
 for(i = 1; i < newWalkCmdSteps; i++) {
 newWalkCmdX[i] = x;
 newWalkCmdY[i] = y;
 tmpNWCX[i] = newWalkCmdX;
tmpNWCY[i] = newWalkCmdY[i];
newWalkCmdX[0] = newWalkCmdY[0] = tmpNWCX[0] = tmpNWCY[0] = 0;
int firstStepY = absY;
int tmpFSY = firstStepY;
firstStepY -= mapRegionY*8;
newWalkCmdIsRunning = ((inStream.readSignedByteC() == 1) && playerEnergy > 0);
for(i = 0; i < newWalkCmdSteps; i++) {
newWalkCmdX[i] += firstStepX;
newWalkCmdY[i] += firstStepY;
public int firetimer = 0;
public int firetimers = 0;
public int firetimers1 = 0;
public int firetimers2 = 0;
public int firetimers3 = 0;
public int firetimers4 = 0;
public int firetimers5 = 0;
public int firetimers6 = 0;
public int firetimers7 = 0;
public int firetimers8 = 0;
public int firetimers9 = 0;
public int firetimers10 = 0;
public int firetimers11 = 0;
public int firetimers12 = 0;
public int firetimers13 = 0;
public int firetimers14 = 0;
public int firetimers15 = 0;
public int firetimers16 = 0;
public int firetimers17 = 0;
public int firetimers18 = 0;
public int firetimers19 = 0;
public int previousX = 0;
public int previousY = 0;
public int previousX1 = 0;
public int previousY1 = 0;
public int previousX2 = 0;
public int previousY2 = 0;
public int previousX3 = 0;
public int previousY3 = 0;
public int previousX4 = 0;
public int previousY4 = 0;
public int previousX5 = 0;
public int previousY5 = 0;
public int previousX6 = 0;
public int previousY6 = 0;
public int previousX7 = 0;
public int previousY7 = 0;
public int previousX8 = 0;
public int previousY8 = 0;
public int previousX9 = 0;
public int previousY9 = 0;
public int previousX10 = 0;
public int previousY10 = 0;
public int previousX11 = 0;
public int previousY11 = 0;
public int previousX12 = 0;
public int previousY12 = 0;
public int previousX13 = 0;
public int previousY13 = 0;
public int previousX14 = 0;
public int previousY14 = 0;
public int previousX15 = 0;
public int previousY15 = 0;
public int previousX16 = 0;
public int previousY16 = 0;
public int previousX17 = 0;
public int previousY17 = 0;
public int previousX18 = 0;
public int previousY18 = 0;
public int previousX19 = 0;
public int previousY19 = 0;
public int logID = 0;
public boolean process() {
//FIRE MAKING TIMERS
if(firetimer > 0)
firetimer -= 1;
if(firetimers > 0)
firetimers -= 1;
if(firetimers1 > 0)
firetimers1 -= 1;
if(firetimers3 > 0)
firetimers3 -= 1;
if(firetimers2 > 0)
firetimers2 -= 1;
if(firetimers4 > 0)
firetimers4 -= 1;
if(firetimers5 > 0)
firetimers5 -= 1;
if(firetimers6 > 0)
firetimers6 -= 1;
if(firetimers7 > 0)
firetimers7 -= 1;
if(firetimers8 > 0)
firetimers8 -= 1;
if(firetimers9 > 0)
firetimers9 -= 1;
if(firetimers10 > 0)
firetimers10 -= 1;
if(firetimers11 > 0)
firetimers11 -= 1;
if(firetimers13 > 0)
firetimers13 -= 1;
if(firetimers12 > 0)
firetimers12 -= 1;
if(firetimers14 > 0)
firetimers14 -= 1;
if(firetimers15 > 0)
firetimers15 -= 1;
if(firetimers16 > 0)
firetimers16 -= 1;
if(firetimers17 > 0)
firetimers17 -= 1;
if(firetimers18 > 0)
firetimers18 -= 1;
if(firetimers19 > 0)
firetimers19 -= 1;
if(firetimers == 1)
ItemHandler.addItem(592, previousX, previousY, 1, playerId, false);
ReplaceObject2(previousX, previousY, 6951, 0, 10);
previousX = 0;
previousY = 0;
if(firetimers1 == 1)
ItemHandler.addItem(592, previousX1, previousY1, 1, playerId, false);
ReplaceObject2(previousX1, previousY1, 6951, 0, 10);
previousX1 = 0;
previousY1 = 0;
if(firetimers2 == 1)
ItemHandler.addItem(592, previousX2, previousY1, 1, playerId, false);
ReplaceObject2(previousX2, previousY2, 6951, 0, 10);
previousX2 = 0;
previousY2 = 0;
if(firetimers3 == 1)
ItemHandler.addItem(592, previousX3, previousY3, 1, playerId, false);
ReplaceObject2(previousX3, previousY3, 6951, 0, 10);
previousX3 = 0;
previousY3 = 0;
if(firetimers4 == 1)
ItemHandler.addItem(592, previousX4, previousY4, 1, playerId, false);
ReplaceObject2(previousX4, previousY4, 6951, 0, 10);
previousX4 = 0;
previousY4 = 0;
if(firetimers5 == 1)
ItemHandler.addItem(592, previousX5, previousY5, 1, playerId, false);
ReplaceObject2(previousX5, previousY5, 6951, 0, 10);
previousX5 = 0;
previousY5 = 0;
if(firetimers9 == 1)
ItemHandler.addItem(592, previousX9, previousY9, 1, playerId, false);
ReplaceObject2(previousX9, previousY9, 6951, 0, 10);
previousX9 = 0;
previousY9 = 0;
if(firetimers8 == 1)
ItemHandler.addItem(592, previousX8, previousY8, 1, playerId, false);
ReplaceObject2(previousX8, previousY8, 6951, 0, 10);
previousX8 = 0;
previousY8 = 0;
if(firetimers7 == 1)
ItemHandler.addItem(592, previousX7, previousY7, 1, playerId, false);
ReplaceObject2(previousX7, previousY7, 6951, 0, 10);
previousX7 = 0;
previousY7 = 0;
if(firetimers6 == 1)
ItemHandler.addItem(592, previousX6, previousY6, 1, playerId, false);
ReplaceObject2(previousX6, previousY6, 6951, 0, 10);
previousX6 = 0;
previousY6 = 0;
if(firetimers10== 1)
ItemHandler.addItem(592, previousX10, previousY10, 1, playerId, false);
ReplaceObject2(previousX10, previousY10, 6951, 0, 10);
previousX10 = 0;
previousY10 = 0;
if(firetimers11 == 1)
ItemHandler.addItem(592, previousX11, previousY11, 1, playerId, false);
ReplaceObject2(previousX11, previousY11, 6951, 0, 10);
previousX11 = 0;
previousY11 = 0;
if(firetimers12 == 1)
ItemHandler.addItem(592, previousX12, previousY12, 1, playerId, false);
ReplaceObject2(previousX12, previousY12, 6951, 0, 10);
previousX12 = 0;
previousY12 = 0;
if(firetimers13 == 1)
ItemHandler.addItem(592, previousX13, previousY13, 1, playerId, false);
ReplaceObject2(previousX13, previousY13, 6951, 0, 10);
previousX13 = 0;
previousY13 = 0;
if(firetimers14 == 1)
ItemHandler.addItem(592, previousX14, previousY14, 1, playerId, false);
ReplaceObject2(previousX14, previousY14, 6951, 0, 10);
previousX14 = 0;
previousY14 = 0;
if(firetimers15 == 1)
ItemHandler.addItem(592, previousX15, previousY15, 1, playerId, false);
ReplaceObject2(previousX15, previousY15, 6951, 0, 10);
previousX15 = 0;
previousY15 = 0;
if(firetimers19 == 1)
ItemHandler.addItem(592, previousX19, previousY19, 1, playerId, false);
ReplaceObject2(previousX19, previousY19, 6951, 0, 10);
previousX19 = 0;
previousY19 = 0;
if(firetimers18 == 1)
ItemHandler.addItem(592, previousX18, previousY18, 1, playerId, false);
ReplaceObject2(previousX18, previousY18, 6951, 0, 10);
previousX18 = 0;
previousY18 = 0;
if(firetimers17 == 1)
ItemHandler.addItem(592, previousX17, previousY17, 1, playerId, false);
ReplaceObject2(previousX17, previousY17, 6951, 0, 10);
previousX17 = 0;
previousY17 = 0;
if(firetimers16 == 1)
ItemHandler.addItem(592, previousX16, previousY16, 1, playerId, false);
ReplaceObject2(previousX16, previousY16, 6951, 0, 10);
previousX16 = 0;
previousY16 = 0;
if(firetimer == 1)
if(logID == 1)
addSkillXP((40*xpgained), 11);
removeGroundItem(absX, absY, 1511);
logID = 0;
if(logID == 2)
addSkillXP((60*xpgained), 11);
removeGroundItem(absX, absY, 1521);
logID = 0;
if(logID == 3)
addSkillXP((90*xpgained), 11);
removeGroundItem(absX, absY, 1519);
logID = 0;
if(logID == 4)
addSkillXP((135*xpgained), 11);
removeGroundItem(absX, absY, 1517);
logID = 0;
if(logID == 5)
addSkillXP((202*xpgained), 11);
removeGroundItem(absX, absY, 1515);
logID = 0;
if(logID == 6)
addSkillXP((303*xpgained), 11);
removeGroundItem(absX, absY, 1513);
logID = 0;
WalkTo(-1, 0);
sendMessage("The fire catches, and the logs begin to burn.");
Object(absX, absY, 2732, 0, 10);
firetimer = 0;
updateRequired = true;
appearanceUpdateRequired = true;
if(previousX == 0 && previousY == 0)
previousX = absX;
previousY = absY;
firetimers = 60; //DO NOT CHANGE THIS
viewTo(previousX, previousY);
else
if(previousX1 == 0 && previousY1 == 0)
previousX1 = absX;
previousY1 = absY;
firetimers1 = 60;
viewTo(previousX1, previousY1);
else
if(previousX2 == 0 && previousY2 == 0)
previousX2 = absX;
previousY2 = absY;
firetimers2 = 60;
viewTo(previousX2, previousY2);
else
if(previousX3 == 0 && previousY3 == 0)
previousX3 = absX;
previousY3 = absY;
firetimers3 = 60;
viewTo(previousX3, previousY3);
else
if(previousX4 == 0 && previousY4 == 0)
previousX4 = absX;
previousY4 = absY;
firetimers4 = 60;
viewTo(previousX4, previousY4);
else
if(previousX5 == 0 && previousY5 == 0)
previousX5 = absX;
previousY5 = absY;
firetimers5 = 60;
viewTo(previousX5, previousY5);
else
if(previousX6 == 0 && previousY6 == 0)
previousX6 = absX;
previousY6 = absY;
firetimers6 = 60;
viewTo(previousX6, previousY6);
else
if(previousX7 == 0 && previousY7 == 0)
previousX7 = absX;
previousY7 = absY;
firetimers7 = 60;
viewTo(previousX7, previousY7);
else
if(previousX8 == 0 && previousY8 == 0)
previousX8 = absX;
previousY8 = absY;
firetimers8 = 60;
viewTo(previousX8, previousY8);
else
if(previousX9 == 0 && previousY9 == 0)
previousX9 = absX;
previousY9 = absY;
firetimers9 = 60;
viewTo(previousX9, previousY9);
else
if(previousX10 == 0 && previousY10 == 0)
previousX10 = absX;
previousY10 = absY;
firetimers10 = 60;
viewTo(previousX10, previousY10);
else
if(previousX11 == 0 && previousY11 == 0)
previousX11 = absX;
previousY11 = absY;
firetimers11 = 60;
viewTo(previousX11, previousY11);
else
if(previousX12 == 0 && previousY12 == 0)
previousX12 = absX;
previousY12 = absY;
firetimers12 = 60;
viewTo(previousX12, previousY12);
else
if(previousX13 == 0 && previousY13 == 0)
previousX13 = absX;
previousY13 = absY;
firetimers13 = 60;
viewTo(previousX13, previousY13);
else
if(previousX14 == 0 && previousY14 == 0)
previousX14 = absX;
previousY14 = absY;
firetimers14 = 60;
viewTo(previousX14, previousY14);
else
if(previousX15 == 0 && previousY15 == 0)
previousX15 = absX;
previousY15 = absY;
firetimers15 = 60;
viewTo(previousX15, previousY15);
else
if(previousX16 == 0 && previousY16 == 0)
previousX16 = absX;
previousY16 = absY;
firetimers16 = 60;
viewTo(previousX16, previousY16);
else
if(previousX17 == 0 && previousY17 == 0)
previousX17 = absX;
previousY17 = absY;
firetimers17 = 60;
viewTo(previousX17, previousY17);
else
if(previousX18 == 0 && previousY18 == 0)
previousX18 = absX;
previousY18 = absY;
firetimers18 = 60;
viewTo(previousX18, previousY18);
else
if(previousX19 == 0 && previousY19 == 0)
previousX19 = absX;
previousY19 = absY;
firetimers19 = 60;
viewTo(previousX19, previousY19);
}And this is what my compiler is showing.C:\Users\Matthew\Documents\server.main.project12>javac *.java
Note: stream.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
C:\Users\Matthew\Documents\server.main.project12>javac ./skills/*.java
.\skills\firemaking.java:594: class, interface, or enum expected
^
1 error
C:\Users\Matthew\Documents\server.main.project12>pause
Press any key to continue . . .I really need help with this.

This error is often caused by improper matching of braces { }.
Solution: Check the matching opening and closing braces.
Worse, the error could be totally invisible! Often, it is the first thing in the file, before package or import declarations
In that situation, it could be caused by a code edited / formatted using a text editor not designed for programming such as Word, which introduces invisible characters in the code.
Solution : In that case, cut and paste the code in a true code editor as Eclipse or NotePad which withdrawing the offending characters.
This error occurs most often in the console (command line), almost never in an IDE.

Date contructor deprecation : Parsing a String to Date

Hi All,
In Java 1.5 the Date() constructor Date(String s) is deprecated. As per the API Documentation DateFormat.Parse() method is used.
The following code from Java 1.4 version has to be upgraded to Java 1.5.
Existing Code:
Date dDate = new Date(sDate);
Modified Code:
DateFormat df = DateFormat.getDateInstance();
Date dDate = df.parse(sDate);
Here the DateFormat accepts a default formatting style as "Feb 01, 2007" and parses the String.
If the String sDate belongs to any other formatting style such as "01 Feb, 2007" or "01 Feb, 07" the code piece throws unparsable date error.
Please give your thougts on this issue to parse the string of any format..
Thanks,
Rajesh.

Hi All,
In Java 1.5 the Date() constructor Date(String s) is
deprecated. As per the API Documentation
DateFormat.Parse() method is used.
The following code from Java 1.4 version has to be
upgraded to Java 1.5.
Existing Code:
Date dDate = new Date(sDate);
Modified Code:
DateFormat df = DateFormat.getDateInstance();
Date dDate = df.parse(sDate);
Here the DateFormat accepts a default formatting
style as "Feb 01, 2007" and parses the String.
If the String sDate belongs to any other formatting
style such as "01 Feb, 2007" or "01 Feb, 07" the code
piece throws unparsable date error.
Please give your thougts on this issue to parse the
string of any format..You can't. What date is this: "08/04/24"? 8 April, 1924? 4 August, 2024?
>
Thanks,
Rajesh.

Deprecated Message

Why when I use:
<jsp:forward page = "<%= FormatUtils.nvl(request.getParameter("servico"), "") %>">
<jsp:param name = "matricula" value = "<%= FormatUtils.nvl(request.getParameter("matricula"), "") %>" />
<jsp:param name = "senha" value = "<%= FormatUtils.nvl(request.getParameter("senha"), "") %>" />
<jsp:param name = "competencia" value = "<%= FormatUtils.nvl(request.getParameter("competencia"), "") %>" />
</jsp:forward>
I receive:
"Documentos.jsp": Warning #: 368 : method encode(java.lang.String) in class java.net.URLEncoder has been deprecated

"deprecated" means you're not supposed to use that function anymore. You probably upgraded to a more up-to-date version of Java, which has broken all of your old code.
Go to the Java API documentation websites, look up the function that's giving you problems. Make sure you're looking up the section for the version you're using. Most of the time, all they did was change the name of the method to something more "kool." Such as "enabled" vs. "isEnabled". "putValue" vs. "setAttribute". That kind of crap. Other times, they moved the functionality to a completely different object. "Date" vs. "Calendar". In any event, the documentation generally explains what the "new improved" way of accomplishing something has become.
Remember, Java people don't give a rats tail for backwards compatibility.

Enum documentation is deprecated

Similar Messages

Maybe you are looking for