Messages

Hi Jason,

You could set this search order value in a custom field in each product then set in the DataDescriptor that you want to order by that field.. then call searchForProducts.

See:  http://www.konakart.com/javadoc/server/com/konakart/appif/KKEngIf.html#searchForProducts(java.lang.String, com.konakart.appif.DataDescriptorIf, com.konakart.appif.ProductSearchIf, int)

That's left up to you but you could use the ANT build file under the custom directory as a starting point.

The User Guide includes the Developer's guide.   It's included as part of the download package.

Default location is:

"C:\\Program Files\\KonaKart\\doc\\KonaKart_User_Guide.pdf"

Yes, we have been able to reproduce.  Thanks for reporting this problem.

See a code fix in this thread:
http://www.konakart.com/forum/index.php/topic,1545.msg6125.html#msg6125

This will be fixed in 5.5.0.1 which should be available within the next few days.

If you go into the Admin App and enable the user in question, then the password will work.   It's not working because the user is not enabled.  It's not enabled because of the problem with the new user registration in GWT in 5.5.0.0 which you reported earlier.

We have seen the problem with the one page checkout new user registration and will fix that and prepare a 5.5.0.1 release very soon.

In the meantime you could switch to using the JSP version of the checkout where the new user registration works fine.

Thanks for reporting the problem.

We have failed to reproduce on our demo or on our own local systems.

When you get your password back in the email, you're not using the period (".") at the end as part of your password are you?

This is not part of the password. 

I think we'll remove that period in future versions.

I've just tried this and couldn't reproduce the problem.

What are your platform details?  Ops Sys?, DB?, java?

We have added an automatic re-connection in v5.7.0.0 but there is no way to configure this in earlier versions.

Supported customers should make contact through the normal channels for other options.

the documentation had nothing that even hints that this would be the issue, but if you use a DataDescriptor, you must use setLimit() to get any actual objects back

The javadoc for setLimit gives you a pretty good hint where it states:

void   setLimit(int limit)
          It defines the maximum number of objects returned.

fixed in v 5.5.0.0

Note that this is only a problem in Oracle 11gR2 ENTERPRISE edition where the new DEFERRED_SEGMENT_CREATION is set to TRUE.

A workaround for this has been added to the KonaKart installers from v5.6.0.0

A good way to diagnose the problem for yourself is to turn on the SQL debugging so that you can see the queries being executed.

When you do that I imagine you will see that you need to set something in the DataDescriptor - maybe something like the Limit to something large?

I assume you have seen the Admin APIs?

The javadoc is installed in the standard installation at http://localhost:8780/javadoc/

You should look at the KKAdminIf for the Admin APIs

getOrders looks like a possible candidate although it might be a bit heavy for just getting the count.   I guess it depends if getting the orders back is useful to you or not.... and also how many orders you're likely to retrieve and how often you call this.


Failing that you could create your own API call (see the custom() call (or customSecure() call))  and define your own parameters to define your search conditions - then your implementation can execute your count functions.   

It really depends what you need to achieve.

In some instances creating a BIRT report might even be the best solution... or indeed a custom query as you are doing already!

might seem a silly question but did you refresh the browser to ensure you weren't caching the old one page checkout code?     

If you don't want to use the GWT One page checkout you could always switch to the JSP-based multi-page version instead.

However, if you haven't looked closely at GWT yet you still might want to try to understand that first.  For a java programmer it should be easy to understand as it's all java code.  The GWT compiler converts that java code into javascript but you don't need to worry about those details.

You can even import this one page checkout GWT code into Eclipse and debug it easily from there - stepping through your java code as the javascript executes.   It's very clever stuff.

Check out the User Guide for details.