October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-266) KIE resolving dependend artifacts issue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-266?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-266: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> made a comment on [bug 1014157|https://bugzilla.redhat.com/show_bug.cgi?id=1014157] > KIE resolving dependend artifacts issue > --------------------------------------- > > Key: DROOLS-266 > URL: https://issues.jboss.org/browse/DROOLS-266 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR3 > Reporter: Kurt Stam > Assignee: Mario Fusco > Fix For: 6.0.0.CR5 > > Attachments: kie-load-from-maven-issue.tgz, kie-load-from-maven-issue.tgz > > > This happens when for a dependency the scope is > - set to 'provided' and > - a parameter (in the case ${jbpm.version}) is used in the version field. > So the relevant entry in the pom is: > <dependency> > <groupId>org.drools</groupId> > <artifactId>drools-core</artifactId> > <version>${drools.version}</version> > <scope>provided</scope> > </dependency> > which leads to > 11:15:02,584 WARN Dependency artifact not found for: org.jbpm:jbpm-bpmn2:${jbpm.version} > and then the NPE. I'm guessing the parameter is not being resolved. > 1. it probably should resolve parameters > 2. if a dependency is scoped as 'provided' I think it is supposed to locate it on the classpath and NOT from maven. However I'm not sure this is the way that works in testing anyway. > 3. if the dependency cannot be found it should probably stop and not even proceed rather then warn? > 4. it should be interesting to see why it gets the NPE. > If you change the dependency from 'provided' to 'test' things work fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2201) Server-side XTS handlers not added if @WebService#portName is missing

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-2201?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on WFLY-2201: --------------------------------------- I do not want to raise the PR until JBTM-1963 is sorted, because it may cause the applications to fail unexpectedly... > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: WFLY-2201 > URL: https://issues.jboss.org/browse/WFLY-2201 > Project: WildFly > Issue Type: Bug > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 8.0.0.CR1 > > > To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails with: > {code} > "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" > {code} > The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SASL-39) Support for stronger hashes as alternatives to MD5

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-39?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-39: --------------------------------- Fix Version/s: 1.0.4.CR2 (was: 1.0.4.CR1) > Support for stronger hashes as alternatives to MD5 > -------------------------------------------------- > > Key: SASL-39 > URL: https://issues.jboss.org/browse/SASL-39 > Project: JBoss SASL Provider > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Fix For: 1.0.4.CR2 > > > Presently Digest authentication is based on MD5 - however we should either update the mechanism or add new mechanisms to support the use of stronger hashes. > As this library is used both client and server side installations that require the stronger hashes can just ensure the client and server have the latest version of this library - installations that still require interaction with MD5 will need to ensure that it is still available as a mechanism. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SASL-11) From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-11?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-11: --------------------------------- Fix Version/s: 1.0.4.CR2 (was: 1.0.4.CR1) > From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect > --------------------------------------------------------------------------------------------------------------------------- > > Key: SASL-11 > URL: https://issues.jboss.org/browse/SASL-11 > Project: JBoss SASL Provider > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.4.CR2 > > > By using space as the separator a single realm name that contains a space is split into two realms. > Either support quoted realm names if they contain a space or choose a different delimiter - (A different delimiter other than a control character may be difficult as the rest can appear in a realm name) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SASL-10) Pluggable nonce handling strategy

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-10?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-10: --------------------------------- Fix Version/s: 1.0.4.CR2 (was: 1.0.4.CR1) > Pluggable nonce handling strategy > --------------------------------- > > Key: SASL-10 > URL: https://issues.jboss.org/browse/SASL-10 > Project: JBoss SASL Provider > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.4.CR2 > > > Implement a pluggable nonce handling strategy. > At the very least we need to be able to switch to using a SecureRandom instead of Random. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SASL-11) From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-11?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-11: --------------------------------- Sprint: Sprint 1 > From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect > --------------------------------------------------------------------------------------------------------------------------- > > Key: SASL-11 > URL: https://issues.jboss.org/browse/SASL-11 > Project: JBoss SASL Provider > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.4.CR2 > > > By using space as the separator a single realm name that contains a space is split into two realms. > Either support quoted realm names if they contain a space or choose a different delimiter - (A different delimiter other than a control character may be difficult as the rest can appear in a realm name) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SASL-39) Support for stronger hashes as alternatives to MD5

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-39?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-39: --------------------------------- Sprint: Sprint 1 > Support for stronger hashes as alternatives to MD5 > -------------------------------------------------- > > Key: SASL-39 > URL: https://issues.jboss.org/browse/SASL-39 > Project: JBoss SASL Provider > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Fix For: 1.0.4.CR2 > > > Presently Digest authentication is based on MD5 - however we should either update the mechanism or add new mechanisms to support the use of stronger hashes. > As this library is used both client and server side installations that require the stronger hashes can just ensure the client and server have the latest version of this library - installations that still require interaction with MD5 will need to ensure that it is still available as a mechanism. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-291) ClassCastException during constraint jitting when an interface is used for implementation and traiting

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-291?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-291. -------------------------------- Fix Version/s: 5.5.1.Final 6.0.0.CR5 Resolution: Done > ClassCastException during constraint jitting when an interface is used for implementation and traiting > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-291 > URL: https://issues.jboss.org/browse/DROOLS-291 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR4 > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > The following combination is needed: > - an interface IX with at least one getter/setter pair > - a trait IY extending IX > - a class K implementing IX > - a jittable constraint on IX > The constraint is first triggered by an "instance" of IY, > but jitted by an instance of K. > The condition analyzer assumes that IY is the natural > domain of the constratint, rather than IX. The jitted > constraint will then try to cast K to IY, resulting in > a disruptive CCE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SASL-40) Update the local authentication mechanism to allow permissions to be specified for the challenge file.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-40?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-40: --------------------------------- Fix Version/s: 1.0.4.CR2 (was: 1.0.4.CR1) > Update the local authentication mechanism to allow permissions to be specified for the challenge file. > ------------------------------------------------------------------------------------------------------ > > Key: SASL-40 > URL: https://issues.jboss.org/browse/SASL-40 > Project: JBoss SASL Provider > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.4.CR2 > > > (This would include switching to a dependency on Java 7 server side at least) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SASL-43) Release JBoss SASL 1.0.4.CR1

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-43?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved SASL-43. ---------------------------------- Fix Version/s: 1.0.4.CR1 Resolution: Done > Release JBoss SASL 1.0.4.CR1 > ---------------------------- > > Key: SASL-43 > URL: https://issues.jboss.org/browse/SASL-43 > Project: JBoss SASL Provider > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.4.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013