[JBoss JIRA] (ELY-220) Add a RegExSplittingNameRewriter
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-220?page=com.atlassian.jira.plugin.sy... ]
David Lloyd commented on ELY-220:
---------------------------------
In that case you'd use something like this:
{code}
NameRewriter transformingRewriter = new RegexNameRewriter(Pattern.compile("\\bdc=([^,]+)"), "$1", false);
{code}
This would extract the first dc= value out of the string (though it wouldn't deal with LDAP escape sequences).
> Add a RegExSplittingNameRewriter
> ---------------------------------
>
> Key: ELY-220
> URL: https://issues.jboss.org/browse/ELY-220
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Utils
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Alpha2
>
>
> The existing implementations allow for replacing a portion of a name based on a regular expression or validating a name based on a regular expression - however we do not have a form that allows you to easily extract a portion of a name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (WFLY-4839) annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4839?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-4839:
-----------------------------------------------
Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1235627|https://bugzilla.redhat.com/show_bug.cgi?id=1235627] from NEW to ASSIGNED
> annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4839
> URL: https://issues.jboss.org/browse/WFLY-4839
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Alpha4
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> {noformat}
> ### Description of problem:
> Annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true.
> Note that Servlet 3.0 specification clearly states the following:
> ~~~
> 1.6.2 Processing annotations
> In Servlet 2.5, metadata-complete only affected the scanning of annotations at
> deployment time. The notion of web-fragments did not exist in servlet 2.5. However
> in servlet 3.0 metadata-complete affects scanning of all annotations and web-
> fragments at deployment time. The version of the descriptor MUST not affect which
> annotations you scan for in a web application. An implementation of a particular
> version of the specification MUST scan for all annotations supported in that
> configuration, unless metadata-complete is specified.
> ~~~
> ### How reproducible:
> Anytime
> ### Steps to Reproduce:
> 1. Create a library jar which contains a servlet filter using @WebFilter
> 2. Put the jar under WEB-INF/lib of the web application which web.xml version is 2.3 or 2.4
> 3. Start JBoss EAP 6
> 4. Access the web application and see if the servlet filter works
> ### Actual results:
> The servlet filter is not invoked
> ### Expected results:
> The servlet filter is invoked
> ### Additional info:
> It works when the version of web.xml is 2.5 or 3.0
> [reply] [−]
> Private
> Comment 1 Masafumi Miura 2015-06-25 07:18:17 EDT
> RED HAT CONFIDENTIAL
> It looks metadata-complete is always set to true when the version of web.xml is 2.3 or 2.4 at the line 96 of web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java.
> Though Servlet 2.3/2.3 specification does not have metadata-complete attribute, Servlet 3.0 specification states the following. I think it means that the metadata-complete attribute default to false if it is not specified.
> ~~~
> 8.1 Annotations and pluggability
> if the metadata-complete attribute is not specified or is set to "false", the
> deployment tool must examine the class files of the application for annotations, and
> scan for web fragments.
> ~~~
> * web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java
> 76 public class WarMetaDataProcessor implements DeploymentUnitProcessor {
> 77
> 78 @Override
> 79 public void deploy(DeploymentPhaseContext phaseContext) throws DeploymentUnitProcessingException {
> ...
> 87 boolean isComplete = false;
> 88 WebMetaData specMetaData = warMetaData.getWebMetaData();
> 89 if (specMetaData != null) {
> 90 if (specMetaData instanceof Web25MetaData) {
> 91 isComplete |= ((Web25MetaData) specMetaData).isMetadataComplete();
> 92 } else if (specMetaData instanceof Web30MetaData) {
> 93 isComplete |= ((Web30MetaData) specMetaData).isMetadataComplete();
> 94 } else {
> 95 // Any web.xml 2.4 or earlier deployment is metadata complete
> 96 isComplete = true;
> 97 }
> 98 }
> 99
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (WFLY-4840) Deprecated element cluster-passivation-store from ejb subsystem does not work
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created WFLY-4840:
--------------------------------------
Summary: Deprecated element cluster-passivation-store from ejb subsystem does not work
Key: WFLY-4840
URL: https://issues.jboss.org/browse/WFLY-4840
Project: WildFly
Issue Type: Bug
Components: EJB, Domain Management
Reporter: Ondřej Chaloupka
Assignee: Brian Stansberry
There is a mismatch in behaviour of deprecated element {{cluster-passivation-store}} under {{ejb}} subsystem.
When element is deprecated still it should work and only prints warning that it's deprecated.
{code}
[standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:read-resource()
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0216: Management resource '[
(\"subsystem\" => \"ejb3\"),
(\"cluster-passivation-store\" => \"infinispan\")
]' not found",
"rolled-back" => true
}
{code}
but
{code}
[standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:add()
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb.cache.factory.distributable.infinispan is already registered",
"rolled-back" => true
}
{code}
_A note:_ the element {{cluster-passivation-store}} was replaced by {{passivation-store}} which works fine
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (ELY-220) Add a RegExSplittingNameRewriter
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-220?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse commented on ELY-220:
--------------------------------------
Given the following String "cn=John Doe,dc=example,dc=com" the result I want is either 'dc=example' or 'example' - wouldn't the replaceAll call just replace matches with previous matches and not extract this small match?
> Add a RegExSplittingNameRewriter
> ---------------------------------
>
> Key: ELY-220
> URL: https://issues.jboss.org/browse/ELY-220
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Utils
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Alpha2
>
>
> The existing implementations allow for replacing a portion of a name based on a regular expression or validating a name based on a regular expression - however we do not have a form that allows you to easily extract a portion of a name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (WFLY-4839) annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4839?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-4839:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1235627
> annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4839
> URL: https://issues.jboss.org/browse/WFLY-4839
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Alpha4
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> {noformat}
> ### Description of problem:
> Annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true.
> Note that Servlet 3.0 specification clearly states the following:
> ~~~
> 1.6.2 Processing annotations
> In Servlet 2.5, metadata-complete only affected the scanning of annotations at
> deployment time. The notion of web-fragments did not exist in servlet 2.5. However
> in servlet 3.0 metadata-complete affects scanning of all annotations and web-
> fragments at deployment time. The version of the descriptor MUST not affect which
> annotations you scan for in a web application. An implementation of a particular
> version of the specification MUST scan for all annotations supported in that
> configuration, unless metadata-complete is specified.
> ~~~
> ### How reproducible:
> Anytime
> ### Steps to Reproduce:
> 1. Create a library jar which contains a servlet filter using @WebFilter
> 2. Put the jar under WEB-INF/lib of the web application which web.xml version is 2.3 or 2.4
> 3. Start JBoss EAP 6
> 4. Access the web application and see if the servlet filter works
> ### Actual results:
> The servlet filter is not invoked
> ### Expected results:
> The servlet filter is invoked
> ### Additional info:
> It works when the version of web.xml is 2.5 or 3.0
> [reply] [−]
> Private
> Comment 1 Masafumi Miura 2015-06-25 07:18:17 EDT
> RED HAT CONFIDENTIAL
> It looks metadata-complete is always set to true when the version of web.xml is 2.3 or 2.4 at the line 96 of web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java.
> Though Servlet 2.3/2.3 specification does not have metadata-complete attribute, Servlet 3.0 specification states the following. I think it means that the metadata-complete attribute default to false if it is not specified.
> ~~~
> 8.1 Annotations and pluggability
> if the metadata-complete attribute is not specified or is set to "false", the
> deployment tool must examine the class files of the application for annotations, and
> scan for web fragments.
> ~~~
> * web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java
> 76 public class WarMetaDataProcessor implements DeploymentUnitProcessor {
> 77
> 78 @Override
> 79 public void deploy(DeploymentPhaseContext phaseContext) throws DeploymentUnitProcessingException {
> ...
> 87 boolean isComplete = false;
> 88 WebMetaData specMetaData = warMetaData.getWebMetaData();
> 89 if (specMetaData != null) {
> 90 if (specMetaData instanceof Web25MetaData) {
> 91 isComplete |= ((Web25MetaData) specMetaData).isMetadataComplete();
> 92 } else if (specMetaData instanceof Web30MetaData) {
> 93 isComplete |= ((Web30MetaData) specMetaData).isMetadataComplete();
> 94 } else {
> 95 // Any web.xml 2.4 or earlier deployment is metadata complete
> 96 isComplete = true;
> 97 }
> 98 }
> 99
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (WFLY-4839) annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-4839?page=com.atlassian.jira.plugin.... ]
Chao Wang commented on WFLY-4839:
---------------------------------
quickstart reproducer checks that filter did not function with web.xml version 2.4 https://github.com/soul2zimate/quickstart/tree/WFLY-4839-reproducer/servl...
> annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4839
> URL: https://issues.jboss.org/browse/WFLY-4839
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Alpha4
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> {noformat}
> ### Description of problem:
> Annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true.
> Note that Servlet 3.0 specification clearly states the following:
> ~~~
> 1.6.2 Processing annotations
> In Servlet 2.5, metadata-complete only affected the scanning of annotations at
> deployment time. The notion of web-fragments did not exist in servlet 2.5. However
> in servlet 3.0 metadata-complete affects scanning of all annotations and web-
> fragments at deployment time. The version of the descriptor MUST not affect which
> annotations you scan for in a web application. An implementation of a particular
> version of the specification MUST scan for all annotations supported in that
> configuration, unless metadata-complete is specified.
> ~~~
> ### How reproducible:
> Anytime
> ### Steps to Reproduce:
> 1. Create a library jar which contains a servlet filter using @WebFilter
> 2. Put the jar under WEB-INF/lib of the web application which web.xml version is 2.3 or 2.4
> 3. Start JBoss EAP 6
> 4. Access the web application and see if the servlet filter works
> ### Actual results:
> The servlet filter is not invoked
> ### Expected results:
> The servlet filter is invoked
> ### Additional info:
> It works when the version of web.xml is 2.5 or 3.0
> [reply] [−]
> Private
> Comment 1 Masafumi Miura 2015-06-25 07:18:17 EDT
> RED HAT CONFIDENTIAL
> It looks metadata-complete is always set to true when the version of web.xml is 2.3 or 2.4 at the line 96 of web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java.
> Though Servlet 2.3/2.3 specification does not have metadata-complete attribute, Servlet 3.0 specification states the following. I think it means that the metadata-complete attribute default to false if it is not specified.
> ~~~
> 8.1 Annotations and pluggability
> if the metadata-complete attribute is not specified or is set to "false", the
> deployment tool must examine the class files of the application for annotations, and
> scan for web fragments.
> ~~~
> * web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java
> 76 public class WarMetaDataProcessor implements DeploymentUnitProcessor {
> 77
> 78 @Override
> 79 public void deploy(DeploymentPhaseContext phaseContext) throws DeploymentUnitProcessingException {
> ...
> 87 boolean isComplete = false;
> 88 WebMetaData specMetaData = warMetaData.getWebMetaData();
> 89 if (specMetaData != null) {
> 90 if (specMetaData instanceof Web25MetaData) {
> 91 isComplete |= ((Web25MetaData) specMetaData).isMetadataComplete();
> 92 } else if (specMetaData instanceof Web30MetaData) {
> 93 isComplete |= ((Web30MetaData) specMetaData).isMetadataComplete();
> 94 } else {
> 95 // Any web.xml 2.4 or earlier deployment is metadata complete
> 96 isComplete = true;
> 97 }
> 98 }
> 99
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (WFLY-4839) annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true
by Chao Wang (JIRA)
Chao Wang created WFLY-4839:
-------------------------------
Summary: annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true
Key: WFLY-4839
URL: https://issues.jboss.org/browse/WFLY-4839
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 10.0.0.Alpha4
Reporter: Chao Wang
Assignee: Chao Wang
{noformat}
### Description of problem:
Annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true.
Note that Servlet 3.0 specification clearly states the following:
~~~
1.6.2 Processing annotations
In Servlet 2.5, metadata-complete only affected the scanning of annotations at
deployment time. The notion of web-fragments did not exist in servlet 2.5. However
in servlet 3.0 metadata-complete affects scanning of all annotations and web-
fragments at deployment time. The version of the descriptor MUST not affect which
annotations you scan for in a web application. An implementation of a particular
version of the specification MUST scan for all annotations supported in that
configuration, unless metadata-complete is specified.
~~~
### How reproducible:
Anytime
### Steps to Reproduce:
1. Create a library jar which contains a servlet filter using @WebFilter
2. Put the jar under WEB-INF/lib of the web application which web.xml version is 2.3 or 2.4
3. Start JBoss EAP 6
4. Access the web application and see if the servlet filter works
### Actual results:
The servlet filter is not invoked
### Expected results:
The servlet filter is invoked
### Additional info:
It works when the version of web.xml is 2.5 or 3.0
[reply] [−]
Private
Comment 1 Masafumi Miura 2015-06-25 07:18:17 EDT
RED HAT CONFIDENTIAL
It looks metadata-complete is always set to true when the version of web.xml is 2.3 or 2.4 at the line 96 of web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java.
Though Servlet 2.3/2.3 specification does not have metadata-complete attribute, Servlet 3.0 specification states the following. I think it means that the metadata-complete attribute default to false if it is not specified.
~~~
8.1 Annotations and pluggability
if the metadata-complete attribute is not specified or is set to "false", the
deployment tool must examine the class files of the application for annotations, and
scan for web fragments.
~~~
* web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java
76 public class WarMetaDataProcessor implements DeploymentUnitProcessor {
77
78 @Override
79 public void deploy(DeploymentPhaseContext phaseContext) throws DeploymentUnitProcessingException {
...
87 boolean isComplete = false;
88 WebMetaData specMetaData = warMetaData.getWebMetaData();
89 if (specMetaData != null) {
90 if (specMetaData instanceof Web25MetaData) {
91 isComplete |= ((Web25MetaData) specMetaData).isMetadataComplete();
92 } else if (specMetaData instanceof Web30MetaData) {
93 isComplete |= ((Web30MetaData) specMetaData).isMetadataComplete();
94 } else {
95 // Any web.xml 2.4 or earlier deployment is metadata complete
96 isComplete = true;
97 }
98 }
99
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (WFLY-4743) Unable to start server on Windows from path containing special characters jboss-eap-ŽlutýKůň-7.0
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-4743?page=com.atlassian.jira.plugin.... ]
Bartosz Baranowski resolved WFLY-4743.
--------------------------------------
Resolution: Rejected
> Unable to start server on Windows from path containing special characters jboss-eap-ŽlutýKůň-7.0
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-4743
> URL: https://issues.jboss.org/browse/WFLY-4743
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 10.0.0.Alpha2
> Reporter: Marek Kopecký
> Assignee: Bartosz Baranowski
>
> *Description of problem:*
> Server is unable to start if JBOSS_HOME contaings "ŽlutýKůň" characters. This issue is valid for standalone and domain.
> *How reproducible:*
> Windows
> *Steps to Reproduce:*
> * standalone.bat
> * standalone.ps1
> *Actual results:*
> {noformat}
> ....
> Error: Unable to access jarfile C:\Users\Administrator\7.0.0.DR3\jboss-eap-Älut²Kun\jboss-modules.jar
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years