You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/07/30 12:54:16 UTC
[jira] Resolved: (JAMES-354) optimize James integration under J2EE
for next release
[ https://issues.apache.org/jira/browse/JAMES-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved JAMES-354.
---------------------------------
Fix Version/s: 3.0-M1
(was: Trunk)
Resolution: Fixed
We now have a war builld too :)
> optimize James integration under J2EE for next release
> ------------------------------------------------------
>
> Key: JAMES-354
> URL: https://issues.apache.org/jira/browse/JAMES-354
> Project: JAMES Server
> Issue Type: Improvement
> Affects Versions: 2.2.0
> Environment: any (linux/solaris)
> Reporter: Ralf Hauser
> Assignee: Norman Maurer
> Fix For: 3.0-M1
>
>
> For a large corporate environment, I have been asked whether the James Pop with TLS would work under WebSphere.
> So far, I haven't tried, but I expect some less than optimum issues such as JAMES-348 (hard-coded SunJSSE).
> Now that the dependency on avalon/cornerstone most likely needs to be readjusted (http://avalon.apache.org/closed.html --> 4 new projects Excalibur, Loom, Metro,Castle - unclear where cornerstone went...) wouldn't this be an opportunity to become more J2EE mainstream?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org