pavan kumar seeram

Greenhorn
+ Follow
since Nov 21, 2007
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 pavan kumar seeram

That fine......... Arvind........

Yes, you can access your rule service using webservice tooo and that is pretty simple also....... Suppose your Rule Service was deployed as EJB, then you can directly expose your invoking function in EJB as webservice and call your Ruleservice.
12 years ago
Error java.lang.NoClassDefFoundError: org/jboss/logging/Logger indicates the jar file is missing with package name org.jboss.logging.Logger in your .ear file, please place this jar file and try to deploy again. If still this doesnt work try to include the classpath in MANIFEST.MF as Class-Path: log4j-1.2.7.jar
you can see you manifest file at META-INF/MANIFEST.MF in your .ear file
12 years ago
Precompiling means... we are compling the project through the console using .dmanager file and .server file, so that blaze rule engine will create the .adb file and _ser.dmanger for the Repository mentioned in the .dmanger file.

this is the precompile statement we have to execute on console. Here "TestProjectServer.dmanager" and "TestProject.server" are .dmanager and .server files for "TestProject". These files are generated during deployment of project

java -mx256m com.blazesoft.server.deploy.tools.NdAdvisorProjectCompiler -deploymentManager "./TestProjectServer.dmanager" -server "./TestProject.server"

If you have any more doubts regarding Blaze rule engine.... let me know....
13 years ago
Thanks to all for helping me............ I especially thanks to Joe Ess for suggestions.........

I got the solution for the problem by precompiling the project from the console using all the dependent jar files, .server and .dmanager files(these files are generated by blaze rule engine)

this is the precompile statement

java -mx256m com.blazesoft.server.deploy.tools.NdAdvisorProjectCompiler -deploymentManager "./TestProjectServer.dmanager" -server "./TestProject.server"
[ April 29, 2008: Message edited by: pavan kumar seeram ]
13 years ago
yes, i have implemented Serializable interface to all the dependent classes in the Application. i dont know why the blaze rule engine was not able to serialize the instances of my classes when i use the rmiregistry.

And i also tested some samples applications on Blaze advisor Rule engine with rmiregistry.... by giving simple string and not using any dependent classes, this worked perfectly fine...... but when i am using some any classes its giving the above error which i posted last time........

plese give some suggestion,...........
13 years ago
I am working with Blaze Rule Engine and reading the binary rules file from the service code that is written in Java. I have to use some classes (located in jars) which supports my application and all the classes are serialized.

after deploying my application as ejb in Oracle Apps, i can use 'rmiregistry' for generating the response.

so, my application is working perfectly fine without rmiregistry and also giving the proper response........ but when i am using the rmiregistry its giving the following error




Ofcouse i have serialized all the classes in jarfiles...... even then i am getting error when i use 'rmiregistry'

Please suggest me some solution.........
13 years ago
why cant you try this............
String[] applicant = (application.getApplicants().toString());
13 years ago