Thanks for asking. I found the problem. In the JBoss Plugin 1.2.2 Tutorial page 12, it
says Edit the project properties by right clicking on the
project and select Properties. It can be confused with Project-Preference.
Instead, it means the project in Package Explorer and then select property.
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20041024022743
BUILD FAILEDAnt Error Message:file:/home/cruisecontrol/work/scripts/build-jboss-head.xml:89: exec returned: 1Date of build:10/24/2004 02:27:43Time to build:173 minutes 8 secondsLast
Hi everbody,
I am getting a problem with jboss 3.2.3 and for 3.2.5 also is, i see error like
this.
org.jboss.util.NestedSQLException: No ManagedConnections available within configured
blocking timeout...
After then nothing works. I have to restart the server. Can anybody help me in
Hi everbody,
I am getting a problem with jboss 3.2.3 and 3.2.5 as well is, i see error like this.
org.jboss.util.NestedSQLException: No ManagedConnections available within configured
blocking timeout...
After then nothing works. I have to restart the server. Can anybody help me in solving
Hi,
depending on which loadtime method you want to use
http://docs.jboss.org/aop/aspect-framework/reference/en/html/running.html
you basically just pass in a system property/jvm argument. The examples shown are for
running off the command line, but you do exactly the same for the ant task.
Can you post the Eclipse log? It should be in the .metadata directory of your eclipse
workspace location. Only post the relative entry, not the whole thing ;-)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852462#3852462
Reply to the post :
I totally argree with Thomas, that a custom server exception should be mapped to a
java exception on the client side using the QName.
To do so, requires that the fault message contains the QName.
What I wanted to point out is, that any server side custom exception, thrown by a SEI
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20041024054117Lbuild.89
BUILD COMPLETE-build.89Date of build:10/24/2004 05:41:17Time to build:99 minutes 39 secondsLast changed:10/24/2004 03:29:14Last log entry:Remove the obsolete oil2 tests
!SESSION Out 24, 2004 08:58:19.62 --
eclipse.buildId=I200406251208
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_BR
!ENTRY org.eclipse.osgi Out 24, 2004 08:58:19.62
!MESSAGE An error
!SESSION Out 24, 2004 08:58:19.62 --
eclipse.buildId=I200406251208
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_BR
!ENTRY org.eclipse.osgi Out 24, 2004 08:58:19.62
!MESSAGE An error
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20041024072639Lbuild.146
BUILD COMPLETE-build.146Date of build:10/24/2004 07:26:39Time to build:82 minutes 29 secondsLast changed:10/24/2004 07:01:11Last log entry:Added DeploymentService
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20041024085934Lbuild.341
BUILD COMPLETE-build.341Date of build:10/24/2004 08:59:34Time to build:72 minutes 49 secondsLast changed:10/24/2004 03:16:08Last log entry:Add an RMI/SSL custom
Bugs item #1053229, was opened at 2004-10-24 15:22
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=1053229group_id=22866
Category: JBossCMP
Group: v4.0
Status: Open
Resolution:
anonymous wrote : Root exception:
| org.eclipse.core.internal.resources.ResourceException: Resource /AFTT is not open.
| at
org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:126)
| at org.eclipse.core.internal.resources.Project.hasNature(Project.java:456)
|
Bugs item #1053237, was opened at 2004-10-24 15:41
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=1053237group_id=22866
Category: JBossServer
Group: v4.0
Status: Open
Resolution:
Bugs item #1053229, was opened at 2004-10-24 08:22
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=1053229group_id=22866
Category: JBossCMP
Group: v4.0
Status: Closed
Resolution: Wont Fix
Bugs item #1053237, was opened at 2004-10-24 08:41
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=1053237group_id=22866
Category: JBossServer
Group: v4.0
Status: Open
Resolution: Accepted
Have these tests been added? The
org.jboss.test.jbossmx.compliance.monitor.BasicTestCase
is failing because javax.management.monitor.CounterMonitor is a standard
mbean
that is now emitting AVCs it should not be. Its an implementation detail
that we are deploying standard mbeans as xmbeans, but
Bugs item #1051955, was opened at 2004-10-21 21:28
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=1051955group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: Accepted
Bugs item #1053277, was opened at 2004-10-24 10:16
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=1053277group_id=22866
Category: JBossMX
Group: v4.0
Status: Open
Resolution:
I know of no MBeanTracker class so can you clarify what your talking about here?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852470#3852470
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3852470
We plan on doing a 3.2.7 release within a couple of weeks, curently targetd at Nov
10th to address some jdk 5.0 and jdk 1.3 issues in the 3.2 codebase.
This topic is a list of the issues to be complete for the 3.2.7 release.
Get the testuite running completely under jdk5.0, Assigned to Scott
We are planning to do a 4.0.1 release on Oct 29. The following dynamic list of tasks
need to be completed to complete the release. Any other tasks that be posted here and
I'll integrate them into this summary.
Bugs #1040200, Authentication exception, principal=null initially on login.
,
Bugs item #1051007, was opened at 2004-10-20 13:04
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=1051007group_id=22866
Category: Clustering
Group: v4.0
Status: Closed
Resolution: Fixed
I receive the same error independent of AFTT project status (opened/closed)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852475#3852475
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3852475
Hello All.
I have:
Eclipse 3.0.1 (On WinXP)
JBoss IDE 1.3.30 - org.jboss.ide.eclipse_1.3.30
jdk1.5.0
3 Steps to problem ;-)
1) create Entity bean
cut of UbiqBean.java
package org.itx.jbalance.l0;
import java.rmi.RemoteException;
import javax.ejb.EJBException;
import
This is [ 1048467 ] MMBs do not emit AttributeChangeNotification to
Listeners?
https://sourceforge.net/tracker/index.php?func=detailaid=1048467group_
id=22866atid=376685
Although the implementation is a standard mbean, it is deployed
as an xmbean and should have AVCs for the attribute changes.
When you opened the project, did you restart Eclipse? The exception is happening on
plugin loadup time (eclipse startup).
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852478#3852478
Reply to the post :
It basically allows you to generate deployment descriptors
(using velocity templates) and move them in and out of ./deploy.
Read more at:
[URL]http://www.jboss.org/wiki/Wiki.jsp?page=DeploymentService[/URL]
Comments/suggestions are welcome
View the original post :
That is right, I expect that the SeriveceConfigurator is just going to get a list of
the attribute object to apply to the mbeans by passing in the jboss-service.xml
document to the jbossxb framework. It should know nothing about xml element
representing this information.
That the
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20041024134720Lbuild.147
BUILD COMPLETE-build.147Date of build:10/24/2004 13:47:20Time to build:74 minutes 18 secondsLast changed:10/24/2004 13:39:37Last log entry:added
[EMAIL PROTECTED] wrote : I can't just add jbossxb:mapping elements to the attribute
element and have this validate against the service xsd simply because this element is
from a foreign namespace, correct?
Correct. Then we could probably use processing instructions?
| ?jbossxb
Marshall,
The Wizard ONLY works if I open all projects in workspace and restart Eclipse. I don't
see any relation between existent projects and the new one...
Is it a bug?
Thanks,
Andr
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852483#3852483
Reply to
Hi,
I'm trying the reference guide example, and create a Ant project to do loadtime
weaving (I don't want to precompile). It's not working... the result is AOP! (not
Hello, AOP!)
Any ideas?
Thanks,
Andr
No, nothing wrong with putting the processing instructions in the xsd, and as you said
this is promoted by jaxb.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852485#3852485
Reply to the post :
Post some more info
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852487#3852487
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3852487
---
This SF.net email is
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20041024150920Lbuild.342
BUILD COMPLETE-build.342Date of build:10/24/2004 15:09:20Time to build:86 minutes 29 secondsLast changed:10/24/2004 14:37:46Last log entry:Include the
Class:
package teste;
public class HelloAOP {
public void callMe() {
System.out.println(AOP!);
}
public static void main(String args[]) {
new HelloAOP().callMe();
}
}
Aspect:
package teste;
import org.jboss.aop.advice.Interceptor;
import org.jboss.aop.joinpoint.Invocation;
AOP xml:
?xml version=1.0 encoding=UTF-8 standalone=yes?
| aop
| bind pointcut=execution(public void HelloAOP-callMe())
| interceptor class=HelloAOPInterceptor/
| /bind
| /aop
Ant:
project default=weave
| target name=weave
| property name=jboss.dir
Try:
| java classname=teste.HelloAOP classpathref=jboss.path
| sysproperty key=java.system.class.loader
value=org.jboss.aop.standalone.SystemClassLoader/
| sysproperty key=jboss.aop.path value=teste.xml/
|
| /java
|
If that doesn't work, try renaming the teste.xml to
Thanks, but still not working...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852492#3852492
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3852492
---
This SF.net
Note the pakage names:
| ?xml version=1.0 encoding=UTF-8 standalone=yes?
| aop
| bind pointcut=execution(public void teste.HelloAOP-callMe())
| interceptor class=teste.HelloAOPInterceptor/
| /bind
| /aop
|
View the original post :
Still not working (again)...
Is there a verbose mode?
Is there a way to send to you the files?
Thanks,
Andr
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852495#3852495
Reply to the post :
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20041024170609Lbuild.343
BUILD COMPLETE-build.343Date of build:10/24/2004 17:06:09Time to build:79 minutes 0 secondsLast changed:10/24/2004 16:48:31Last log entry:javadoc
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20041024204423Lbuild.91
BUILD COMPLETE-build.91Date of build:10/24/2004 20:44:23Time to build:84 minutes 0 secondsLast changed:10/24/2004 17:11:54Last log entry:Wrap exceptions in an
This is what I expected. It is definately a bug, and I've pushed the fix out to CVS.
Here's a brief rundown on what's going on:
The first time you use something from a supplied plugin (in this case, the New AOP
Project Wizard), Eclipse starts up that plugin by calling a method start within the
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20041024222013Lbuild.148
BUILD COMPLETE-build.148Date of build:10/24/2004 22:20:13Time to build:66 minutes 32 secondsLast changed:10/24/2004 14:50:17Last log entry:change the copy/removal
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20041024233536Lbuild.92
BUILD COMPLETE-build.92Date of build:10/24/2004 23:35:36Time to build:73 minutes 25 secondsLast changed:10/24/2004 22:45:56Last log entry:Remove the test of
48 matches
Mail list logo
