March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBREM-236) support for remote connection factory

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-236?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-236. ----------------------------- Resolution: Out of Date Assignee: (was: Tom Elrod) > support for remote connection factory > ------------------------------------- > > Key: JBREM-236 > URL: https://jira.jboss.org/jira/browse/JBREM-236 > Project: JBoss Remoting > Issue Type: Task > Components: general > Reporter: Tom Elrod > Priority: Minor > Fix For: External_issues > > > http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3904970#3904970 > This is for JBAS-1794. -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-407) deploying servlet-invoker.war within JBossAS

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-407?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-407. ----------------------------- Resolution: Out of Date Assignee: (was: Tom Elrod) > deploying servlet-invoker.war within JBossAS > -------------------------------------------- > > Key: JBREM-407 > URL: https://jira.jboss.org/jira/browse/JBREM-407 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: External_issues > Reporter: Tom Elrod > Fix For: External_issues > > > remoting has a servlet-invoker.war that needs to be deployed within JBossAS if is going to have a remoting transport that uses a servlet for the transport (i.e. ejb3 configured to use servlet transport). > Need to determine if should be included by default within JBossAS distribution, and if so, how to get it there (because jboss-remoting.jar is a file kept in repository that is downloaded, but servlet-invoker.war is not and am not sure if can be). -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-322) disconnect error with servlet and http transport (when using ejb3)

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-322?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-322. ----------------------------- Resolution: Out of Date Assignee: (was: Tom Elrod) > disconnect error with servlet and http transport (when using ejb3) > ------------------------------------------------------------------ > > Key: JBREM-322 > URL: https://jira.jboss.org/jira/browse/JBREM-322 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: transport > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > Fix For: External_issues > > > When doing an ejb3 remove using the servlet and http transport, get an error. -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-567) Update ejb3 project for use of 2.0.0 of remoting

by Tom Elrod (JIRA)

Update ejb3 project for use of 2.0.0 of remoting ------------------------------------------------ Key: JBREM-567 URL: http://jira.jboss.com/jira/browse/JBREM-567 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.CR1 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: External_issues Need to make sure 'xmbean-dd="org/jboss/remoting/transport/Connector.xml" is removed from all the service descriptors, as Connector is now a standard mbean and not an xmbean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBREM-565) integration testing for 2.0.0 release

by Tom Elrod (JIRA)

integration testing for 2.0.0 release ------------------------------------- Key: JBREM-565 URL: http://jira.jboss.com/jira/browse/JBREM-565 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.CR1 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.GA (Boon) Need to do some integration testing with new 2.0.0.CR1 of remoting with JBossAS 4 & 5 to make sure everything is working correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBEE-42) remove obsolete javax.annotation classes

by Shelly McGowan (JIRA)

remove obsolete javax.annotation classes ---------------------------------------- Key: JBEE-42 URL: https://jira.jboss.org/jira/browse/JBEE-42 Project: JBoss JavaEE APIs Issue Type: Bug Reporter: Shelly McGowan Assignee: Shelly McGowan Specifically, javax.annotation.Named javax.annotation.NonBinding javax.annotation.Stereotype I have confirmed these are no longer part of the javax.annotation package: http://java.sun.com/javaee/6/docs/api/ and https://glassfish.dev.java.net/issues/show_bug.cgi?id=11016 -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBAS-7818) RMIAdaptor replacement based on JSR160

by Scott Marlow (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7818?page=com.atlassian.jira.plug... ] Scott Marlow commented on JBAS-7818: ------------------------------------ I took a few thread dumps during the ten minute (initial pause) during as boot. http://pastebin.com/jyjVA7pv > RMIAdaptor replacement based on JSR160 > -------------------------------------- > > Key: JBAS-7818 > URL: https://jira.jboss.org/jira/browse/JBAS-7818 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Scott M Stark > Assignee: Scott Marlow > Fix For: JBossAS-6.0.0.M3 > > > A replacement for the proprietary RMIAdaptor is needed that supports authentication, authorization and SSL. -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-7818) RMIAdaptor replacement based on JSR160

by Scott Marlow (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7818?page=com.atlassian.jira.plug... ] Scott Marlow commented on JBAS-7818: ------------------------------------ I tried enabling the sun remote jmx connector but got the "Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl@359ecd80..." problem mentioned on http://community.jboss.org/wiki/UseJDK5JConsole As recommend, I added to run.conf: JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager" JAVA_ARGS="$JAVA_OPTS -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl" JBOSS_CLASSPATH="lib/jboss-logmanager.jar" But, that seems to cause an initial ten second pause before the AS boot echos the "INFO [HornetQServerImpl] live server is starting.." message. Then, right after the "[remoting] JBoss Remoting version 3.1.0.Beta2" console message, I see the "[service] Removing bootstrap log handlers" message. The AS server seems to pause at that point. The last messages on the console are: " 14:33:32,432 INFO [remoting] JBoss Remoting version 3.1.0.Beta2 14:33:32,562 INFO [service] Removing bootstrap log handlers " If I run without the above run.conf changes, I see a normal boot sequence: " 14:37:07,974 INFO [remoting] JBoss Remoting version 3.1.0.Beta2 14:37:08,083 INFO [TomcatDeployment] deploy, ctxPath=/ 14:37:08,165 INFO [service] Removing bootstrap log handlers 14:37:08,205 INFO [org.jboss.system.server.profileservice.ProfileServiceBootstrap] Loading profile: ProfileKey@1c5ab93[domain=default, server=default, name=default] 14:37:08,215 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080 14:37:08,229 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 14:37:08,229 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.SNAPSHOT "Neo"] Started in 18s:284ms " > RMIAdaptor replacement based on JSR160 > -------------------------------------- > > Key: JBAS-7818 > URL: https://jira.jboss.org/jira/browse/JBAS-7818 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Scott M Stark > Assignee: Scott Marlow > Fix For: JBossAS-6.0.0.M3 > > > A replacement for the proprietary RMIAdaptor is needed that supports authentication, authorization and SSL. -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBXB-244) don't use repeatable handlers for terms inside unordered sequences

by Alexey Loubyansky (JIRA)

don't use repeatable handlers for terms inside unordered sequences ------------------------------------------------------------------ Key: JBXB-244 URL: https://jira.jboss.org/jira/browse/JBXB-244 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-2.0.2.Beta5 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA People are asking for over-the-edge freedom in (un)ordering their elements in xml. Not only terms of unordered sequences should be allowed to appear in any order but also repeatable terms should be allowed to be spread and mixed with other terms, i.e. not necessarily appear in a sequence. Which of course breaks collecting and setting values by repeatable particle handlers. So, the only way to have repeatable terms collected correctly is to disable repeatable particle handlers and add items directly to the properties. -- 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

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBXB-242) binding repeatable elements into model group all should fail

by Alexey Loubyansky (JIRA)

binding repeatable elements into model group all should fail ------------------------------------------------------------ Key: JBXB-242 URL: https://jira.jboss.org/jira/browse/JBXB-242 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.2.Beta5 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA AllBinding currently silently accepts repeatable elements which it shouldn't according to the spec. Schema Component Constraint: All Group Limited When a model group has {compositor} all, then all of the following must be true: 1 It appears only as the value of one or both of the following properties: 1.1 the {model group} property of a model group definition. 1.2 the {term} property of a particle with {max occurs}=1which is part of a pair which constitutes the {content type} of a complex type definition. 2 The {max occurs} of all the particles in the {particles} of the group must be 0 or 1. -- 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

14 years, 10 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010