Re: [jboss-as7-dev] Two transaction manager feature requests for CR1
For AS7-775, it is possible it is fixed as I'm testing a branch of my
own that may not include a change. I'll at least verify if it is
working, and then there is still the question of whether we want the
default manifestly in the base configuration files. My feeling is that
any socket port or file that is created by the server should have an
explicit configuration in the domain model.
On 5/13/11 9:36 AM, Brian Stansberry wrote:
Sounds good.
Re: AS7-775, I thought I'd fixed that a few weeks back, but I guess not.
On 5/13/11 11:18 AM, Scott Stark wrote:
> The following two feature requests for improving transaction subsystem configuration
for environments like cloud providers are two I would like to get in next week for CR1. If
there are no objections I'll assign these to myself and work on them.
>
> Specify default values for the urn:jboss:domain:transaction object-store
> ------------------------------------------------------------------------
>
> Key: AS7-775
> URL:https://issues.jboss.org/browse/AS7-775
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Transactions
> Affects Versions: 7.0.0.Beta3
>
>
> Arjuna service creating an anonymous localhost binding outside of standalone.xml
configuration.
>
-----------------------------------------------------------------------------------------------
>
> Key: JBAS-9373
> URL:https://issues.jboss.org/browse/JBAS-9373
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public (Everyone can see)
> Components: Transaction Manager Integration (Arjuna)
> Affects Versions: 7.0.0.Beta3
> Reporter: Scott Stark
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev