[jbossws-dev] Re: [jboss-dev] metadata not attached to DeploymentUnit

[Thomas Diesler]

I modified JBossWebAppParsingDeployer to always attach a
JBossWebMetaData object.

http://fisheye.jboss.com/changelog/JBossAS/?cs=66108


This workaround only applies to web meta data and does not address the
general problem of the jboss specific meta data not being attached to
the DeploymentUnit if there is no jboss DD. Please review and modify if
needed.

cheers
-thomas


On Fri, 2007-10-12 at 08:01 -0700, Scott M Stark wrote:
> There should always be a JBossWebMetaData object. Just need to look at
> making the WebMetaData as optional input to the JBossWebParsingDeployer.
> 
> Thomas Diesler wrote:
> > Yes, JBossWebMetaData always used to be there. Now I only have
> > WebMetaData attached if there is no jboss-web.xml.
> > 
> > On Fri, 2007-10-12 at 15:32 +0200, Carlo de Wolf wrote:
> >> This might be because the JBossWebMetaData isn't specified as an
> >> optional input for that deployer. Which deployer are you talking about?
> >>
> >> Carlo
> >>
> >> On Fri, 2007-10-12 at 14:41 +0200, Thomas Diesler wrote:
> >>> Hi Scott,
> >>>
> >>> we used to be able to detect a webapp deployment like this. Later, we
> >>> inspect the meta data for WS relevant servlet classes.
> >>>
> >>> After the recent change to the new metadata model, the attachment is
> >>> missing. Is this work in progress (i.e. will the attachment be there
> >>> again) or should we do things differently?
> >>>
> >>>    public boolean isWebServiceDeployment(DeploymentUnit unit)
> >>>    {
> >>>       if (unit.getAttachment(JBossWebMetaData.class) == null)
> >>>          return false;
> >>>
> >>>       return true;
> >>>    }
> >>>
> >>> cheers
> >>> -thomas
> >>>
> >> _______________________________________________
> >> jboss-development mailing list
> >> jboss-development at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx