Kiran,

Yes, we knew about these limitations or bugs..  There are several issues that 
are not addressed in the initial version of CASA but will be addressed in FCS 
post J1. In general, these are issues/limitation of the current CASA related 
to editing of wsdl elements:

1. The user should not be allowed to edit any artifact from a component SU, 
e.g., elements/attributes of a wsdl file in a bpel project.  Currently, we 
could not force them to read-only without adding new api to the wsdl editor. 
It will be addressed post J1.

2. Only elements/attributes defined or auto-generated by CompApp/CASA can be 
edit in the CASA editor.

-- 
Tientien Li

Kiran Bhumana wrote:
>
> Ok, I think i may have found the bug. The bug here (atleast in my case is 
CASA editor). I am using CASA editor to connect to a file BC. And when the 
file BC's binding section is generated by the CASA editor it seems to not read 
the potential/possible binding sections from the existing WSDLs. It creates 
new WSDLs with generated binding sections. And these new binding sections 
ignore the user defined binding properties. In my case the file name, file 
append attributes.
> file name seems to always be hard coded to "test.xml" and only one other 
attribute "polling" is added.
>
> Maybe this is a known issue to the CASA editor folks.