When a DynamoDbBean class use primitive types as setter's parameter, it will not be called.

[mikeyan123]

Describe the bug

As say, I have a order class:
@DynamoDbBean
public class Order {
private Long id;
private Integer amount;

public Order() {
}

public Order(long l, int i) {
	this.id = l;
	this.amount = i;
}

@DynamoDbPartitionKey
public Long getId() {
	return id;
}

public void setId(Long id) {
	this.id = id;
}

public Integer getAmount() {
	return amount;
}

public void setAmount(int amount) {
	this.amount = amount;
}

}
In this class, I use int other than Integer as the parameter of setAmount, strangely, when I try to retrieve the order I put before , the value of amount is null.

class OrderRepositoryTest {

@Autowired
DynamoDbEnhancedClient enhancedClient;

@Test
void findById() {
	DynamoDbTable<Order>  table = enhancedClient.table("order", TableSchema.fromBean(Order.class));
	try {
		table.createTable();
	}
	catch (Exception e){System.out.println(e.getMessage());}
	table.putItem(new Order(1L, 10));
	var order = table.getItem(Key.builder().partitionValue(1L).build());
	assertThat(order.getAmount()).isEqualTo(10);
}

}

Is that a bug?

Expected Behavior

I think even use primitive type as the parameter, it should work, or throw an exception.

Current Behavior

It don't call the setAmount method.

Reproduction Steps

See the code.

Possible Solution

I think even use primitive type as the parameter, it should work, or throw an exception.

Additional Information/Context

No response

AWS Java SDK version used

2.17.201

JDK version used

18

Operating System and version

macOS Monterey 12.4

[monika-sivamoorthy]

Can I work on this bug?

[debora-ito]

@mikeyan123 apologies for the delay.

Our recommendation is to use non-primitive Java data types only.
Could not find this recommendation in the DynamoDB Enhanced Client documentation, so I'm marking this as a task to improve our docs.

[debora-ito]

This is now addressed in the "Learn the basics of the DynamoDB Enhanced Client API" documentation:

The attribute types (properties) of your Java data classes should be objects types, not primitives. For example, always use Long and Integer object data types, not long and int primitives.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.