[Beginner's Corner] - sources for jasper-jdt.jar ?
by ranjix
ranjix [http://community.jboss.org/people/ranjix] created the discussion
"sources for jasper-jdt.jar ?"
To view the discussion, visit: http://community.jboss.org/message/552824#552824
--------------------------------------------------------------
Hi guys, sorry for the bother.
I did run into an issue with some imports in a jsp file, in the sense that the compilation of the java-generated-servlet complains about a specific package:
+An error occurred at line: 14 in the generated java file+
+The import com.bluemartini.remotedesktop.itemchooser cannot be resolved+
The thing is that the other packages imported work fine, and the specific above package (folder + classes) mentioned in the error is obviously next to the other packages (folders) which seem to work. Tests playing with changing the name of the package and also the folder with the classes worked (I changed the name of the package to ...itemchooser2, changed the name of the folder with the classes the same, and it worked), but as soon as I got back to this particular package name, it failed. It drives me nuts, makes no sense, so I wanted to debug this to see what's going on. The problem is that I can't find the sources for the classes inside jasper-jdt.jar, which seem to be some eclipse related classes. I did download the sources for jboss5.1.0, but none of the jars inside contains the sources for org.eclipse.jdt.... packages.
Any idea how to get those? Is not really obvious which version of eclipse sources have been used, otherwise I would go to eclipse and download those.
Thanks for any suggestion,
ranjix
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552824#552824]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
Re: [jboss-user] [JBoss Microcontainer] - MemoryFileFactory in jboss-vfs 3.0.0.CR5
by Ales Justin
Ales Justin [http://community.jboss.org/people/alesj] replied to the discussion
"MemoryFileFactory in jboss-vfs 3.0.0.CR5"
To view the discussion, visit: http://community.jboss.org/message/552818#552818
--------------------------------------------------------------
> The MemoryFileFactory class has been replaced with a InMemoryClassesDeployer which is a deployer targeted at the DESCRIBE stage.
>
I wouldn't say replaced, the deployer used to use MFF, but now used different approach,
with temp file locations, instead of keeping bytes in-memory.
> What it does is that is mounts a temporary file system (by default in the servers tmp/vfs directory) that other deployments can add things to. In the ESB case, things like a generated servlets class, a wsdl file, and schema files would be added.
> So our deployers we would do somethings like this:
>
> VirtualFile inMemRootDir = unit.getAttachment(InMemoryClassesDeployer.DYNAMIC_CLASS_KEY, VirtualFile.class);
> VirtualFile wsdlFile = VFS.getChild(inMemRootDir.getPathName() + "/" + serviceInfo.getWSDLFileName());
> *final* String wsdl = generateWsdl();
> VFSUtils.writeFile(wsdlFile, wsdl.getBytes());
> unit.appendMetaDataLocation(wsdlFile);
>
>
>
>
>
>
> Is this the intended usage of the InMemoryClassesDeployer?
Yes, the IMCD's intent is to create a new temp classpath root.
VirtualFile wsdlFile = VFS.getChild(inMemRootDir.getPathName() + "/" + serviceInfo.getWSDLFileName());
--> VirtualFile wsdlFile = inMemoryRootDir.getChild(serviceInfo.getWSDLFileName());
For "unit::appendMetaDataLocation", you should append file's owner directory, not the file itself.
> Now our deployer do not need to do any clean up in their undeploy methods as this is done by the InMemoryClassesDeployer which will remove the filesystem when the deployment is undeployed.
Yes.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552818#552818]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
Re: [jboss-user] [EJB 3.0] - Default Interceptor Not called
by jaikiran pai
jaikiran pai [http://community.jboss.org/people/jaikiran] replied to the discussion
"Default Interceptor Not called"
To view the discussion, visit: http://community.jboss.org/message/552795#552795
--------------------------------------------------------------
> paresh bhavsar wrote:
>
>
> <interceptor-binding>
>
> <ejb-name>*</ejb-name>
>
> <interceptor-class>com.eks.ias.service.location.service.ExceptionInterceptor</interceptor-class>
>
> <method>
>
> <method-name>test</method-name>
>
> </method>
>
> </interceptor-binding>
>
>
As per the spec:
3.
<interceptor-binding>
<ejb-name>EJBNAME</ejb-name>
<interceptor-class>INTERCEPTOR</interceptor-class>
<method>
<method-name>METHOD</method-name>
</method>
</interceptor-binding>
This style is used to associate a method-level interceptor with
the specified enterprise bean. If there are multiple methods
with the same overloaded name, the element of this style refers
to all the methods with the overloaded name. Method-level
interceptors can only be associated with business methods of the
bean class. Note that the wildcard value * cannot be used
to specify method-level interceptors.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552795#552795]
Start a new discussion in EJB 3.0 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
Re: [jboss-user] [EJB 3.0] - Problem with NotEligibleForDirectInvocationException
by Manu Osten
Manu Osten [http://community.jboss.org/people/argonist] replied to the discussion
"Problem with NotEligibleForDirectInvocationException"
To view the discussion, visit: http://community.jboss.org/message/552788#552788
--------------------------------------------------------------
Hello,
"session" object:
static EJBHandler ejbHandler;
static AccountingInterface session;
static AuthInterface authsession;
@BeforeClass
public static void setUpBeforeClass() throws Exception {
// ExecuteMySQLScripts executeScripts = new ExecuteMySQLScripts();
// executeScripts.executeMySQLScripts();
ejbHandler = new EJBHandler();
session = ejbHandler.accoutingsession;
authsession = ejbHandler.authSession;
}
EJBHandler
package de.kirchedlau.ponte.utils.sessions;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import com.sun.corba.se.impl.javax.rmi.PortableRemoteObject;
import de.kirchedlau.ponteseam.sessions.AccountingInterface;
import de.kirchedlau.ponteseam.sessions.AuthInterface;
import de.kirchedlau.ponteseam.sessions.ContentInterface;
import de.kirchedlau.ponteseam.sessions.MailInterface;
import de.kirchedlau.ponteseam.sessions.RequestInterface;
public class EJBHandler {
Context jndiContext = null;
public ContentInterface contentSession = null;
public RequestInterface requestSession = null;
public AuthInterface authSession = null;
public MailInterface mailsession = null;
public AccountingInterface accoutingsession = null;
public EJBHandler() {
setContext();
contentSession = new SessionFinder<ContentInterface>().getRef("PonteSeam-ear/ContentBean/remote", ContentInterface.class);
requestSession = new SessionFinder<RequestInterface>().getRef("PonteSeam-ear/RequestBean/remote", RequestInterface.class);
authSession = new SessionFinder<AuthInterface>().getRef("PonteSeam-ear/AuthBean/remote", AuthInterface.class);
mailsession = new SessionFinder<MailInterface>().getRef("PonteSeam-ear/MailBean/remote",MailInterface.class);
accoutingsession = new SessionFinder<AccountingInterface>().getRef("PonteSeam-ear/AccountingBean/remote",AccountingInterface.class);
}
private void setContext()
{
try {
jndiContext = new InitialContext();
} catch (NamingException e) {
e.printStackTrace();
}
}
// T: SessionBean Interface
public class SessionFinder<T>
{
@SuppressWarnings("unchecked")
public T getRef(String className, Class classOfT){
try {
Object ref1 = jndiContext.lookup(className);
T session = (T) new PortableRemoteObject().narrow( ref1, classOfT);
return session;
} catch (NamingException e) {
e.printStackTrace();
}
return null;
}
}
}
I think that classpath is right.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552788#552788]
Start a new discussion in EJB 3.0 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months