created branch for a completely redesigned API
first commit of the brand new branch (so many things added...)
- written enough API to be able to run old JUnit tests
- SumoTraciConnection: renamed getXXByName() to getXXByID()
- added some essential javadoc
- Query didn't jave to hold DataIn/OutputStream references; its subclasses do
- removed some unused imports
- added support for reading links of a lane, and related JUnit test
- MultiQuery.sendRequestsAndDispatchResponses() renamed to a simpler run()
- ObjectCollectionQuery: javadoc a bit better
- removed "final"ness of the ObjectFactory used by the Repository to allow for lanes repositories to specify an object factory that points to the repository itself
- added an Utils class with some commodity methods
ObjectCollectionQuery now wants a Repository instead of an ObjectFactory, in order not to make duplicate TraCI objects. The same does RouteQuery
Using Repositories to give lanes and edges  (and other Traci objects in the future) to the outside world
some data checks moved in Utils
- primo aggiornamento alle newquery di TraCI4J
- alcuni warning rimossi
- Wiped old TraCI4J classes (i.p.a.traci only)
- Moved classes from i.p.a.traci.newquery to i.p.a.traci
- created a new CloseQuery
- Wiped old TraCI4J classes (i.p.a.traci.query)
- changed visibility of some classes, constructors and methods
- JUnit tests moved to i.p.a.traci.test
- SimValues renamed to SimulationData, and STC.getSimValues() to getSimulationData()
- renamed parameters of VehicleLifecycleObserver
BUG: forgot to read position data type identifier
piccolo refactoring per rendere piu' chiaro l'uso di ValueReadQuery
removed unneeded XML libraries and added HTTP tests
added Javadoc for TraciObject
- added support for color type (needs testing)
- added some Javadoc
added support for POIs and related JUnit tests. This revision may be used to know, in one place, all the points in the source to be "touched" in order to implement a new SUMO object class.
added a small piece of javadoc
- added induction loop object
- Repository now can accept variable sets, e.g. vehicles. A Repository of Vehicle is necessary to implement queries that return collections of vehicles, like InductionLoop.VEHICLES
- since Repository.Vehicles requires a corresponding StringListQ, we now instantiate one and use that also for determining which vehicle departed or arrived
removed warnings