Finder methods problem

Hi
I met a very funny problem. when I try to deploy a entity BMP.(compile was ok).
The bean have a method called findSubElements(this is not a finder method). I
got the a exception:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ejbFindXXX method
for 'findSubElements(java.lang.String,jav
a.lang.String,java.lang.String)' not found on class 'entity.XXXEntityBean_sgz73u_Impl'.
what should I do to fix that ?
Thanks for help.

Hi
It's working on WLS6.0 SP2 very well.
Macsym
PenFriend <[email protected]> wrote:
Macsym,
this isa known issue Cr06867. As a workaround chamge the name of the
methods to not start with
a find.
macsym wrote:
I've tried to re-run it. In my
classpath=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;
but the problem still here. I'v just changed examples under WLS totest it.
BTW I using WLS6.1 SP1.
Thanks any way.
Macsym
Rob Woollen <rob@trebor_nelloow.moc> wrote:
It looks like you need to re-run weblogic.ejbc. Also make sure that
your classes are only
in the ejb-jar file and not the server's classpath.
Finally, what version of WLS are you using? It shouldn't be throwing
an AssertionError for
this.
-- Rob
macsym wrote:
Hi
I met a very funny problem. when I try to deploy a entity BMP.(compilewas ok).
The bean have a method called findSubElements(this is not a findermethod). I
got the a exception:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ejbFindXXXmethod
for 'findSubElements(java.lang.String,jav
a.lang.String,java.lang.String)' not found on class 'entity.XXXEntityBean_sgz73u_Impl'.
what should I do to fix that ?
Thanks for help.

Similar Messages

CMP Custom Finder Method Problem

Hi everybody,
I have a problem about CMP Custom Finder Method.
I made CMP Entity Bean and deployed.
Then, I updated finder section in orion-ejb-jar.xml to add my custom finder query.
Here is updating finder section in my orion-ejb-jar.xml.
<finder-method query="(($schStartDate <= TO_DATE($1,'MM-DD-YYYY a HH:MI') and $schEndDate >= TO_DATE($1,'MM-DD-YYYY a HH:MI')) or ($schStartDate <= TO_DATE($2,'MM-DD-YYYY a HH:MI') and $schEndDate >= TO_DATE($2,'MM-DD-YYYY a HH:MI'))) and ($schRoom = $3)">

<method>
<ejb-name>RoomSchedule</ejb-name>
<method-name>findBySchDateAndRoom</method-name>
<method-params>
<method-param>java.lang.String</method-param>
<method-param>java.lang.String</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</method>
</finder-method>
<resource-ref-mapping name="jdbc/OracleDS" />
And, i restarted oc4j. so, oc4j redepoyed CMP bean.
But, when my client program called CMP Bean, lookup() was ok, but calling findBySchDateAndRoom() was bad.
I couldn't get any result collection.
Here is my client code.
Context ctx = new InitialContext();
Object ref = ctx.lookup("RoomSchedule");
roomScheduleHome = (RoomScheduleHome) PortableRemoteObject.narrow(ref, RoomScheduleHome.class);
String startDT = new String("07-30-2002 am 10:30");
String endDT = new String("07-30-2002 pm 05:20);
String roomID = "TEST";
Collection roomAllSch = roomScheduleHome.findBySchDateAndRoom(startDT, endDT, roomID1);
Iterator roomSchItr = roomAllSch.iterator();
int schQty = 0;
while (roomSchItr.hasNext()) {
roomSchedule = (RoomSchedule) roomSchItr.next();
if(roomSchedule.getStatus().equals("A"))
schQty++;
After excuting above code, schQty was still zero!!
Because Collection roomAllSch had not any items.
But, table ROOMSCHEDULE had 30 records which were same query condition in my database.
I traced SQL statement using P6Spy Class.
Here is spy.log.
1028006337814|10|0|statement|select * from RoomSchedule where ((RoomSchedule.schStartDate <= TO_DATE(?,'MM-DD-YYYY A.M. HH:MI') and RoomSchedule.schEndDate >= TO_DATE(?,'MM-DD-YYYY A.M. HH:MI')) or (RoomSchedule.schStartDate <= TO_DATE(?,'MM-DD-YYYY A.M. HH:MI') and RoomSchedule.schEndDate >= TO_DATE(?,'MM-DD-YYYY A.M. HH:MI'))) and (RoomSchedule.schRoom = ?)|select * from RoomSchedule where ((RoomSchedule.schStartDate <= TO_DATE('7-30-2002 ?@@| 01:00','MM-DD-YYYY A.M. HH:MI') and RoomSchedule.schEndDate >= TO_DATE('7-30-2002 ?@@| 01:00','MM-DD-YYYY A.M. HH:MI')) or (RoomSchedule.schStartDate <= TO_DATE('7-30-2002 ?@HD 12:00','MM-DD-YYYY A.M. HH:MI') and RoomSchedule.schEndDate >= TO_DATE('7-30-2002 ?@HD 12:00','MM-DD-YYYY A.M. HH:MI'))) and (RoomSchedule.schRoom = 'Earth')
1028006337824|10|0|statement|select RoomSchedule.schTitle, RoomSchedule.schStartDate, RoomSchedule.schEndDate, RoomSchedule.schDayAll, RoomSchedule.status, RoomSchedule.schRoom, RoomSchedule.reqUser, RoomSchedule.apprUser, RoomSchedule.purpose, RoomSchedule.relatoinID, RoomSchedule.schDesc, RoomSchedule.reqDate, RoomSchedule.apprDate from RoomSchedule where (RoomSchedule.schID = ?)|select RoomSchedule.schTitle, RoomSchedule.schStartDate, RoomSchedule.schEndDate, RoomSchedule.schDayAll, RoomSchedule.status, RoomSchedule.schRoom, RoomSchedule.reqUser, RoomSchedule.apprUser, RoomSchedule.purpose, RoomSchedule.relatoinID, RoomSchedule.schDesc, RoomSchedule.reqDate, RoomSchedule.apprDate from RoomSchedule where (RoomSchedule.schID = 0)
As you see it, two query statement were executed.
First query statement was ok and got some result records.
But, second query statement was bad so didn't get any result records.
I didn't understand why second query statement was executed.
When roomAllSch.iterator() was being excuted in my client program, second query statment was executed.
I couldn't believe....
What's wrong? Please help me....
OC4J : Version 9 Release 2
Database : Oracle 8i
OS : Windows 2000 Professional

I created CMP of EJB 1.1, I wanted to add a finder
there, but it didn't work.
the error message is:
"AccountEJB_vkbo0d_HomeImpl.java":
AccountEJB_vkbo0d_HomeImpl should be declared
abstract; it does not define findBySalary(float) in
AccountEJB_vkbo0d_HomeImpl at line 11, column 1I think I don't remember CMPs having finder methods anything other than abstract. The code goes in the deployment descriptor. I hope you atleast got that right.
Richard.

Problem when creating CAF Entity Service finder Methods

Guys,
Can any one please suggest me appropriatly to the below problem.
I am using NWDS 7.06. I have no problem when creating CAF project, Application Service and Entity Service even.
But in the Entity Service:
1. Add a string or longtext attribute.
2. try to create a custom finder method in operations tab, during that operation i am not finding the attribute which i have created in step1.
That means i am not able to create the my own finder methods with parameters.
I was able to do that in some version long ago but i have forgotten that NWDS version.
summary of Problem Is: " Cannot create custom methods with custom parameters in Entity Service"
Can you please suggest me the right version or a solution to this problem on urgent basis please.
I promise you that i will give you full points to you who ever gives me the right solution.
Please mail your suggestions to [email protected]

Guys,
I have solved the problem successfully. Thanks for your attention.

Deployment problem with finder method

I have a problem deploying an application that was working prior to my adding a finder method to one of the entity beans. Here is the Descriptor from the EJB Module that i created (which appears to be ok):
<?xml version="1.0" encoding="UTF-8"?>
<!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>RFXModule</display-name>
<enterprise-beans>
<session>
<display-name>RFXManager</display-name>
<ejb-name>RFXManager</ejb-name>
<home>au.com.alphawest.trader.rfx.business.management.RFXManagerHome</home>
<remote>au.com.alphawest.trader.rfx.business.management.RFXManagerRemote</remote>
<ejb-class>au.com.alphawest.trader.rfx.business.management.RFXManagerBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
<ejb-local-ref>
<ejb-ref-name>ejb/rfx/RFXDocument</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>au.com.alphawest.trader.rfx.business.data.RFXDocumentLocalHome</local-home>
<local>au.com.alphawest.trader.rfx.business.data.RFXDocumentLocal</local>
<ejb-link>RFXDocument</ejb-link>
</ejb-local-ref>
</session>
<entity>
<display-name>RFXAttachment</display-name>
<ejb-name>RFXAttachment</ejb-name>
<local-home>au.com.alphawest.trader.rfx.business.data.RFXAttachmentLocalHome</local-home>
<local>au.com.alphawest.trader.rfx.business.data.RFXAttachmentLocal</local>
<ejb-class>au.com.alphawest.trader.rfx.business.data.RFXDocumentAttachment</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<abstract-schema-name>RFXAttachment</abstract-schema-name>
<cmp-field>
<field-name>name</field-name>
</cmp-field>
<cmp-field>
<field-name>type</field-name>
</cmp-field>
<cmp-field>
<field-name>attachmentContents</field-name>
</cmp-field>
<primkey-field>name</primkey-field>
</entity>
<entity>
<display-name>RFXDocument</display-name>
<ejb-name>RFXDocument</ejb-name>
<local-home>au.com.alphawest.trader.rfx.business.data.RFXDocumentLocalHome</local-home>
<local>au.com.alphawest.trader.rfx.business.data.RFXDocumentLocal</local>
<ejb-class>au.com.alphawest.trader.rfx.business.data.RFXDocumentBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>au.com.alphawest.trader.rfx.business.data.RFXDocumentPK</prim-key-class>
<reentrant>False</reentrant>
<abstract-schema-name>RFXDocument</abstract-schema-name>
<cmp-field>
<field-name>documentGUID</field-name>
</cmp-field>
<cmp-field>
<field-name>creationDate</field-name>
</cmp-field>
<cmp-field>
<field-name>creatorGUID</field-name>
</cmp-field>
<cmp-field>
<field-name>description</field-name>
</cmp-field>
<cmp-field>
<field-name>dueDate</field-name>
</cmp-field>
<cmp-field>
<field-name>emailAddress</field-name>
</cmp-field>
<cmp-field>
<field-name>faxNo</field-name>
</cmp-field>
<cmp-field>
<field-name>locked</field-name>
</cmp-field>
<cmp-field>
<field-name>notes</field-name>
</cmp-field>
<cmp-field>
<field-name>organisationName</field-name>
</cmp-field>
<cmp-field>
<field-name>ownerGUID</field-name>
</cmp-field>
<cmp-field>
<field-name>requestId</field-name>
</cmp-field>
<cmp-field>
<field-name>subject</field-name>
</cmp-field>
<cmp-field>
<field-name>telephoneNo</field-name>
</cmp-field>
<cmp-field>
<field-name>unitGUID</field-name>
</cmp-field>
<cmp-field>
<field-name>buyer</field-name>
</cmp-field>
<cmp-field>
<field-name>organisationGUID</field-name>
</cmp-field>
<cmp-field>
<field-name>sourceId</field-name>
</cmp-field>
<ejb-local-ref>
<ejb-ref-name>ejb/rfx/RFXDocumentAttachment</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>au.com.alphawest.trader.rfx.business.data.RFXAttachmentLocalHome</local-home>
<local>au.com.alphawest.trader.rfx.business.data.RFXAttachmentLocal</local>
<ejb-link>RFXAttachment</ejb-link>
</ejb-local-ref>
<ejb-local-ref>
<description>A line item attached to this document</description>
<ejb-ref-name>ejb/rfx/RFXLineItem</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>au.com.alphawest.trader.rfx.business.data.RFXLineItemLocalHome</local-home>
<local>au.com.alphawest.trader.rfx.business.data.RFXLineItemLocal</local>
<ejb-link>RFXLineItemBean</ejb-link>
</ejb-local-ref>
<query>
<description>Find the rfx documents related to the given supplier through it's line items</description>
<query-method>
<method-name>findBySupplierId</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</query-method>
<ejb-ql>SELECT OBJECT(d) FROM RFXDocument AS d, IN(d.lineItems) l WHERE l.supplierGuid = 'DummySupplierGuid'</ejb-ql>
</query>
</entity>
<entity>
<display-name>RFXLineItem</display-name>
<ejb-name>RFXLineItem</ejb-name>
<local-home>au.com.alphawest.trader.rfx.business.data.RFXLineItemLocalHome</local-home>
<local>au.com.alphawest.trader.rfx.business.data.RFXLineItemLocal</local>
<ejb-class>au.com.alphawest.trader.rfx.business.data.RFXLineItemBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.math.BigDecimal</prim-key-class>
<reentrant>False</reentrant>
<abstract-schema-name>RFXLineItem</abstract-schema-name>
<cmp-field>
<field-name>itemId</field-name>
</cmp-field>
<cmp-field>
<field-name>rfxGuid</field-name>
</cmp-field>
<cmp-field>
<field-name>contractCode</field-name>
</cmp-field>
<cmp-field>
<field-name>supplierGuid</field-name>
</cmp-field>
<cmp-field>
<field-name>productCode</field-name>
</cmp-field>
<cmp-field>
<field-name>description</field-name>
</cmp-field>
<cmp-field>
<field-name>quantity</field-name>
</cmp-field>
<cmp-field>
<field-name>units</field-name>
</cmp-field>
<primkey-field>itemId</primkey-field>
</entity>
</enterprise-beans>
<relationships>
<ejb-relation>
<ejb-relation-name>RFXDocument-RFXAttachment</ejb-relation-name>
<ejb-relationship-role>
<ejb-relationship-role-name>RFXDocument</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>RFXDocument</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>attachments</cmr-field-name>
<cmr-field-type>java.util.Collection</cmr-field-type>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>RFXAttachment</ejb-relationship-role-name>
<multiplicity>Many</multiplicity>
<cascade-delete/>
<relationship-role-source>
<ejb-name>RFXAttachment</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>
<ejb-relation>
<ejb-relation-name>RFXDocument-RFXLineItem</ejb-relation-name>
<ejb-relationship-role>
<ejb-relationship-role-name>RFXDocument</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>RFXDocument</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>lineItems</cmr-field-name>
<cmr-field-type>java.util.Set</cmr-field-type>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>RFXLineItem</ejb-relationship-role-name>
<multiplicity>Many</multiplicity>
<cascade-delete/>
<relationship-role-source>
<ejb-name>RFXLineItem</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>
</relationships>
<assembly-descriptor>
<container-transaction>
<description>This value was set as a default by Sun ONE Studio.</description>
<method>
<ejb-name>RFXAttachment</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<description>This value was set as a default by Sun ONE Studio.</description>
<method>
<ejb-name>RFXDocument</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<description>This value was set as a default by Sun ONE Studio.</description>
<method>
<ejb-name>RFXLineItem</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<description>This value was set as a default by Sun ONE Studio.</description>
<method>
<ejb-name>RFXManager</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
I get the following error message when i try to run the EJB Module through the Sun One Verifier Tool:
Error: ** Error trying to process file: java.lang.RuntimeException: No method found for XML query element: Ambiguous or invalid <query-method>
java.lang.RuntimeException: No method found for XML query element: Ambiguous or invalid <query-method>
at com.sun.enterprise.deployment.xml.EjbNode.parseQueries(EjbNode.java:700)
at com.sun.enterprise.deployment.xml.EjbNode.completeLoadingDescriptor(EjbNode.java:671)
at com.sun.enterprise.deployment.xml.EjbBundleNode.completeLoadingDescriptor(EjbBundleNode.java:524)
at com.iplanet.ias.deployment.EjbBundleXmlReader.load(EjbBundleXmlReader.java:249)
at com.iplanet.ias.deployment.EjbBundleXmlReader.loadStdAloneModule(EjbBundleXmlReader.java:162)
at com.sun.enterprise.tools.verifier.Verifier.openEjbJar(Verifier.java:2421)
at com.sun.enterprise.tools.verifier.Verifier.loadEjbJar(Verifier.java:1318)
at com.sun.enterprise.tools.verifier.Verifier.loadJar(Verifier.java:866)
at com.sun.enterprise.tools.verifier.gui.MainPanel.run(MainPanel.java:187)
at java.lang.Thread.run(Thread.java:536)
Look in file "RFXModule.jar_verified.xml" for detailed results on test assertions.
Any help would be greatly appreciated.
Mark Hesketh

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.Click the Clear Display icon in the toolbar. Then try the action that you're having trouble with again. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

Not able to reload the data from DB using finder methods

Hi all,

I am facing a weird problem while using finder methods.
I am using weblogic 8.1 SP3 and entity beans are CMP with DB concurrency.DB is oracle

<h4>Problem Description</h4>

I am having one session bean which internally interacts with my entity beans,
Now say my transaction is getting initiated in one of the session bean and I use some finder in it.


To make the problem more clear lets say my entity bean is loanBean with loanId as primary key.
Now say method A of session bean initiates the transaction and I use something like
 
LoanLocal loanLocal =loanLocalHome.findByLoanId(loanId);
 
Note that I am not using findByPrimaryKey method
 
now this method A calls some other method B on some session bean which is having Required as its transaction attribute.
 
But before the call of B some other thread or background process updates the DB for this loanId and commits,
 
now when I fire the same finder in method B I am still getting the old data, ie I am not getting the data which has been modified in DB and committed by some other thread, I still get the old data and when I tried to generate the SQL queries which weblogic is firing, I see
it fires the SQL for every finder other that findByPrimaryKey.
 

Now my problem is I am getting the old data only and I need the new updated data of DB. isolation-level of DB and beans is READCOMMITTED.
Note:: I cant use new transaction to read the data.

 
And I couldn't understand that when weblogic is firing query for every finder then why it should not refresh the data in its cache. Is there any way to disable this kind of caching and say that everytime when i use finder just go to DB and get me the last committed data.

 
Any help in this regard would be very helpful to me.
 
Thanks and Regards
 
Manish Garg.


Hi,
In my understanding, cache is not involved in this scenario. As you
observed, the container fires sql every time when you invoke this finder.
So, it should just give the result that it got from the DB. Is there a
possibility that the DB is using repeatable_read or serializable for
isolation level?
You can debug further by doing couple of things -
1. Instrument the code in the generated RDBMS java file for the entity bean
(if you use -keepgenerated option for weblogic.ejbc, u can get the source of
this file). This class will have the implementation for ejbFindByLoanId. You
can just print the result set data after the query is fired.
2. Try the same scenario without the ejb container. Like, write a jsp which
will start a user tx and fire the query twice such that there is an update
between the two queries. Note that, you need to use a TxDataSource to get
the JDBC connection so that it will be tx aware.
--Sathish
<Manish Garg> wrote in message news:[email protected]...
Hi all,

I am facing a weird problem while using finder methods.
I am using weblogic 8.1 SP3 and entity beans are CMP with DB
concurrency.DB is oracle

<h4>Problem Description</h4>

I am having one session bean which internally interacts with my entity
beans,
Now say my transaction is getting initiated in one of the session bean and
I use some finder in it.


To make the problem more clear lets say my entity bean is loanBean with
loanId as primary key.
Now say method A of session bean initiates the transaction and I use
something like
 
LoanLocal loanLocal =loanLocalHome.findByLoanId(loanId);
 
Note that I am not using findByPrimaryKey method
 
now this method A calls some other method B on some session bean which is
having Required as its transaction attribute.
 
But before the call of B some other thread or background process updates
the DB for this loanId and commits,
 
now when I fire the same finder in method B I am still getting the old
data, ie I am not getting the data which has been modified in DB and
committed by some other thread, I still get the old data and when I tried
to generate the SQL queries which weblogic is firing, I see
it fires the SQL for every finder other that findByPrimaryKey.
 

Now my problem is I am getting the old data only and I need the new
updated data of DB. isolation-level of DB and beans is READCOMMITTED.
Note:: I cant use new transaction to read the data.

 
And I couldn't understand that when weblogic is firing query for every
finder then why it should not refresh the data in its cache. Is there any
way to disable this kind of caching and say that everytime when i use
finder just go to DB and get me the last committed data.

 
Any help in this regard would be very helpful to me.
 
Thanks and Regards
 
Manish Garg.

Class cast exception using Finder method

Hello. I'm new to J2EE. I have set up one entity bean but am having trouble
with my current one.
Basically, I have two finder methods:
public ShareHistory findByPrimaryKey(Integer historyId)
        throws FinderException, RemoteException;
    public Collection findByShare(String shareId)
         throws FinderException, RemoteException; findByPrimaryKey works fine, but findByShare causes a class cast exception in java.lang.String.
The stack trace in the server logs shows that it is my ejbActivate method in my entity bean causing the problem:
public void ejbActivate() {
      //String numberString = (String) context.getPrimaryKey();
      //historyId = new Integer(numberString);
    historyId = (Integer) context.getPrimaryKey();
    }The stack trace from my client shows that the class cast exception occurs
in the client at the System.out.println("shareid" + ": " + sh.getShareId());
line:
Collection c = sharesHistoryHome.findByShare("DCAN");
                 Iterator i = c.iterator();
                      while (i.hasNext()) {
                     ShareHistory sh = (ShareHistory) i.next();
                System.out.println("shareid" + ": " + sh.getShareId());
                System.out.println("value" + ": " + sh.getValue());
                 System.out.println("time" + ": " + sh.getTime());
                 System.out.println("date" + ": " + sh.getDate());
                 }//whileAs you can see I tried casting to a string in ejbactivate, but that simply causes an Integer class cast exception during findByprimaryKey instead. How do I allow both Integer and String objects to be used?
Also I am a bit confused as to why the String passed to findByShare(String) is being used in context.getPrimaryKey() in the first place (if that is actually what's happening).

Oops my FindByShare method was returning a collection of shareId's (strings) instead of a collection of Integer primary keys, which would explain the class cast exception.

Custom finder methods

I'm tring to deploy an Entity bean (CMP) with custom finder method that gets a parameter.
I encountered two problems :
1) defining the query in the deployment descriptor coased the app server to generate the a query without the where cloase - this was fixed by changing manualy the orion-ejb-jar.xml in the application-deployments directory.
2)the second, and yet unresolved problem, is that OC4J doesn't bind the parameter that the query uses during runtime. I'm recieving an ORA msg that claims that not all the parameters are binded.

see sample code
http://otn.oracle.com/sample_code/tech/java/oc4j/htdocs/oc4jsamplecode/oc4j-demo-ejb.html
also there should be a section in our documentation about cmp custom finder methods. oc4j attempts to generate custome finder methods based on home interface
<finder-method query="$empNo = $1">
<method>
 <ejb-name>EmployeeBean</ejb-name>
 <method-name>findByEmpNo</method-name>
 <method-params>
 <method-param>java.lang.Integer</method-param>
 </method-params>
 </method>
 </finder-method>

Ejb-ql in finder method

Hi all,
I have a table which has no primary key then I made the complex primary key by 2 fields which are foriegn keys(Primary key in other tables or entity beans) , the problem is that whenever I write a finder method ,I face with an error telling these 2 fields are not cmp field .
could you please guide me .In addition I need a finder method which gets 2 parameters (the 2 foriegn keys) then return the the raw.
Not having known so much about reletionship in EJB ,please give me a sample code
Cheers
Pooyan

What do you expect us to tell without even a small description of your problem (a stack trace or error message would have been helpful). Anyway, read here... you should find some sample code too.
http://www.theserverside.com/books/masteringEJB/index.jsp

Finder-method in orion-ejb-jar.xml

Hi,
Is there a way to let jdeveloper 9.0.3 preview to automatically generate finder-method descriptors for us? When I was developing a cmp-based entity bean, although I defined the ejb-ql in ejb-jar.xml, JDeveloper still just generated the first orion-ejb-jar.xml shown below. In the first orion-ejb-jar.xml, there is no definition for any finder-method. I have to manually add my own definition to it, which is shown in the second orion-ejb-jar.xml. I know that the oc4j container will generate the finder-method after deployment, but in some situation it generated incorrect finder-method descriptors. One of such situation is the between query like "between ?1 and ?2". Anyway, if JDeveloper can generate the finder-method during development, then we can know whether the descriptor is correct or not before deployment, and we can make modifications before deploying it to oc4j server.
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" " " target="_new">http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd"> <orion-ejb-jar>
<enterprise-beans>
<entity-deployment name="BooksBean" data-source="jdbc/bookDS" table="BOOKS">
<primkey-mapping>
<cmp-field-mapping>
<fields>
<cmp-field-mapping name="isbn" persistence-name="ISBN" persistence-type="NUMBER(10)"/>
</fields>
</cmp-field-mapping>
</primkey-mapping>
<cmp-field-mapping name="isbn" persistence-name="ISBN" persistence-type="NUMBER(10)"/>
<cmp-field-mapping name="title" persistence-name="TITLE" persistence-type="VARCHAR2(50)"/>
<cmp-field-mapping name="author" persistence-name="AUTHOR" persistence-type="VARCHAR2(50)"/>
<cmp-field-mapping name="price" persistence-name="PRICE" persistence-type="NUMBER(6,2)"/>
</entity-deployment>
</enterprise-beans>
<assembly-descriptor>
<default-method-access>
<security-role-mapping name="<default-ejb-caller-role>" impliesAll="true"/>
</default-method-access>
</assembly-descriptor>
</orion-ejb-jar>
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" " " target="_new">http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd"> <orion-ejb-jar>
<enterprise-beans>
<entity-deployment name="BooksBean" data-source="jdbc/bookDS" table="BOOKS">
<primkey-mapping>
<cmp-field-mapping name="isbn" persistence-name="ISBN" persistence-type="NUMBER(10)"/>
</primkey-mapping>
<cmp-field-mapping name="isbn" persistence-name="ISBN" persistence-type="NUMBER(10)"/>
<cmp-field-mapping name="title" persistence-name="TITLE" persistence-type="VARCHAR2(50)"/>
<cmp-field-mapping name="author" persistence-name="AUTHOR" persistence-type="VARCHAR2(50)"/>
<cmp-field-mapping name="price" persistence-name="PRICE" persistence-type="NUMBER(6,2)"/>
<finder-method query="select * from books where $author like $1">
<method>
<ejb-name>BooksBean</ejb-name>
<method-name>findByAuthor</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
</finder-method>
<finder-method query="select * from books where $title like $1">
<method>
<ejb-name>BooksBean</ejb-name>
<method-name>findByTitle</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
</finder-method>
<finder-method query="$price between $1 and $2">
<method>
<ejb-name>BooksBean</ejb-name>
<method-name>findByPriceRange</method-name>
<method-params>
<method-param>double</method-param>
<method-param>double</method-param>
</method-params>
</method>
</finder-method>
</entity-deployment>
</enterprise-beans>
<assembly-descriptor>
<default-method-access>
<security-role-mapping impliesAll="true" name="<default-ejb-caller-role>"/>
</default-method-access>
</assembly-descriptor>
</orion-ejb-jar>
Any one has any idea?
Thanks,
Jingzhi

Jingzhi -- If you define the correct EJB-QL you should get the correct SQL generated for the finder. If that's not happening can you verify it against the OC4J v903 production release and see if it is still happening. I don't know if this helps with the JDeveloper problem specifically but if you don't need to create your own finders then that I hope should help.
Thanks -- Jeff

Strange behavior of std::string find method in SS12

Hi
I faced with strange behavior of std::string.find method while compiling with Sunstudio12.
Compiler: CC: Sun C++ 5.9 SunOS_sparc Patch 124863-14 2009/06/23
Platform: SunOS xxxxx 5.10 Generic_141414-07 sun4u sparc SUNW,Sun-Fire-V250
Sometimes find method does not work, especially when content of string is larger than several Kb and it is needed to find pattern from some non-zero position in the string
For example, I have some demonstration program which tries to parse PDF file.
It loads PDF file completely to a string and then iterately searches all ocurrences of "obj" and "endobj".
If I compile it with GCC from Solaris - it works
If I compile it with Sunstudio12 and standard STL - does not work
If I compile it with Sunstudio12 and stlport - it works.
On win32 it always works fine (by VStudio or CodeBlocks)
Is there any limitation of standard string find method in Sunstudio12 STL ?
See below the code of tool.
Compilation: CC -o teststr teststr.cpp
You can use any PDF files larger than 2kb as input to reproduce the problem.
In this case std::string failes to find "endobj" from some position in the string,
while this pattern is located there for sure.
Example of output:
CC -o teststr teststr.cpp
teststr in.pdf Processing in.pdf
Found object:1
Broken PDF, endobj is not found from position1155
#include <string>
#include <iostream>
#include <fstream>
using namespace std;
bool parsePDF (string &content, size_t &position)
 position = content.find("obj",position);
 if( position == string::npos ) {
 cout<<"End of file"<<endl;
 return false;
 position += strlen("obj");
 size_t cur_pos = position;
 position = content.find("endobj",cur_pos);
 if( position == string::npos ){
 cerr<<"Broken PDF, endobj is not found from position"<<cur_pos<<endl;;
 return false;
 position += strlen("endobj");
 return true;
int main(int argc, char ** argv)
 if( argc < 2 ){
 cout<<"Usage:"<<argv[0]<<" [pdf files]\n";
 return -3;
 else {
 for(int i = 1;i<argc;i++) {
 ifstream pdfFile;
 pdfFile.open(argv,ios::binary);
if( pdfFile.fail()){
cerr<<"Error opening file:"<<argv[i]<<endl;
continue;
pdfFile.seekg(0,ios::end);
int length = pdfFile.tellg();
pdfFile.seekg(0,ios::beg);
char *buffer = new char [length];
if( !buffer ){
cerr<<"Cannot allocate\n";
continue;
pdfFile.read(buffer,length);
pdfFile.close();
string content;
content.insert(0,buffer,length);
delete buffer;
// the lets parse the file and find all endobj in the buffer
cout<<"Processing "<<argv[i]<<endl;
size_t start = 0;
int count = 0;
while( parsePDF(content,start) ){
cout<<"Found object:"<<++count<<"\n";
return 0;

Well, there is definitely some sort of problem here, maybe in string::find, but possibly elsewhere in the library.
Please file a bug report at [http://bugs.sun.com] and we'll have a look at it.

Error in finder method wrapper resulting in a connection leak

we ar using OC4J 1.0.2.2.1 and dicowered some problems with connection leaking.
The same was reproducable on 9.0.2.1 and 9.0.3 (the "J2EE 1.3 certified" version).
Using CMP/CMT for Entity EJB.
If we define the transaction attribute for a finder method returning single object as NotSupported
and ObjectNotFound exception is thrown as a result of call to the finder method,
connection is not closed.
With emulated datasource this results in a connection pool overflow, with XA datasource
the console gets conenction not closed exceptions but at least connections are closed (seriously influencin performance while waiuting for connection timeout).
the same code executes with no problem on JBoss 2.4.x and 3.0 and on iPlanet.
any comments on this - is this a bug or feature ?

Please log a TAR with your support repesentative so that we can drill down on this issue. As described, this does not sound like the correct behavior but until the details are examined it is hard to tell.
Thanks -- Jeff

CMP finder method error

I'm now using Jbuilder7+weblogic7 to do some EJB develop.
Weblogic server is configured to run inside the Jbuilder IDE, and my CMP entity bean has been deployed successfully.
I new a "EJB test client" within Jbuilder to test my CMP bean, I could create entity bean via create method, but when I using finder method to find a bean, the client report that "java.sql.SQLException: No data found"!
My EJB-QL is:"SELECT OBJECT(o) FROM Account o WHERE o.ownername = ?1"
And below is the exception report:
javax.ejb.FinderException: Problem in findByOwnername while preparing or executing statement: 'weblogic.jdbc.rmi.SerialPreparedStatement@1d2384':
java.sql.SQLException: No data found
java.sql.SQLException: No data found
     at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:6212)
     at sun.jdbc.odbc.JdbcOdbc.SQLGetDataString(JdbcOdbc.java:3266)
     at sun.jdbc.odbc.JdbcOdbcResultSet.getDataString(JdbcOdbcResultSet.java:5398)
     at sun.jdbc.odbc.JdbcOdbcResultSet.getString(JdbcOdbcResultSet.java:326)
     at weblogic.jdbc.jts.ResultSet.getString(ResultSet.java:84)
     at weblogic.jdbc.rmi.internal.ResultSetImpl.getString(ResultSetImpl.java:178)
     at weblogic.jdbc.rmi.internal.ResultSetStraightReader.getString(ResultSetStraightReader.java:37)
     at weblogic.jdbc.rmi.SerialResultSet.getString(SerialResultSet.java:128)
     at cmptest.AccountBean_8259n1__WebLogic_CMP_RDBMS.__WL_loadGroup0FromRS(AccountBean_8259n1__WebLogic_CMP_RDBMS.java:945
Can anybody help me out? Thanks.

The Exception is pretty clear there are no Records found for the Owner Name u give. Try Creating the Suitable record from ur Entity Bean(create method of course) then check in the DB for the Record and then try to retrieve it....I don't think there should be any problem....
Cheers,
manja

Finder method in Entity bean

how many Finder method in Entity bean i can write ?
look below...
public Account findByPrimaryKey(AccountPK key) throws FinderException,
RemoteException;
public Enumeration findByOwnerName(String name) throws FinderException,
RemoteException;here 2 finder methods are there.......i am asking how much freedom i have ? can write as many as finder method i wish ?
say, findXXXX() ?

my problem is on the signature of the find
method.
OK let me ask you some other way.
java DOC says
Each enterprise Bean has a home interface. The home
interface must extend the javax.ejb.EJBHome
interface, and define the enterprise Bean type
specific create and finder methods (session Beans do
not have finders).
look it says " finder methods "....right .
so i want to ask 2 question about this phrase . PLZ
do confirm me whether i am right or wrong.
fact 1. finder methods means you can write
any method name which starts with word find
and ONLY find
Example: findABCD( ) , findEFGH(),
findBLAHBLAH()...any thing starts with find[i]
are called finder methods...others are NOT.
is This fact correct ?
Yes.
fact 2. Is not it Strange that i need to
append some letters after the word find to
get a finder method name !! why not wrting a simple
method name ( say abcdfgrty () instead of
findXXXX() which will do the job ??You can... but it has to be called form a findXXXX() method :)
As such there is no problem in writng a
find_ANY_WORDS_HERE() to get a finder method but
problem is why i need to stick to the word
find and append some words after it
t to get a finder method ? if i had to do it
seriously then whats the role of the container ? how
w it is linking ?Once someone takes the pain of going through the EJB specs, he would not have a problem. Imagine each vendor using his own brains and the developer getting bugged with new features in each AS. EJB specs are flexible enough already :)

OC4J: EJB FREEZING IN FINDER METHOD

I HAVE VARIOUS EJB BASED ON VIEWS, AND ALL EXCEPT ONE FREEZES WHEN I INVOQUE IT'S FINDER METHODS. I HAVE CHECKED EVERYTHING AND FOUND THE FOLLOWING MESSAGES:
Thr[thread 5]-DriverManagerPooledConnection.close(): begin---this.nextConnectionNumber=1
Thr[thread 5]-DriverManagerPooledConnection.close(): begin---this.closed=false
AND IT LOOPS FOREVER WITH THE FOLLOWING MESSAGES:
Thr[thread 5]-ApplicationServerTransaction.setRollbackOnly(message, Throwable_Obj): begin--message=timed out
Thr[thread 5]-ApplicationServerTransaction.setRollbackOnly(message, Throwable_Obj): begin--Throwable_Obj=null
Thr[thread 5]-ApplicationServerTransaction.setRollbackOnly(message, Throwable_Obj): end
Erika.

Hi Erika,
It looks like you are running OC4J in "debug" mode. I don't know whether this will help you, but I have found that sometimes, running in debug mode can cause problems, but these problems will "disappear" when not running in debug mode. So have you tried running OC4J in "normal" (i.e. not debug) mode?
Good Luck,
Avi.

60 Second Delays in Client Getting Entity Bean (after finder method)

I am running WLS5.1 with SP10. I have a stateless EJB that gets a
read-write BMP entity EJB. My test client that executes the stateless
session bean periodically encounters long delays (60 seconds or more)
when acquiring the entity bean using its finder method. Logging shows
the finder method is executing properly, and typically takes 180 ms to
locate the entity bean; however, from the stateless session beans side,
it appears to take 60 seconds. The test client is only a single thread,
so I know the pool is not depleted, or anything like that. Something
appears to be going haywire with the container.
Does anybody have an idea what might be going on?
Thanks.
Greg

Hi Greg,
On a whim, I tried the same test with the thin driver, and the same
delay occurred. This time, instead of a rollback being at the top ofthe
thread dump stack trace, it was in some other Oracle call, with the
top of the stack trace being a socketreader.are you using MTS? Is the db-server a SMP-box? Which exact patch level
does your Oracle instance have? If yes, can you try to force a dedicated
server connection and see if the problem disappears? I guess for an OCI
connection you will have to edit tnsnames.ora, for a
thin-driver-connection you would have to modify the connect string to
something like this:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOS
T=<dnsname>)(PORT=1521)))(CONNECT_DATA=(SID=<your
sid>)(SERVER=DEDICATED))))
There is a bug in 8.1.6.0 which is supposed to be fixed in 8.1.6.3, but
I can still reproduce it in 9i :-(. It makes the MTS-dispatcher hang for
60 seconds if you have an SMP box with low load, so maybe this could be
your problem.
Daniel
-----Original Message-----
From: Greg Crider [mailto:[email protected]]
Posted At: Wednesday, November 28, 2001 8:17 AM
Posted To: ejb
Conversation: 60 Second Delays in Client Getting Entity Bean (after
finder method)
Subject: Re: 60 Second Delays in Client Getting Entity Bean (after
finder method)
My client has been using OCI in production and development
with JTS for
over a year now without a problem. We went to OCI because
there was some
other problem with the thin driver. I'm not sure what the
problem was,
but Oracle acknowledged it, but said it wouldn't be corrected until
Oracle 9i came out. We're still using 8.1.6, so from what I'm
told, we
don't use the thin driver.
On a whim, I tried the same test with the thin driver, and the same
delay occurred. This time, instead of a rollback being at the
top of the
thread dump stack trace, it was in some other Oracle call, with the
top of the stack trace being a socketreader.
Somebody else suggested that there may be a problem with
transactions.
Does this ring a bell? Again, I have a stateless session bean
invoking a
read-write entity bean, invoking a read-only entity bean. From
everything I read, including weblogic docs, I should just rely on my
deployment descriptor to control transactions and stay away from JTA.
Hi Greg,
I remeber long ago there were an issue with jts/oci driver combination
when the connections were opened but never used...
Buy the way, are there any specific reasons to use OCI instead of
thin driver?
"Greg Crider" <[email protected]> wrote in message
news:[email protected]...
I know. That's what I don't get. BTW Slava, I am using the
latest OCI
driver; thanks for the suggestion. I tried tweaking some of the Solaris
kernel settings as relates to TCP, but that didn't clear up the problem
either; however, it did change the frequency. Modifying the retransmit
settings (very small values, sub 1.5 seconds) seemed to make it occur
less frequently.
It seems like its time for me to contact BEA Support and see what they
can turn up. Thanks for the suggestions. If anybody else has an idea,
let me know. I'm betting this is a simple, stupid config problem. I'll
post back here when I find out what's up.
But for some reason WebLogic code called the rollback:
... rollback
at
weblogic.jdbc.common.internal.ConnectionEnv.cleanup(Connection
Env.java:499)
at
weblogic.jdbc.common.internal.ConnectionEnv.destroy(Connection
Env.java:417)
at
weblogic.jdbc.common.internal.ConnectionEnv.destroy(Connection
Env.java:393)
at weblogic.jdbcbase.jts.Connection.close(Connection.java:274)
at weblogic.jdbcbase.jts.Connection.commit(Connection.java:530)
at
weblogic.jdbcbase.jts.TxConnection.commitOnePhase(TxConnection
.java:55)
at
weblogic.jts.internal.CoordinatorImpl.commitSecondPhase(Coordi
natorImpl.java
:484)
at
weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:383)
at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
Slava Imeshev <[email protected]> wrote:
Hi Greg,
Which version of OCI driver do you use? OCI driver proved to be
not that stable as the thin driver. Could you try to download
and to install the latest version of the OCI driver and
let us know
if it helps?
Regards,
Slava Imeshev
[email protected]
"Greg Crider" <[email protected]> wrote in message
news:[email protected]...
Yup, get fresh connection from the db connection pool,
and close it
>when
I'm done. The logs don't indicate that I've ever exhausted the
connection pool.
It's interesting to note these problems are occurring on
Solaris with
Oracle OCI connections. Running the same code under Linux with thin
driver connections works just fine.
Weird. Do you obtain database connection from a
datasource and close
>it
every time
you use it?
Greg Crider <[email protected]> wrote:
Okay, this appears to be the offending thread. As it
turns out, the
>same
behavior as first described in my initial post, is
occurring this
>time
in the
business method of the entity bean, as opposed to the
finder. The
getNextURL() is the business method in this case. I am using BMP, and
the
ejbLoad() and ejbStore() methods are not throwing any
SQLExceptions.
Also, I
don't see anything in the error logs that indicate a
EJB transaction
failure.
This being the case, why would an Oracle rollback be
attempted? Am I
misinterpretting this stack trace?
"ExecuteThread-67" daemon prio=5 tid=0x14e300 nid=0x51 runnable
[0xe7880000..0xe7881a30]
at oracle.jdbc.oci8.OCIDBAccess.do_rollback(Native Method)
at oracle.jdbc.oci8.OCIDBAccess.rollback(OCIDBAccess.java:417)
at
oracle.jdbc.driver.OracleConnection.rollback(OracleConnection.java:510)
at
weblogic.jdbc.common.internal.ConnectionEnv.cleanup(ConnectionEnv.java:4
>99
at
weblogic.jdbc.common.internal.ConnectionEnv.destroy(Conne
ctionEnv.java:4
>17
at
weblogic.jdbc.common.internal.ConnectionEnv.destroy(Conne
ctionEnv.java:3
>93
at weblogic.jdbcbase.jts.Connection.close(Connection.java:274)
at weblogic.jdbcbase.jts.Connection.commit(Connection.java:530)
at
weblogic.jdbcbase.jts.TxConnection.commitOnePhase(TxConnec
tion.java:55)
at
weblogic.jts.internal.CoordinatorImpl.commitSecondPhase(CoordinatorImpl.
>ja
va:484)
at
weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorIm
pl.java:383)
at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
at
weblogic.ejb.internal.StatefulEJBObject.postInvokeOurTx(StatefulEJBObjec
>t.
java:320)
at
weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObje
ct.java:845)
at
com.pi.speechport.ETO.LoadShare.ETOLoadShareEJBEOImpl.getNextURL(ETOLoad
>Sh
areEJBEOImpl.java:114)
at
com.pi.speechport.ETO.Transcription.ETOTranscriptionBusin
ess.getVendorUR
>L(
ETOTranscriptionBusiness.java:146)
at
com.pi.speechport.ETO.Transcription.ETOTranscriptionBusin
ess.transcribe(
>ET
OTranscriptionBusiness.java:193)
at
com.pi.speechport.ETO.Transcription.ETOTranscriptionEJBEO
Impl.transcribe
>(E
TOTranscriptionEJBEOImpl.java:188)
at
com.pi.speechport.ETO.Transcription.ETOTranscriptionEJBEO
Impl_WLSkel.inv
>ok
e(ETOTranscriptionEJBEOImpl_WLSkel.java:223)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(B
asicServerObjec
>tA
dapter.java:347)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest
(BasicRequestHa
>nd
ler.java:86)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicEx
ecuteRequest.ja
>va
:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Dimitri Rakitine wrote:
Make a thread dump during these 60 seconds to see
what server is
>doing.
Greg Crider <[email protected]> wrote:
I am running WLS5.1 with SP10. I have a stateless
EJB that gets a
read-write BMP entity EJB. My test client that executes the
stateless
session bean periodically encounters long delays (60
seconds or
>more)
when acquiring the entity bean using its finder
method. Logging
>shows
the finder method is executing properly, and
typically takes 180 ms
>to
locate the entity bean; however, from the stateless
session beans
side,
it appears to take 60 seconds. The test client is
only a single
thread,
so I know the pool is not depleted, or anything like that.
Something
appears to be going haywire with the container.
Does anybody have an idea what might be going on?
Thanks.
Greg
Dimitri
Greg
>__
GREGORY K. CRIDER, Emerging Digital Concepts
Systems Integration/Enterprise Solutions/Web &
Telephony Integration
(e-mail) [email protected]
(web) http://www.EmergingDigital.com
(voicemail) 866-474-4147
(phone) 703-335-0974
(cell) 703-851-5073
(fax) 703-365-0223

Finder methods problem

Similar Messages

Maybe you are looking for