[ssamprathi]

Hi,
We have problem with XDoclet and PVCS integration.
If we disassociate a EJB project from PVCS, XDoclet runs properly,
Otherwise MyEclipse, throws a dialog with “An Internal Error Occurred during: XDoclet Generation”

Please help.

Thanks,

[Riyad Kalla]

Can you please give us the information from your MyEclipse > About > Configuration Summary, also tell us the version of PVCS you are using to see if we can help.

[ssamprathi]

MyEclipse JSF Support
Version: 4.0.0
Build id: 20050829-4.0.0-GA

Eclipse Platform
Version: 3.1.0
Build id: I20050627-1435

PVCS
Merant Version Manager
Version : 8.0.2.0 (Build 651)

[Riyad Kalla]

Hmm, check your log file (<workspace dir>\.metadata\.log) for any tips that might point us in a direction here. Look for exceptions near the bottom, they are appended as they occur. So maybe force an error to occur then open the log file and scroll to the bottom and look what was written.

[ssamprathi]

Hi,
Attached is the error

!ENTRY org.eclipse.core.runtime 4 2 2006-01-25 09:40:22.390
!MESSAGE An internal error occurred during: “XDoclet Generation”.
!STACK 0
java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/Framework_EJB
at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java:58)
at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:117)
at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:211)
at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:81)
at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:190)
at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:96)
at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1674)
at org.eclipse.core.internal.resources.File.create(File.java:107)
at org.eclipse.core.internal.resources.File.create(File.java:183)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.transformBuildFile(ProjectUtil.java:430)
at org.jboss.ide.eclipse.xdoclet.run.ui.XDocletRunAction$2.run(XDocletRunAction.java:319)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

[Riyad Kalla]

I have filed this for investigation with our development team.

[ssamprathi]

Could you please let me know if there any further updates!..

Thanks,

[Riyad Kalla]

There has been no update at this time. In the mean time can you try something:

1) Clean install of Eclipse 3.1.2 SDK into a new directory
2) Clean install of MyEclipse 4.1 GA into a new directory pointing at your new Eclipse dir from step #1
3) A new workspace
4) Install the PVCS plugin
5) Checkout your project, see if XDoclet works.

[ssamprathi]

We tried the steps as mentioned above, infact we now even have a standard license, still no luck.
Please help,

Thanks..

[Riyad Kalla]

A dev pointed out to me this morning that he has run into this problem as well and it’s already filed in our bug tracker to be addressed. It hasn’t been targetted for a specific release yet. Sorry for the inconvenience of this.

[ssamprathi]

Could you please let us know the status of this?
We are still waiting on this bug to be fixed.

[Riyad Kalla]

I’m sorry for the delay. The problem stems from the XDoclet work we integrated from an old release of JBossIDE. Until we do a refresh on that XDoclet integration this problem most likely won’t be fixed. I have not seen this issue prioritized but will ask management to reconsider it.

[Paul Faulstich]

We are having the same problem, but with ClearCase as the SCM tool. This is a major component of our tool selection process, so its important that we get it resolved. Not being able to do EJB development & deployment would be a show-stopper.

This was posted a year ago – has it been resolved yet? If not, is there another plugin that we can use for EJB development & deployment?

Here is the exception we get:

!SESSION 2007-04-11 10:31:18.394 ———————————————–
eclipse.buildId=M20060921-0945
java.version=1.5.0_08
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86

This is a continuation of log file C:\llbtools\myeclipse\workspaces\ComparisonTest2\.metadata\.bak_0.log
Created Time: 2007-04-11 10:37:34.170

!ENTRY org.eclipse.core.jobs 4 2 2007-04-11 10:37:34.180
!MESSAGE An internal error occurred during: “XDoclet Generation”.
!STACK 0
java.lang.StackOverflowError
at org.eclipse.core.runtime.Path.<init>(Path.java:195)
at org.eclipse.core.runtime.Path.setDevice(Path.java:861)
at org.eclipse.core.runtime.Path.append(Path.java:235)
at org.eclipse.core.internal.resources.Container.findMember(Container.java:74)
at org.eclipse.core.internal.resources.Container.findMember(Container.java:67)
at com.genuitec.eclipse.core.util.Util.getResource(Util.java:180)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.populateClassPath(ProjectUtil.java:125)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.populateClassPath(ProjectUtil.java:177)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.populateClassPath(ProjectUtil.java:101)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.populateClassPath(ProjectUtil.java:151)
[about a hundred identical lines deleted…]
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.populateClassPath(ProjectUtil.java:101)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.populateClassPath(ProjectUtil.java:151)

[Riyad Kalla]

So if you run this same code on a project that isn’t under ClearCase source control, it’s fine?

[Paul Faulstich]

yes, that is correct.

[Author]

Posts