ohla-user — OHLA user list. Used to discuss user issues with OHLA.

[ohla-user] OHLA 0.6.0 released

[Michael N. <mic...@gm...>]

Lots of updates and bug fixes in this release.
- Completed Time Management implementation
- Completed Save/Restore implementation
- Updated 3rd party libraries
- Added example Circles JavaFX application that has HLA 1.3, IEEE 1516, and
IEEE 1516e federates

Thanks,
Michael

[ohla-user] newer With ohla

[Virginia P. S. <vir...@gm...>]

i'm newer in ohla. there is any guide to implement a web service using  
ieee-513e?
Thanks in advance
Virginia

[ohla-user] OHLA 0.5.0 Released

[Michael N. <mic...@gm...>]

Lots of updates in this release.

- Added IEEE 1516 Evolved API support. HLA 1.3, IEEE 1516, and IEEE 1516
Evolved are all interoperable with each other.
- Migrated to Netty from MINA.
- Implemented custom encoding for performance increases.
- Implemented Data Distribution Management.
- Completed Ownership Management
- Added Internationalization support

I have yet to thoroughly test Time Management, but I will be working on that
for a 0.5.1 release.

I will also be working on a set of performance tests to put OHLA up against
some of the other RTIs out there.

Feel free to download and check it out:
https://sourceforge.net/projects/ohla/files/ohla

Thanks,
Michael

[ohla-user] hello users

[Artis <art...@gm...>]

is there any activity in this mailing list?

[ohla-user] OHLA in SVN

[Newcomb, Michael-P. <Mic...@gd...>]

OHLA is now checked into SVN.

SVN structure:

trunk/
 - holds main development branch
 - currently at 0.4

svn co http://ohla.svn.sourceforge.net/svnroot/ohla/trunk ohla-0.4

branches/
 - holds branches that have been released
 - when trunk is nearing release, the branch is copied to here
 - currently holds 0.3 branch

svn co http://ohla.svn.sourceforge.net/svnroot/ohla/branches/0.3
ohla-0.3.1

releases/
 - holds released versions
 - no development is allowed on these
 - when a branch is ready to be released, it is copied to here
 - currently holds 0.3.0

svn co http://ohla.svn.sourceforge.net/svnroot/ohla/releases/0.3.0
ohla-0.3.0

Changes to the repository are sent to the ohla-devel mailing list.

Thanks,
Michael

[ohla-user] OHLA 0.3 released

[Newcomb, Michael-P. <Mic...@gd...>]

OHLA 0.3 has been released.=20

This is a major refactoring of the project with a focus on moving the
infrastructure to MINA.=20

Ownership Management support has also been added. There are still a few
peices to implement, for instance, when ownership is divested the RTI
does not ask federates to assume ownership, they will remain unowned
until a federate requests ownership. This will be added in 0.3.1.=20

Initial JLC support is included, and current test cases have been
implemented using the RtiFactory classes, but no test cases have been
written yet for the encoding/decoding classes.

Thank you for your patience and hopefully future releases will be soon
to follow.=20

Thanks,=20
Michael=20

[ohla-user] OHLA Status and Roadmap

[Newcomb, Michael-P. <Mic...@gd...>]

It has been a while since I last sent out an update on the development
progress, so here is an update ;).

0.3 is very close to release (within the week). The focus of 0.3 was
moving away from the RMI/socket API that I had developed to a more
robust framework. I started working with Jgroups but it did not fit my
strategy of send-side filtering. So, I found a gem of a project from
Apache called MINA.

>From MINA's website
(http://directory.apache.org/subprojects/mina/index.html):

MINA (Multipurpose Infrastructure for Network Applications) is a network
application framework which helps users develop high performance and
high scalability network applications easily.

I'm not going to go over MINA's architecture in this e-mail but I
encourage you to read up on this project.

I have also been implementing the concurrency strategy that will allow
multiple threads to utilize one FederateAmbassador in a truly concurrent
manner. Therefore, you will see heavy use of the java.util.concurrent
package (particularly ReadWriteLock).

I've laid the foundation for most of the services and as of right now,
I'm almost done with the Ownership Management test case (just have to
test requesting divestiture). When that test case is complete, I will
release 0.3.

Below is the roadmap for OHLA releases. Hopefully one will come every
3-4 weeks or so.

0.3
 - re-architect to use Apache MINA
 - ownerhsip management

0.4
 - time management
 - JLC

0.5
 - DDM

0.6
 - MOM support

0.7
 - C++ API

0.8
 - optimize message encoding/decoding

0.9
 - maintenance

1.0
 - final


Thanks,
Michael

[ohla-user] OHLA 0.2.2 released

[Newcomb, Michael-P. <Mic...@gd...>]

0.2.2 has been released. You can download it here
http://sourceforge.net/project/showfiles.php?group_id=3D134950
=20
This release contains a bug fix that fired multiple discover objects
instance calls.

Thanks,
Michael

[ohla-user] OHLA 0.2.1 released

[Newcomb, Michael-P. <Mic...@gd...>]

0.2.1 has been released. You can download it here
http://sourceforge.net/project/showfiles.php?group_id=3D134950
=20
This release contains a bug fix that prevented late joining federates
from discovering already registered object instances.

0.3 is nearing completion and should include DDM, time management, and
hopefully the first cut of the toolkit which allows for easier use of
HLA.

Thanks,
Michael

[ohla-user] OHLA 0.2 released

[Newcomb, Michael-P. <Mic...@gd...>]

This release includes initial HLA 1.3 support. IEEE 1516 and HLA 1.3
clients can communicate on the same federation.

Testsuite was moved from JUnit to TestNG.

Some refactoring was done to enable HLA 1.3 support.

Thanks,
Michael

[Ohla-user] hello, world!

[Dillman, B. <Bra...@dr...>]

My name is Brad Dillman, I work for Defence Research & Development
Canada Atlantic.

=20

I'm working on time management for OpenHLA in my spare time (what there
is), check out the development mailing list. I've spent some time
learning how time management algorithms work when used on WANs (with
latency of 10's or 100's of milliseconds).

=20

We develop simulations for the Canadian Forces, mostly RPR2-D17 and VMSA
FOMs, all written in Java (and Groovy). Our simulations usually focus on
navy or air platforms and scenarios.

=20

However, most of our colleagues use C++, though a few use Java.

=20

Thanks,

Brad Dillman, DRDC Atlantic