|
»
»
[cargo-dev] [jira] Created: (CARGO-340) org.jboss.deployment.Deploymen
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
[cargo-dev] [jira] Created: (CARGO-340) org.jboss.deployment.Deploymen |
|
|
[jira] Updated: (CARGO-340) Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/CARGO-340?page=all ]
Vincent Massol updated CARGO-340: --------------------------------- Component: (was: Maven2) Jetty Summary: Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser (was: org.jboss.deployment.DeploymentException: No Attribute found with name: ServerMode) Changed description to better reflect the issue > Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser > ------------------------------------------------------------------------------------- > > Key: CARGO-340 > URL: http://jira.codehaus.org/browse/CARGO-340 > Project: Cargo > Type: Bug > Components: Jetty > Versions: 0.8 > Reporter: Andreas Schildbach > > > org.jboss.deployment.DeploymentException: No Attribute found with name: ServerMode > at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:263) > at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:163) > at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:117) > This happens with the cargo maven2 plugin 0.8 when using a standalone local config (which is the default) on JBoss 3.2.7. When looking at the generated jboss-service.xml, there is the following entry: > <mbean code="org.jboss.security.plugins.JaasSecurityManagerService" > name="jboss.security:service=JaasSecurityManager"> > <!-- A flag which indicates whether the SecurityAssociation server mode > is set on service creation. This is true by default since the > SecurityAssociation should be thread local for multi-threaded server > operation. > --> > <attribute name="ServerMode">true</attribute> > [...] > When search for "ServerMode" on the JBoss JIRA, it becomes clear that this setting has been added in JBoss 3.2.8 RC1: > http://jira.jboss.com/jira/browse/JBAS-2143 > Please stay compatible to released versions! > The problem is also present in the 0.9-SNAPSHOT as of a few hours ago. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (CARGO-340) Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/CARGO-340?page=comments#action_67193 ]
Vincent Massol commented on CARGO-340: -------------------------------------- For the record, I've just done a diff between a jboss 3.2.7 jboss-service.xml with the one generated by Cargo and this ServerMode attribute is the only difference. Thus a good-enough implementation is to create an Ant filter token for this. > Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser > ------------------------------------------------------------------------------------- > > Key: CARGO-340 > URL: http://jira.codehaus.org/browse/CARGO-340 > Project: Cargo > Type: Bug > Components: Jetty > Versions: 0.8 > Reporter: Andreas Schildbach > > > org.jboss.deployment.DeploymentException: No Attribute found with name: ServerMode > at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:263) > at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:163) > at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:117) > This happens with the cargo maven2 plugin 0.8 when using a standalone local config (which is the default) on JBoss 3.2.7. When looking at the generated jboss-service.xml, there is the following entry: > <mbean code="org.jboss.security.plugins.JaasSecurityManagerService" > name="jboss.security:service=JaasSecurityManager"> > <!-- A flag which indicates whether the SecurityAssociation server mode > is set on service creation. This is true by default since the > SecurityAssociation should be thread local for multi-threaded server > operation. > --> > <attribute name="ServerMode">true</attribute> > [...] > When search for "ServerMode" on the JBoss JIRA, it becomes clear that this setting has been added in JBoss 3.2.8 RC1: > http://jira.jboss.com/jira/browse/JBAS-2143 > Please stay compatible to released versions! > The problem is also present in the 0.9-SNAPSHOT as of a few hours ago. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (CARGO-340) Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/CARGO-340?page=comments#action_67194 ]
Vincent Massol commented on CARGO-340: -------------------------------------- We'll also need to implement a version comparator to know if the user is using a version lesser or greater than 3.2.7... > Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser > ------------------------------------------------------------------------------------- > > Key: CARGO-340 > URL: http://jira.codehaus.org/browse/CARGO-340 > Project: Cargo > Type: Bug > Components: Jetty > Versions: 0.8 > Reporter: Andreas Schildbach > > > org.jboss.deployment.DeploymentException: No Attribute found with name: ServerMode > at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:263) > at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:163) > at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:117) > This happens with the cargo maven2 plugin 0.8 when using a standalone local config (which is the default) on JBoss 3.2.7. When looking at the generated jboss-service.xml, there is the following entry: > <mbean code="org.jboss.security.plugins.JaasSecurityManagerService" > name="jboss.security:service=JaasSecurityManager"> > <!-- A flag which indicates whether the SecurityAssociation server mode > is set on service creation. This is true by default since the > SecurityAssociation should be thread local for multi-threaded server > operation. > --> > <attribute name="ServerMode">true</attribute> > [...] > When search for "ServerMode" on the JBoss JIRA, it becomes clear that this setting has been added in JBoss 3.2.8 RC1: > http://jira.jboss.com/jira/browse/JBAS-2143 > Please stay compatible to released versions! > The problem is also present in the 0.9-SNAPSHOT as of a few hours ago. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Updated: (CARGO-340) Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/CARGO-340?page=all ]
I Nyoman Winardi updated CARGO-340: ----------------------------------- Component: (was: Jetty) JBoss Change the component to JBoss, was Jetty > Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser > ------------------------------------------------------------------------------------- > > Key: CARGO-340 > URL: http://jira.codehaus.org/browse/CARGO-340 > Project: Cargo > Type: Bug > Components: JBoss > Versions: 0.8 > Reporter: Andreas Schildbach > > > org.jboss.deployment.DeploymentException: No Attribute found with name: ServerMode > at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:263) > at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:163) > at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:117) > This happens with the cargo maven2 plugin 0.8 when using a standalone local config (which is the default) on JBoss 3.2.7. When looking at the generated jboss-service.xml, there is the following entry: > <mbean code="org.jboss.security.plugins.JaasSecurityManagerService" > name="jboss.security:service=JaasSecurityManager"> > <!-- A flag which indicates whether the SecurityAssociation server mode > is set on service creation. This is true by default since the > SecurityAssociation should be thread local for multi-threaded server > operation. > --> > <attribute name="ServerMode">true</attribute> > [...] > When search for "ServerMode" on the JBoss JIRA, it becomes clear that this setting has been added in JBoss 3.2.8 RC1: > http://jira.jboss.com/jira/browse/JBAS-2143 > Please stay compatible to released versions! > The problem is also present in the 0.9-SNAPSHOT as of a few hours ago. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (CARGO-340) Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/CARGO-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189599#action_189599 ] Matt Wringe commented on CARGO-340: ----------------------------------- does anyone still care about this issue, or can we close it as wont fix? We should look into how many people are still using JBoss 3x with Cargo. > Do not use the "ServerMode" attribute in jboss-service.xml for JBoss 3.2.7 and lesser > ------------------------------------------------------------------------------------- > > Key: CARGO-340 > URL: http://jira.codehaus.org/browse/CARGO-340 > Project: Cargo > Issue Type: Bug > Components: JBoss > Affects Versions: 0.8 > Reporter: Andreas Schildbach > > org.jboss.deployment.DeploymentException: No Attribute found with name: ServerMode > at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:263) > at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:163) > at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:117) > This happens with the cargo maven2 plugin 0.8 when using a standalone local config (which is the default) on JBoss 3.2.7. When looking at the generated jboss-service.xml, there is the following entry: > <mbean code="org.jboss.security.plugins.JaasSecurityManagerService" > name="jboss.security:service=JaasSecurityManager"> > <!-- A flag which indicates whether the SecurityAssociation server mode > is set on service creation. This is true by default since the > SecurityAssociation should be thread local for multi-threaded server > operation. > --> > <attribute name="ServerMode">true</attribute> > [...] > When search for "ServerMode" on the JBoss JIRA, it becomes clear that this setting has been added in JBoss 3.2.8 RC1: > http://jira.jboss.com/jira/browse/JBAS-2143 > Please stay compatible to released versions! > The problem is also present in the 0.9-SNAPSHOT as of a few hours ago. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |
