David Jencks (JIRA | 1 Mar 2005 03:17
Picon
Favicon

[jira] Closed: (GERONIMO-451) geronimo connector xsd refers to sun schemas

     [ http://issues.apache.org/jira/browse/GERONIMO-451?page=history ]

David Jencks closed GERONIMO-451:
---------------------------------

      Assign To: David Jencks
     Resolution: Fixed
    Fix Version: 1.0-M4

fixed a while back: r123327 | djencks | 2004-12-24 23:34:42 -0800 (Fri, 24 Dec 2004)

> geronimo connector xsd refers to sun schemas
> --------------------------------------------
>
>          Key: GERONIMO-451
>          URL: http://issues.apache.org/jira/browse/GERONIMO-451
>      Project: Geronimo
>         Type: Bug
>   Components: connector
>     Versions: 1.0-M2
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.0-M4

>
> There are some uses of j2ee namespace elements in the connector schema. These should be replaced by
independent elements.

--

-- 
This message is automatically generated by JIRA.
(Continue reading)

David Jencks (JIRA | 1 Mar 2005 03:17
Picon
Favicon

[jira] Assigned: (GERONIMO-568) Switch system-datasource plan to the derby xa connector

     [ http://issues.apache.org/jira/browse/GERONIMO-568?page=history ]

David Jencks reassigned GERONIMO-568:
-------------------------------------

    Assign To: David Jencks

> Switch system-datasource plan to the derby xa connector
> -------------------------------------------------------
>
>          Key: GERONIMO-568
>          URL: http://issues.apache.org/jira/browse/GERONIMO-568
>      Project: Geronimo
>         Type: Improvement
>     Reporter: John Sisson
>     Assignee: David Jencks
>     Priority: Minor
>  Attachments: SystemDatasource_patch.txt
>
> In a dev mail discussion titled "Re: derby-connector RAR not in Geronimo's repository directory", David
Jencks suggested it would be a good idea to switch the system-datasource plan to the xa connector as well as
moving the timer gbeans to the system datasource plan.  
> I am currently working on a patch.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
(Continue reading)

David Jencks (JIRA | 1 Mar 2005 07:18
Picon
Favicon

[jira] Closed: (GERONIMO-568) Switch system-datasource plan to the derby xa connector

     [ http://issues.apache.org/jira/browse/GERONIMO-568?page=history ]

David Jencks closed GERONIMO-568:
---------------------------------

     Resolution: Fixed
    Fix Version: 1.0-M4

Applied, many thanks!

> Switch system-datasource plan to the derby xa connector
> -------------------------------------------------------
>
>          Key: GERONIMO-568
>          URL: http://issues.apache.org/jira/browse/GERONIMO-568
>      Project: Geronimo
>         Type: Improvement
>     Reporter: John Sisson
>     Assignee: David Jencks
>     Priority: Minor
>      Fix For: 1.0-M4
>  Attachments: SystemDatasource_patch.txt
>
> In a dev mail discussion titled "Re: derby-connector RAR not in Geronimo's repository directory", David
Jencks suggested it would be a good idea to switch the system-datasource plan to the xa connector as well as
moving the timer gbeans to the system datasource plan.  
> I am currently working on a patch.

--

-- 
This message is automatically generated by JIRA.
(Continue reading)

Gianny DAMOUR (JIRA | 1 Mar 2005 08:46
Picon
Favicon

[jira] Created: (GERONIMO-598) ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context

ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
-------------------------------------------------------------------------

         Key: GERONIMO-598
         URL: http://issues.apache.org/jira/browse/GERONIMO-598
     Project: Geronimo
        Type: Bug
  Components: OpenEJB  
    Versions: 1.0-M3    
    Reporter: Gianny DAMOUR
 Assigned to: Gianny DAMOUR 
     Fix For: 1.0-M4

Currently database operations are flushed upon TX commit.

This is an issue where:
* an Entity Bean is created; and
* then an ejbFind<> or ejbSelect<>, whose result is modified by the previously created Entity Bean, is
executed in the same TX context.

It should be possible to force/configure a database flush prior any finder or select method.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira
(Continue reading)

Gianny DAMOUR (JIRA | 1 Mar 2005 08:46
Picon
Favicon

[jira] Closed: (GERONIMO-595) Recursive CMRs do not work

     [ http://issues.apache.org/jira/browse/GERONIMO-595?page=history ]

Gianny DAMOUR closed GERONIMO-595:
----------------------------------

    Resolution: Fixed

Fixed.

> Recursive CMRs do not work
> --------------------------
>
>          Key: GERONIMO-595
>          URL: http://issues.apache.org/jira/browse/GERONIMO-595
>      Project: Geronimo
>         Type: Bug
>     Versions: 1.0-M3
>     Reporter: Gianny DAMOUR
>     Assignee: Gianny DAMOUR
>      Fix For: 1.0-M4

>
> Recursive CMRs, i.e. a CMR used to traverse from an Entity Bean to another Entity Bean of the same type, do
not work.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
(Continue reading)

Venkat Reddy | 1 Mar 2005 13:42
Picon

Re: Axis GBean is deployable?

David, Thanks for the valuable clarification !

I thought Geronimo will use Axis core for its SOAP stack and EWS code
for JSR-921 support. I'm aware that both need tailoring to fit into
Geronimo architecture. Is there any document or discussion that talks
more about this? I'm interested in contributing in the areas of
integrating Axis and EWS with Geronimo. What's the to-do list for this
area of work? How is the webservices support for Geronimo is being
planned ?

Thanks
Venkat

On Mon, 28 Feb 2005 08:19:47 -0800, David Jencks
<david_jencks@...> wrote:
> -- Current state of axis integration --
> 
> There are currently 2 sets of code for axis integration, and they may
> look mingled together.  There's Srinath's original work, in the axis
> module in org/apache/geronimo/axis, and there's my work, in
> axis-builder and org/apache/geronimo/axis/client.  I think David
> Blevins is about to commit some server-side code.
> 
> Srinath's original work, including the Axis gbean, doesn't fit into the
> geronimo architecture very well, especially including the separation of
> deployment and runtime phases.  It also appears to have a very
> Axis-centric view of the world that I don't feel is entirely
> appropriate for existence in an application server.  This code has not
> been maintained for several months and is not currently used in
> Geronimo.
(Continue reading)

Mark | 1 Mar 2005 20:39
Picon
Favicon

Deployment EJB with Mail Resource References

Hello,

I tried to deploy a simple ejb with a javax.mail.Session Resource-ref, 
but it fails with the error message below.  (Also see deployment 
descriptor below)

Are there any documents that describe how to configure (pre deployment, 
post deployment) a mail session so it can be wired to a resource ref?

Thanks.
Mark

<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">

<ejb-jar>
 <display-name>Mail</display-name>
 <enterprise-beans>
  <session>
   <ejb-name>Mail</ejb-name>
   <home>examples.MailHome</home>
   <remote>examples.Mail</remote>
   <local-home>examples.MailLocalHome</local-home>
   <local>examples.MailLocal</local>
   <ejb-class>examples.MailBean</ejb-class>
   <session-type>Stateless</session-type>
   <transaction-type>Container</transaction-type>
   <resource-ref>
    <description>A description for ResourceRefName</description>
    <res-ref-name>mail/mymailserver</res-ref-name>
(Continue reading)

David Jencks | 1 Mar 2005 21:00
Picon
Favicon

Re: Axis GBean is deployable?


On Mar 1, 2005, at 4:42 AM, Venkat Reddy wrote:

> David, Thanks for the valuable clarification !
>
> I thought Geronimo will use Axis core for its SOAP stack and EWS code
> for JSR-921 support.

When I looked at EWS it looked to me as if it did 2 things:
1) code generation of stubs
2) partial translation of jaxrpc-mapping file to wsdd xml file. As far 
as I can tell this mapping translation is completely ignoring the 
javabean property to xml element name mapping and the exception 
mapping.

After examing the generated code it looked to me as if it would be 
easier to use a cglib proxy solution than to compile the generated code 
from EWS.
One of the basic principles behind geronimo is that we "compile" all 
xml deployment descriptors into binary gbean configurations ready to be 
loaded and started at runtime.  Following this principle, if we were to 
use wsdd, we would have to preprocess it during deployment into the 
actual objects that configure axis, and serialize those.  AFAICT this 
would involve major surgery on the axis deployment system.  I believe 
it is much simpler simply to process the j2ee deployment descriptors 
directly into the appropriate axis configuration objects, entirely 
skipping the wsdd file format.  We've done this, and I don't see 
anything else in EWS that we can use.

In particular we have some code that, using the XmlBeans schema type 
(Continue reading)

David Jencks | 1 Mar 2005 21:11
Picon
Favicon

Re: Deployment EJB with Mail Resource References

It looks like despite all the work on mail lately no one remembered to  
put a mail gbean in the j2ee-server-plan.xml or anywhere else.

Adding something like this to your app plan or j2ee-server-plan.xml  
should help:

     <gbean namePart="mail/MailSession"  
class="org.apache.geronimo.mail.MailGBean">
         <attribute name="properties">
             mail.smtp.host=mail.apache.com
         </attribute>
     </gbean>

thanks
david jencks

On Mar 1, 2005, at 11:39 AM, Mark wrote:

> Hello,
>
> I tried to deploy a simple ejb with a javax.mail.Session Resource-ref,  
> but it fails with the error message below.  (Also see deployment  
> descriptor below)
>
> Are there any documents that describe how to configure (pre  
> deployment, post deployment) a mail session so it can be wired to a  
> resource ref?
>
> Thanks.
> Mark
(Continue reading)

Dain Sundstrom | 1 Mar 2005 22:07

Re: mx4j 3.0.1 upgrade [svn commit: r155800]

On Mar 1, 2005, at 8:53 AM, jboynes@... wrote:

> ======================================================================= 
> =======
> --- geronimo/trunk/applications/demo/project.xml (original)
> +++ geronimo/trunk/applications/demo/project.xml Tue Mar  1 08:53:09  
> 2005
>  <at>  <at>  -48,7 +48,7  <at>  <at> 
>
>          <dependency>
>              <groupId>mx4j</groupId>
> -            <artifactId>mx4j-jmx</artifactId>
> +            <artifactId>mx4j</artifactId>
>              <version>${mx4j_version}</version>
>              <url>http://mx4j.sourceforge.net</url>
>          </dependency>

Quick qustion: Should now we always, use the "mx4j" artifactId and  
specifically never use "mx4j-jmx"?  Is there a difference between these  
two archives or are they just pseudonyms?

-dain


Gmane