[JBWS-2174] Cannot Obtain Destination for Request

[ropalka]

Hi Folks,

I'd like to brainstorm with you on http://jira.jboss.org/jira/browse/JBWS-2174.
First of all I'll describe the problem. We're using web context parameter to specify the CXF specific deployment descriptor extension location. However I discovered this parameter isn't propagated for EJB3 endpoints, because for those endpoint we're generating the web.xml (AS 5 Beta 4) or we're generating JBossWebMetaData in memory (for AS 5 trunk).
I was able to fix this issue for AS 5 trunk, see: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossws/stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/DescriptorDeploymentAspect.java/?revision=7181&r1=7181&r2=7180.
I don't like this fix very much.

So my first question is, do you have some ideas how to do it better?

The second problem I have is described in JBWS-2174 comments. I'm not able to think out the solution for AS 5 Beta 4 for generated web.xml.

So the second question I'm asking do you have an idea or trick how to achieve that?

[thomas.diesler]

You fix is fundamentally wrong, because it creates a dependency on the container.

WS stack integration must stay clear of container details.

Container integration must stay clear of stack details.

If the problem only pertains to AS50Beta4, we can resolve it as "Won't fix"

With the old build system your fix should not even have compiled. I'm looking into how this can be enforced in maven.

[ropalka]

You fix is fundamentally wrong, because it creates a dependency on the container.

How to do it right? Give me an idea and I'll do it. As I said before I don't like my current fix.

[thomas.diesler]

It is not so much about "like" and "don't like". Your change results in a stack specific deployment aspect that is not usable in any but one specific container.

Do you understand the fundamentals behind SPI, container/stack integration?

The build should enforce these principals to prevent these types of mistakes. If it does not, it is actually my mistake.

To give you the correct solution I would have to look into that in more detail. It may indicate a problem with the EJB3 integration layer. Maybe Heiko can give a short answer.

[ropalka]

In short the problem is the context parameter pointing to CXF specific DD isn't propagated to servlet for EJB3 endpoints.