[JBossWS] - Re: If I deploy more than one webservice I get
by rickcr
Thanks Heiko for the information. My only question now (and pardon if this is a very 'newbie' question) but what would I set the web context to? In other words, do I need to make sure the various webapp wars that might be in the ear all have web.xml definitions that point to the ejbs so that I can create a context for the ejbs through the web.xml? If so, this seems like a lot of extra work.
I guess I'm just confused how I know what @WebContext to use for the ejbs? I could have several wars that all have their own web context. I would think the ejb context would be independent of those contexts, but just giving it an arbitrary context doesn't help in regard to having the wsdl being located.
If someone could provide a simple example of what to set this @WebContext to I'd appreciate. I'm sure I'm missing something simple.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046133#4046133
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046133
19 years, 1 month
[EJB/JBoss] - EJB3.0 with Jboss4.0.5
by kalyanbikkani
Hi,
i am new to this forum,
I am using jboss4.0.5 and ejb3.0
I wrote simple ejb module and deploy it,
I wrote ejb-jar.xml like this
[
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
version="3.0">
<enterprise-beans>
<ejb-name>SalesEJB</ejb-name>
com.ehms.sales.SalesHome
com.ehms.sales.Sales
<ejb-class>com.ehms.sales.SalesBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</enterprise-beans>
</ejb-jar>
]
at the time of deploy i got an exception like this
org.jboss.deployment.DeploymentException: ejb-jar.xml must either obey the right
xml schema or define a valid DOCTYPE!
at org.jboss.metadata.ApplicationMetaData.importEjbJarXml(ApplicationMet
aData.java:339)
at org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:166)
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:541)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor
.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Intercepto
rServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInt
erceptor.java:74)
at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(Deployer
InterceptorEJB.java:44)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
ptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy26.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
run(AbstractDeploymentScanner.java:225)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046131#4046131
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046131
19 years, 1 month
[JBossWS] - Re: WSDL-location help?
by heiko.braun＠jboss.com
Taken from the JAX-WS 2.0 specs, section 5.2.5.3:
anonymous wrote :
|
| Use of @WebService(wsdlLocation) and Metadata
|
| There are some restrictions on the packaging of the description and any associated metadata documents.
| The goal of these restrictions is to make it possible to publish an endpoint without forcing a JAX-WS
| implementation to retrieve, store and patch multiple documents from potentially remote sites.
| The value of the wsdlLocation annotation element on an endpoint implementation class, if any, MUST
| be a relative URL. The document it points to MUST be packaged with the application. Moreover, it MUST
| follow the requirements in section 5.2.5.4 below (?Application-specified Service?).
|
|
|
Therefore i don't consider this to be a bug.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046127#4046127
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046127
19 years, 1 month
[JBoss Portal] - JBoss portal + two GWT portlets
by wodzuu
Hi!
Have anyone tried to use GWT portles in JBoss portal? I have following problem:
I have two jsp pages that render gwt:
<%@ page contentType="text/html" %>
| <meta name='gwt:module'
| content='/ejb/www/com.sius.gwt.CategoriesManager=com.sius.gwt.CategoriesManager'>
| <div id="categoriesManager_div">
| </div>
| <script language="javascript"
| src="/ejb/www/com.sius.gwt.CategoriesManager/gwt.js">
and
<%@ page contentType="text/html" %>
| <meta name='gwt:module'
| content='/ejb/www/com.sius.gwt.PasswordsManager=com.sius.gwt.PasswordsManager'>
| <div id="categoriesManager_div">
| </div>
| <script language="javascript"
| src="/ejb/www/com.sius.gwt.PasswordsManager/gwt.js">
when I put them on my portal separately everything is ok, but when I
want them together only the first portlet renders but this time twice
in a same portlet window (second portlet window is now empty). I know
that problem of double-rendering can be solved by using only one
reference to gwt.js per site but I cannot delete it form any of those
portlets becouse they may be used separately.
The second problem is that <mete name='gwt:module... tags must be used
one by one to make portlets render correctly but I cannot do that -
JBoss portal puts those whole jsp pages one by one so it still rendes
incorrectly.
Can anyone help me ?
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046125#4046125
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046125
19 years, 1 month
[JBoss jBPM] - Re: why
by estaub
Simon,
anonymous wrote : Every API needs a contract, a set of documented rules that defines a model and how the model is affected.
As far as I can see, the kind of documentation you're looking for won't happen in this project until either:
- there's some immediate, undeniable business imperative for JBoss, like a big customer demanding it. I am hopeful - it's pretty scary to be basing commercial product on something whose behavior I know well only where I've dug hard into the code. Presumably some major customer will have the same misgivings.
or
- folks come up with a clean way for it to be incrementally contributed to by users. Since the doc at the level you're looking for is classically in the javadoc, that's hard, because it requires either committer access or for someone to take the time to merge comments. Ensuring accuracy from folks who aren't the primary authors will be hard, too. They might consider contributing unit tests, as well, which significantly raises the effort level required. I don't know if anyone would be interested.
Also, as far as I know, there's currently no formal notion of "the JBPM interface" - i.e., a restricted set of classes/methods that are intended for use outside the jar. Any contract/specification work would need to start with that definition of what is intended to be "truly public".
I don't have any idea whether the current committers would find any value in any of this. So far, no sign of it.
On the other hand... given where we are... for myself (and apparently for Ronald ;-)), I'd certainly appreciate it if you'd prune your technical queries by doing a bit more legwork. In the current case, the fact that a JbpmContext scopes transactions is documented in both user guide and javadocs, and could have been surmised by anyone with your experience - it's a common pattern.
-Ed Staub
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046124#4046124
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046124
19 years, 1 month