8:58 a.m.
WRT: https://jira.jboss.org/jira/browse/JBAS-5897
I'd like to include the "web profile"
in the open source distribution.
We would document this as "experimental", i.e.
the configuration is likely to change before
it is stabilised.
That's because it is not quite finished yet,
there's still issues with making jta/jca optional,
factoring out the jpa deployer from ejb3 and
the http invoker currently required to make
shutdown.sh work.
Including the web profile easier now we have the shared libraries
since it won't increase the size of the
distribution anything like as much as before.
I propose that you should be able to start it using:
./run.sh -c web
The web profile currently looks like this:
deployers:
alias-deployers-jboss-beans.xml
ejb3.deployer
jboss-aop-jboss5.deployer
jboss-jca.deployer
jbossweb.deployer
metadata-deployer-jboss-beans.xml
security-deployer-jboss-beans.xml
deploy:
hsqldb-ds.xml
http-invoker.sar
jboss-local-jdbc.rar
jbossweb.sar
jboss-xa-jdbc.rar
jca-jboss-beans.xml
jmx-console.war
jmx-invoker-service.xml
ROOT.war
security
transaction-jboss-beans.xml
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
9:38 a.m.
How much time does it takes to start?
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-
development-bounces(a)lists.jboss.org] On Behalf Of Adrian Brock
Sent: lundi, 10 novembre 2008 15:59
To: JBoss.org development list
Subject: [jboss-dev] web profile in jboss5?
WRT: https://jira.jboss.org/jira/browse/JBAS-5897
I'd like to include the "web profile"
in the open source distribution.
We would document this as "experimental", i.e.
the configuration is likely to change before
it is stabilised.
That's because it is not quite finished yet,
there's still issues with making jta/jca optional,
factoring out the jpa deployer from ejb3 and
the http invoker currently required to make
shutdown.sh work.
Including the web profile easier now we have the shared libraries
since it won't increase the size of the
distribution anything like as much as before.
I propose that you should be able to start it using:
./run.sh -c web
The web profile currently looks like this:
deployers:
alias-deployers-jboss-beans.xml
ejb3.deployer
jboss-aop-jboss5.deployer
jboss-jca.deployer
jbossweb.deployer
metadata-deployer-jboss-beans.xml
security-deployer-jboss-beans.xml
deploy:
hsqldb-ds.xml
http-invoker.sar
jboss-local-jdbc.rar
jbossweb.sar
jboss-xa-jdbc.rar
jca-jboss-beans.xml
jmx-console.war
jmx-invoker-service.xml
ROOT.war
security
transaction-jboss-beans.xml
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
9:43 a.m.
On Mon, 2008-11-10 at 16:38 +0100, Sacha Labourey wrote:
How much time does it takes to start?
On my laptop about 25 seconds.
Of that about 10 seconds is the bootstrap processing:
16:14:37,582 INFO [ServerImpl] Starting JBoss (Microcontainer)...
<snip/>
16:14:45,384 INFO [MetaDataAwareProfile] Using profile
root:/home/ejort/development/jboss-head/build/output/jboss-5.0.0.GA/server/web-profile
which is almost certainly the initial hot deployment scanning
of deployers and deploy?
The deployers times still show unnecessary annotation scanning and ejb3
processing (biggest hits - times in milli-seconds):
BeanMetaDataDeployer 7193 (pojos)
FilteredAnnotationEnvironmentDeployer 5455 (annotation scanning)
ServiceDeployer 2655 (jmx)
AbstractLevelClassLoaderSystemDeployer 1387 (classloader)
Ejb3Deployer 1121 (ejb3 ??? - there are none)
In terms of real deployments the big hits are:
deploy/transaction-jboss-beans.xml 2576 (jta)
conf/jboss-service.xml 2079 (jndi???)
deployers/jboss-jca.deployer/ 1696 (jca)
deployers/ejb3.deployer/ 1662 (ejb3)
deploy/jbossweb.sar/ 999 (web runtime)
deployers/jbossweb.deployer 894 (web deployment)
deploy/hsqldb-ds.xml 667 (hypersonic)
...
And the vast majority of the annotation scanning comes from
looking at jbossweb.sar (with all the jars it contains).
So not much has changed since last time I posted on this. :-(
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-
> development-bounces(a)lists.jboss.org] On Behalf Of Adrian Brock
> Sent: lundi, 10 novembre 2008 15:59
> To: JBoss.org development list
> Subject: [jboss-dev] web profile in jboss5?
>
> WRT: https://jira.jboss.org/jira/browse/JBAS-5897
>
> I'd like to include the "web profile"
> in the open source distribution.
>
> We would document this as "experimental", i.e.
> the configuration is likely to change before
> it is stabilised.
>
> That's because it is not quite finished yet,
> there's still issues with making jta/jca optional,
> factoring out the jpa deployer from ejb3 and
> the http invoker currently required to make
> shutdown.sh work.
>
> Including the web profile easier now we have the shared libraries
> since it won't increase the size of the
> distribution anything like as much as before.
>
> I propose that you should be able to start it using:
> ./run.sh -c web
>
> The web profile currently looks like this:
>
> deployers:
> alias-deployers-jboss-beans.xml
> ejb3.deployer
> jboss-aop-jboss5.deployer
> jboss-jca.deployer
> jbossweb.deployer
> metadata-deployer-jboss-beans.xml
> security-deployer-jboss-beans.xml
>
> deploy:
> hsqldb-ds.xml
> http-invoker.sar
> jboss-local-jdbc.rar
> jbossweb.sar
> jboss-xa-jdbc.rar
> jca-jboss-beans.xml
> jmx-console.war
> jmx-invoker-service.xml
> ROOT.war
> security
> transaction-jboss-beans.xml
>
> --
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Adrian Brock
> Chief Scientist
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
6:23 a.m.
Instead of excluding all of our deploy/ deployments,
which of them should actually be scanned for annotations?
Ales Justin wrote:
> And the vast majority of the annotation scanning comes from
looking at
> jbossweb.sar (with all the jars it contains).
>
> So not much has changed since last time I posted on this. :-(
I'll add a set of excluded files we don't want to scan,
jbossweb.sar being one of them. ;-)
6:10 a.m.
On Tue, 2008-11-11 at 13:23 +0100, Ales Justin wrote:
Instead of excluding all of our deploy/ deployments,
which of them should actually be scanned for annotations?
A better approach would be to have jboss deployment
descriptor (an attachment) that specifies which parts of the
deployment (classpath) you scan.
For javaee deployments this would be populated from the
relevant dds, i.e. ejb-jar.xml and web.xml
according the rules from the spec.
For anything else, we ignore scanning unless this
deployment descriptor says to do it.
i.e. sar files won't be scanned unless you say
to do so by adding the new dds.
Ales Justin wrote:
>> And the vast majority of the annotation scanning comes from looking at
>> jbossweb.sar (with all the jars it contains).
>>
>> So not much has changed since last time I posted on this. :-(
>
> I'll add a set of excluded files we don't want to scan,
> jbossweb.sar being one of them. ;-)
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
6:15 a.m.
On Tue, 2008-11-11 at 13:10 +0100, Adrian Brock wrote:
For anything else, we ignore scanning unless this
deployment descriptor says to do it.
i.e. sar files won't be scanned unless you say
to do so by adding the new dds.
Or somebody writes a deployer that changes the default
rule. i.e. it creates the new dds for whatever rules
they want.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
6:58 a.m.
I've actually added [VFS]DeploymentUnitFilter to AnnEnvDeployer,
public interface [VFS]DeploymentUnitFilter {
boolean accepts([VFS]DeploymentUnit deploymentUnit);
}
so this is completely free to impl whatever we decide.
Currently I'm just excluding certain files.
And since [Filtered]AnnEvnDeployer already takes different filters
(resource and recursion), you can even add those (to DU::attachments),
if you decide that deployment needs to be scanned.
protected <T> T getFilter(DeploymentUnit unit, Class<T>
expectedClass, String suffix, T defaultValue)
{
String name = expectedClass.getName() + "." + (suffix != null ?
suffix : "");
T result = unit.getAttachment(name, expectedClass);
if (result == null)
result = defaultValue;
return result;
}
;-)
Adrian Brock wrote:
On Tue, 2008-11-11 at 13:10 +0100, Adrian Brock wrote:
> For anything else, we ignore scanning unless this
> deployment descriptor says to do it.
> i.e. sar files won't be scanned unless you say
> to do so by adding the new dds.
Or somebody writes a deployer that changes the default
rule. i.e. it creates the new dds for whatever rules
they want.
7 a.m.
On Tue, 2008-11-11 at 13:58 +0100, Ales Justin wrote:
I've actually added [VFS]DeploymentUnitFilter to AnnEnvDeployer,
public interface [VFS]DeploymentUnitFilter {
boolean accepts([VFS]DeploymentUnit deploymentUnit);
}
so this is completely free to impl whatever we decide.
Currently I'm just excluding certain files.
That's nothing like as easy as modifying your deployment
to add an e.g. META-INF/jboss-scanning.xml
Also how do you override the rules from the
profile service/management console?
e.g. I only want to scan one jar in my big archive.
When it comes to policy decisions, declarative is best.
In this case, it means being able to say exactly what jars you
want to scan in this deployment.
Configuration on a deployer should be for when you
have a general rule that is different to the default rule.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
7:53 a.m.
That's nothing like as easy as modifying your deployment
to add an e.g. META-INF/jboss-scanning.xml
By default we should still scan everything,
as users mostly expect that things just work, no extra dds.
I can add this, but I doubt it's gonna be widely used.
Perhaps the .sar example you gave earlier.
How exactly do you get this kind of info from ejb-jar.xml or web.xml?
--> let's move this discussion to the forum ...
Also how do you override the rules from the
profile service/management console?
e.g. I only want to scan one jar in my big archive.
By adding predetermined DU filter attachment + proper delegate DU filter
on AnnEnvDeployer?
7:52 a.m.
On Tue, 2008-11-11 at 14:53 +0100, Ales Justin wrote:
> That's nothing like as easy as modifying your deployment
> to add an e.g. META-INF/jboss-scanning.xml
By default we should still scan everything,
as users mostly expect that things just work, no extra dds.
That's funny, because I wouldn't expect jbossweb.sar
(which is the webserver) to be scanned for javaee annotations?
I can add this, but I doubt it's gonna be widely used.
Perhaps the .sar example you gave earlier.
If we get the defaults correct, then maybe 5% will use it.
Probably mainly as an optimization for large deployments where
only a few jars need to be scanned
or only a few classes within a large jar?
How exactly do you get this kind of info from ejb-jar.xml or web.xml?
RTFS (read the fine spec :-)
--> let's move this discussion to the forum ...
I'm not really that interested in the discussion beyond removing
~10 seconds of useless waiting everytime I reboot JBoss5.
The rest of the discussion is just about how simple/intuitive
you can make it (I mean for the user/admin rather than yourself :-).
> Also how do you override the rules from the
> profile service/management console?
> e.g. I only want to scan one jar in my big archive.
By adding predetermined DU filter attachment + proper delegate DU filter
on AnnEnvDeployer?
Is that a managed object?
Do I have to know how the filter is implemented or can I just declare
which jars (classes?) get scanned for this deployment?
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
8:30 a.m.
> By default we should still scan everything,
> as users mostly expect that things just work, no extra dds.
>
That's funny, because I wouldn't expect jbossweb.sar
(which is the webserver) to be scanned for javaee annotations?
I meant user's deployments.
I already exclude all of our stuff:
<bean
class="org.jboss.deployment.FileNameVirtualFileFilter">
<constructor>
<parameter>
<map keyClass="java.lang.String"
valueClass="java.util.Set">
<entry>
<key>jbossweb.sar</key>
<value><null/></value>
</entry>
<entry>
<key>console-mgr.sar</key>
<value><null/></value>
</entry>
<entry>
<key>jbossws.sar</key>
<value><null/></value>
</entry>
<entry>
<key>jmx-remoting.sar</key>
<value><null/></value>
</entry>
<entry>
<key>jboss-local-jdbc.rar</key>
<value><null/></value>
</entry>
<entry>
<key>jboss-xa-jdbc.rar</key>
<value><null/></value>
</entry>
<entry>
<key>jms-ra.rar</key>
<value><null/></value>
</entry>
<entry>
<key>mail-ra.rar</key>
<value><null/></value>
</entry>
<entry>
<key>quartz-ra.rar</key>
<value><null/></value>
</entry>
<entry>
<key>jmx-console.war</key>
<value><null/></value>
</entry>
</map>
</parameter>
</constructor>
</bean>
Hence taking off a few secs. ;-)
8:36 a.m.
> How exactly do you get this kind of info from ejb-jar.xml or
web.xml?
RTFS (read the fine spec :-)
I know nothing about ejbs and web. ;-)
I'm not really that interested in the discussion beyond removing
~10 seconds of useless waiting everytime I reboot JBoss5.
I got your web profile from 25sec to 20sec
with my simple name exclusion. :-)
The rest of the discussion is just about how simple/intuitive
you can make it (I mean for the user/admin rather than yourself :-).
I'll think of something here:
- http://www.jboss.com/index.html?module=bb&op=viewtopic&t=145436
Is that a managed object?
Do I have to know how the filter is implemented or can I just declare
which jars (classes?) get scanned for this deployment?
ScanningMetaData should solve this.
10:30 a.m.
The new 'web' profile is going to be included anyway at some point, so the sooner
the
better, I guess.
Also, I'm waiting for things to stabilize in trunk to introduce the 'standard'
profile.
Maybe with this newer more lightweight web-profile we could change the 'default'
one to have
the 'standard' settings, rather than introducing yet another one. This more or
less means
adding iiop, call-by-value and classloading isolation.
I'm not yet clear what is the best choice.
Adrian Brock wrote:
WRT: https://jira.jboss.org/jira/browse/JBAS-5897
I'd like to include the "web profile"
in the open source distribution.
We would document this as "experimental", i.e.
the configuration is likely to change before
it is stabilised.
That's because it is not quite finished yet,
there's still issues with making jta/jca optional,
factoring out the jpa deployer from ejb3 and
the http invoker currently required to make
shutdown.sh work.
Including the web profile easier now we have the shared libraries
since it won't increase the size of the
distribution anything like as much as before.
I propose that you should be able to start it using:
./run.sh -c web
The web profile currently looks like this:
deployers:
alias-deployers-jboss-beans.xml
ejb3.deployer
jboss-aop-jboss5.deployer
jboss-jca.deployer
jbossweb.deployer
metadata-deployer-jboss-beans.xml
security-deployer-jboss-beans.xml
deploy:
hsqldb-ds.xml
http-invoker.sar
jboss-local-jdbc.rar
jbossweb.sar
jboss-xa-jdbc.rar
jca-jboss-beans.xml
jmx-console.war
jmx-invoker-service.xml
ROOT.war
security
transaction-jboss-beans.xml
11:49 a.m.
On Mon, 2008-11-10 at 18:30 +0200, Dimitris Andreadis wrote:
The new 'web' profile is going to be included anyway at some
point, so the sooner the
better, I guess.
Ok, I've done this. There is now a server configuration called "web".
There was no good place to put changed config files
so I put them in server/src/etc/conf/web,
even though one of these files really goes in deploy. ;-)
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
10:38 a.m.
On Mon, Nov 10, 2008 at 3:58 PM, Adrian Brock <abrock(a)redhat.com> wrote:
WRT: https://jira.jboss.org/jira/browse/JBAS-5897
I'd like to include the "web profile"
in the open source distribution.
Good move :)
Rémy
5883
days inactive
5884
days old
jboss-development@lists.jboss.org
15 comments
5 participants
participants (5)
-
Adrian Brock -
Ales Justin -
Dimitris Andreadis -
Rémy Maucherat -
Sacha Labourey