The web profile prevents one from using features accidentally from the
full profile. So if a developer is creating an app targeted for the web
profile in production, but they have the full profile in development,
they may used some features that they shouldn't and there wouldn't be
anything to stop them.
Of course, you can remove packages to bring a full to a web profile:
pkg uninstall
pkg:/glassfish-appclient
pkg:/glassfish-cmp
pkg:/glassfish-common-full
pkg:/glassfish-corba
pkg:/glassfish-ejb
pkg:/glassfish-full-incorporation
pkg:/glassfish-jms
pkg:/glassfish-web-profile
pkg:/metro
pkg:/mq-bin-exe
pkg:/mq-bin-sh
pkg:/mq-config-gf
pkg:/mq-server
pkg:/glassfish-full-profile
but I don't think that is what you are looking for if you want this to
be only for a single domain.
Tom
On 2/9/2011 5:46 PM, Jason Lee wrote:
> What would the advantage be? The server only starts what's needed,
> right?
>
> On 2/9/11 5:44 PM, Ludovic Champenois wrote:
>> On 2/9/11 3:34 PM, Vince Kraemer wrote:
>>> Say I download the 'full' glassfish 3.1 bits.
>>>
>>> Is there a way for users to create a web profile domain from these
>>> bits?
>>>
>>> Thanks,
>>> vbk
>> not that I know.
>> The profile setup is at the server level, not the domain level.
>> Ludo
>
>