[EJB 3.0] - Re: 10,000 Recorc Per Second (In EJB 3.0)
by snau2005
"fhh" wrote : Can you post the code of your stored procedure?
|
| 40.000 records in 5-6 seconds is too low. I would expect much better performance.
|
| Regards
|
| Felix
here it is the function. Please ignore parameters (i just took one function as example, as you see i generate id's by myself (was lazy to create sequence :)). I use the same table (TUser as in ejb implementation)
FUNCTION GETTUSER(traderCode varchar2, userName varchar2) RETURN varchar2 is
| rez varchar2(4000);
| aaa number(10);
| iii number(10);
|
| begin
| select max(id) into aaa from TUser;
| FOR iii in (aaa + 1) .. (aaa + 40001) LOOP
| insert into TUser (id, userid, username, userdesc) values (iii, 'useridproc', 'usernameproc', 'userdesc'||iii);
| END LOOP;
| commit;
| rez := 'hoho and the bottle of rum';
| return rez;
| end;
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039872#4039872
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039872
19 years
[JBoss Seam] - BUG - EntityQuery paging requires client-side state saving?
by ASavitsky
I haven't found any mentions on that in Seam docs, but it seems that the example code in 10.3 ("Query Objects") that shows pagination support for EntityQuery, only works when javax.faces.STATE_SAVING_METHOD is "client". When the state is saved on the server, the application always shows the first page. Is this the way it was intended to work, or is this a bug?
components.xml:
<fwk:entity-query name="auditRecords" ejbql="FROM AuditInfo"
| order="createdOn DESC" max-results="10" />
auditLog.xhtml:
<h:dataTable id="table" var="auditRecord" value="#{auditRecords.resultList}">
| <f:facet name="footer">
| <h:panelGrid columns="4">
| <s:link value="First">
| <f:param name="start" value="0" />
| </s:link>
| <s:link value="Prev">
| <f:param name="start" value="#{auditRecords.previousFirstResult}" />
| </s:link>
| <s:link value="Next">
| <f:param name="start" value="#{auditRecords.nextFirstResult}" />
| </s:link>
| <s:link value="Last>
| <f:param name="start" value="#{auditRecords.lastFirstResult}" />
| </s:link>
| </h:panelGrid>
| </f:facet>
| <h:column>
| <f:facet name="header">
| <h:outputText value="Id" />
| </f:facet>
| <h:outputText value="#{auditRecord.id}" />
| </h:column>
| <h:column>
| <f:facet name="header">
| <h:outputText value="Date" />
| </f:facet>
| <h:outputText value="#{auditRecord.createdOn}" />
| </h:column>
| <h:column>
| <f:facet name="header">
| <h:outputText value="User" />
| </f:facet>
| <h:outputText value="#{auditRecord.createdBy}" />
| </h:column>
| </h:dataTable>
|
pages.xml:
<page view-id="/auditLog.xhtml">
| <param name="start" value="#{auditRecords.firstResult}" />
| </page>
|
Thanks,
Alex
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039865#4039865
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039865
19 years
[JBoss Seam] - Re: Login Best Practices
by chubby
Thank you for the responses.
Shane, it looks like a JIRA was already opened on the subject (see my link), but I could open another if you think its best?
I am using facelets and I agree it would probably not be too much trouble to roll my own solution. I've just been trying to do things the "seam" way first.
I also agree that its best for the Seam team to move carefully, especially in the area of security. It just had me wondering if there wasn't a good reason for not supporting a scheme attribute and perhaps a larger issue I should be aware of. After all, its not really a seam issue, JSF doesn't support it either.
Anyhow, for us, we decided to replace our login form on the home page with a link to the login form instead.
Thanks for the help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039859#4039859
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039859
19 years