[ JDK VERSION : 1.6.0_02 ]

allowing a web project to have a web service reference to a web
service exposed by a composite application is a problem.

I have a bpel project, the encasing composite app, and a
straight-forward web project that needs a web service reference to a
web service that's exposed by the composite app.

If I try to create the web service client in the web project, I don't
get to see the composite app as an option in the dialog box, so
that's not an option.

The option to make a reference to the wsdl file directly exists, and,
if I use that, everything works just fine, until I try opening the
same set of projects on a solaris platform (the initial set of
projects was created on a windows box).

The project has an absolute path reference to the wsdl from the
composite app, which is not good.

Also, I suspect that if I were, on the windows box, to move the
composite app to another location (as often happens in
multi-developer, shared source versioning scenarios, as I have here),
the reference would be broken also.

it seems like if relative paths were always used, then this would
alleviate the problem to a great degree, for both the multi-platform
and same-platform but different location scenarios.

if there are scenarios where this is not deemed the ideal, then at
least the person creating the reference should be given the option of
indicating that it should be relative instead of absolute.