[JBoss JIRA] Created: (JBXB-79) Array parameter is being appended rather than passed intact
by David Boeren (JIRA)
Array parameter is being appended rather than passed intact
-----------------------------------------------------------
Key: JBXB-79
URL: http://jira.jboss.com/jira/browse/JBXB-79
Project: JBoss XML Binding (JBossXB)
Issue Type: Bug
Reporter: David Boeren
When I call a webservice method and pass an object containing an array of another object type, the server receives the array with additional elements. The array elements that I pass are appended, so that if I send 1 element the server receives 81. If I send 80 elements, the server receives 160. There are always 80 element preceding the first one that I pass.
The value 80 comes from code in the object constructor that preinitializes the array to this size.
This form causes the bug:
public class Coils implements Serializable{
private int numberOfCoils;
private CoilData[] array = new CoilData[80];
}
This form likewise causes the bug:
public class Coils implements Serializable{
private int numberOfCoils;
private CoilData[] array;
public Coils() {
array = new CoilData[80];
}
}
This form does not cause the bug:
public class Coils implements Serializable{
private int numberOfCoils;
private CoilData[] array;
public Coils() {
}
}
Coils coils = new Coils();
coils.setArray(new CoilData[80]);
So, it has something to do with initializing it in the construction of the object.
Attached is a full Eclipse project exhibiting the bug that you can run on JBoss 4.0.4.GA with JBossWS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Created: (JBAS-3484) non portable JDK dependant clasess (sun.**)
by Andrew Oliver (JIRA)
non portable JDK dependant clasess (sun.**)
-------------------------------------------
Key: JBAS-3484
URL: http://jira.jboss.com/jira/browse/JBAS-3484
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMS service, Security
Affects Versions: JBossAS-4.0.4.GA, JBossAS-5.0.0.CR1
Reporter: Andrew Oliver
Assigned To: Adrian Brock
We should not be using sun.** classes in tests or in code. they are naughty and break working on non Sun JDKs.
[andy@localhost jboss-4.0.x]$ find . -name "*.java" -exec grep -i "sun.misc.BASE64Encoder" '{}' ';'
sun.misc.BASE64Encoder encoder = new sun.misc.BASE64Encoder();
[andy@localhost jboss-4.0.x]$ find . -name "*.java" -exec grep -Hi "sun.misc.BASE64Encoder" '{}' ';'
./security/src/main/org/jboss/test/UtilTestCase.java: sun.misc.BASE64Encoder encoder = new sun.misc.BASE64Encoder();
[andy@localhost jboss-4.0.x]$ find . -name "*.java" -exec grep -Hi "sun.misc" '{}' ';'
./security/src/main/org/jboss/test/UtilTestCase.java: /** Compare Util.encodeBase64 against the sun misc class
./security/src/main/org/jboss/test/UtilTestCase.java: sun.misc.BASE64Encoder encoder = new sun.misc.BASE64Encoder();
./jaxrpc/src/main/org/jboss/axis/utils/Base64.java: * Eliminates dependency on sun.misc.Base64Encoding,
./jaxrpc/src/main/org/jboss/axis/utils/Base64.java: * (it's an access exception to load sun.misc.* classes
[andy@localhost jboss-4.0.x]$ find . -name "*.java" -exec grep -Hi "sun.io" '{}' ';'
./messaging/src/main/org/jboss/mq/xml/XElement.java: sun.io.CharToByteUTF8 conv = new sun.io.CharToByteUTF8();
./messaging/src/main/org/jboss/mq/xml/XElement.java: } catch ( sun.io.MalformedInputException e ) {
[andy@localhost jboss-4.0.x]$
Moreover the
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Created: (JBXB-76) optimize unmarshalling of arrays of repeatable particles
by Alexey Loubyansky (JIRA)
optimize unmarshalling of arrays of repeatable particles
--------------------------------------------------------
Key: JBXB-76
URL: http://jira.jboss.com/jira/browse/JBXB-76
Project: JBoss XML Binding (JBossXB)
Issue Type: Feature Request
Affects Versions: JBossXB-1.0.0.CR6
Reporter: Alexey Loubyansky
Assigned To: Alexey Loubyansky
Fix For: JBossXB-1.0
When an repeatable XSD term (element, model group or wildcard) is bound to a field of an array type, the current implementation acts inefficient.
Each time the term is unmarshalled, the array which is the value of the field is recreated to add the just unmarshalled particle. Instead, repeatable terms should be recognized, the array items should be collected in a temp collection and the final array should be created when the last repeated term is unmarshalled.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Created: (JBTM-116) setting of default timeout logic broken in mbean
by Mark Little (JIRA)
setting of default timeout logic broken in mbean
------------------------------------------------
Key: JBTM-116
URL: http://jira.jboss.com/jira/browse/JBTM-116
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.1
Reporter: Mark Little
Assigned To: Mark Little
Fix For: 4.2.2
The mbean code for setting the default timeout says:
public void setTransactionTimeout(int timeout) throws javax.transaction.SystemException
{
if (timeout > 0)
{
TxControl.setDefaultTimeout(timeout);
}
else
throw new javax.transaction.SystemException("Transaction Timeout < 0");
}
This means that it's not possible for anyone to provide a value of -1, which means: transactions never timeout. Also, the if clause should say >= 0 if the else clause is to be accurate.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Created: (JBAS-3386) Expose "in process" messages via JMX
by Adrian Brock (JIRA)
Expose "in process" messages via JMX
------------------------------------
Key: JBAS-3386
URL: http://jira.jboss.com/jira/browse/JBAS-3386
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: JMS service
Reporter: Adrian Brock
Expose the number of "in process" (i.e. unacknowledged messages given to the client)
via the JMX interfaces.
e.g. change
org.jboss.mq.server.jmx.Queue to have
public int getInProcessCount()
{
return jmsQueue.getInProcessCount();
}
org.jboss.mq.server.JMSQueue to have
public int getInProcessCount()
{
return basicQueue.getInProcessCount();
}
org.jboss.mq.server.BasicQueue to have
public int getInProcessCount()
{
return unacknowledgeMessages.size();
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Created: (JBPM-716) make the timer duedate optional
by Tom Baeyens (JIRA)
make the timer duedate optional
-------------------------------
Key: JBPM-716
URL: http://jira.jboss.com/jira/browse/JBPM-716
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Priority: Minor
Fix For: jBPM 3.1.3, jBPM 3.2 alpha 1
now, it's not possible to have a timer without a dueDate. if we add a nullpointercheck, users can associate an action with the timer that fills in the dueDate programmatically.
in org.jbpm.scheduler.def.CreateTimerAction a nullpointercheck should be added to the following two lines in the createTimer method :
Duration duration = new Duration(dueDate);
Date dueDate = businessCalendar.add( new Date(), duration );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months