Raja Sagar Panamgipalli

Ranch Hand
+ Follow
since Aug 13, 2003
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Raja Sagar Panamgipalli

Hi,
resolved the error, renaming the element works,but must ensure we hit it on the right place.
I'm using Axis 1.1, so simply renamed the bean class<element in WSDL>,actually generated from WSDL2Java its references in the server-config.wsdd.

Checked if the wsdl was updated by accesing the web-root/services, and alas could see my renamed element published in the wsdl.

Thanks,
Sagar
13 years ago
Hi All,

We have a webservice and its corresponding Java Bean classes(generated out of Apache Axis WSDL2Java emitter) for each element in the incoming Soap message body.

Now the problem comes when i've have to rename an element in the soap body, how should i make Axis runtime invoke the same webservice without regenerating the entire Java2WSDL and WSDL2Java.

I have tried renaming the Java Bean class and all its corresponding references in deploy.wsdd, server-config.wsdd etc.

The exception is get is ...

CAUSED BY INITIAL EXCEPTION]
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultString: org.xml.sax.SAXException: Invalid element in XXXXXXXX - YYYYYYYYYYY



Hope i'm clear.
Appreciate quick response.....SOS...


Thank you.
13 years ago
Hi All,

We have a webservice and its corresponding Java Bean classes(generated out of Apache Axis WSDL2Java emitter) for each element in the incoming Soap message body.

Now the problem comes when i've have to rename an element in the soap body, how should i make Axis runtime invoke the same webservice without regenerating the entire Java2WSDL and WSDL2Java.

I have tried renaming the Java Bean class and all its corresponding references in deploy.wsdd, server-config.wsdd etc.

The exception is get is ...

CAUSED BY INITIAL EXCEPTION]
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultString: org.xml.sax.SAXException: Invalid element in XXXXXXXX - YYYYYYYYYYY



Hope i'm clear.
Appreciate quick response.....SOS...


Thank you.
13 years ago
Hi Folks,

Cleared the exam with 74% ...
Headfirst helped,and the spec really pulled me to the other end.

Life cycle, and operations allowed during the same...just get a good grip of the these then..ur done.
Roles and responsibilities.
EJBQL Identification,path expressions can be a little tricky...

Hope that helps....

Thanks Valentin Crettaz for being there.....Man..



14 years ago
The purpose of Stateful session bean is to serve the client,i.e maintain a history of Client's wish list, right when the client enters the application,it cannot drop off in the middle (unless the server goes down).

So,resources can be accessed by the bean because he(client) is initiating the process of bean creation(i.e.. HE wants to interact with the app,a state for himself), which again based on the business logic will trigger call to resource mgrs and other beans.

So its because the creation is triggered by the client,(again impl dependent), we give him "exclusively made for U" bean.

Where as in case of stateless session bean we are leaving creation at the container's will n wish, so that bean doesn't hang around with connection to resource mgr open and gossipping around with other beans in the pool.

Correct me if i'm wrong.....
Hi Satish,
IMHO and earlier as Peer Reynders its about keeping the interfaces consistent.

Else We would have had seperate individual interfaces for both stateless and stateful session beans.I think more to do with the idea of making API generic.

Oops please correct me if happened...

Thanks & regards,
Sagar
The container vendor may implement naming service using LDAP,RMI,COS or any other way.



Each naming service has its own characteristics with respect to what kind of objects it is capable of storing, whether it is persistent or transient, etc. JNDI itself does not dictate those characteristics. It merely provides an abstraction for accessing the naming service in a way that protects your code from the gory details of the specific naming service implementation as much as possible.

JNDI is not the naming service itself. It's just an API you use to access a naming service. Just like JDBC is not a database. It's just an API you use to access a database. Someone needs to make a conscious decision to expose a particular naming service, LDAP, CosNaming, etc. via JNDI.

This decision would typically be made by the implementors of the naming service, but could be done by a 3rd party as well.



So basically its for vendors usage and their comfort.

Expect corrections.

Regards,
Sagar
Hi,

1)Opinion for (1) Question:-
Spec says:

An enterprise bean with bean-managed transaction demarcation must not use the getRollbackOnly() and setRollbackOnly() methods of the EJBContext interface.

An enterprise bean with bean-managed transaction demarcation has no need to use these methods,
because of the following reasons:
� An enterprise bean with bean-managed transaction demarcation can obtain the status of a transaction by using the getStatus() method of the javax.transaction.UserTransaction interface.
� An enterprise bean with bean-managed transaction demarcation can rollback a transaction using the rollback() method of the UserTransaction interface.

I think its like we are not supposed to interfere with the working of container.When we say we are going for BMT then we must pretty much adhere to it.

(2)Opinion for Question(2)

Stateless Session bean's creation and removal is tied to the container, so there may be an unspecified transaction context running during stateless session bean creation and context settings.
This may be the reason why we cannot call setRollbackOnly() on the SessionContext object.

Expect Corrections from all... :roll:

Regards,
Sagar.
Hi all,
I was wondering if anyone can post a reply .

Thanx,
Sagar
Hey Guys,

I was wondering if the the OID in the ejb spec is conveying the the right message about the sequence of call the are triggered during the entity bean passivation and activation pg:209.

The diagram shows the first part i.e. bean passivation in lines with my preparation and understanding but i see the during the activation i.e when an entity bean is in passivated state, and client calls business method on the EJBObject, the OIdiagram shows as EJBObject calling ejbActivate() on the instance.

But i'm in the impression that the call to ejbActivate is made by the Container on the instance.followed by ejbLoad().

OR

is it that since the EJBObject is implemented by the container, it doesn't matter how the container wishes, activation is done.(i mean Is the code that container calls activation on an instance,part of EJBObject interface implementation).

Have i messed it up ?

Thanks & Regards,

Sagar.
Hi All,

I have this exception coming when i'm trying to run my client program,
I'm passing a normal String Object as parameter to a business method on my EJBObject.

It would be great if anybody could let me know the actual cause...String being serializable but still i'm getting this error.

CustomerProxyTestCase is the client class name.

grmmClient=(GRMMClient[])custProxy.getClientInfoForAccount(accountId);




Hi All,

I have this exception coming when i'm trying to run my client program,
I'm passing a normal String Object as parameter to a business method on my EJBObject.

It would be great if anybody could let me know the actual cause...

CustomerProxyTestCaseis the client class name.

Hi,

Can you be more specific and clear in your query...

Thanks,

Regds,
Sagar.
Hi,

Can you be more specific and clear in your query...

Thanks,

Regds,
Sagar.
Hi

Every body in this forum have been suggested when preparing for SCBCD was to run their Beans inside Sun J2ee1.3 RI.
I think you should try it as well,its very simple and easy.(with a minor bug).


regds
Sagar