On 8/20/2010 4:36 PM, Lin Sun wrote:
It seems hard to remove javamail given openejb depends on it. At
least for the javamail schema for JNDI, which is used by the
openejb-client.
Also, I don't quite understand this comment in G roomt pom.xml -
!-- Use
Ok, thanks, I'll take your recommendation and keep both. :)
I just removed the webservices-common and webservices-builder.
We still need geronimo-webservices module since it is used by
geronimo-tomcat whenever user requests to retrieve to see the wsdl via
http and the work is delegated to the
Sounds good to me.
Jarek
On Mon, Aug 23, 2010 at 2:37 PM, Lin Sun linsun@gmail.com wrote:
Ok, thanks, I'll take your recommendation and keep both. :)
I just removed the webservices-common and webservices-builder.
We still need geronimo-webservices module since it is used by
Sounds right. Thanks for looking at this.
-Donald
On 8/23/10 2:37 PM, Lin Sun wrote:
Ok, thanks, I'll take your recommendation and keep both. :)
I just removed the webservices-common and webservices-builder.
We still need geronimo-webservices module since it is used by
geronimo-tomcat
We need connector, TranQL and RAs for OpenJPA
-Donald
On 8/20/10 2:29 PM, Lin Sun wrote:
Ok, regarding tranql RAs, the derby ones are pulled in by
system-database. The other RAs are pulled in as part of the
db-connectors plugin which is part of the eba-tomcat plugin group.
I think we
Yes they are all in the current web profile assembly with no plan to
remove them.
Thanks,
Lin
On Mon, Aug 23, 2010 at 4:19 PM, Donald Woods dwo...@apache.org wrote:
We need connector, TranQL and RAs for OpenJPA
-Donald
On 8/20/10 2:29 PM, Lin Sun wrote:
Ok, regarding tranql RAs, the
Hi
I am checking at our web profile assemblies to ensure it met the
requirements for Java EE 6 web profile and prune the unnecessary
artifacts. I've been mainly look at the tomcat7-javaee6-web and I
have some comments/questions:
felix core: i assume we'll always ship 2 osgi runtime?
connector
On 8/20/2010 10:09 AM, Lin Sun wrote:
Hi
I am checking at our web profile assemblies to ensure it met the
requirements for Java EE 6 web profile and prune the unnecessary
artifacts. I've been mainly look at the tomcat7-javaee6-web and I
have some comments/questions:
felix core: i assume
For the OpenEJB, I do not see that it is possible to have only ejb lite
function
For those spec jars, if they are there, I think that they should be required
by other components. Like Jaxws, some classes are refered by OpenEJB.
BTW, we might search the dependencies.xml for the jar dependency, e.g.
On Fri, Aug 20, 2010 at 10:09 AM, Lin Sun linsun@gmail.com wrote:
Hi
I am checking at our web profile assemblies to ensure it met the
requirements for Java EE 6 web profile and prune the unnecessary
artifacts. I've been mainly look at the tomcat7-javaee6-web and I
have some
Hi,
Thanks Rick/Ivan/Jarek much for the comments so far. I agree with
most of the comments. I think these are what we agreed on -
1. keep extra spec jars instead of spending time to sort them out.
2. mina, yoko are needed.
3. pluto/portal are needed.
4. openejb: going to be hard to break down
Ok, regarding tranql RAs, the derby ones are pulled in by
system-database. The other RAs are pulled in as part of the
db-connectors plugin which is part of the eba-tomcat plugin group.
I think we are fine to keep these RAs in, if we want to support these
different dbs like db2, oracle, sql
It seems hard to remove javamail given openejb depends on it. At
least for the javamail schema for JNDI, which is used by the
openejb-client.
Also, I don't quite understand this comment in G roomt pom.xml -
!-- Use org.apache.geronimo.javamail/geronimo-javamail_1.4_mail
13 matches
Mail list logo
