Deployment update

Hi all,

I will make a modification on nuxeo deployment - renaming
nuxeo.nxp back 
to nuxeo.ear
beacuse WebServices doesn't work anymore when using another
extension 
than .ear for an ear
(or even when putting jars containg ejb3 beans inside a
directory that 
is not ending in .ear)

This have the following impact on the application:

1. Nuxeo will replace the default JBoss EAR deployer. The
default 
deployer will be still used for regular EARs - Nuxeo
deployer will 
delegate  the deployment of  regular EARs to  the default
one. EARs that 
contains a file OSGI-INF/deployment-container.xml will be
treated as a 
Nuxeo EAR and preprocessed before delegating their
deployment to the 
default EAR deployer.

2. EJB3 JNDI names changes: All JNDI names for EJB3 
components will 
begin with "nuxeo/"

I will change all these JNDI names  and will test on my
laptop. I let 
you know when all the modifications will be commited.

Bogdan
_______________________________________________
ECM mailing list
ECMlists.nuxeo.com
http://li
sts.nuxeo.com/mailman/listinfo/ecm

I commited the changes.
If you are updating from svn don't forget to remove any file
deployed by 
nuxeo from jboss deploy directory
(like nuxeo.nxp, nuxeo.deployer etc)
And redeploy all by running deploy-ecm-all from
Nuxeo/build.xml

If you experience problems checks that you don't have
anymore nuxeo.nxp 
in you deploy dir .
If it exists this means there are some projects that are
deployed in the 
old location (so you need to modify build.properties)
Also check that that your modules use the new JNDI names -
names 
starting with "nuxeo/"

Bogdan


Bogdan Stefanescu wrote:
> Hi all,
>
> I will make a modification on nuxeo deployment -
renaming nuxeo.nxp 
> back to nuxeo.ear
> beacuse WebServices doesn't work anymore when using
another extension 
> than .ear for an ear
> (or even when putting jars containg ejb3 beans inside a
directory that 
> is not ending in .ear)
>
> This have the following impact on the application:
>
> 1. Nuxeo will replace the default JBoss EAR deployer.
The default 
> deployer will be still used for regular EARs - Nuxeo
deployer will 
> delegate  the deployment of  regular EARs to  the
default one. EARs 
> that contains a file OSGI-INF/deployment-container.xml
will be treated 
> as a Nuxeo EAR and preprocessed before delegating their
deployment to 
> the default EAR deployer.
>
> 2. EJB3 JNDI names changes: All JNDI names for EJB3 
components will 
> begin with "nuxeo/"
>
> I will change all these JNDI names  and will test on my
laptop. I let 
> you know when all the modifications will be commited.
>
> Bogdan
> _______________________________________________
> ECM mailing list
> ECMlists.nuxeo.com
> http://li
sts.nuxeo.com/mailman/listinfo/ecm
>

_______________________________________________
ECM mailing list
ECMlists.nuxeo.com
http://li
sts.nuxeo.com/mailman/listinfo/ecm

Bogdan Stefanescu wrote:
> 
> I commited the changes.
> If you are updating from svn don't forget to remove any
file deployed by
> nuxeo from jboss deploy directory
> (like nuxeo.nxp, nuxeo.deployer etc)
> And redeploy all by running deploy-ecm-all from
Nuxeo/build.xml
> 
> If you experience problems checks that you don't have
anymore nuxeo.nxp
> in you deploy dir .
> If it exists this means there are some projects that
are deployed in the
> old location (so you need to modify build.properties)
> Also check that that your modules use the new JNDI
names - names
> starting with "nuxeo/"
> 
> Bogdan
> 
> 
> Bogdan Stefanescu wrote:
>> Hi all,
>>
>> I will make a modification on nuxeo deployment -
renaming nuxeo.nxp
>> back to nuxeo.ear
>> beacuse WebServices doesn't work anymore when using
another extension
>> than .ear for an ear
>> (or even when putting jars containg ejb3 beans
inside a directory that
>> is not ending in .ear)
>>
>> This have the following impact on the application:
>>
>> 1. Nuxeo will replace the default JBoss EAR
deployer. The default
>> deployer will be still used for regular EARs -
Nuxeo deployer will
>> delegate  the deployment of  regular EARs to  the
default one. EARs
>> that contains a file
OSGI-INF/deployment-container.xml will be treated
>> as a Nuxeo EAR and preprocessed before delegating
their deployment to
>> the default EAR deployer.
>>
>> 2. EJB3 JNDI names changes: All JNDI names for EJB3
 components will
>> begin with "nuxeo/"
>>
>> I will change all these JNDI names  and will test
on my laptop. I let
>> you know when all the modifications will be
commited.

Just tried out with your latest checkins. Seems to work just
fine on my box.

Thanks.

	J.


-- 
Julien Anguenot | Nuxeo R&D (Paris, France)
Open Source ECM - http://www.nuxeo.com
Nuxeo 5 : http://www.nuxeo.org
Mobile: +33 (0) 6 72 57 57 66

_______________________________________________
ECM mailing list
ECMlists.nuxeo.com
http://li
sts.nuxeo.com/mailman/listinfo/ecm