Create an EJB Module.
Create a webservice and deploy it.
Create a BPEL Prj.
Create a BPEL Process.
D& D the newly created WebService to the Design area.
Edit the WebService by adding a new Parameter to the WebService Operation.
Redeploy the webservice
The BPEL process and WSDL that is imported is not insync with these changes.

yes its out of synch. But this is not a bug ... yet.
There is not automated refresh of the partner artifacts. I am re-assigning to
XML to ask what is the expectation re: detection of modified WSDL now on the
server. At one point there was suggestion that the retreiver would automatically
indicate the the rerieved artifacts were out of synch and ask you if you wanted
to re-retrieve them. I am not sure what the status is of that proposed feature.
XML team may indicate that it is out of scope.
Also, today, if you re-retrieved you would have to re-generate the
PartnerLinkType (or it would do the regen automatically). But the point is the
older retreived WSDL would be overwritten.
But, we are working on option in the PartnerLink editor that will let you
specify that you want the new PartnerLinkType defintions added to a wrapper WSDL
instead of the retrieved WSDL. Specifically, to avoid loss of information on a
re-retrieval. See bug 85417 for that case.

At this point there is not intention for automatic detection of a changed
artifact. In this scenario which I suspect would be common:
User 1 does the drag and drop of the web service to the BPEL process
and everything works fine (although the original address where the service came
from in the catalog which may have host specific information)
User 2 now is the one to add and deploy, so if there is host specific
information trying to access the original non stable URL would likely fail.
I think perhaps a better solution for this problem would be to enable
refactoring across worker service artifacts and having a standard project
reference system. In the case above, if the web service was created from WSDL
then the BPEL process would reference the original WSDL from the EE project.
This would allow refactoring (to support all open projects). The other case
where the web service is created from Java would require that the BPEL project
react to changes to a synthetic WSDL file.
I think the above solution is more feasible than attempting to do this from the
retriever as the user likely thinks of this as a composite application since
this is being developed together so refactoring and project system would handle
this. The retriever could also be used to work with stable URL checking, there
is an enhancement for an action, see issue #83879.
I think this is definately more of an enhancement than a bug and needs more
discussion on where this support should be.