[JBoss Tools] New message: "Re: NPE in portal module with multiple faces config files"
by Denis Golovin
User development,
A new message was posted in the thread "NPE in portal module with multiple faces config files":
http://community.jboss.org/message/522833#522833
Author : Denis Golovin
Profile : http://community.jboss.org/people/dgolovin
Message:
--------------------------------------------------------------
Looks like an issue because code in
JSFPortletFacetInstallDelegate
     private void configureFacesConfig(IProject project,               IProgressMonitor monitor, IDataModel config) {          String facesConfigString = getFacesConfigFile(project, monitor);          FacesConfigArtifactEdit facesConfigEdit = null;          try {               facesConfigEdit = FacesConfigArtifactEdit                         .getFacesConfigArtifactEditForWrite(project,                                   facesConfigString);
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522833#522833
14 years, 3 months
[Spring Integration] New message: "Re: ClassNotFound error for classes in spring archives lib directory"
by Mike Karrys
User development,
A new message was posted in the thread "ClassNotFound error for classes in spring archives lib directory":
http://community.jboss.org/message/522831#522831
Author : Mike Karrys
Profile : http://community.jboss.org/people/mikekarrys
Message:
--------------------------------------------------------------
Thanks for the help Ales.
I'm using AS 5.1.0.GA with the jboss-spring-3.2.deployer.
So after I wrote this I thought that maybe I should package everything in an EAR but when I do that the mavnen-ear-plugin packager converts my .spring to .jar and then can't resolve the spring context.
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/C:/Applications/jboss-5.1.0.GA/server/default/deploy/avm-ear.ear/" is in error due to the following reason(s): org.xml.sax.S
AXParseException: The prefix "context" for element "context:annotation-config" is not bound.
The maven-ear-plugin puts the my .spring archive in as a .jar.
Does it need to be a .spring in the ear to deploy correctly or is it a configuration problem?
Thanks,
Mike
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522831#522831
14 years, 3 months
[JBoss Tools] New message: "NPE in portal module with multiple faces config files"
by Stefan Tausendpfund
User development,
A new message was posted in the thread "NPE in portal module with multiple faces config files":
http://community.jboss.org/message/522830#522830
Author : Stefan Tausendpfund
Profile : http://community.jboss.org/people/Stefan_Tausendpfund
Message:
--------------------------------------------------------------
Hello,
when importing an existing portal web project with more than one config.xml in web.xml I get an NPE and an error message *"Failed while installing JBoss JSF Portlet 1.0."*
Here the configuration in web.xml:
<context-param>
<param-name>javax.faces.CONFIG_FILES</param-name>
<param-value>/WEB-INF/faces-config.xml,/WEB-INF/a-config.xml</param-value>
</context-param>
The viewhandler and statemangager are configured in faces-config.xml.
The Stack Trace:
java.lang.NullPointerException
at org.jboss.tools.portlet.core.internal.project.facet.JSFPortletFacetInstallDelegate.configureFacesConfig(JSFPortletFacetInstallDelegate.java:146)
at org.jboss.tools.portlet.core.internal.project.facet.JSFPortletFacetInstallDelegate.execute(JSFPortletFacetInstallDelegate.java:115)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1467)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:438)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1171)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1107)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:321)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:336)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:252)
at org.jboss.tools.maven.seam.configurators.PortletProjectConfigurator.installPortletFacet(PortletProjectConfigurator.java:146)
at org.jboss.tools.maven.seam.configurators.PortletProjectConfigurator.installWarFacets(PortletProjectConfigurator.java:121)
at org.jboss.tools.maven.seam.configurators.PortletProjectConfigurator.configureInternal(PortletProjectConfigurator.java:82)
at org.jboss.tools.maven.seam.configurators.PortletProjectConfigurator.mavenProjectChanged(PortletProjectConfigurator.java:96)
at org.maven.ide.eclipse.project.configurator.AbstractProjectConfigurator.mavenProjectChanged(AbstractProjectConfigurator.java:118)
at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:678)
at org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.notifyProjectChangeListeners(MavenProjectManagerImpl.java:629)
at org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.applyMutableProjectRegistry(MavenProjectManagerImpl.java:757)
at org.maven.ide.eclipse.internal.project.MavenProjectManagerRefreshJob.run(MavenProjectManagerRefreshJob.java:99)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
My configuration:
eclipse.buildId=M20090917-0800
java.version=1.5.0_21
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
JBoss Tools Version:
Version: 1.1.0.v201001270902N-H171-CR2
regards
Stefan
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522830#522830
14 years, 3 months
[jBPM Development] New message: "How to submit modifications to jBPM BPEL source code?"
by Carlos Oliveira
User development,
A new message was posted in the thread "How to submit modifications to jBPM BPEL source code?":
http://community.jboss.org/message/522828#522828
Author : Carlos Oliveira
Profile : http://community.jboss.org/people/karluqs
Message:
--------------------------------------------------------------
Hi,
I'm from Brazil, and I work for CPqD, an enterprise who provides software solutions and consultancy for the telecom and energy market.
About one year ago we choose to install and use jBPM BPEL (RiftSaw was not available by that time) to integrate some systems in the production environment of one of our customers, but a lot of changes were demanded to attend the high volume of processes and the performance requirements that the production environment demands. Every day thousands of processes are created and stay in execution for some days util they are finally finished, so performance, hardware resources consumption and reliability were our main concerns.
To provide that, I have made a huge modification in the jBPM BPEL 1.1.1 source code, fixing bugs and doing a lot of otimizations and performance improvements. The modifications were tested by our team, and the result is running at the production environment today, so the modification were very successful.
Now we want to send the modified code to the jBPM BPEL project. I noticed that jBPM BPEL is not actively anymore. Is the source code still helpfull to you? How can I do that ? What is the procedure to be followed?
Thanks,
Carlos
Here the list of modifications:
- The architecture based on JMS didn't support thousands of process instances in receive state (tested with 50000 process), itcaused high memory consumption (25GB) and several minutes waiting jboss to start to load all jms receivers (about 20 minutes on a server with 12 cores and Oracle 10g). We removed JMS parts and altered to query the database when receiving a message to continue a process . This caused the loss of asynchronous messages which are not necessary for us. Another solution will be required if someone needs to use of asynchronous messages.
- Performance was degradated when executed hundreds of processes at same time causing crashes on JBoss. AThreadPoolExecutor was added to SoapHandler.java to limit the number of processes executing at same time.
- Added a class to provide a central configuration for JBPM (ConfigurationManager.java), this classes uses Jgroups to replicate configuration modifications on runtime.
- Added static map (PROCESSES_IN_EXECUTION on JbpmContext.java) to provide a way to the cluster doesn't execute the same process at the same time. JGroups was added to support sending of messages between the machines to provide information about which processes are running.
- Added support for 2nd level cache cluster using EhCache and Jgroups, configuration on jbpm.hibernate.cfg.xml and ehcache_jbpm.xml
- Inclusion of table JBPM_NODE_EXECUTED, to track the path a process instance followed on bpel graph, we tried to use JBPM_TOKEN but it's unpredictable and confuse to track a path.
- XMLs messages with quotes ( " and ' ) has several issues when parsing to and from xerces, the quotes are lost due to the fact that XMLUtil.java encodes & to &amp;. This happens with other characters (>, <, space, -, & and #). It was necessary to modify ElementType.java to properly encode/unencode the xml files.
- Added support to XSL transformations using javax.xml.transform.Transformer in org.jbpm.bpel.sublang.xpath.cpqd.XSLTransformation file. The deploy of processes was altered to include xsd files on table JBPM_BYTEBLOCK
- JBPM_JOB has a design problem, it executes only one process by cycle, altered to execute as many as necessary, each one in a transaction with crash recovery. Also added a class to monitor
- Use of JBPM_LOG was altered, studies of database growth showed that this table was responsible for 30% of all database, so a configuration was added to choose to log or not to log, see DbLoggingService.java
- If a process crashes , the transaction is rolled back depending on exception type so all the graph is lost and if the process passed for a node that cannot be executed again the message can't be resended. StartInstance and ResumeInstance was rewritten to provide means to always save data.
- Added Xpath function to send email based on a xml with the data (org.jbpm.bpel.sublang.xpath.cpqd.SendEmail)
- When assigning a node that has several sub nodes with the same name, only the first node is assigned. XPathEvaluator.java (method selectOrCreateNodes) was fixed.
- When copying xmls nodes between different xmls namespace, the original namespaces are copied also. XPathEvaluator.java was fixed.
- LockMonitorThread.java monitors when a job is executing for a long time, but was not full implemented or used, it was modified to properly monitor the jobs.
- ByteBlockChopper.java had performance issues when glueing the chops because it created a new array for each chop, altered to create only one initial array and glue the chops in the right position.
- Added class JbossWebDescriptorTool.java on JBPM-BPEL-TOOLS, this class creates a jboss-web.xml to provide one context (/jbpmservices) for all processes deployed.
- The .war file deployed does not have version information, this causes the old processes instances crashs, several classes of JBPM-BPEL-TOOLS was modified to provide version information on classes generated and file names.
- On deploying a process definition create classes without using namespace for packaging, it causes a crash because of confliting xml nodes with the same name, modified to create packages for each namespace.
- Added column STATE_ to JBPM_PROCESSDEFINITION table, the definition is put in a activing state when deploying, so a process can be deployed with jbpm in use and the users can not access it until .war file is fully deployed.
- CatalogEntry is cached when used for the first time, so an external web service address could not be modified on runtime. The class was modified to support notification of urls for all the process using the addresses on ServiceCatalog.java, even in cluster.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522828#522828
14 years, 3 months
[JBoss AOP] New message: "Detecting annotated classes"
by Marko Mrvelj
User development,
A new message was posted in the thread "Detecting annotated classes":
http://community.jboss.org/message/522825#522825
Author : Marko Mrvelj
Profile : http://community.jboss.org/people/markom
Message:
--------------------------------------------------------------
Hi All!
I am a noob to AOP. I need to create a setup where I need to detect specific annotation inside classes during EAR deployment. Basically I need to provide a mean for another developer to mark certain methods inside class, and then to be able to find all marked methods deployed on JBoss AS.
I don't know if this is possible with AOP.
For example:
Annotation:
@Target( { ElementType.METHOD })(a)Retention(value=RetentionPolicy.RUNTIME)public @interface MarkMe {
}
Annotated class:
public class TestClass {
@MarkMe
public void testMethod1() {
System.out.println("Invoked testMethod1");
}
}
Now I can create interceptor :
public class TestInterceptor implements Interceptor {
@Override public String getName() { return "TestInterceptor"; }
@Override public Object invoke(Invocation invocation) throws Throwable { System.out.println("INSIDE INTERCEPTOR"); return invocation.invokeNext(); }
}
to trigger during invocation of the method:
<?xml version="1.0" encoding="UTF-8"?>
<aop xmlns="urn:jboss:aop-beans:1.0">
<interceptor name="TestInt" class="TestInterceptor"/>
<bind pointcut="execution(public void *->@MarkMe())">
<interceptor-ref name="TestInt"/>
</bind>
</aop>
However is it possible to detect during deployment of the class that it has been annotated? I thought to use +has+ but it seems that it is only for refinement of the expression.
Could somebody provide me with some hints how to do this?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522825#522825
14 years, 3 months
[JBoss AOP] New message: "Re: withincode from JUnit test not working"
by Alan Nisbet
User development,
A new message was posted in the thread "withincode from JUnit test not working":
http://community.jboss.org/message/522818#522818
Author : Alan Nisbet
Profile : http://community.jboss.org/people/nizzy
Message:
--------------------------------------------------------------
Flavio your a genius, well as far as I'm concerned anyway,
In JUnit test (ExampleManagerBeanTest) changed;
private ExampleManager man;
where ExampleManager is the remote interface of the ExampleManagerBean to;
private ExampleManagerBean man;
And that seemed to do the trick. The exception was thrown as I would have expected. I will also try the alteration to the pointcut you suggested, however the quck check was enough for now. Normally when testing session beans outside the container we explicitly create instance of the class directly, and do not use the interface.
It always simple when you know the solution,
Thanks for the help, I simply did not know what else to try!
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522818#522818
14 years, 3 months