problem with the classloader, not able to load a JDBC driver

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

problem with the classloader, not able to load a JDBC driver

Flemming Harms
Hi

I'm trying to finish https://issues.jboss.org/browse/AS7-1371 but I ran into a problem with the class loader. I need way to load the class for a specified JDBC driver, but I can't seem to figure out how to make it available on the classpath too my authentication service.

I try to load the connection class like this, and testing it with the existing H2 JDBC driver:
ClassLoader original = null;
        try {
            original = Thread.currentThread().getContextClassLoader();
            if (original != null) {
                Thread.currentThread().setContextClassLoader(null);
            }
            Class.forName(this.driver).newInstance();
        } finally {
            if (original != null) {
                Thread.currentThread().setContextClassLoader(original);
            }
}
 
The user can setup a outbound connection to a database for authentication, by using the configuration below

 <security-realm name="ManagementRealm">
      <authentication>
           <local default-user="$local"/>
           <database connection="db" plain-text="true">
             <!-- simple-select-users table="users" username-field="user" password-field="password"/ -->
             <sql-select-users sql="select user,password from users where user = ?" />
           </database>
      </authentication>
</security-realm>

<outbound-connections>
        <database>
            <connection driver="org.h2.jdbcx.JdbcDataSource" name="db" url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa" password="" min-pool-size="10" max-pool-size="20" />
        </database>
</outbound-connections>

Any suggestions how to solve this?

Thanks!

br
Flemming

_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: problem with the classloader, not able to load a JDBC driver

Flemming Harms
I found a solution to my problem. Had to update the xsd schema with an extra attribute "module" and then user need pack his JDBC driver as module.

I use the code below to load the model and the driver class.

Class<?> driverClass = Module.loadClassFromCallerModuleLoader(ModuleIdentifier.fromString(moduleName),  driver);
driverClass.newInstance();

<outbound-connections>
        <database>
            <connection module="com.h2database.h2" driver="org.h2.jdbcx.JdbcDataSource" name="db" url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa" password="" min-pool-size="10" max-pool-size="20" />
        </database>
</outbound-connections>

Does it make sense?

Thanks

2012/7/20 Flemming Harms <[hidden email]>
Hi

I'm trying to finish https://issues.jboss.org/browse/AS7-1371 but I ran into a problem with the class loader. I need way to load the class for a specified JDBC driver, but I can't seem to figure out how to make it available on the classpath too my authentication service.

I try to load the connection class like this, and testing it with the existing H2 JDBC driver:
ClassLoader original = null;
        try {
            original = Thread.currentThread().getContextClassLoader();
            if (original != null) {
                Thread.currentThread().setContextClassLoader(null);
            }
            Class.forName(this.driver).newInstance();
        } finally {
            if (original != null) {
                Thread.currentThread().setContextClassLoader(original);
            }
}
 
The user can setup a outbound connection to a database for authentication, by using the configuration below

 <security-realm name="ManagementRealm">
      <authentication>
           <local default-user="$local"/>
           <database connection="db" plain-text="true">
             <!-- simple-select-users table="users" username-field="user" password-field="password"/ -->
             <sql-select-users sql="select user,password from users where user = ?" />
           </database>
      </authentication>
</security-realm>

<outbound-connections>
        <database>
            <connection driver="org.h2.jdbcx.JdbcDataSource" name="db" url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa" password="" min-pool-size="10" max-pool-size="20" />
        </database>
</outbound-connections>

Any suggestions how to solve this?

Thanks!

br
Flemming


_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: problem with the classloader, not able to load a JDBC driver

Jesper Pedersen
On 07/23/2012 11:42 AM, Flemming Harms wrote:

> I found a solution to my problem. Had to update the xsd schema with an
> extra attribute "module" and then user need pack his JDBC driver as module.
>
> I use the code below to load the model and the driver class.
>
> Class<?> driverClass =
> Module.loadClassFromCallerModuleLoader(ModuleIdentifier.fromString(moduleName),
> driver);
> driverClass.newInstance();
>
> <outbound-connections>
>          <database>
>              <connection module="com.h2database.h2"
> driver="org.h2.jdbcx.JdbcDataSource" name="db"
> url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa" password=""
> min-pool-size="10" max-pool-size="20" />
>          </database>
> </outbound-connections>
>
> Does it make sense?

The -ds.xml functionality uses the module through the <driver> tag, so
this would be similar.

Things to watch out for is of course the password attribute - it should
at least support the vault mechanism I would say.

Best regards,
  Jesper
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: problem with the classloader, not able to load a JDBC driver

jtgreene
Administrator
In reply to this post by Flemming Harms
That's the correct solution for this.

On 7/23/12 10:42 AM, Flemming Harms wrote:

> I found a solution to my problem. Had to update the xsd schema with an
> extra attribute "module" and then user need pack his JDBC driver as module.
>
> I use the code below to load the model and the driver class.
>
> Class<?> driverClass =
> Module.loadClassFromCallerModuleLoader(ModuleIdentifier.fromString(moduleName),
> driver);
> driverClass.newInstance();
>
> <outbound-connections>
>          <database>
>              <connection module="com.h2database.h2"
> driver="org.h2.jdbcx.JdbcDataSource" name="db"
> url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa" password=""
> min-pool-size="10" max-pool-size="20" />
>          </database>
> </outbound-connections>
>
> Does it make sense?
>
> Thanks
>
> 2012/7/20 Flemming Harms <[hidden email]
> <mailto:[hidden email]>>
>
>     Hi
>
>     I'm trying to finish https://issues.jboss.org/browse/AS7-1371 but I
>     ran into a problem with the class loader. I need way to load the
>     class for a specified JDBC driver, but I can't seem to figure out
>     how to make it available on the classpath too my authentication service.
>
>     I try to load the connection class like this, and testing it with
>     the existing H2 JDBC driver:
>     ClassLoader original = null;
>              try {
>                  original = Thread.currentThread().getContextClassLoader();
>                  if (original != null) {
>                      Thread.currentThread().setContextClassLoader(null);
>                  }
>                  Class.forName(this.driver).newInstance();
>              } finally {
>                  if (original != null) {
>                      Thread.currentThread().setContextClassLoader(original);
>                  }
>     }
>
>     The user can setup a outbound connection to a database for
>     authentication, by using the configuration below
>
>       <security-realm name="ManagementRealm">
>            <authentication>
>                 <local default-user="$local"/>
>                 <database connection="db" plain-text="true">
>                   <!-- simple-select-users table="users"
>     username-field="user" password-field="password"/ -->
>                   <sql-select-users sql="select user,password from users
>     where user = ?" />
>                 </database>
>            </authentication>
>     </security-realm>
>
>     <outbound-connections>
>              <database>
>                  <connection driver="org.h2.jdbcx.JdbcDataSource"
>     name="db" url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa"
>     password="" min-pool-size="10" max-pool-size="20" />
>              </database>
>     </outbound-connections>
>
>     Any suggestions how to solve this?
>
>     Thanks!
>
>     br
>     Flemming
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>


--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: problem with the classloader, not able to load a JDBC driver

jtgreene
Administrator
In reply to this post by Jesper Pedersen
On 7/23/12 10:51 AM, Jesper Pedersen wrote:

> On 07/23/2012 11:42 AM, Flemming Harms wrote:
>> I found a solution to my problem. Had to update the xsd schema with an
>> extra attribute "module" and then user need pack his JDBC driver as module.
>>
>> I use the code below to load the model and the driver class.
>>
>> Class<?> driverClass =
>> Module.loadClassFromCallerModuleLoader(ModuleIdentifier.fromString(moduleName),
>> driver);
>> driverClass.newInstance();
>>
>> <outbound-connections>
>>           <database>
>>               <connection module="com.h2database.h2"
>> driver="org.h2.jdbcx.JdbcDataSource" name="db"
>> url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa" password=""
>> min-pool-size="10" max-pool-size="20" />
>>           </database>
>> </outbound-connections>
>>
>> Does it make sense?
>
> The -ds.xml functionality uses the module through the <driver> tag, so
> this would be similar.
>
> Things to watch out for is of course the password attribute - it should
> at least support the vault mechanism I would say.

If you make the attribute definition have expressions=true, it will
automatically enable vault support.

--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: problem with the classloader, not able to load a JDBC driver

Tomaž Cerar-2


On Mon, Jul 23, 2012 at 5:58 PM, Jason T. Greene <[hidden email]> wrote:
On 7/23/12 10:51 AM, Jesper Pedersen wrote:
> On 07/23/2012 11:42 AM, Flemming Harms wrote:
>> I found a solution to my problem. Had to update the xsd schema with an
>> extra attribute "module" and then user need pack his JDBC driver as module.
>>
>> I use the code below to load the model and the driver class.
>>
>> Class<?> driverClass =
>> Module.loadClassFromCallerModuleLoader(ModuleIdentifier.fromString(moduleName),
>> driver);
>> driverClass.newInstance();
>>
>> <outbound-connections>
>>           <database>
>>               <connection module="com.h2database.h2"
>> driver="org.h2.jdbcx.JdbcDataSource" name="db"
>> url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa" password=""
>> min-pool-size="10" max-pool-size="20" />
>>           </database>
>> </outbound-connections>
>>
>> Does it make sense?
>
> The -ds.xml functionality uses the module through the <driver> tag, so
> this would be similar.
>
> Things to watch out for is of course the password attribute - it should
> at least support the vault mechanism I would say.

If you make the attribute definition have expressions=true, it will
automatically enable vault support.

given that you use AD.parseAndSetParameter() when parsing and setting field and  AD.resolveModelAttribute() when getting data from model
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: problem with the classloader, not able to load a JDBC driver

Flemming Harms
Thanks!

I had to do one more thing to make it work with the module class loader, since the database driver was loaded in it's own class loader and it was not known to the current class loader I had to find a way to make it available

I solve it by wrapping the driver in my own class and register the driver to the DriverManager

Like this :
 DriverManager.registerDriver(new DatabaseDriverWrapper(driver));
 DriverManager.getConnection(url, user, password);

2012/7/23 Tomaž Cerar <[hidden email]>


On Mon, Jul 23, 2012 at 5:58 PM, Jason T. Greene <[hidden email]> wrote:
On 7/23/12 10:51 AM, Jesper Pedersen wrote:
> On 07/23/2012 11:42 AM, Flemming Harms wrote:
>> I found a solution to my problem. Had to update the xsd schema with an
>> extra attribute "module" and then user need pack his JDBC driver as module.
>>
>> I use the code below to load the model and the driver class.
>>
>> Class<?> driverClass =
>> Module.loadClassFromCallerModuleLoader(ModuleIdentifier.fromString(moduleName),
>> driver);
>> driverClass.newInstance();
>>
>> <outbound-connections>
>>           <database>
>>               <connection module="com.h2database.h2"
>> driver="org.h2.jdbcx.JdbcDataSource" name="db"
>> url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa" password=""
>> min-pool-size="10" max-pool-size="20" />
>>           </database>
>> </outbound-connections>
>>
>> Does it make sense?
>
> The -ds.xml functionality uses the module through the <driver> tag, so
> this would be similar.
>
> Things to watch out for is of course the password attribute - it should
> at least support the vault mechanism I would say.

If you make the attribute definition have expressions=true, it will
automatically enable vault support.

given that you use AD.parseAndSetParameter() when parsing and setting field and  AD.resolveModelAttribute() when getting data from model
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev



_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: problem with the classloader, not able to load a JDBC driver

jtgreene
Administrator
I can't remember if I replied to this one or not, but a better solution
is to use the Driver class directly. We should avoid sticking random
things in the global registry which might even end up containing
conflicting values.

On 7/24/12 7:53 AM, Flemming Harms wrote:

> Thanks!
>
> I had to do one more thing to make it work with the module class loader,
> since the database driver was loaded in it's own class loader and it was
> not known to the current class loader I had to find a way to make it
> available
>
> I solve it by wrapping the driver in my own class and register the
> driver to the DriverManager
>
> Like this :
>   DriverManager.registerDriver(new DatabaseDriverWrapper(driver));
>   DriverManager.getConnection(url, user, password);
>
> 2012/7/23 Tomaž Cerar <[hidden email] <mailto:[hidden email]>>
>
>
>
>     On Mon, Jul 23, 2012 at 5:58 PM, Jason T. Greene
>     <[hidden email] <mailto:[hidden email]>> wrote:
>
>         On 7/23/12 10:51 AM, Jesper Pedersen wrote:
>          > On 07/23/2012 11:42 AM, Flemming Harms wrote:
>          >> I found a solution to my problem. Had to update the xsd
>         schema with an
>          >> extra attribute "module" and then user need pack his JDBC
>         driver as module.
>          >>
>          >> I use the code below to load the model and the driver class.
>          >>
>          >> Class<?> driverClass =
>          >>
>         Module.loadClassFromCallerModuleLoader(ModuleIdentifier.fromString(moduleName),
>          >> driver);
>          >> driverClass.newInstance();
>          >>
>          >> <outbound-connections>
>          >>           <database>
>          >>               <connection module="com.h2database.h2"
>          >> driver="org.h2.jdbcx.JdbcDataSource" name="db"
>          >> url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa"
>         password=""
>          >> min-pool-size="10" max-pool-size="20" />
>          >>           </database>
>          >> </outbound-connections>
>          >>
>          >> Does it make sense?
>          >
>          > The -ds.xml functionality uses the module through the
>         <driver> tag, so
>          > this would be similar.
>          >
>          > Things to watch out for is of course the password attribute -
>         it should
>          > at least support the vault mechanism I would say.
>
>         If you make the attribute definition have expressions=true, it will
>         automatically enable vault support.
>
>     given that you use AD.parseAndSetParameter() when parsing and
>     setting field and  AD.resolveModelAttribute() when getting data from
>     model
>
>         --
>         Jason T. Greene
>         JBoss AS Lead / EAP Platform Architect
>         JBoss, a division of Red Hat
>         _______________________________________________
>         jboss-as7-dev mailing list
>         [hidden email] <mailto:[hidden email]>
>         https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
>
>     _______________________________________________
>     jboss-as7-dev mailing list
>     [hidden email] <mailto:[hidden email]>
>     https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>


--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: problem with the classloader, not able to load a JDBC driver

Flemming Harms
Jason,

Just so I'm sure I follow you, what you suggestion is solution like this, right?

Properties cg = new Properties();
cg.put("user", user);
cg.put("password", password);
Connection conn = driverClass.connect(url, cg);

2012/7/31 Jason T. Greene <[hidden email]>
I can't remember if I replied to this one or not, but a better solution is to use the Driver class directly. We should avoid sticking random things in the global registry which might even end up containing conflicting values.


On 7/24/12 7:53 AM, Flemming Harms wrote:
Thanks!

I had to do one more thing to make it work with the module class loader,
since the database driver was loaded in it's own class loader and it was
not known to the current class loader I had to find a way to make it
available

I solve it by wrapping the driver in my own class and register the
driver to the DriverManager

Like this :
  DriverManager.registerDriver(new DatabaseDriverWrapper(driver));
  DriverManager.getConnection(url, user, password);

2012/7/23 Tomaž Cerar <[hidden email] <mailto:[hidden email]>>




    On Mon, Jul 23, 2012 at 5:58 PM, Jason T. Greene
    <[hidden email] <mailto:[hidden email]>> wrote:

        On 7/23/12 10:51 AM, Jesper Pedersen wrote:
         > On 07/23/2012 11:42 AM, Flemming Harms wrote:
         >> I found a solution to my problem. Had to update the xsd
        schema with an
         >> extra attribute "module" and then user need pack his JDBC
        driver as module.
         >>
         >> I use the code below to load the model and the driver class.
         >>
         >> Class<?> driverClass =
         >>
        Module.loadClassFromCallerModuleLoader(ModuleIdentifier.fromString(moduleName),
         >> driver);
         >> driverClass.newInstance();
         >>
         >> <outbound-connections>
         >>           <database>
         >>               <connection module="com.h2database.h2"
         >> driver="org.h2.jdbcx.JdbcDataSource" name="db"
         >> url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa"
        password=""
         >> min-pool-size="10" max-pool-size="20" />
         >>           </database>
         >> </outbound-connections>
         >>
         >> Does it make sense?
         >
         > The -ds.xml functionality uses the module through the
        <driver> tag, so
         > this would be similar.
         >
         > Things to watch out for is of course the password attribute -
        it should
         > at least support the vault mechanism I would say.

        If you make the attribute definition have expressions=true, it will
        automatically enable vault support.

    given that you use AD.parseAndSetParameter() when parsing and
    setting field and  AD.resolveModelAttribute() when getting data from
    model

        --
        Jason T. Greene
        JBoss AS Lead / EAP Platform Architect
        JBoss, a division of Red Hat
        _______________________________________________
        jboss-as7-dev mailing list
        [hidden email] <mailto:[hidden email]>

        https://lists.jboss.org/mailman/listinfo/jboss-as7-dev



    _______________________________________________
    jboss-as7-dev mailing list
    [hidden email] <mailto:[hidden email]>

    https://lists.jboss.org/mailman/listinfo/jboss-as7-dev




_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev



--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat


_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: problem with the classloader, not able to load a JDBC driver

Jason T. Greene
Right that's correct.

Sent from my iPhone

On Aug 1, 2012, at 2:19 AM, Flemming Harms <[hidden email]> wrote:

Jason,

Just so I'm sure I follow you, what you suggestion is solution like this, right?

Properties cg = new Properties();
cg.put("user", user);
cg.put("password", password);
Connection conn = driverClass.connect(url, cg);

2012/7/31 Jason T. Greene <[hidden email]>
I can't remember if I replied to this one or not, but a better solution is to use the Driver class directly. We should avoid sticking random things in the global registry which might even end up containing conflicting values.


On 7/24/12 7:53 AM, Flemming Harms wrote:
Thanks!

I had to do one more thing to make it work with the module class loader,
since the database driver was loaded in it's own class loader and it was
not known to the current class loader I had to find a way to make it
available

I solve it by wrapping the driver in my own class and register the
driver to the DriverManager

Like this :
  DriverManager.registerDriver(new DatabaseDriverWrapper(driver));
  DriverManager.getConnection(url, user, password);

2012/7/23 Tomaž Cerar <[hidden email] <mailto:[hidden email]>>




    On Mon, Jul 23, 2012 at 5:58 PM, Jason T. Greene
    <[hidden email] <mailto:[hidden email]>> wrote:

        On 7/23/12 10:51 AM, Jesper Pedersen wrote:
         > On 07/23/2012 11:42 AM, Flemming Harms wrote:
         >> I found a solution to my problem. Had to update the xsd
        schema with an
         >> extra attribute "module" and then user need pack his JDBC
        driver as module.
         >>
         >> I use the code below to load the model and the driver class.
         >>
         >> Class<?> driverClass =
         >>
        Module.loadClassFromCallerModuleLoader(ModuleIdentifier.fromString(moduleName),
         >> driver);
         >> driverClass.newInstance();
         >>
         >> <outbound-connections>
         >>           <database>
         >>               <connection module="com.h2database.h2"
         >> driver="org.h2.jdbcx.JdbcDataSource" name="db"
         >> url="jdbc:h2:/tmp/test;DB_CLOSE_DELAY=-1" username="sa"
        password=""
         >> min-pool-size="10" max-pool-size="20" />
         >>           </database>
         >> </outbound-connections>
         >>
         >> Does it make sense?
         >
         > The -ds.xml functionality uses the module through the
        <driver> tag, so
         > this would be similar.
         >
         > Things to watch out for is of course the password attribute -
        it should
         > at least support the vault mechanism I would say.

        If you make the attribute definition have expressions=true, it will
        automatically enable vault support.

    given that you use AD.parseAndSetParameter() when parsing and
    setting field and  AD.resolveModelAttribute() when getting data from
    model

        --
        Jason T. Greene
        JBoss AS Lead / EAP Platform Architect
        JBoss, a division of Red Hat
        _______________________________________________
        jboss-as7-dev mailing list
        [hidden email] <mailto:[hidden email]>

        https://lists.jboss.org/mailman/listinfo/jboss-as7-dev



    _______________________________________________
    jboss-as7-dev mailing list
    [hidden email] <mailto:[hidden email]>

    https://lists.jboss.org/mailman/listinfo/jboss-as7-dev




_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev



--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat


_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev