You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2007/08/18 05:38:32 UTC
[jira] Created: (OPENEJB-638) doc: deployments.html
doc: deployments.html
---------------------
Key: OPENEJB-638
URL: https://issues.apache.org/jira/browse/OPENEJB-638
Project: OpenEJB
Issue Type: Sub-task
Reporter: David Blevins
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENEJB-638) doc: deployments.html
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520782 ]
David Blevins commented on OPENEJB-638:
---------------------------------------
The text "As of 1.0 beta1, " can be deleted.
All references to openejb-1.0-beta1 should be switched to openejb-3.0
" If OpenEJB finds a META-INF directory with an 'ejb-jar.xml' fine inside, then OpenEJB will treat the directory as an unpacked ejb jar" Not so sure that is how it works anymore. I think it goes, if the directory has a META-INF/ejb-jar.xml or META-INF/application.xml or class files, it's an unpacked application directory. Otherwise it's assumed to be a directory containing applications.
Not sure the log statement 'Loaded EJBs' is exactly correct anymore. We should check. Would be somehwere in the ConfigurationFactory or the Assembler.
"Deployment ID listed is the JNDI name used..." is not correct. The JNDI name is now different than the deployment id.
Also, the log message ending with "Jar failed validation. Use the validation tool for more details" is now just "Jar failed validation" as the validation output should preceed that log statement if it failed to validate.
It's also very important to note that we support ejb jars and application client jars or ears containging ejbs and/or app clients. This doc only mentions ejb jars. We support ears containing ejbs and application clients. We do not support war files in ears or resource archives (rar files) in ears, wars and rars in an ear will be ignored during deployment.
"OpenEJB will simply skip over jars that do contain the required 'META-INF/ejb-jar.xml' file." no longer true as ejb-jar.xml files (for ejbs) or application.xml files (ears) or application-client.xml files (app clients) are not required in javaee 5. See DeploymentLoader.discoverModuleType for the details that should be in the documentation (don't include a link to source please).
> doc: deployments.html
> ---------------------
>
> Key: OPENEJB-638
> URL: https://issues.apache.org/jira/browse/OPENEJB-638
> Project: OpenEJB
> Issue Type: Sub-task
> Reporter: David Blevins
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.