Hi again :)
> 2.) Did you encounter any problems with log4j 1.5?
Sorry, I didn't explain very well the issue. It wasn't properly a problem,
only a clarification.
I wonder why in the README.TXT file is written to use log4j version 1.2.15 but
in build.xml file, in the "jarWithDep" rule, the version 1.2.14 is required
instead. Which version was used in ltkjava 1.0.0.6?
Anyway I used the 1.2.14 version and everything went fine but I wonder if I am
doing something wrong or if it's simply an error in README file (note that in
all cvs version of buld.xml file the loj4j version required is 1.2.14).
> 1.) could you give some more information on what the problem is? The
> exception should give you some information what caused the
> InvalidLLRPMEssageException, if you could also send the message sent (or the
> code snipped run), that would be very helpful
Sorry for not reporting the details last time.
Follows the exception stack and the code that caused that:
private synchronized boolean connettiAlReader(String ipReader,
int portReader) {
this.connector = new LLRPConnector(this,
ipReader, portReader);
try {
this.connector.connect();
<-exception!!!
return true;
} catch (LLRPConnectionAttemptFailedException
cafe) {
cafe.printStackTrace();
System.out.println("LLRPConnectionAttemptFailedException: "
+
cafe.getMessage());
return false;
}
}
org.llrp.ltk.exceptions.InvalidLLRPMessageException: LTK XML message can not be
validated against schema org/llrp/ltk/llrp-1x0.xsd<?xml version="1.0"
encoding="UTF-8"?>
<llrp:READER_EVENT_NOTIFICATION
xmlns:llrp="http://www.llrp.org/ltk/schema/core/encoding/xml/1.0"
xmlns:Impinj="http://developer.impinj.com/ltk/schema/encoding/xml/1.8"
Version="1" MessageID="1938794141">
<llrp:ReaderEventNotificationData>
<llrp:UTCTimestamp>
<llrp:Microseconds>2011-01-05T19:05:12.421289+01:00</llrp:Microseconds>
</llrp:UTCTimestamp>
<llrp:ConnectionAttemptEvent>
<llrp:Status>Success</llrp:Status>
</llrp:ConnectionAttemptEvent>
</llrp:ReaderEventNotificationData>
</llrp:READER_EVENT_NOTIFICATION>
because src-resolve.4.2: Error resolving component 'xs:Int'. It was detected
that 'xs:Int' is in namespace 'http://www.w3.org/2001/XMLSchema', but
components from this namespace are not referenceable from schema document
'null'. If this is the incorrect namespace, perhaps the prefix of 'xs:Int'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to 'null'.
at
org.llrp.ltk.types.LLRPMessage.isValidXMLMessage(LLRPMessage.java:392)
at
org.llrp.ltk.generated.messages.READER_EVENT_NOTIFICATION.encodeXML(READER_EVENT_NOTIFICATION.java:162)
at
org.llrp.ltk.types.LLRPMessage.toXMLString(LLRPMessage.java:418)
at
org.llrp.ltk.net.LLRPIoHandlerAdapterImpl.messageReceived(LLRPIoHandlerAdapterImpl.java:83)
at
org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:570)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648)
at
org.apache.mina.filter.codec.support.SimpleProtocolDecoderOutput.flush(SimpleProtocolDecoderOutput.java:58)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:180)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648)
at
org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:220)
at
org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:264)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
Source)
at
org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51)
at java.lang.Thread.run(Unknown Source)
Caused by: org.xml.sax.SAXParseException: src-resolve.4.2: Error resolving
component 'xs:Int'. It was detected that 'xs:Int' is in namespace
'http://www.w3.org/2001/XMLSchema', but components from this namespace are not
referenceable from schema document 'null'. If this is the incorrect namespace,
perhaps the prefix of 'xs:Int' needs to be changed. If this is the correct
namespace, then an appropriate 'import' tag should be added to 'null'.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDSimpleTypeTraverser.findDTValidator(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDSimpleTypeTraverser.getSimpleType(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDSimpleTypeTraverser.traverseSimpleTypeDecl(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDSimpleTypeTraverser.traverseGlobal(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseSchemas(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(Unknown
Source)
at
com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newSchema(Unknown
Source)
at javax.xml.validation.SchemaFactory.newSchema(Unknown Source)
at
org.llrp.ltk.types.LLRPMessage.isValidXMLMessage(LLRPMessage.java:375)
Replacing llrp-1x0.xsd version 1.8 with version 1.7 and llrp-1x0-def.xml
version 1.12 with version 1.11 fix the problem.
Luca
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel