August 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMETA-295) Add public constructors to TransportConfig, ASContextConfig and SASContextConfig that allow setting all properties on these classes

by Stefan Guilhen (JIRA)

Add public constructors to TransportConfig, ASContextConfig and SASContextConfig that allow setting all properties on these classes ----------------------------------------------------------------------------------------------------------------------------------- Key: JBMETA-295 URL: https://jira.jboss.org/browse/JBMETA-295 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ejb Affects Versions: jboss-metadata-common-2.0.0-alpha-16, 1.0.5.GA Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: jboss-metadata-ejb-2.0.0-alpha-17, 1.0.6.GA IorSecurityConfigMetaData has setter methods for TransportConfig, ASContextConfig and SASContextConfig but these classes only offer default public constructors that set default values for all their properties. As the classes are immutable, they don't have setter methods for the properties, so we need a constructor that allows the specification of the values that should be assigned to each property. -- 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

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2144) Specifying remote-binding / client-bind-url in jboss.xml binds under ProxyFactory in JNDI

by Brad Maxwell (JIRA)

Specifying remote-binding / client-bind-url in jboss.xml binds under ProxyFactory in JNDI ----------------------------------------------------------------------------------------- Key: EJBTHREE-2144 URL: https://jira.jboss.org/browse/EJBTHREE-2144 Project: EJB 3.0 Issue Type: Bug Affects Versions: 1.1.22 Environment: Sun JDK 6, JBoss EAP 5.0.1 Reporter: Brad Maxwell Assignee: Andrew Lee Rubinger >From JNDI View - here is what is bound. The binding under ProxyFactory shouldn't be there. +- HelloBean (class: org.jnp.interfaces.NamingContext) | +- https (class: Proxy for: com.jboss.examples.ejb3.Hello) | +- http (class: Proxy for: com.jboss.examples.ejb3.Hello) +- helloWorld (class: org.jnp.interfaces.NamingContext) | +- HelloBean (class: org.jnp.interfaces.NamingContext) | | +- local-com.jboss.examples.ejb3.HelloLocal (class: Proxy for: com.jboss.examples.ejb3.HelloLocal) | | +- local (class: Proxy for: com.jboss.examples.ejb3.HelloLocal) | | +- remote-com.jboss.examples.ejb3.Hello (class: Proxy for: com.jboss.examples.ejb3.Hello) +- ProxyFactory (class: org.jnp.interfaces.NamingContext) | +- helloWorld (class: org.jnp.interfaces.NamingContext) | | +- HelloBean (class: org.jnp.interfaces.NamingContext) | | | +- HelloBean (class: org.jnp.interfaces.NamingContext) | | | | +- https (proxy: $Proxy145 implements interface EJB Definition: @Stateless(name="HelloBean") public class HelloBean implements Hello, HelloLocal { ... } public @Remote interface Hello { ... } public @Local interface HelloLocal { } <?xml version="1.0" encoding="UTF-8"?> <jboss xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" version="3.0"> <enterprise-beans> <session> <ejb-name>HelloBean</ejb-name> <remote-binding> <jndi-name>HelloBean/http</jndi-name> <client-bind-url> http://${jboss.bind.address}:8080/unified-invoker/Ejb3ServerInvokerServlet/?return-exception=true </client-bind-url> </remote-binding> <remote-binding> <jndi-name>HelloBean/https</jndi-name> <client-bind-url> https://${jboss.bind.address}:8443/unified-invoker/SSLEjb3ServerInvokerServlet/?return-exception=true </client-bind-url> </remote-binding> </session> </enterprise-beans> </jboss> -- 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

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1241) Update svn properties

by Ron Sigal (JIRA)

Update svn properties --------------------- Key: JBREM-1241 URL: https://jira.jboss.org/browse/JBREM-1241 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.3.SP2 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.3.SP3 Some of the files are missing the svn:eol-style property. -- 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

15 years, 11 months

1
2
0 / 0

[JBoss JIRA] Assigned: (JBAS-8303) Investigate better ways of doing injection into into EJB instances than using an interceptor

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8303?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici reassigned JBAS-8303: -------------------------------------- Assignee: Marius Bogoevici > Investigate better ways of doing injection into into EJB instances than using an interceptor > -------------------------------------------------------------------------------------------- > > Key: JBAS-8303 > URL: https://jira.jboss.org/browse/JBAS-8303 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > > Especially, a better way of getting the EJB name -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMETA-272) Update jboss-web.xml DTDs to reflect elimination of FIELD granularity session replication

by Brian Stansberry (JIRA)

Update jboss-web.xml DTDs to reflect elimination of FIELD granularity session replication ----------------------------------------------------------------------------------------- Key: JBMETA-272 URL: https://jira.jboss.org/jira/browse/JBMETA-272 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: web Reporter: Brian Stansberry Fix For: jboss-metadata-web-2.0.0-alpha-15 For the legacy version DTDs, add comments that FIELD is not supported in 6.x. For 6.x version, eliminate references to FIELD. -- 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

15 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8210) JVM configuration schema

by Brian Stansberry (JIRA)

JVM configuration schema ------------------------ Key: JBAS-8210 URL: https://jira.jboss.org/browse/JBAS-8210 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.0.0.M1 Domain configuration schema elements related to JVM configuration. I believe this is largely done. :) -- 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

15 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2613) Add the version for the wagon extension in the parent pom

by Mauricio Salatino (JIRA)

Add the version for the wagon extension in the parent pom --------------------------------------------------------- Key: JBRULES-2613 URL: https://jira.jboss.org/browse/JBRULES-2613 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mauricio Salatino Assignee: Mark Proctor Fix For: 5.2.0.M1 Just for correctness -- 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

15 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBJCA-396) Maven support

by Jesper Pedersen (JIRA)

Maven support ------------- Key: JBJCA-396 URL: https://jira.jboss.org/browse/JBJCA-396 Project: IronJacamar Issue Type: Task Components: Validator Reporter: Jesper Pedersen Assignee: Jeff Zhang Fix For: 1.0.0.Beta2 We need Maven support for our validator -- 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

15 years, 11 months

2
1
0 / 0

[JBoss JIRA] Closed: (JBAS-8218) Investigate potential issues with no-interface views

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8218?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici closed JBAS-8218. ---------------------------------- Resolution: Out of Date > Investigate potential issues with no-interface views > ---------------------------------------------------- > > Key: JBAS-8218 > URL: https://jira.jboss.org/browse/JBAS-8218 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-8276) Weld Extension vs. Tomcat deployer in JBoss 6

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8276?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici commented on JBAS-8276: ---------------------------------------- Heiko, Could you upload a war for reproducing the issue? Thanks > Weld Extension vs. Tomcat deployer in JBoss 6 > --------------------------------------------- > > Key: JBAS-8276 > URL: https://jira.jboss.org/browse/JBAS-8276 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Affects Versions: 6.0.0.M4 > Reporter: Heiko Braun > Assignee: Marius Bogoevici > > When I deploy a web application that contains CDI beans to JBoss6-M4 I can see that bean deployment being executed two times. First the CDI deployer kicks in, then Tomcat deployer re-deploys the war archive, which causes a second execution of the extension: > 12:20:34,082 INFO [org.jboss.weld.Version] WELD-000900 1.0.1 (SP4) > 12:20:34,516 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Discovered Errai Service: class com.foo.server.HelloWorldService > 12:20:34,564 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Register CDI component as MessageCallback: @Service @ApplicationScoped com.foo.server.HelloWorldService > 12:20:34,583 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy, ctxPath=/funky-app > 12:20:34,720 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] Found BeanManager at java:comp/BeanManager > 12:20:39,776 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] undeploy, ctxPath=/funky-app > 12:20:40,246 INFO [org.jboss.weld.Version] WELD-000900 1.0.1 (SP4) > 12:20:40,733 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Discovered Errai Service: class com.foo.server.HelloWorldService > 12:20:40,844 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Register CDI component as MessageCallback: @Service @ApplicationScoped com.foo.server.HelloWorldService > 12:20:40,856 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy, ctxPath=/funky-app > 12:20:40,929 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] Found BeanManager at java:comp/BeanManager > Shouldn't it be the execution the extension tight to the tomcat deployer lifecycle? I.e. be dependent on it's meta data? -- 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

15 years, 11 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 August 2010