[jboss-dev-forums] [Design of JBoss Web Services] - Re: JBWS-1858 + JBWS-1797: when to generate wsdl?

OK, back to this issue after the vacation... "heiko.braun(a)jboss.com" wrote : IMO any container (or deployment) dependent meta data should be processed and massaged into the SPI artifacts before transitioning into the actual stack. So I'd say what you suggest makes perfect sense. Process those bits earlier and find a good representation in the SPI artifacts. I didn't look at it myself, but the stack shouldnt deal with container meta data directly at all: | I agree with you Heiko. Unfortunately after checking the code, I think the most proper place to read those bits is in the ContainerMetaDataDeploymentAspect that is part of the 4.0 & 4.2 AS code base; this of course could also be performed in another aspect (even an existing one, for example in the UnifiedMetaDataDeploymentAspect, before actually building the MD), but I don't like the idea of parsing the web.xml there... even if I tried it and of course it fixes JBWS-1797 with AS 4.2 ( I save the config name/file in 2 properties using the org.jboss.wsf.spi.deployment.Deployment then read them in the JAXWSServerMetaDataBuilder in case the same info is not available through the JSEArchiveMetaData) How should we proceed in this case? We can't change the AS4.2 code now, right? Please also consider that we could of course forget about JBWS-1797 with AS4.2 (as a matter of fact it is marked as resolved), but in that case I think JBWS-1858 should be marked as won't fix since generating the wsdl later is useless at least as far as the only reason for doing so is related to the endpoint config. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116752#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...