Yes, the intent was equivalent to "disabled".
There are really two similar notions in the xsd and I'd like to clean
them up, so I'll semi-hijack this thread to discuss that:
1) This "allowed" flag which if false says that mapping the deployment
to a server-group is forbidden. If the deployment can't be mapped it
will never be deployed. If "false" the deployment is present in the
central deployment content repo maintained by the domain controller but
wouldn't get pushed to any other hosts.
2) A "start" flag that indicates whether deployment content that is
available on the host is actually deployed (and should be deployed at
server start). If "false" the content is available for use on the host
but isn't actually deployed. This applies to both domain mode and
standalone mode.
I don't see much point to "allowed". And "start" is a poor name.
So I'd
like to:
a) get rid of "allowed".
b) change "start" to "disabled"
Thoughts?
On 2/18/11 2:59 AM, Heiko Braun wrote:
taken form the jboss_7_0.xsd :
<xs:complexType name="deploymentType">
<xs:annotation>
<xs:documentation>Deployment represents anything that can be deployed
(e.g. an application such as EJB-JAR,
WAR, EAR,
any kind of standard archive such as RAR or JBoss-specific deployment),
which can be enabled or disabled on a domain level.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="mapped-deploymentType">
*<xs:attribute name="allowed" use="optional"
type="xs:boolean"
default="true">*
<xs:annotation>
<xs:documentation>W*hether the mapping the deployment to a server group
is allowed.*
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
Can somebody explain the attribute "allowed" to me? What does it mean,
if a deployment is not "allowed" to be mapped
to a server group? Is this an equivalent to "disabled"?
Ike
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat