Sharon Cleary

Hi all,

A quick question.
I am getting a number of warnings while building with JDK 1.5 pe code snippet below

cast to java.lang.Object for a varargs call
cast to java.lang.Object[] for a non-varargs call and to suppress this warning
return MessageFormat.format(message, new String[] {argument});

I did attempt changing this new String to new Object however this breaks my code.

Is is safe to leave these warnings in there or should I be doing something after changing it to new Object[]?

Thanks,
S

Its set in the java code.
When I remove the c:set bit of code and try to reference it directly it works? Is there something wrong with the set code as I need to use this functionality...

Hi,

Im getting the following error on a jsp page

An error occurred while evaluating custom action attribute "value" with value "${timing}": Attempt to convert String "${set.timing}" to type "java.util.Date", but there is no PropertyEditor for that type (null)
at org.apache.taglibs.standard.lang.jstl.Evaluator.evaluate

The variable timing is set using a c:set tag at the top of the page
<c:set var="timing" value="${set.timing}"/>

this is followed on by

<fmt:formatDate value="${timing}" pattern="MM/dd/yyyy',' h:mm a z"/>

This code previously worked so I have no idea whats after happening to it.
Any one have ideas as I'm really struggling with this.

Thanks

Hi,

The HTML source for that line is

<td>�0.00</td>

It would seem that that Safari has issues with JSTL tags. This be possible?

Hi,

I understand that the encoding is XML related. However what i am not clear on is why my new environment (WwebSphere 6.1 & JDK1.5) decided to raise this as an error when previously the exact same request passed. The request itself contains HTML so this is obviously the reaqson why it is now failing. I would just like to understand what has caused things to become more strict if that makes sense?
In the meantime I changed the encoding on the XML request to ISO 8859-1. Im not sure if this was the coorect thing to do from an XML point of view. Should I perhaps just written code to remove the non UTF-8 chars?

Thanks

Hi,

We are using the JSTL formatNumber tag to display the value that is set in our business object.

<fmt:formatNumber value="${number}" type="currency"/>

If you need more info let me know.

Thanks

Hi,

Has anyone come across any issues displaying dollar signs in Safari on the Mac. Firefox and IE show the $ but Safari is displaying an * symbol which is baffling me. Any help would be greatly appreciated.

Thanks

Hi all,

I recently moved to 6.1 from 5.1 and a previously working soap request is now failing

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>java.io.UTFDataFormatException: Invalid UTF8 encoding.</faultstring>
<detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>


I changed the encoding on my request to ISO-8859-1 and it now works in WAS 6.1.

So my question is does anyone why that is? Obviously its become more strict but I havent been able to locate any documentation on it. I am not even sure if I selected a good encoding method now. If anyone has any better suggestions then let me know. The request Im sending is basically a html page in CDATA tags.

Thanks a lot