Rakesh,
Again, sorry you are running into “irregularities” with FIXatdl v1.1 and atdl4j.
I put together a little example file and I could replicate some unexpected behavior with xsi:type=“lay:TextField_t” and “listeners” associated with state rules around that. I couldn’t initialize a text field as enabled=false and that seemed to be an omission in the FIXatdl spec for “lay:TextField_t”. Greg may have had a reason for this?
I too have had trouble posting any meaningful code on this BBS. Have asked for help. FAQ was not available to me.
I may have a work around by using two state rules.
Try out text.xml at: http://clbcm.com/x/
#1 - your example, works as expected
#2 - some oddness noted, for sure (likely related to listeners)
#3 - a possible work around using two state rules
I tried to make the example file complete with ref to the schema so I can look up the components when writing code (using an old version of XMLspy) and to do “hard” validations before turning attention to atdl4j testing.
Unfortunately I’m backed up on other projects so it may be a while if I need to get back to this. I have seen a few issues with atdl4j before but most of the time it was “expecting” things that were optional or not putting widgets on the screen so everything fit and played nicely.
Rick
