[374 total ]
Database "JFire_JBossMQ" on server "jdbc:mysql://localhost/" could not be created [by danga]

General:: Database "JFire_JBossMQ" on server "jdbc:mysql://localhost/" could not be created
Dear all,

When I start the server I am getting the next error. How can I solve this ?

regards,
Danny

12:54:12,031 INFO ... [More] [DatabaseAdapterMySQL] Creating database "JFire_JBossMQ" on server "jdbc:mysql://localhost/"
12:54:12,828 INFO [DatabaseAdapterMySQL] Database "JFire_JBossMQ" on server "jdbc:mysql://localhost/" could not be created, because of an unexpected failure!
com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Access denied for user 'jfire'@'%' to database 'jfire_jbossmq'
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2870)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1573)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1665)
at com.mysql.jdbc.Connection.execSQL(Connection.java:3118)
at com.mysql.jdbc.Connection.execSQL(Connection.java:3047)
at com.mysql.jdbc.Statement.execute(Statement.java:692)
at org.nightlabs.jfire.servermanager.db.DatabaseAdapterMySQL.createDatabase(DatabaseAdapterMySQL.java:104)
at org.nightlabs.jfire.jboss.serverconfigurator.ServerConfiguratorJBossMySQL.doConfigureServer(ServerConfiguratorJBossMySQL.java:55)
at org.nightlabs.jfire.serverconfigurator.ServerConfigurator.configureServer(ServerConfigurator.java:112)
at org.nightlabs.jfire.servermanager.ra.JFireServerManagerFactoryImpl.configureServerAndShutdownIfNecessary(JFireServerManagerFactoryImpl.java:489)
at org.nightlabs.jfire.servermanager.ra.JFireServerManagerFactoryImpl.serverStarted(JFireServerManagerFactoryImpl.java:560)
at org.nightlabs.jfire.jboss.j2ee.J2EEAdapterJBoss$1.handleNotification(J2EEAdapterJBoss.java:124)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:153)
at $Proxy219.handleNotification(Unknown Source)
at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotification(JBossNotificationBroadcasterSupport.java:127)
at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotification(JBossNotificationBroadcasterSupport.java:108)
at org.jboss.system.server.ServerImpl.sendNotification(ServerImpl.java:916)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:497)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Unknown Source)
12:54:12,828 FATAL [JFireServerManagerFactoryImpl] Problem in serverStarted()! [Less]

Re: Mac OSX [by marco]

Installation / Setup:: Mac OSX
Hello!

We have no Mac OS X here and therefore don't provide any Mac OS X package, yet. If you want to build one, please follow these steps:

1) Download the Eclipse RCP (the platform) for the Mac ... [More] from here: http://www.eclipse.org/downloads/

2) Extract the downloaded platform.

3) Download the JFire Linux client.

4) Copy all plugins (both directories and single-jar-plugins) matching the following file name patterns from the JFire Linux package to the extracted Mac OS X platform:
com.essiembre.eclipse.i18n.*org.holongate.*org.nightlabs.*I hope that I didn't forget any.

5) Then you replace the file ${mac-rcp}/configuration/config.ini by the one from the JFire Linux package.

6) Delete the file ${mac-rcp}/eclipse.ini and copy the file ${jfire-linux}/jfire.ini to your Mac-RCP instead. Rename the file to eclipse.ini (or rename the executable to jfire - the executable must have the same name as the ini-file).

7) Try whether it works. Start your Mac's RCP with the parameters -debug -consolelog to see what's going on.

8) If it works, you can try to replace the plugin org.eclipse.ui.workbench by our patched version. Our patch binds editors to perspectives (just like views), because it makes no sense at all to have for example a User editor open in the Trade perspective.

Background: To understand what the steps above mean, here just a short explanation: Eclipse uses SWT which is a native UI library. All JFire codes are platform independent, hence you can copy the JFire plugins together with the configuration to the Mac's Eclipse RCP platform (containing the native SWT for the Mac). If you copy all required plugins and you don't copy too much (i.e. replacing native Mac code by native Linux code) it should work fine.

Best regards, Marco [Less]

Business Logic [by Holger Sachse]

General:: Business Logic
Hi,

I am testing at the moment the business logic of the 0.9.2 version.

Some behavior is not intuitively understandable! Is there any business process flow oriented requirement documentation existing?

Holger

Re: Issue Reporting System [by marco]

General:: Issue Reporting System
Hello Holger,

I've just added a field "Occurrence Distro" - the field "Target Distro" was already existing.

The "Occurrence Distro" is the version in which a ... [More] bug occurred, while the "Target Distro" is the version we intend to fix the bug. Both versions reference the "distro" - i.e. the complete bundle of all plugins. Most plugins use the same version number as the distro, but some don't.

Best regards, Marco [Less]

Re: Eclipse client distribution [by marco]

General:: Eclipse client distribution
Quote:Tomas wrote:
[...]

gtk32, gtk64 and win32 - enable - false

[...]Nearly everything is deployed for "allplatforms", since it's pure Java and thus platform-independent ... [More] (the property "rcp.deploy.allplatforms.enable" is "true" by default). The platform-dependent deployments are normally only necessary if you use JNI (native libraries) which is a rare exception.

Marco [Less]

https://www.jfire.org/modules/newbb/forum_7.html [by Holger Sachse]

Contribute:: https://www.jfire.org/modules/newbb/forum_7.html
Contributor License Agreement

You and NightLabs hereby accept and agree to the following terms and conditions:

1. Your "Contributions" means all of your ... [More] past, present and future contributions of object code, source code and documentation to a NightLabs project, however submitted to this project, excluding any submissions that are conspicuously marked or otherwise designated in writing by You as "Not a Contribution."

2. You hereby grant to NightLabs a non-exclusive, irrevocable, worldwide, no-charge, transferable copyright license to use, execute, prepare derivative works of, and distribute (internally and externally, in object code and, if included in your Contributions, source code form) your Contributions. Except for the rights granted to NightLabs in this paragraph, You reserve all right, title and interest in and to your Contributions. By contributing to a NightLabs project, you accept especially, but not exclusively, that the project's license is applied to your Contributions.

3. You represent that you are legally entitled to grant the above license. If your employer(s) have rights to intellectual property that you create, you represent that you have received permission to make the Contributions on behalf of that employer, or that your employer has waived such rights for your Contributions to a NightLabs project.

4. You represent that, except as disclosed in your Contribution submission(s), each of your Contributions is your original creation. You represent that your Contribution submission(s) include complete details of any license or other restriction (including, but not limited to, related patents[1] and trademarks) associated with any part of your Contribution(s) (including a copy of any applicable license agreement). You agree to notify NightLabs of any facts or circumstances of which you become aware that would make Your representations in this Agreement inaccurate in any respect.

5. You are not expected to provide support for your Contributions, except to the extent you desire to provide support. You may provide support for free, for a fee, or not at all. Your Contributions are provided as-is, with all faults defects and errors, and without warranty of any kind (either expressed or implied) including, without limitation, any implied warranty of merchantability and fitness for a particular purpose and any warranty of non-infringement.

Your Name: Holger Sachse
Your eMail: var id='holger.sachse';var host1='alice.it';var host2='';document.write('' id '@' host1 '.' host2 '');
Your Country: Italy
Your SourceForge User ID: ________________________________ [Less]

Re: Pricing [by Holger Sachse]

General:: Pricing
Marco,

regarding price lists, what I mean is:

Product grid hierarchy (in my terms)
Product Family
Product Group
Product
Article

Customer hierarchy
Branch (in the ... [More] company)
Region
Customer Group
Customer

Price lists must be able to define prices on every combination of hierarchy. I see from the documentation that Jfire is able to handle a single hierarchy but I can not find any documentation about combinations.

Your mentioned details I would use for nett/ gross price and bonus and other conditions. Also I can not find the concept of a price list in the GUI part.

I do not say that Jfire is not capable to handle this issue, i just can not find it.

Holger [Less]

Re: backhand article [by marco]

General:: backhand article
Thanks a lot for the clarification!

Re: Product Type, Product, Article [by marco]

General:: Product Type, Product, Article
The difference between a product-type and a product is explained in the wiki page ProductType vs. Product. Hope that helps

An instance of the class Article is used to link a Product into an Offer ... [More] or another ArticleContainer (e.g. invoice). Since a product can be sold, reversed and sold again, it occurs in multiple offers and therefore there are multiple articles (for each offer one).

JFire manages ProductType instances in a tree structure, so what you refer to as a "product group" is simply a superordinate product-type in the tree (if I understand you correctly).

Sth. like a package size is currently solely existing in the dynamic product-types (which are used to specify during the sale process what you're about to sell and how much of it - mainly used for immaterial things - e.g. services or royalties).

The "simple" products and the vouchers are managed individually (for example one individual screen with one serial number is one instance of SimpleProduct). [Less]

Re: JPOX 1.2.0-rc-1 [by marco]

Announcements:: JPOX 1.2.0-rc-1
Hello Andy,

thanks a lot for this notification! I'll try the new JPOX out again as soon as I can allocate some time - probably by the end of this week.

We're really looking forward to ... [More] use the new JPOX! I hope, Erik was successful in fixing the last JCA-problem that unfortunately only occured in JFire (not in his small test case).

I'll post my feedback to your forum.

Best regards, Marco [Less]