8:41 a.m.
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
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
9:32 a.m.
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
9:51 a.m.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
11:01 a.m.
New subject: [jbossws-dev] Re: metadata not attached to DeploymentUnit
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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
8:12 a.m.
New subject: [jbossws-dev] Re: metadata not attached to DeploymentUnit
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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
9:59 a.m.
To me this is the wrong approach anyway.
There shouldn't be any code that does
if (ejbdeployment)
doThis();
else if (webdeployment)
doThat();
else if (unknowntype) // OOPS (pun intended ;-)
cantDoIt();
The webservice deployers should be working off some generic
metadata that triggers them to operate.
Then each type of deployment can populate that metadata
to say "I want a webservice endpoint for this".
This is a seperate deployer for each type we know how
to map to a webservice it takes the ejb/web/other
metadata and maps or bridges it to the webservice
metadata.
It shouldn't just be restricted to ejbs and wars.
e.g. An MBean should be capable of being an endpoint if
there is a deployer that creates the relevant
metadata attachment from say a META-INF/jboss-webservice.xml in the sar.
The security deployers take the same brain dead
(non object orientated) approach.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
6131
days inactive
6132
days old
jboss-development@lists.jboss.org
5 comments
4 participants
participants (4)
-
Adrian -
Carlo de Wolf -
Scott M Stark -
Thomas Diesler