3:32 a.m.
Cannot deploy nested JSE endpoint in SAR
----------------------------------------
Key: JBWS-1854
URL: http://jira.jboss.com/jira/browse/JBWS-1854
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: jbossws-2.0.1.SP2
We have an issue, JBoss Portal WSRP service doesn't deploy in Branch
4.2, the issue seems to be related to the WS changes.
I noticed that in jbossws.sar/META-INF/jboss-service.xml the following
has been removed:
<!--
A deployer service for JSE endpoints that are nested in service
archives (sar).
-->
<mbean name="jboss.ws:service=DeployerInterceptorNestedJSE"
code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
<depends optional-attribute-name="MainDeployer"
proxy-type="attribute">jboss.system:service=MainDeployer</depends>
<depends>jboss.ws:service=WebServiceDeployerJSE</depends>
</mbean>
We do have a jse included into a sar and the end result is that the WSRP
service doesn't start with the following error message:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@be17fae3 {
url=file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
}
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch:
file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
altDD: null
lastDeployed: 1192192027649
lastModified: 1192191975000
mbeans:
I wanted to let you know. I didn't investigate more than that, other
than trying to find the corresponding class for the deployer, but it
seems that it's not in the codebase anymore.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:19 a.m.
New subject: [JBoss JIRA] Reopened: (JBWS-1854) Cannot deploy nested JSE endpoint in SAR
[ http://jira.jboss.com/jira/browse/JBWS-1854?page=all ]
Chris Laprun reopened JBWS-1854:
--------------------------------
Cannot deploy nested JSE endpoint in SAR
----------------------------------------
Key: JBWS-1854
URL: http://jira.jboss.com/jira/browse/JBWS-1854
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-2.0.1.SP2
We have an issue, JBoss Portal WSRP service doesn't deploy in Branch
4.2, the issue seems to be related to the WS changes.
I noticed that in jbossws.sar/META-INF/jboss-service.xml the following
has been removed:
<!--
A deployer service for JSE endpoints that are nested in service
archives (sar).
-->
<mbean name="jboss.ws:service=DeployerInterceptorNestedJSE"
code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
<depends optional-attribute-name="MainDeployer"
proxy-type="attribute">jboss.system:service=MainDeployer</depends>
<depends>jboss.ws:service=WebServiceDeployerJSE</depends>
</mbean>
We do have a jse included into a sar and the end result is that the WSRP
service doesn't start with the following error message:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@be17fae3 {
url=file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
}
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch:
file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
altDD: null
lastDeployed: 1192192027649
lastModified: 1192191975000
mbeans:
I wanted to let you know. I didn't investigate more than that, other
than trying to find the corresponding class for the deployer, but it
seems that it's not in the codebase anymore.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:19 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-1854) Cannot deploy nested JSE endpoint in SAR
[ http://jira.jboss.com/jira/browse/JBWS-1854?page=comments#action_12382296 ]
Chris Laprun commented on JBWS-1854:
------------------------------------
Hmm, you use an embedded war file. Our service endpoint is bundled as a .jse file.
Cannot deploy nested JSE endpoint in SAR
----------------------------------------
Key: JBWS-1854
URL: http://jira.jboss.com/jira/browse/JBWS-1854
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-2.0.1.SP2
We have an issue, JBoss Portal WSRP service doesn't deploy in Branch
4.2, the issue seems to be related to the WS changes.
I noticed that in jbossws.sar/META-INF/jboss-service.xml the following
has been removed:
<!--
A deployer service for JSE endpoints that are nested in service
archives (sar).
-->
<mbean name="jboss.ws:service=DeployerInterceptorNestedJSE"
code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
<depends optional-attribute-name="MainDeployer"
proxy-type="attribute">jboss.system:service=MainDeployer</depends>
<depends>jboss.ws:service=WebServiceDeployerJSE</depends>
</mbean>
We do have a jse included into a sar and the end result is that the WSRP
service doesn't start with the following error message:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@be17fae3 {
url=file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
}
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch:
file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
altDD: null
lastDeployed: 1192192027649
lastModified: 1192191975000
mbeans:
I wanted to let you know. I didn't investigate more than that, other
than trying to find the corresponding class for the deployer, but it
seems that it's not in the codebase anymore.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:27 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-1854) Cannot deploy nested JSE endpoint in SAR
[ http://jira.jboss.com/jira/browse/JBWS-1854?page=comments#action_12382297 ]
Thomas Diesler commented on JBWS-1854:
--------------------------------------
In Branch_4_2 the nested war deployment is fixed.
Packaging a war with the jse extension is not necessary any more.
Cannot deploy nested JSE endpoint in SAR
----------------------------------------
Key: JBWS-1854
URL: http://jira.jboss.com/jira/browse/JBWS-1854
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-2.0.1.SP2
We have an issue, JBoss Portal WSRP service doesn't deploy in Branch
4.2, the issue seems to be related to the WS changes.
I noticed that in jbossws.sar/META-INF/jboss-service.xml the following
has been removed:
<!--
A deployer service for JSE endpoints that are nested in service
archives (sar).
-->
<mbean name="jboss.ws:service=DeployerInterceptorNestedJSE"
code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
<depends optional-attribute-name="MainDeployer"
proxy-type="attribute">jboss.system:service=MainDeployer</depends>
<depends>jboss.ws:service=WebServiceDeployerJSE</depends>
</mbean>
We do have a jse included into a sar and the end result is that the WSRP
service doesn't start with the following error message:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@be17fae3 {
url=file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
}
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch:
file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
altDD: null
lastDeployed: 1192192027649
lastModified: 1192191975000
mbeans:
I wanted to let you know. I didn't investigate more than that, other
than trying to find the corresponding class for the deployer, but it
seems that it's not in the codebase anymore.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-1854) Cannot deploy nested JSE endpoint in SAR
[ http://jira.jboss.com/jira/browse/JBWS-1854?page=comments#action_12382434 ]
Thomas Diesler commented on JBWS-1854:
--------------------------------------
This was already fixed in 4.2.1
14:27:49,547 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA
date=200707261016)] Started in 29s:697ms
14:29:31,313 INFO [TomcatDeployer] deploy, ctxPath=/jaxws-jbws1854,
warUrl=.../tmp/deploy/tmp59549jaxws-jbws1854.sar-contents/jaxws-jbws1854-exp.war/
14:29:31,523 INFO [WSDLFilePublisher] WSDL published to:
file:/home/tdiesler/svn/jbossas/tags/JBoss_4_2_1_GA/build/output/jboss-4.2.1.GA/server/default/data/wsdl/jaxws-jbws1854.sar/jaxws-jbws1854.war/TestEndpointService59550.wsdl
14:29:31,543 INFO [ServiceEndpointManager] WebService started:
http://127.0.0.1:8080/jaxws-jbws1854
Cannot deploy nested JSE endpoint in SAR
----------------------------------------
Key: JBWS-1854
URL: http://jira.jboss.com/jira/browse/JBWS-1854
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-2.0.1.SP2
We have an issue, JBoss Portal WSRP service doesn't deploy in Branch
4.2, the issue seems to be related to the WS changes.
I noticed that in jbossws.sar/META-INF/jboss-service.xml the following
has been removed:
<!--
A deployer service for JSE endpoints that are nested in service
archives (sar).
-->
<mbean name="jboss.ws:service=DeployerInterceptorNestedJSE"
code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
<depends optional-attribute-name="MainDeployer"
proxy-type="attribute">jboss.system:service=MainDeployer</depends>
<depends>jboss.ws:service=WebServiceDeployerJSE</depends>
</mbean>
We do have a jse included into a sar and the end result is that the WSRP
service doesn't start with the following error message:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@be17fae3 {
url=file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
}
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch:
file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
altDD: null
lastDeployed: 1192192027649
lastModified: 1192191975000
mbeans:
I wanted to let you know. I didn't investigate more than that, other
than trying to find the corresponding class for the deployer, but it
seems that it's not in the codebase anymore.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:25 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-1854) Cannot deploy nested JSE endpoint in SAR
[ http://jira.jboss.com/jira/browse/JBWS-1854?page=comments#action_12382614 ]
Dimitris Andreadis commented on JBWS-1854:
------------------------------------------
Thomas Heute reports that repackaging works on both versions. So we should be fine:
"Ok, so the war deployment works on 4.2.1 and 4.2.2. At least we won't need 2
versions of JBoss Portal 2.6.3 so we are fine with that. I have several WARNs that i
didn't have on 4.2.1 but this doesn't seem to have bad affect on WSRP (see below).
Hopefully not too many people were using JSEs. But at least the fix is easy.
15:49:57,971 WARN [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef
serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_ServiceDescription_PortType
portQName=null
enableMTOM=false
portComponentLink=null
callProperties=[]
stubProperties=[]
configName=null
configFile=null
15:49:58,920 WARN [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef
serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_Markup_PortType
portQName=null
enableMTOM=false
portComponentLink=null
callProperties=[]
stubProperties=[]
configName=null
configFile=null
15:49:59,827 WARN [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef
serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_PortletManagement_PortType
portQName=null
enableMTOM=false
portComponentLink=null
callProperties=[]
stubProperties=[]
configName=null
configFile=null
15:50:01,753 WARN [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef
serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_Registration_PortType
portQName=null
enableMTOM=false
portComponentLink=null
callProperties=[]
stubProperties=[]
configName=null
configFile=null
Cannot deploy nested JSE endpoint in SAR
----------------------------------------
Key: JBWS-1854
URL: http://jira.jboss.com/jira/browse/JBWS-1854
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-2.0.1.SP2
We have an issue, JBoss Portal WSRP service doesn't deploy in Branch
4.2, the issue seems to be related to the WS changes.
I noticed that in jbossws.sar/META-INF/jboss-service.xml the following
has been removed:
<!--
A deployer service for JSE endpoints that are nested in service
archives (sar).
-->
<mbean name="jboss.ws:service=DeployerInterceptorNestedJSE"
code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
<depends optional-attribute-name="MainDeployer"
proxy-type="attribute">jboss.system:service=MainDeployer</depends>
<depends>jboss.ws:service=WebServiceDeployerJSE</depends>
</mbean>
We do have a jse included into a sar and the end result is that the WSRP
service doesn't start with the following error message:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@be17fae3 {
url=file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
}
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch:
file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
altDD: null
lastDeployed: 1192192027649
lastModified: 1192191975000
mbeans:
I wanted to let you know. I didn't investigate more than that, other
than trying to find the corresponding class for the deployer, but it
seems that it's not in the codebase anymore.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:15 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-1854) Cannot deploy nested JSE endpoint in SAR
[ http://jira.jboss.com/jira/browse/JBWS-1854?page=comments#action_12382653 ]
Thomas Diesler commented on JBWS-1854:
--------------------------------------
Also works in 4.2.0
09:10:00,866 INFO [Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA
date=200706280849)] Started in 36s:392ms
09:11:05,759 INFO [ServiceEndpointManager] WebService stopped:
http://127.0.0.1:8080/jaxws-jbws1854
Cannot deploy nested JSE endpoint in SAR
----------------------------------------
Key: JBWS-1854
URL: http://jira.jboss.com/jira/browse/JBWS-1854
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-2.0.1.SP2
We have an issue, JBoss Portal WSRP service doesn't deploy in Branch
4.2, the issue seems to be related to the WS changes.
I noticed that in jbossws.sar/META-INF/jboss-service.xml the following
has been removed:
<!--
A deployer service for JSE endpoints that are nested in service
archives (sar).
-->
<mbean name="jboss.ws:service=DeployerInterceptorNestedJSE"
code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
<depends optional-attribute-name="MainDeployer"
proxy-type="attribute">jboss.system:service=MainDeployer</depends>
<depends>jboss.ws:service=WebServiceDeployerJSE</depends>
</mbean>
We do have a jse included into a sar and the end result is that the WSRP
service doesn't start with the following error message:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@be17fae3 {
url=file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
}
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch:
file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
altDD: null
lastDeployed: 1192192027649
lastModified: 1192191975000
mbeans:
I wanted to let you know. I didn't investigate more than that, other
than trying to find the corresponding class for the deployer, but it
seems that it's not in the codebase anymore.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:20 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-1854) Cannot deploy nested JSE endpoint in SAR
[ http://jira.jboss.com/jira/browse/JBWS-1854?page=all ]
Thomas Diesler updated JBWS-1854:
---------------------------------
Fix Version/s: (was: jbossws-2.0.1.SP2)
Cannot deploy nested JSE endpoint in SAR
----------------------------------------
Key: JBWS-1854
URL: http://jira.jboss.com/jira/browse/JBWS-1854
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
We have an issue, JBoss Portal WSRP service doesn't deploy in Branch
4.2, the issue seems to be related to the WS changes.
I noticed that in jbossws.sar/META-INF/jboss-service.xml the following
has been removed:
<!--
A deployer service for JSE endpoints that are nested in service
archives (sar).
-->
<mbean name="jboss.ws:service=DeployerInterceptorNestedJSE"
code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
<depends optional-attribute-name="MainDeployer"
proxy-type="attribute">jboss.system:service=MainDeployer</depends>
<depends>jboss.ws:service=WebServiceDeployerJSE</depends>
</mbean>
We do have a jse included into a sar and the end result is that the WSRP
service doesn't start with the following error message:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@be17fae3 {
url=file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
}
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch:
file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
altDD: null
lastDeployed: 1192192027649
lastModified: 1192191975000
mbeans:
I wanted to let you know. I didn't investigate more than that, other
than trying to find the corresponding class for the deployer, but it
seems that it's not in the codebase anymore.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6262
days inactive
6303
days old
jbossws-issues@lists.jboss.org
7 comments
3 participants
participants (3)
-
Chris Laprun (JIRA) -
Dimitris Andreadis (JIRA)
-
Thomas Diesler (JIRA)