What steps will reproduce the problem?
1. Create a port using the constructor.
2. Set port parameters using #setParams(...)
3. No option to access the port parameters on the resulting port instance.
What is the expected output? What do you see instead?
It is helpful to be able to access the port's parameters at a later point in
its lifetime.
What version of the product are you using? On what operating system?
1.9.1
Please provide any additional information below.
I added an implementation of an extended port as an attachment. It would be
good if the parameter access operations (and the toString()) could make it into
a later release.
The getXxx()-operations allow to access the ports parameters after the port was
created.
An additional constructor allows to create a port in one step with a number of
parameters.
#getParameterString() and #createPortFromParameters() allow to read all port
parameters in a single step and recreate it lateron. This is used in our
solution to save thge ports parameters into the Application preferences at
application end and reopen the port again, when the application is started.
Original issue reported on code.google.com by micha...@gmail.com on 3 Aug 2012 at 6:28
Original issue reported on code.google.com by
micha...@gmail.com
on 3 Aug 2012 at 6:28Attachments: