When creating a new LlrpClient, the class creates an IoHandler. The IoHandler's constructor parameters keepAliveAck and keepAliveForward always default to true, false.

It would be nice if we could somehow configure these values if needed.

Hi,
When I try to establish more than one simultaneous connection to my llrp server the NioHandler launches a NullPointerException with the next message:

Error while processing network channel
java.lang.NullPointerException
	at net.enilink.llrp4j.net.NioServer.run(NioServer.java:80)
	at java.lang.Thread.run(Thread.java:745)

With only one connection it works properly. Is your class 'LlrpServer' currently multithread?
This is my endpoint implementation:

LlrpEndpoint() {

	@Override
	public void errorOccured(String arg0, Throwable arg1) {
		System.err.println(arg0);
		System.err.println(arg1.getMessage());
		arg1.printStackTrace();
	}

	@Override
	public void messageReceived(LlrpMessage message) {
		String messageName = message.getClass().getSimpleName(); 
		Class<?> responseType = message.getResponseType();
		LlrpMessage response = handleMessage(message);
		if (response != null) {
			server.send(response);
		}
	}
};

Hi,

After tag's read when we try to send STOP_ROSPEC message, it is our first stopping message, the client.transact generates for us an java.lang.NullPointerException. We run our code inside raspberry, we hope that the reason could be memory problem? If any one have an response, it could be helpful.
Thank

Hi!

I'm trying to get the reader MAC address from reader configuration response, but with the method readerID(), the return value is unreadable format, I can someone know how to convert the Unsigned Bytes Array_Hex to int.

Thanks

Right now the NioClient only connects via unencrypted sockets. This would create a client that has support for TLS.

I work for Target and we're utilizing this project for our LLRP layer, but we have a requirement that it must be encrypted. I had planned to submit an implementation of this TLS connector if there was an appetite for it, but this project uses base Java NIO for its networking layer, and using SSL engine is notoriously difficult. One of the marketed pros of using this project is that it only has the single SLF4J dependency, but I wanted to ask before I started if it would be ok to add another small dependency for this project which has a great abstraction over SSLEngine.

Sorry for hijacking this issue as basically an email, but let me know your thoughts or if there's a better way to engage the owners on this.

The BitBuffer's limit and size methods should be called capacity and limit as in java.nio.ByteBuffer and their semantics should be aligned to each other.

When I try to open and decode an XML file containing an LLRP Message I always get an java.lang.NumberFormatException exception from the ctx.xmlDecoder().decodeMessage();

For example here is the beginning of the SET_READER_CONFIG message :

<?xml version="1.0" encoding="UTF-8"?>
<SET_READER_CONFIG xmlns="http://www.llrp.org/ltk/schema/core/encoding/xml/1.0" Version="1" MessageID="3">
  <ResetToFactoryDefault>0</ResetToFactoryDefault>
  <ReaderEventNotificationSpec>
    <EventNotificationState>
      <EventType>Upon_Hopping_To_Next_Channel</EventType>

And I got java.lang.NumberFormatException: For input string: "Upon_Hopping_To_Next_Channel"

But when I replace Upon_Hopping_To_Next_Channel by its value 1, it seems to work.

Maybe related to #1

Allow to create LlrpContext directly from XML definitions and allow to convert between binary and XML representations without mapping to Java objects.