September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8457) Encoding not properly supported for domain.xml

by David Lloyd (JIRA)

Encoding not properly supported for domain.xml ---------------------------------------------- Key: JBAS-8457 URL: https://jira.jboss.org/browse/JBAS-8457 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: David Lloyd Fix For: 7.0.0.M1 The created XML stream reader is created over a Reader rather than an InputStream, thus defeating the native XML encoding detection strategy and requiring domain.xml to be encoded with the platform encoding. Use an InputStream instead. -- 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

14 years

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-6477) Migrate to JBoss Remoting 3

by David Lloyd (JIRA)

Migrate to JBoss Remoting 3 --------------------------- Key: JBAS-6477 URL: https://jira.jboss.org/jira/browse/JBAS-6477 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Remoting Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-5.1.0.GA Parent task for Remoting 3 migration tasks. Optimistically targeted for 5.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

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-8177) Messaging subsystem configuration schema

by Brian Stansberry (JIRA)

Messaging subsystem configuration schema ---------------------------------------- Key: JBAS-8177 URL: https://jira.jboss.org/browse/JBAS-8177 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Domain model configuration schema related to Messaging. -- 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

14 years

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8178) "Standalone server" schema

by Brian Stansberry (JIRA)

"Standalone server" schema -------------------------- Key: JBAS-8178 URL: https://jira.jboss.org/browse/JBAS-8178 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 Schema for the "standalone server" configuration variant. Suppress extraneous concepts like domain.xml vs. host.xml, server-group etc. Note that HA clustering of standalone servers is supported. -- 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

14 years

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8180) Interface and socket configuration schema

by Brian Stansberry (JIRA)

Interface and socket configuration schema ----------------------------------------- Key: JBAS-8180 URL: https://jira.jboss.org/browse/JBAS-8180 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.M1 Domain model schema for declaring interfaces and associating them with IP addresses, plus configuring socket bindings. -- 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

14 years

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8176) Web server configuration schema

by Brian Stansberry (JIRA)

Web server configuration schema ------------------------------- Key: JBAS-8176 URL: https://jira.jboss.org/browse/JBAS-8176 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Remy Maucherat Fix For: 7.0.0.M1 Domain model configuration schema for JBoss Web subsystem. -- 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

14 years

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8175) JCA related domain schema

by Brian Stansberry (JIRA)

JCA related domain schema ------------------------- Key: JBAS-8175 URL: https://jira.jboss.org/browse/JBAS-8175 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management, JCA service Reporter: Brian Stansberry Assignee: Stefano Maestri Fix For: 7.0.0.M1 Domain model schema for JCA-related elements (datasources, resource adapters etc) Initially assigned to Stefano as I understand he's the one working on this. -- 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

14 years

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8190) Standalone server configuration object model

by Brian Stansberry (JIRA)

Standalone server configuration object model -------------------------------------------- Key: JBAS-8190 URL: https://jira.jboss.org/browse/JBAS-8190 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 Object model that represents the standalone configuration schema. Note that it's quite possible that there will not be a separate, distinct object model for this and the object model that represents a regular Server in a Domain will suffice. Or perhaps we'll provide a class that provides a view onto the regular Domain/ServerGroup/Server object model for use by clients (e.g. embedded AS users) who want a simplified view. Key thing is we don't want every subsystem that needs to understand the domain configuration model to have to understand both the standalone and the full variant of it. -- 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

14 years

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8259) Socket based communication between ServerManager and ProcessManager

by Brian Stansberry (JIRA)

Socket based communication between ServerManager and ProcessManager ------------------------------------------------------------------- Key: JBAS-8259 URL: https://jira.jboss.org/browse/JBAS-8259 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Default communication mechanism between SM and PM is via stdio. This should almost always be fine, since we use the jboss-stdio lib to capture application usage of stdio and preserve the original streams for our own use. But there is a slight possibility that an extension module running in the SM will use JNI, which can pollute the stdio streams. So, we need an option to allow users to configure SM-PM communication via sockets. (The same issue applies for Server-PM and Server-SM communication, but there the SM can parse host.xml and get configuration from it, so the details are different from this SM-PM use case.) Tasks: 1) Put SM-PM communication behind an abstraction 2) Implement stdio-based and socket-based versions of the abstraction 3) Modify process manager module to accept PM socket configuration via command line params 4) PM passes it's socket configuration to SM via command line when it starts PM 5) Decide how to configure SM's socket -- via host.xml? (Note SM needs a socket for communication with the DC -- use that?) -- 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

14 years

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8311) Establish a full Sever Manager to Server communication protocol

by John Bailey (JIRA)

Establish a full Sever Manager to Server communication protocol ---------------------------------------------------------------- Key: JBAS-8311 URL: https://jira.jboss.org/browse/JBAS-8311 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: John Bailey Assignee: John Bailey Fix For: 7.0.0.M1 -- 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

14 years

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010