-
1. Re: [JBWS-2174] Cannot Obtain Destination for Request
thomas.diesler May 29, 2008 3:33 AM (in response to ropalka)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. -
2. Re: [JBWS-2174] Cannot Obtain Destination for Request
ropalka May 29, 2008 3:39 AM (in response to ropalka)"thomas.diesler@jboss.com" wrote:
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. -
3. Re: [JBWS-2174] Cannot Obtain Destination for Request
thomas.diesler May 29, 2008 4:03 AM (in response to ropalka)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. -
4. Re: [JBWS-2174] Cannot Obtain Destination for Request
ropalka May 29, 2008 8:38 AM (in response to ropalka)In short the problem is the context parameter pointing to CXF specific DD isn't propagated to servlet for EJB3 endpoints.