July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-2261) Allow application exceptions to be defined when using the throws clause.

by Shaun Appleton (JIRA)

Allow application exceptions to be defined when using the throws clause. ------------------------------------------------------------------------- Key: EJBTHREE-2261 URL: https://issues.jboss.org/browse/EJBTHREE-2261 Project: EJB 3.0 Issue Type: Feature Request Reporter: Shaun Appleton Allow application exceptions to be defined when using the throws clause. This has been incorporated as part of EJBTHREE-2134 and should be allowed for EJB3 used by EAP 5.x Depending on the resolution of http://java.net/jira/browse/EJB_SPEC-20 this may be a bug or rfe -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2257) Create proper API component

by Carlo de Wolf (JIRA)

Create proper API component --------------------------- Key: EJBTHREE-2257 URL: https://issues.jboss.org/browse/EJBTHREE-2257 Project: EJB 3.0 Issue Type: Task Components: ext-api Reporter: Carlo de Wolf Priority: Critical Fix For: 2.0.0-beta-2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Assigned: (JBAS-8297) Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/JBAS-8297?page=com.atlassian.jira.plugin.... ] Ales Justin reassigned JBAS-8297: --------------------------------- Assignee: Remy Maucherat (was: Ales Justin) This appears to be a web request handling order issue -- JBossWeb' task. > Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped > ------------------------------------------------------------------------------------------ > > Key: JBAS-8297 > URL: https://issues.jboss.org/browse/JBAS-8297 > Project: Legacy JBoss Application Server 6 > Issue Type: Bug > Components: Weld/CDI > Environment: JBoss 6.0.0.M2, Windows XP SP3 > Reporter: Marcos Antonio > Assignee: Remy Maucherat > Fix For: 6.1.0 > > Attachments: solicitacoes.zip > > > 2010-04-22 09:55:36,484 WARN [org.apache.catalina.authenticator.FormAuthenticator] (http-127.0.0.1-8080-1) Unexpected error forwarding to login page: javax.servlet.ServletException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-8297) Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/JBAS-8297?page=com.atlassian.jira.plugin.... ] Ales Justin updated JBAS-8297: ------------------------------ Comment: was deleted (was: https://issues.apache.org/bugzilla/show_bug.cgi?id=50789 ) > Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped > ------------------------------------------------------------------------------------------ > > Key: JBAS-8297 > URL: https://issues.jboss.org/browse/JBAS-8297 > Project: Legacy JBoss Application Server 6 > Issue Type: Bug > Components: Weld/CDI > Environment: JBoss 6.0.0.M2, Windows XP SP3 > Reporter: Marcos Antonio > Assignee: Ales Justin > Fix For: 6.1.0 > > Attachments: solicitacoes.zip > > > 2010-04-22 09:55:36,484 WARN [org.apache.catalina.authenticator.FormAuthenticator] (http-127.0.0.1-8080-1) Unexpected error forwarding to login page: javax.servlet.ServletException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-8297) Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/JBAS-8297?page=com.atlassian.jira.plugin.... ] Ales Justin commented on JBAS-8297: ----------------------------------- https://issues.apache.org/bugzilla/show_bug.cgi?id=50789 > Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped > ------------------------------------------------------------------------------------------ > > Key: JBAS-8297 > URL: https://issues.jboss.org/browse/JBAS-8297 > Project: Legacy JBoss Application Server 6 > Issue Type: Bug > Components: Weld/CDI > Environment: JBoss 6.0.0.M2, Windows XP SP3 > Reporter: Marcos Antonio > Assignee: Ales Justin > Fix For: 6.1.0 > > Attachments: solicitacoes.zip > > > 2010-04-22 09:55:36,484 WARN [org.apache.catalina.authenticator.FormAuthenticator] (http-127.0.0.1-8080-1) Unexpected error forwarding to login page: javax.servlet.ServletException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2992) Could not parse escaped characters

by Tomáš Schlosser (JIRA)

Could not parse escaped characters ---------------------------------- Key: JBRULES-2992 URL: https://issues.jboss.org/browse/JBRULES-2992 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tomáš Schlosser Assignee: Mark Proctor Fix For: 5.2.0.M1 When trying to parse rule: rule "Regex-A" when Person(name matches "\w\w\d{3}\w\w") then insert(new Message("Regex-A working")); end I get following exception: Unable to Analyse Expression name ~= "\w\w\d{3}\w\w": [Error: illegal escape sequence: w] [Near : {... name ~= "\w\w\d{3}\w\w" ....}] ^ [Line: 1, Column: 22] : [Rule name='Regex-A'] use of KnowledgeBuilder property 'drools.parser.processStringEscapes' seems to have no effect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (AS7-1340) web subsystem / virtual-server has no description for "enable-welcome-root"

by Heiko Rupp (JIRA)

web subsystem / virtual-server has no description for "enable-welcome-root" ----------------------------------------------------------------------------------- Key: AS7-1340 URL: https://issues.jboss.org/browse/AS7-1340 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.0.0.Final Reporter: Heiko Rupp Assignee: Remy Maucherat /subsystem=web/virtual-server=default-host:read-resource lists "enable-welcome-root" => true, but this is not described with :read-resource-description -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (AS7-1338) Remote JNDI support for AS7

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Richard Opalka updated AS7-1338: -------------------------------- Fix Version/s: 7.1.0.Alpha1 Component/s: Naming > Remote JNDI support for AS7 > --------------------------- > > Key: AS7-1338 > URL: https://issues.jboss.org/browse/AS7-1338 > Project: Application Server 7 > Issue Type: Task > Components: Naming > Reporter: Richard Opalka > Priority: Blocker > Fix For: 7.1.0.Alpha1 > > > <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :( > <opalka> wolfc, dmlloyd in the config I see the following ports defined > <opalka> --- > <opalka> <socket-binding name="jndi" port="1099"/> > <opalka> <socket-binding name="jmx-connector-registry" port="1090"/> > <opalka> <socket-binding name="jmx-connector-server" port="1091"/> > <opalka> --- > <dmlloyd> we don't do JNDI over RMI anymore > <dmlloyd> that listing is an error > <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to? > <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol? > <dmlloyd> no, we will be able to, it'll just work somewhat differently > <opalka> dmlloyd, ok, I'm excluding the tests then ... > <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment? > <dmlloyd> not that I'm aware of, it's just an outstanding task > <dmlloyd> remote invocation is not planned to be covered in next months' beta release > <opalka> dmlloyd, ok, thx for info ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (AS7-1338) Remote JNDI support for AS7

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Richard Opalka moved JBWS-3234 to AS7-1338: ------------------------------------------- Project: Application Server 7 (was: JBoss Web Services) Key: AS7-1338 (was: JBWS-3234) Workflow: GIT Pull Request workflow (was: jira) Security: (was: Public) > Remote JNDI support for AS7 > --------------------------- > > Key: AS7-1338 > URL: https://issues.jboss.org/browse/AS7-1338 > Project: Application Server 7 > Issue Type: Task > Reporter: Richard Opalka > Priority: Blocker > > <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :( > <opalka> wolfc, dmlloyd in the config I see the following ports defined > <opalka> --- > <opalka> <socket-binding name="jndi" port="1099"/> > <opalka> <socket-binding name="jmx-connector-registry" port="1090"/> > <opalka> <socket-binding name="jmx-connector-server" port="1091"/> > <opalka> --- > <dmlloyd> we don't do JNDI over RMI anymore > <dmlloyd> that listing is an error > <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to? > <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol? > <dmlloyd> no, we will be able to, it'll just work somewhat differently > <opalka> dmlloyd, ok, I'm excluding the tests then ... > <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment? > <dmlloyd> not that I'm aware of, it's just an outstanding task > <dmlloyd> remote invocation is not planned to be covered in next months' beta release > <opalka> dmlloyd, ok, thx for info ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Deleted: (AS7-1327) Manage EJB Container through web console

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-1327?page=com.atlassian.jira.plugin.s... ] Heiko Braun deleted AS7-1327: ----------------------------- > Manage EJB Container through web console > ---------------------------------------- > > Key: AS7-1327 > URL: https://issues.jboss.org/browse/AS7-1327 > Project: Application Server 7 > Issue Type: Feature Request > Reporter: Heiko Braun > Assignee: Heiko Braun > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 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 July 2011