Try winCVS and use the complete pserver string this is not normal.
Maybe a firewall?

We will finish jBoss 2.0 stateful support and post it soon. jBoss 2.0
will move really quick.

marc


Lee Turner wrote:
> 
> OK
> 
> Thanks.  When support for stateful is finished will this only be updated in
> the CVS or will there be a binary release that I would be able to download ?
> The reason I ask is that I seem to have problems getting to the CVS using
> jCVS.
> 
> Keep up the good work !!!!
> 
> Lee
> 
> > -----Original Message-----
> > From: marc fleury [SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, May 09, 2000 4:11 PM
> > To:   EJBoss
> > Subject:      Re: Deploying stateful session beans ????
> >
> > Support for stateful is not yet finished, should take us a few days.
> >
> > sorry for the frustration we should have said it clearly
> >
> > Almost everything is in place and EJX support is working
> >
> > marc
> >
> >
> > Lee Turner wrote:
> > >
> > > I have had jBoss 2 set up on Win NT 4 now for about a week and I have
> > > several CMP entity beans deployed.  I am now trying to deploy a session
> > bean
> > > and it only seems to deploy when I specify that it is a stateless
> > session
> > > bean whereas I want it to be a stateful bean.
> > >
> > > I have the following deployment information - ejb-jar.xml :
> > >
> > > <session>
> > >   <display-name>ContactsManager EJB</display-name>
> > >   <ejb-name>ContactsManager</ejb-name>
> > >
> > <home>com.gilchrist.css.cms.bo.contactsmanager.ContactsManagerHome</home>
> > >
> > <remote>com.gilchrist.css.cms.bo.contactsmanager.ContactsManager</remote>
> > >
> > >
> > <ejb-class>com.gilchrist.css.cms.bo.contactsmanager.ContactsManagerBean</e
> > jb
> > > -class>
> > >   <session-type>Stateful</session-type>
> > >   <transaction-type>Bean</transaction-type>
> > > </session>
> > >
> > > I have the following in my jboss.xml:
> > >
> > > <session>
> > >   <ejb-name>ContactsManager</ejb-name>
> > >   <jndi-name>contactsmanager.ContactsManagerBean</jndi-name>
> > >   <configuration-name>Singleton Stateless
> > SessionBean</configuration-name>
> > > </session>
> > >
> > > I was confused as what to put in the <configuration-name> section.
> > There
> > > doesn't seem to be anything for stateful beans.  I knew Singleton
> > Stateless
> > > SessionBean was probably wrong but I didn't know what else to do ???
> > >
> > > When I specify that my bean is a stateless bean in the ejb-jar.xml file
> > it
> > > deploys fine and I get the following message on the server:
> > >
> > > [Container factory] Bound ContactsManager to
> > > contactsmanager.ContactsManagerBean
> > >
> > > However, I get nothing when I specify it as stateful.  I haven't put
> > > anything in my jaws.aml file as I assumed that this was just for mapping
> > > entity beans to the DB.  Am I missing something here ???
> > >
> > > TIA
> > > Lee
> > >
> > > --
> > > --------------------------------------------------------------
> > > To subscribe:        [EMAIL PROTECTED]
> > > To unsubscribe:      [EMAIL PROTECTED]
> > > Problems?:           [EMAIL PROTECTED]
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > Problems?:           [EMAIL PROTECTED]
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to