May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-776) Restore webservice-security integration

by Alessio Soldano (JIRA)

Restore webservice-security integration --------------------------------------- Key: AS7-776 URL: https://issues.jboss.org/browse/AS7-776 Project: Application Server 7 Issue Type: Task Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 7.0.0.CR1 This is required for authentication/authorization (WS-Security UT). We're most likely going to need injecting the SecurityDomainContext somehow into the SPI Endpoint. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-765) Add JBossWS security-domain

by Alessio Soldano (JIRA)

Add JBossWS security-domain --------------------------- Key: AS7-765 URL: https://issues.jboss.org/browse/AS7-765 Project: Application Server 7 Issue Type: Task Components: Security, Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 7.0.0.CR1 Restore "JBossWS" security domain, similarly to what we had on AS 5/6 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-9390) Request context not active during remote EJB invocations

by Marius Bogoevici (JIRA)

Request context not active during remote EJB invocations -------------------------------------------------------- Key: JBAS-9390 URL: https://issues.jboss.org/browse/JBAS-9390 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.Final Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 6.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-697) Add operation handler to list all deployed webservice endpoints

by Jim Ma (JIRA)

Add operation handler to list all deployed webservice endpoints --------------------------------------------------------------- Key: AS7-697 URL: https://issues.jboss.org/browse/AS7-697 Project: Application Server 7 Issue Type: Task Components: Web Services Affects Versions: 7.0.0.Beta3 Reporter: Jim Ma Assignee: Jim Ma Fix For: 7.0.0.Beta4 To list all the deployed webservice endpoints: [localhost:9999 /] /subsystem=webservices:list-endpoints { "outcome" => "success", "result" => { "deployed-count" => 1, "jboss.ws:context=TestService_web,endpoint=W2JTest" => [ ("address" => "http://localhost:8080/TestService_web/jaxws/W2JTest"), ("wsdlURL" => "http://localhost:8080/TestService_web/jaxws/W2JTest?wsdl"), ("shortName" => "W2JTest"), ("implClass" => "org.jboss.ws.W2JTestImpl") ] }, "compensating-operation" => undefined } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-698) Add operation to query ws endpoints metrics

by Jim Ma (JIRA)

Add operation to query ws endpoints metrics ------------------------------------------- Key: AS7-698 URL: https://issues.jboss.org/browse/AS7-698 Project: Application Server 7 Issue Type: Task Components: Web Services Affects Versions: 7.0.0.Beta3 Reporter: Jim Ma Assignee: Jim Ma Fix For: 7.0.0.Beta4 Add operation to read metrics from org.jboss.wsf.spi.management.EndpointMetrics -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3010) invalid dialect attribute value => NPR

by Wolfgang Laun (JIRA)

invalid dialect attribute value => NPR -------------------------------------- Key: JBRULES-3010 URL: https://issues.jboss.org/browse/JBRULES-3010 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.M2 Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.0.CR1 rule insFirst dialect "mvl" when then end Exception in thread "main" java.lang.NullPointerException at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:74) at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:1613) at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:690) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:310) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:486) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1909) clarifiction wanted for Rules docs

by Darrin Mison (JIRA)

clarifiction wanted for Rules docs ---------------------------------- Key: JBRULES-1909 URL: https://jira.jboss.org/jira/browse/JBRULES-1909 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs-expert Reporter: Darrin Mison Assignee: Mark Proctor QE feedback from the SOA edition of the JBoss Rules Reference contained the following clarification request: "Agenda groups are a handy way to create a "flow" between grouped rules." The previous paragraph indicated that a flow between rules cannot be relied on. Are we saying that the flow between groups is a way around that limitation? Or is the term 'flow' being used in a different context here. The content is the same in http://anonsvn.jboss.org/repos/labs/labs/jbossrules/soa_tags/4.3.0.FP01_B... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2609) Bad condition operator "===" (triple equals) in room fire example

by Julien Kronegg (JIRA)

Bad condition operator "===" (triple equals) in room fire example ----------------------------------------------------------------- Key: JBRULES-2609 URL: https://jira.jboss.org/browse/JBRULES-2609 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs-expert Affects Versions: 5.1.0.FINAL Environment: environment not relevant Reporter: Julien Kronegg Assignee: Mark Proctor Priority: Trivial Context: The "Quick Start" chapter/"The Basics" section uses an example of fire in rooms. Issue: In one of the rule example snippet, the condition operator used is "===" (triple equals) instead of "==" (double equals): rule "Status output when things are ok" when not Alarm() not Sprinkler( on === true ) then System.out.println( "Everything is ok" ); end Location: In version 5.1.0.FINAL and also in trunk/rev34481 in the following file: http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-docs/dro... : line 389 Priority: Since this is in the basics, beginners read that chapter, so the priority could be higher than "trivial" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2248) Drools Expert User Guide errors

by Karsten Thoms (JIRA)

Drools Expert User Guide errors ------------------------------- Key: JBRULES-2248 URL: https://jira.jboss.org/jira/browse/JBRULES-2248 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs Affects Versions: 5.0.1.FINAL Reporter: Karsten Thoms Assignee: Mark Proctor Priority: Trivial Some minor issues I found when following the User Guide: Improvement: Variable 'kbase' is not introduced in the first example. Add declaration and instantiation to example in 2.1.1. Rule "Status output when things are ok" error: not Sprinkler( on === true ) correct: not Sprinkler( on == true ) ERROR if ( kbuilder.hasErrors() ) { System.err.println( builder.getErrors().toString() ); } CORRECT if ( kbuilder.hasErrors() ) { System.err.println( kbuilder.getErrors().toString() ); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2763) Event declaration using fqn

by Samuli Saarinen (JIRA)

Event declaration using fqn --------------------------- Key: JBRULES-2763 URL: https://jira.jboss.org/browse/JBRULES-2763 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Environment: Java 1.6 Drools 5.1.1 Reporter: Samuli Saarinen Assignee: Mark Proctor I'm trying to create event declaration using fqn in the declaration but for some reason it doesn't work. I have the following rule: package com.test.pkg declare com.test.Event1 @role(event) @expires(2s) end compiling it produces the following error: [6,11]: [ERR 103] Line 6:11 rule 'end_key' failed predicate: {(validateIdentifierKey(DroolsSoftKeywords.END))}? in com But if I change it as follows: package com.test.pkg import com.test.Event1 declare Event1 @role(event) @expires(2s) end Everything works as expected... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011